Bug 205672
Summary: | Disabling IRQ #7 / nobody cared / usb_hcd_irq | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Simeon Penev <simeon_penev> | ||||||
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5 | CC: | davej, triage, tristanmoody, wtogami | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | bzcl34nup | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-05-06 16:19: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: | |||||||||
Attachments: |
|
Description
Simeon Penev
2006-09-07 22:52:14 UTC
Could you post the kernel panic you get when you don't use noapic? It's pretty normal for noapic to cause problems... It's basically for debugging only these days. Created attachment 135884 [details]
Log from system freeze without the noapic kernel parameter
Actually there is not kernel panic - the system simply freezes after the message: io scheduler cfq registered (default) See the attachment (id=135884) for complete log. I reconstructed it from 2 camera photos, so there could be a gap in the middle. It dies right before: PCI: Setting latency timer of device 0000:00:03.0 to 64 pcie_portdrv_probe->Dev[02fd:10de] has invalid IRQ. Check vendor BIOS I don't know who 02fd is. I don't see it in your lspci. On the other hand I doubt that's the problem. The problem is most likely this stuff here: ACPI Error (psloop-0193): Found unknown opcode FD at AML address ffffc20000016003 offset 5B9F, ignoring [20060127] ACPI Error (psloop-0193): Found unknown opcode FD at AML address ffffc200000160b2 offset 5C4E, ignoring [20060127] ACPI Error (psloop-0193): Found unknown opcode FD at AML address ffffc20000016003 offset 5B9F, ignoring [20060127] ACPI Error (psloop-0193): Found unknown opcode FD at AML address ffffc200000160b2 offset 5C4E, ignoring [20060127] See if there is a BIOS update available from Asus. There may not be one, or it may not help, but that's the first thing to check. I tried the latest bios update from asus, but it didn't help. When the problem occurs, there is a help message about irqpoll. However irqpoll and routeirq have no influence. Is there something else i can try? What's the output of `cat /proc/interrupts` when you use noapic? It's probably going to be a bit bogus leading to the USB failure, but I'm curious. The dmesg also suggests you could try: pci=assign-busses. You may want to try that both with and without the noapic. Created attachment 136557 [details]
/proc/interrupts
Comment on attachment 136557 [details]
/proc/interrupts
Plese see the attachment for '/proc/interrupts'.
I've tried pci=assign-busses with and without the noapic option on both this
kernel and the newest one (2.6.17-1.2187_FC5) but the problem still persists.
Maybe this message has something to do with it:
Asus Laptop ACPI Extras version 0.29
Error calling BSTS
A6T model detected, unsupported, trying default values, supply the developers
with your DSDT
Maybe i have to post it on the ACPI list?
Yeah. Post it on the ACPI list. That's a good idea. Give them all the mobo info you put here. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. Problem still persist with the newest kernel 2.6.18-1.2200.fc5: irq 7: nobody cared (try booting with the "irqpoll" option) Call Trace: [<ffffffff80269387>] show_trace+0x34/0x47 [<ffffffff802693ac>] dump_stack+0x12/0x17 [<ffffffff802b550a>] __report_bad_irq+0x30/0x7d [<ffffffff802b572a>] note_interrupt+0x1d3/0x219 [<ffffffff802b4c67>] __do_IRQ+0xc8/0x107 [<ffffffff8026a3ca>] do_IRQ+0xe7/0xf5 [<ffffffff8025c6c9>] ret_from_intr+0x0/0xa DWARF2 unwinder stuck at ret_from_intr+0x0/0xa Leftover inexact backtrace: <IRQ> <EOI> [<ffffffff888b54f4>] :bluetooth:bt_sock_poll+0x0/0x10c [<ffffffff80268b82>] default_idle+0x29/0x50 [<ffffffff80247e0f>] cpu_idle+0x95/0xb8 [<ffffffff80273d79>] start_secondary+0x45c/0x46b handlers: [<ffffffff803d3797>] (usb_hcd_irq+0x0/0x55) Disabling IRQ #7 Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Same problem in Fedora 12: irq occupied by wlan0 causing problems...maybe ndiswrapper is the source? /var/log/messages output: ---snipped--- Dec 9 10:53:03 thehost rpc.statd[1232]: Version 1.2.1 Starting Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: read connection 'System wlan0' Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Public_Wired ... Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: read connection 'Public Wired' Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Dec 9 10:53:03 thehost NetworkManager: ifcfg-rh: read connection 'System eth0' Dec 9 10:53:03 thehost kernel: irq event 17: bogus return value f5545248 Dec 9 10:53:03 thehost kernel: Pid: 1204, comm: pcscd Tainted: P 2.6.31.6-162.fc12.i686.PAE #1 Dec 9 10:53:03 thehost kernel: Call Trace: Dec 9 10:53:03 thehost kernel: [<c047c2ad>] __report_bad_irq+0x33/0x74 Dec 9 10:53:03 thehost kernel: [<c047c34a>] note_interrupt+0x5c/0x152 Dec 9 10:53:03 thehost kernel: [<c047c960>] handle_fasteoi_irq+0x83/0xa2 Dec 9 10:53:03 thehost kernel: [<c040b1b5>] handle_irq+0x40/0x4b Dec 9 10:53:03 thehost kernel: [<c040a979>] do_IRQ+0x46/0x9a Dec 9 10:53:03 thehost kernel: [<c0409690>] common_interrupt+0x30/0x38 Dec 9 10:53:03 thehost kernel: handlers: Dec 9 10:53:03 thehost kernel: [<f7fb8e5e>] (io_irq_isr+0x0/0x3d [ndiswrapper]) ---snipped--- followed by more tracebacks related to irq event 17. Invariably, the initial problem is related to ndiswrapper. Tried booting with irqpoll and irqfixup--no change in behavior. If you need more info, I'd be glad to provide it. |