Bug 464559
| Summary: | iwl4965: hard kernel lockups with Lenovo X300 laptop, cannot be sysrq'd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher M. Smith <csmith> |
| Component: | kernel | Assignee: | John W. Linville <linville> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | choke, cra, kernel-maint, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-11-18 01:18:00 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: | 438944 | ||
|
Description
Christopher M. Smith
2008-09-29 15:46:09 UTC
Do you have a wireless switch on the side. Or a wifi catcher toggle by any chance? There is a wireless radio switch that turns wireless signals on and off at the hadware level, yes. CMS Try disabling those in BIOS, if you can and see if it panics. Also, try appending pci=routeirq to end of kernel line in /etc/grub.conf This was suggested to me recently and I've had no locks since. I have made this change and disabled all of the on-board wireless items I could and added the pci=routeirq option and still received the same type of non-sysrq capable panic. Sorry :( CMS I have done more testing on my end. Here is what I have found. 1. I reverted myself via a fresh install to F9, leaving the BIOS items disabled and setting pci=routeirq as a kernel boot parameter. I still had the panic issue. 2. I was comparing the environment differences between home and work and noticed that the majority of my panics take place at home. I reviewed my wireless settings and noticed that while work uses WEP, I use WPA. Further, my WPA settings on the router was set to expire the WPA group key every hour. I changed this a larger threshold this morning and am currently experiencing the highest uptime that I've had in weeks. I hope this helps a little bit in narrowing down the issue. Thanks, CMS And as if on command, 5 minutes after writing that message to you it panic'd. Apparently I made less progress than I had thought. CMS So I was able to capture a bit of debug by kicking off an intensive network process and all the open programs I usually use and switching to the F1 virtual console out of X. Here is the (ugh) transcribed bit of the panic string I can actually see: [<f8b4db66>] ? iwl_tx_cmd_complete+0x3d/0x181 [iwlcore] [<c042910d>] ? wake_up_klogd+0x2e/0x31 [<c0429291>] ? release_console_sem+0x181/0x189 [<c063102a>] error_code+0x72/0x78 [<f8b4db66>] ? iwl_tx_cmd_complete+0x3d/0x181 [iwlcore] [<c04fe4d7>] ? list_add+0xa/0xf [<f8ce514a>] iwl_rx_handle+0x241/0x328 [iwl4965] [<f8ce5982>] iwl4965_irq_tasklet+0x751/0x9cf [iwl4965] [<c042cef0>] tasklet_action+0x75/0xd8 [<c042d663>] __do_softirq+0x74/0xe7 [<c0406e2f>] do_softirq+0x74/0xb5 [<c045f5cb>] ? handle_fasteoi_irq+0x0/0xaf [<c042d46b>] irq_exit+0x38/0x6b [<c0406f1c>] do_IRQ+0xac/0xc4 [<c04055eb>] common_interrupt+0x23/0x28 [<c043007b>] ? ptrace_writedata+0xa/0x9b [<c053d2fc>] ? acpi_idle_enter_bm+0x2fe/0x383 [<c043d302>] ? pm_qos_requirement+0x26/0x2b [<c05a58d2>] cpuidle_idle_call+0x62/0x92 [<c05a5870>] ? cpuidle_idle_call+0x62/0x92 [<c0403c4a>] cpu_idle+0xae/0xd0 [<c0621e2e>] rest_init+0x4e/0x50 =========================== --- [ end trace 872a5e4008d466ff ] --- CMS Any ideas on this bug? I'm sort of at an impasse here given that my laptop has an uptime of approximately 20 to 30 minutes at a given time, give or take the day. I'm happy to reinstall or test anything that needs testing as that I've backed up all my data. Thank you for your help. CMS Same as bug 457154 in Fedora 9. Are you using a .11n AP? If so, can you disable .11n on the AP, or use a .11g AP instead? Can you replicate the issue in a .11b/g or a .11g-only environment? Are you still seeing this with recent rawhide kernels? kernel-2.6.27.5-94.fc10 or higher should have a patch that will make this problem a warning instead of an oops/hard lock. Moving to F10Target - I think we've papered over the lockup, and nobody else has been able to reproduce the problem. *** This bug has been marked as a duplicate of bug 457154 *** will, +1. I'm no longer locking up but I do see the "your kernel is generating diagnostic information and passing it along" graphical message within X. The oops is definitely happening in some form, but its not preventing me from operating with wireless either. Best, CMS |