Bug 1119039
| Summary: | [abrt] BUG: unable to handle kernel NULL pointer dereference at (null) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ramindeh | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 20 | CC: | airlied, ajax, bskeggs, gansalmon, itamar, jasoncadmus, jonathan, jwelsh-rhbz, kernel-maint, madhu.chinakonda, mchehab, ramindeh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/d38590f2efdcdf86e0056723444cb1d4976cbdcc | ||||||||
| Whiteboard: | abrt_hash:add002282bd2dbbc6c7f1c16250b21f9d6b6263b | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-06-29 21:34:31 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
ramindeh
2014-07-13 13:35:28 UTC
Created attachment 917620 [details]
File: dmesg
I'm having this crash too; it started when I upgraded to kernel 3.15.6 from 3.14.9, and is still happening on 3.15.8. It seems to happen within a few minutes of bootup, regardless of what's happening in X, even when just on the console. This is a laptop with intel/nvidia hybrid graphics. The nvidia card has never been usable; I tried bumblebee last year, but as I recall it just crashed the system. Perhaps this same bug. Adding modprobe.blacklist=nouveau to the kernel command line seems to have stopped the crashing (a blacklist file in modprobe.d didn't stop the module from loading), but now the laptop seems to be running hot; I suspect the nvidia card is powered up despite not being in use. What Jacob Welsh above describes is basically my scenario. After I did that update I let it reboot, and it locked up during shutdown, so I was forced to press the reset-Button. This caused /dev/fedora-mapper/root to become corrupted. I booted the Laptop from a USB-stick to be able to fsck that filesystem, and the fsck screwed it, so I'm stuck booting from the USB-stick until I find a way to repair the boot filesystem :-( If anybody could post a link to a HOWTO on repairing the boot-fs, that'd be great ... Created attachment 937255 [details]
dmesg on 3.16.2
Still happening on 3.16.2, though with slightly different error messages. Here's a dmesg I captured in between lockups. Nouveau wizards, any other way I can help?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still happening with kernel-3.19.8-100.fc20.x86_64. I'll try Fedora 22 live media as soon as I can. If that doesn't work, I'll have no upgrade path when F20 goes EOL. Still happening on F22 (kernel 4.0.4-301.fc22.x86_64, xorg-x11-drv-nouveau 1.0.11-2.fc22). Fortunately, blacklisting nouveau seems to be keeping things stable. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |