linux-kernel - Re: bug report: irq 19: nobody cared (try booting with the "irqpoll" option)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Dec 2011 17:04:17 +0100
From:	Julian Sikorski <belegdol@...il.com>
To:	Clemens Ladisch <clemens@...isch.de>
CC:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: bug report: irq 19: nobody cared (try booting with the "irqpoll"
 option)

W dniu 15.12.2011 16:56, Clemens Ladisch pisze:
> (CC linux1394-devel)
> 
> Julian Sikorski wrote:
>> W dniu 15.12.2011 15:30, Julian Sikorski pisze:
>>> this is happening every time I reboot from suspend on a Clevo P150HM
>>> machine. It has been occuring for a while, but this report is for Fedora
>>> kernel 3.1.5-2.fc16 (I am running an up-to-date Fedora 16 x86_64 here).
>>> Smolt profile is available here:
>>>
>>> http://www.smolts.org/client/show/pub_1eec606f-137a-46a1-922f-98f40180efa6
>>>
>>> I have the problem itself does not seem to manifest in anything else
>>> except abrt complaining.
> 
> Your FireWire won't work.

Unfortunately I do not have any FW device around to test.
> 
>>> irq 19: nobody cared (try booting with the "irqpoll" option)
> 
>> 05:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller (prog-if 10 [OHCI])
>>         Subsystem: CLEVO/KAPOK Computer Device 5102
>>         Physical Slot: 1
>>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>>         Latency: 0, Cache Line Size: 64 bytes
>>         Interrupt: pin A routed to IRQ 19
>>         Region 0: Memory at f6103000 (32-bit, non-prefetchable) [size=2K]
>>         Region 1: Memory at f6102000 (32-bit, non-prefetchable) [size=128]
>>         Region 4: Memory at f6101000 (32-bit, non-prefetchable) [size=128]
>>         Region 5: Memory at f6100000 (32-bit, non-prefetchable) [size=128]
>>         Capabilities: <access denied>
>>         Kernel driver in use: firewire_ohci
>>         Kernel modules: firewire-ohci
> 
>>            CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7
>> ...
>>  18:          0          0          0          0          0          0          0          0  IR-IO-APIC-fasteoi   jmb38x_ms:slot0, mmc0
>>  19:     100008          0          0          0          0          0          0          0  IR-IO-APIC-fasteoi   firewire_ohci
>> ...
>>  40:          0          0          0          0          0          0          0          0  DMAR_MSI-edge      dmar0
>> ...
> 
> Was it the JMB38x that used a wrong interface number in its PCIe
> transactions, which would make the I/O-MMU map it to the wrong device?
> 
> Julian, try disabling DMAR (probably called IOMMU or something related
> to virtualization) in the BIOS.

There is no such option or anything even remotely related in the BIOS
(this machine uses the AMI Aptio if that matters).
> 
> 
> Regards,
> Clemens

Just to make it clear, booting with irqpoll option made the message go away.

Regards,
Julian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/