[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1158005769.4748.0.camel@localhost.localdomain>
Date: Mon, 11 Sep 2006 22:16:09 +0200
From: Stian Jordet <liste@...det.net>
To: Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Daniel Drake <dsd@...too.org>,
akpm@...l.org, torvalds@...l.org, jeff@...zik.org, greg@...ah.com,
cw@...f.org, bjorn.helgaas@...com, linux-kernel@...r.kernel.org,
harmon@....edu, len.brown@...el.com, vsu@...linux.ru
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
On man, 2006-09-11 at 16:33 +0100, Sergio Monteiro Basto wrote:
> On Sun, 2006-09-10 at 21:21 +0200, Stian Jordet wrote:
> > On søn, 2006-09-10 at 20:41 +0100, Alan Cox wrote:
> > > Feel free to cc me the lspci data and partial diagnostics and I'll try
> > > and help too.
> >
> > Attached is lspci -xxx and dmesg from 2.6.18-rc6.
> > http://bugzilla.kernel.org/show_bug.cgi?id=2874 has some further
> > information about this (stupid) motherboard. Anything else you need?
> >
> > If anyone can help me with this, I'll promise to send the hero some
> > boxes of Norwegian beer!
> >
> >
> Hi, this isn't the case of one USB with IO-APIC-level on legacy
> interrupts ?
> 11: 5333 5326 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3
>
> if it is , was resolved with this [PATCH V3] VIA IRQ quirk behaviour change ?
I have no idea what you mean here, but it's by no means fixed by that
patch, actually it just got worse (usb didn't work, but still got
interrupts from eth0 - and it still used irq 11)
Thanks.
-Stian
-
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