public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Julian Sikorski <belegdol@gmail.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: bug report: irq 19: nobody cared (try booting with the "irqpoll" option)
Date: Thu, 15 Dec 2011 16:56:24 +0100	[thread overview]
Message-ID: <4EEA18A8.5030603@ladisch.de> (raw)
In-Reply-To: <4EEA0521.2030502@gmail.com>

(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.

>> 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.


Regards,
Clemens

  reply	other threads:[~2011-12-15 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 14:30 bug report: irq 19: nobody cared (try booting with the "irqpoll" option) Julian Sikorski
2011-12-15 14:33 ` Julian Sikorski
2011-12-15 15:56   ` Clemens Ladisch [this message]
2011-12-15 16:04     ` Julian Sikorski
2011-12-15 17:49       ` Clemens Ladisch
2011-12-15 17:56         ` Julian Sikorski
2011-12-16  8:37           ` Clemens Ladisch
2011-12-16  9:02             ` Julian Sikorski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EEA18A8.5030603@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=belegdol@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox