From: Grzegorz Kulewski <kangur@polcom.net>
To: Andrew Morton <akpm@osdl.org>
Cc: len.brown@intel.com, duncan.sands@free.fr,
linux-usb-users@lists.sourceforge.net, gregkh@suse.de,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: 2.6.11 (stable and -rc) ACPI breaks USB
Date: Mon, 21 Mar 2005 23:36:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.62.0503212329190.6194@alpha.polcom.net> (raw)
In-Reply-To: <20050321142056.7609d615.akpm@osdl.org>
On Mon, 21 Mar 2005, Andrew Morton wrote:
> Grzegorz Kulewski <kangur@polcom.net> wrote:
>>
>> Hi,
>>
>> I just installed 2.6.11 and I was hit by the same bug (or feature?) I
>> found in -rcs. Basically my USB will work only if acpi=off was passed to
>> the kernel. It looks like without acpi=off it will assign IRQ 10 and with
>> acpi=off it will assign IRQ9. It worked at least with 2.6.9. I do not know
>> if the USB is completly broken but at least my speedtouch modem will not
>> work (the red led will be on for some time then completly black).
>>
>
> I didn't really follow all the ins and outs on this one. Will it end up
> being adequately resolved for 2.6.12?
It was identified (by Bjorn) to be some ACPI VIA PCI IRQ routing quirk
logic change (as far as I understand it). Unfortunatelly it is not good
for my board (AMD 761 North and VIA 686B South). Bjorn (huge thanks to
him) produced testing patch that fixed it for me. Further patches were
presented and discussed in the other thread. The newest one is waiting for
final testing from me (in couple of minutes probably). I will CC you on my
reply (if you are not already). As of what to do next with this patch (if
it still works) Bjorn and others should reply.
> Thanks.
Thanks for interest,
Grzegorz Kulewski
next prev parent reply other threads:[~2005-03-21 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 0:24 Grzegorz Kulewski
2005-03-21 22:20 ` Andrew Morton
2005-03-21 22:36 ` Grzegorz Kulewski [this message]
2005-03-21 23:55 ` Andrew Morton
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=Pine.LNX.4.62.0503212329190.6194@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=duncan.sands@free.fr \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®