From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wilco Beekhuizen <wilcobeekhuizen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA IRQ quirk missing PCI ids since 2.6.16.17
Date: Mon, 06 Nov 2006 13:30:51 +0000 [thread overview]
Message-ID: <1162819851.1566.67.camel@localhost.localdomain> (raw)
In-Reply-To: <6c4c86470611060338j7f216e26od93e35b4b061890e@mail.gmail.com>
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
prev parent reply other threads:[~2006-11-06 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 11:38 VIA IRQ quirk missing PCI ids since 2.6.16.17 Wilco Beekhuizen
2006-11-06 12:47 ` Sergio Monteiro Basto
2006-11-06 21:13 ` Alan Cox
2006-11-07 1:25 ` Dave Jones
2006-11-07 1:34 ` Alan Cox
2006-11-08 8:54 ` Wilco Beekhuizen
2006-11-08 12:43 ` Sergio Monteiro Basto
2006-11-08 14:55 ` Wilco Beekhuizen
2006-11-08 15:19 ` Alan Cox
2006-11-07 4:07 ` Greg KH
2006-11-07 8:31 ` Jeff Garzik
2006-11-08 17:22 ` Sergey Vlasov
2006-11-08 18:05 ` Alan Cox
2006-11-08 20:33 ` Sergey Vlasov
2006-11-06 13:30 ` Alan Cox [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=1162819851.1566.67.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wilcobeekhuizen@gmail.com \
/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