| Summary: | [abrt] WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill Chatfield <bill_chatfield> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | bdjohns1, Claude.Frantz, cz172638, detonadorx, e.misiek, gansalmon, ichavero, itamar, jonathan, jon.ingason, kernel-maint, krush206, madhu.chinakonda, mchehab, Ramanc51, sylvain, vpvainio | ||||
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/1d2c7cb45fa940feea431376b78c2c2d571a8012 | ||||||
| Whiteboard: | abrt_hash:1cb8184e5178967efcc805160e882d70a06fcbe7; | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-04-28 17:25:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Bill Chatfield
2016-11-27 18:45:02 UTC
Created attachment 1224967 [details]
File: dmesg
Description of problem: while open fedora online account Version-Release number of selected component: kernel-PAE-core-4.9.6-100.fc24 Additional info: reporter: libreport-2.7.2 cmdline: BOOT_IMAGE=/vmlinuz-4.9.6-100.fc24.i686+PAE root=UUID=5abad7cf-2369-4dfc-a9f7-1950a34a7c73 ro rhgb quiet LANG=en_IN.UTF-8 kernel: 4.9.6-100.fc24.i686+PAE pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 x86/mm: Found insecure W+X mapping at address e0000000/0xe0000000 Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.6-100.fc24.i686+PAE #1 Hardware name: Dell Inc. Inspiron N4050/02JCHC, BIOS A06 11/14/2011 f7139e78 df36c750 f7139ebc df9622ae f7139ea8 df06c95a df95b834 f7139edc 00000001 df9622ae 000000e1 df061541 000000e1 f7139f3c 80000000 00000000 f7139ec8 df06c9c6 00000009 00000000 f7139ebc df95b834 f7139edc 39e80fab Call Trace: [<df36c750>] dump_stack+0x58/0x78 [<df06c95a>] __warn+0xea/0x110 [<df061541>] ? note_page+0x6a1/0x880 [<df06c9c6>] warn_slowpath_fmt+0x46/0x60 [<df061541>] note_page+0x6a1/0x880 [<df061859>] ptdump_walk_pgd_level_core+0x139/0x300 [<df061a56>] ptdump_walk_pgd_level_checkwx+0x16/0x20 [<df057365>] mark_rodata_ro+0xe5/0x110 [<df76c590>] ? rest_init+0x70/0x70 [<df76c5bc>] kernel_init+0x2c/0x100 [<df096891>] ? schedule_tail+0x11/0x50 [<df76c590>] ? rest_init+0x70/0x70 [<df773843>] ret_from_fork+0x1b/0x28 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. Was anybody able to find a solution to this problem such that the computer can operate again in a more or less normal manner ? Thanks ! |