linux-kernel - Re: VIA IRQ quirk missing PCI ids since 2.6.16.17

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]

Message-Id: <1162819851.1566.67.camel@localhost.localdomain>
Date:	Mon, 06 Nov 2006 13:30:51 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Wilco Beekhuizen <wilcobeekhuizen@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: VIA IRQ quirk missing PCI ids since 2.6.16.17

Ar Llu, 2006-11-06 am 12:38 +0100, ysgrifennodd Wilco Beekhuizen:
> Including PCI_ANY_ID again fixes these problems but is of course a
> pretty evil fix. The problem is I can't find out which PCI ids to
> include. I'm new to this list so suggestions are welcome.

As far as I can make out the correct answer is "none", and then fix the
actual problems in the boxes that need these workarounds. They break as
much if not more than they cure.

Please boot your system without the workarounds (ie a current kernel).
Then do lspci -vxxx and save that to a file. Then go back to a kernel
with working networking and email me and/or the list that result.

>>From that I can take a look at what we've actually got set up for IRQ
routing and try to work out why it might not be working and how we got
where we did.

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