Bug 995708
| Summary: | hard LOCKUP on cpu perhaps in iptables, perhaps apic/acpi | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Trevor Cordes <trevor> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, michele, trevor |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-13 14:43:30 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: | |||
|
Description
Trevor Cordes
2013-08-10 10:06:41 UTC
I took out the "acpi=off noapic nolapic pnpacpi=off pci=noacpi" options one by one trying to see which was actually required to make the system not crash again. I now have *all* of them out and the system is not crashing! I think a kernel update in the interim has fixed whatever the issue was. The kernel used now that is not crashing is: 3.10.9-200.fc19.i686 Closing this bug. Darn, the box just crashed again yesterday. I had recently rebooted into kernel-3.11.1-200.fc19.i686 for the first time in weeks (no acpi/apic options) and now it crashed. Either the bug was put back in between 3.10.9-200.fc19.i686 and 3.11.1-200.fc19.i686, or it just took a long time to hit again. In either case, somewhat strange. I am working on getting a copy of this crash's stack track to paste in the bz. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. 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 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those. Hi Trevor, have you ever been able to get a stack trace with 3.11.x ? thanks, Michele Here is a manual transcript of the oops trace: ? leave_mm+0x80/0x50 smp_call_function_single+0xa4/0x130 ? leave_mm+0x50/0x50 smp_fall_function_many+0x1ec/0x220 ? leave_mm+0x50/0x50 native_flush_tlb_others+0x2b/0x30 flush_tlb_page+0x48/0x90 ptep_clear_flush+0x40/0x50 do_wp_page+0x223/0x7d0 handle_pte_fault+0x315/0x8d0 handle_mm_fault+0xb5/0x110 __do_page_fault+0x189/0x4d0 ? task_stopped_code+0x50/0x50 ? __do_page_fault+0x4d0/0x4d0 ?do_page_fault+0xd/0x10 error_code+0x67/0x6c Sorry for any typos. I can provide more info (I have a pic of it on my phone) if required. Since the last report the computer has since died completely, just the mobo or CPUs. No visible bad caps or other obvious problems. Probably just the ol' it's-AMD-and-it-got-too-old death. This whole bug might therefore be nothing more than hardware dying and I would be fine with closing it as such, especially if the traces don't seem related and/or useful. I replaced the motherboard/cpu with a newer model and everything works fine now for a month. Hi Trevor, given the completely different traces I'd tend to point fingers to HW this time around (ram, cpu,...). So I'd vote for closing it at this point. regards, Michele Ok. Thanks for letting us know. We appreciate the heads up that it was likely hardware related. |