From: Thomas Backlund <tmb@mageia.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] ASUS Sandybridge motherboards + PCI not working (IRQ n: nobody cared)
Date: Sat, 15 Oct 2011 19:51:38 +0300 [thread overview]
Message-ID: <4E99BA1A.3060002@mageia.org> (raw)
In-Reply-To: <4E98175A.8040905@pobox.com>
Chris Palmer skrev 14.10.2011 14:04:
> Interrupt handling for *PCI boards with ASUS Sandybridge motherboards*
> seems to be broken.
>
> It has been seen with network and non-network PCI boards. PCIx network
> boards work OK. And all reports are for ASUS motherboards.
>
> It always results in the infamous "IRQ n: nobody cared" message usually
> within an hour. It is possible to restart things by rmmod/modprobe on
> the appropriate PCI driver.
>
> Andrew Morton kindly took a quick look and thinks it is most likely an
> ACPI bug.
>
> Configuration summary:
> - ASUS P8H67-V/R3 Motherboard (others have problems with similar M/Bs)
> - M/B BIOS 0804 (just updated to that - no change)
> - Core i5/2500K
> - Onboard ethernet (at11c driver - works)
> - Additional PCIx Intel ethernet board (e1000e driver - works)
> - Additional PCI Broadcom BCM5702X ethernet board (tg3 driver - fails)
> [ Also fails with other PCI boards such as RTL8139 ]
> - Kernel 3.0.6
>
>
> Any help much appreciated...
>
Does it help to boot with: pci=nocrs ?
--
Thomas
prev parent reply other threads:[~2011-10-15 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:04 [PROBLEM] ASUS Sandybridge motherboards + PCI not working (IRQ n: nobody cared) Chris Palmer
2011-10-15 0:29 ` Robert Hancock
2011-10-15 8:43 ` Chris Palmer
2011-10-15 16:23 ` Robert Hancock
[not found] ` <4EE72C4D.9080207@pobox.com>
2011-12-14 0:12 ` Fwd: " Edward Donovan
[not found] ` <CADdbW+E9=DKZ-839yPW_R4JM1omXEzqGqT=ae7Txu4Jikyw2=A@mail.gmail.com>
2011-12-14 10:49 ` Chris Palmer
2011-10-15 16:51 ` Thomas Backlund [this message]
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=4E99BA1A.3060002@mageia.org \
--to=tmb@mageia.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).