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:	Fri, 14 Oct 2011 18:29:54 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Chris Palmer <chris.palmer@...ox.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PROBLEM] ASUS Sandybridge motherboards + PCI not working (IRQ
 n: nobody cared)

On 10/14/2011 05:04 AM, Chris Palmer wrote:
> 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...
>
> Previous references:
>
> https://lkml.org/lkml/2011/6/30/197
> https://bugzilla.kernel.org/show_bug.cgi?id=38632
> https://bugzilla.redhat.com/show_bug.cgi?id=713351
> https://bugzilla.kernel.org/show_bug.cgi?id=35332
> https://bugzilla.kernel.org/show_bug.cgi?id=34242
> https://bugzilla.kernel.org/show_bug.cgi?id=32242
> https://bugzilla.kernel.org/show_bug.cgi?id=39122

The bugzilla reports aren't currently accessible so I don't know if it 
was posted there, but can you post the output of "lspci -vv" as root? 
Could be that some other device is configured on that IRQ and sometimes 
spuriously generates interrupts.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ