Bug 1506892
| Summary: | [abrt] kernel-PAE-core: mempool_free_slab(): BUG: unable to handle kernel NULL pointer dereference at 00000004 | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Claude Frantz <Claude.Frantz> | ||||||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 26 | CC: | airlied, ajax, bskeggs, Claude.Frantz, ewk, hdegoede, ichavero, itamar, jarodwilson, jeff.backus, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, steved | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i686 | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | abrt_hash:7ccd263f1913941d09ae0a38f46bef30877f2024; | ||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2018-03-19 15:11:17 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||
| Bug Blocks: | 1489998 | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Claude Frantz
2017-10-27 05:59:04 UTC
Created attachment 1344168 [details]
File: backtrace
Created attachment 1344169 [details]
File: cpuinfo
Created attachment 1344170 [details]
File: dmesg
Created attachment 1344171 [details]
File: not-reportable
Created attachment 1344172 [details]
File: proc_modules
Created attachment 1344173 [details]
File: suspend_stats
The problem occurred while inserting a DVD-RAM in the drive. Hi Claude, Forgive my ignorance, but by DVD-RAM, do you mean a writable DVD? Is this in any way related to issue 1508757? (https://bugzilla.redhat.com/show_bug.cgi?id=1508757) Thanks! Hi Jeff, Yes, it's a writeable DVD and the drive is DVD-RAM capable. A sort of a slow hard disk. This crash occurred at the insertion of the DVD-RAM, but it's not sure that this action is related to the crash. Similar crashes occur in other circumstances, with the last available kernels, making the working with them nearly impossible. I had to reboot with an earlier kernel, to be able to respond to this message. After the crash, the available information in the logs is often truncated. Thanks for helping me! Hi Claude, Yes, I imagine so! Sorry you are having to go through this. So it sounds like these crashes are somewhat random? And if so, perhaps bug 1508757 is another symptom of the same issue? I'll ask the same question I asked there, but feel free to just answer it here: It looks like your machine is capable of 64bit. Have you tried using the 64bit version of Fedora? If so, does it also crash? Hi Jeff, Considering the present observations, these crashes are somewhat random, but there are probably not really because there are so many interactions of so many components that it's very difficult for me to find where the problematic sequence started. In most cases, it's at a rather short time after the boot. Yes, the machine is 64 bit capable. But because the RAM is of modest size (4 GB), I have never used this 64 bit mode. Hi, Please allow me to point to the following lines which appear at the begin of the dmesg output: [ 3.338614] Hardware name: ASUSTeK Computer Inc. P50IJ /P50IJ , BIOS 203 12/04/2009 [ 3.338671] task: f712c600 task.stack: f7122000 [ 3.338721] EIP: note_page+0x670/0x860 [ 3.338722] EFLAGS: 00010246 CPU: 1 [ 3.338723] EAX: 00000041 EBX: f7123f50 ECX: 00000001 EDX: da0acc28 [ 3.338725] ESI: 80000000 EDI: 00000000 EBP: f7123f1c ESP: f7123ef0 [ 3.338726] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 3.338727] CR0: 80050033 CR2: b7f075ac CR3: 1a098000 CR4: 000406f0 [ 3.338729] Call Trace: [ 3.338779] ptdump_walk_pgd_level_core+0x1fc/0x2e0 [ 3.338831] ptdump_walk_pgd_level_checkwx+0x16/0x20 [ 3.338882] mark_rodata_ro+0xd5/0xf7 [ 3.338931] ? rest_init+0xa0/0xa0 [ 3.338979] kernel_init+0x2e/0xea [ 3.339038] ret_from_fork+0x19/0x24 [ 3.339092] Code: d9 e9 0c fb ff ff f7 c6 00 10 00 00 74 8c 68 a9 c9 dc d9 e9 16 fe ff ff 52 52 68 44 c a dc d9 c6 05 e6 b4 f6 d9 01 e8 2d 67 06 00 <0f> ff 8b 53 0c 83 c4 0c e9 38 fa ff ff 50 6a 08 52 6a 08 68 59 [ 3.339195] ---[ end trace 7cb359b140464c53 ]--- [ 3.339277] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. [ 3.339280] rodata_test: all tests were successful I ignore if this is related to the crash which occurs sometime later. I do not more remember exactly at which time these above mentioned lines have began to appear in the output. But I remember that the crash never appeared before. While using the 4.13.11-200 kernel now, the crash never occurred up to now. While using the 4.13.12-200.fc26.i686+PAE kernel now, the crash occurs again. Created attachment 1355963 [details]
dmesg output
Hi Jeff,
Today, I have tried to start this computer sing a Fedora-Xfce-live DVD 27-1-6 x86_64. The kernel is presented as 4.13.9-300.fc27.x86_64. Please note here:
x86/mm: Checked W+X mappings: passed, no W+X pages found.
This different from the 32 bit mode.
Please excuse me to return to this difficult subject. Because of this bug, I have now some corrupted files on different media, including on backup files. That made it difficult to restore to the expected state. Now, I'm forced to use CD-Rescue to generate backups and to use an outdated kernel for the other tasks on Fedora 26. You will easily understand that this cannot be considered as a solution. I cannot afford to test every released kernel in the distribution, because I cannot afford to risk to increase the number of corrupted files I have. Please allow me to ask few questions: What module and/or part of the kernel is causing the issue ? Is work in progress in order to fix it ? In which release will a reasonable fix be available ? What can I do further ? The suspected relationship between the failed W+X page check could not be confirmed by my further observations. Many thanks to you all. We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. 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 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those. Now, I'm at the current 4.15.9-200.fc26.i686+PAE. It allows a stable work but there are (In reply to Laura Abbott from comment #17) > We apologize for the inconvenience. There is a large number of bugs to go > through and several of them have gone stale. The kernel moves very fast so > bugs may get fixed as part of a kernel update. Due to this, we are doing a > mass bug update across all of the Fedora 26 kernel bugs. > > Fedora 26 has now been rebased to 4.15.4-200.fc26. 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 27, and are still experiencing this issue, > please change the version to Fedora 27. > > If you experience different issues, please open a new bug report for those. I'm on 4.15.9-200.fc26.i686+PAE now. The system is stable but there are some problematic entries in the log like: Mar 19 08:12:38 defi kernel: x86/mm: Found insecure W+X mapping at address 57d76a8e/0xc00a0000 Mar 19 08:12:38 defi kernel: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:266 note_page+0x670/0 Mar 19 08:12:38 defi kernel: Modules linked in: Mar 19 08:12:38 defi kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.9-200.fc26.i686+PAE #1 Mar 19 08:12:38 defi kernel: Hardware name: ASUSTeK Computer Inc. P50IJ /P50IJ , Mar 19 08:12:38 defi kernel: EIP: note_page+0x670/0x860 Mar 19 08:12:38 defi kernel: EFLAGS: 00010296 CPU: 0 Mar 19 08:12:38 defi kernel: EAX: 00000041 EBX: f2525f4c ECX: 00000001 EDX: d7905ea8 Mar 19 08:12:38 defi kernel: ESI: 80000000 EDI: 00000000 EBP: f2525f18 ESP: f2525eec Mar 19 08:12:38 defi kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Mar 19 08:12:38 defi kernel: CR0: 80050033 CR2: b7f2d5ac CR3: 178f2000 CR4: 000406f0 Mar 19 08:12:38 defi kernel: Call Trace: Mar 19 08:12:38 defi kernel: ptdump_walk_pgd_level_core+0x204/0x2e0 Mar 19 08:12:38 defi kernel: ptdump_walk_pgd_level_checkwx+0x18/0x20 Mar 19 08:12:38 defi kernel: mark_rodata_ro+0xd5/0xf7 Mar 19 08:12:38 defi kernel: ? rest_init+0xa0/0xa0 Mar 19 08:12:38 defi kernel: kernel_init+0x2e/0xf0 Mar 19 08:12:38 defi kernel: ret_from_fork+0x2e/0x38 Mar 19 08:12:38 defi kernel: Code: d7 e9 0c fb ff ff f7 c6 00 10 00 00 74 8c 68 9d 65 61 d7 e9 16 fe ff ff Mar 19 08:12:38 defi kernel: ---[ end trace 2044d6512605a61a ]--- Mar 19 08:12:38 defi kernel: x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. Further, /sys/devices/system/cpu/vulnerabilities/meltdown contains: Vulnerable Please do not switch to the Fedora 28 release until the kernel becomes stable. The meltdown issue is known since 32-bit support is still pending, please see https://lists.fedoraproject.org/archives/list/x86@lists.fedoraproject.org/thread/ABTEQGUHUNPQMELINGCIHWQ2LBFWC7LC/ The other issue is also known and there is a bugzilla somewhere (sorry, can't find it). I'm going to close this particular bug since the original issue isn't seen anymore, Please follow up elsewhere for other issues. |