Bug 1170534
| Summary: | Cannot report kernel crash: "more than one oops" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Milan Bouchet-Valat <nalimilan> | ||||
| Component: | abrt | Assignee: | Matej Habrnal <mhabrnal> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | abrt-devel-list, dvlasenk, iprikryl, jfilak, mhabrnal, mmilata, rvokal | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | abrt-2.3.0-9.fc21 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-25 13:10:19 UTC | Type: | Bug | ||||
| 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
Milan Bouchet-Valat
2014-12-04 09:41:03 UTC
Thank you for the report! I am afraid that there is no easy way to convince ABRT to report that kernel panic. The problem is that ABRT extracts dmesg from vmcore and expects exactly one kernel oops (the one which caused the panic) in the dmesg file. You can extract dmesg manually using the following command: # makedumpfile --dump-dmesg -f /var/crash/[vmcore dir]/vmcore dmesg_log The information you need should appear in 'dmesg_log' file. Actually, dmesg_log is already present in that directory, I'm attaching it. It seems that the first problem is in the intel video driver, and then a whole series of traces are printed. Should I consider that the bug is in the intel video driver then? Is that enough to report it, or is there a better way of getting information about that oops, if the others are disturbing abrt? Created attachment 964575 [details]
dmesg_log
(In reply to Milan Bouchet-Valat from comment #2) > Should I consider that the bug is in the intel video driver then? I would say yes. > Is that enough to report it Yes, dmesg_log is enough to open a bug report against kernel component. ABRT only extracts some meta-data (kernel version, taint flags, etc) from the backtrace to be able to file a bug report, but you don't need it, because you already known all these information. > , or is there a better way of getting information about > that oops, if the others are disturbing abrt? I don't think so. I'm going to teach ABRT to use the first found oops in order to fix this bug. Thanks! I've filed it upstream as https://bugzilla.kernel.org/show_bug.cgi?id=89241 I've opened the pull request https://github.com/abrt/abrt/pull/1010 which fixes the bug. gnome-abrt-1.0.0-4.fc21,abrt-2.3.0-9.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gnome-abrt-1.0.0-4.fc21,abrt-2.3.0-9.fc21 Package gnome-abrt-1.0.0-4.fc21, abrt-2.3.0-9.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-1.0.0-4.fc21 abrt-2.3.0-9.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13776/gnome-abrt-1.0.0-4.fc21,abrt-2.3.0-9.fc21 then log in and leave karma (feedback). This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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. |