From: Sergey Vlasov <vsu@altlinux.ru>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: Andrew Morton <akpm@osdl.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Chris Wedgwood <cw@f00f.org>,
kernel list <linux-kernel@vger.kernel.org>,
linux-usb-users@lists.sourceforge.net,
linux-acpi@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Johny <kernel@agotnes.com>
Subject: Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
Date: Tue, 20 Jun 2006 17:59:38 +0400 [thread overview]
Message-ID: <20060620135938.GS3206@master.mivlgu.local> (raw)
In-Reply-To: <1150810206.7194.33.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 581 bytes --]
On Tue, Jun 20, 2006 at 02:30:06PM +0100, Sergio Monteiro Basto wrote:
> someone has it has a case similar and said that won't work without
> acpi=noirq
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6654
Yes, acpi=noirq will work around this bug in many cases, because Linux
will not try to reassign IRQs set up by BIOS.
BTW, the problem may be considered as an ACPI BIOS bug, because
reconfiguring a PCI Interrupt Link should set up IRQ routing, but it
obviously does not. Unfortunately, this problem seems to be widespread,
so a workaround in kernel is needed.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 191 bytes --]
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
prev parent reply other threads:[~2006-06-20 13:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 11:38 [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Johny Ågotnes
2006-06-20 11:21 ` Johny
2006-06-20 11:40 ` Andrew Morton
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-21 10:50 ` Johny
2006-06-22 0:36 ` who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Sergio Monteiro Basto
2006-06-22 0:47 ` Randy.Dunlap
2006-06-22 1:04 ` how I " Sergio Monteiro Basto
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 22:46 ` Sergio Monteiro Basto
2006-06-22 22:54 ` Chris Wedgwood
2006-06-23 1:00 ` Sergio Monteiro Basto
2006-06-23 1:39 ` Randy.Dunlap
2006-06-23 1:50 ` Sergio Monteiro Basto
2006-06-23 2:02 ` Randy.Dunlap
2006-06-28 1:08 ` [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergio Monteiro Basto
2006-06-23 1:40 ` how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Johny
2006-06-22 23:25 ` Randy.Dunlap
2006-06-23 1:30 ` Sergio Monteiro Basto
2006-06-23 15:31 ` [linux-usb-devel] who I do " David Brownell
2006-06-20 12:09 ` [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergey Vlasov
2006-06-20 13:30 ` Sergio Monteiro Basto
2006-06-20 13:59 ` Sergey Vlasov [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=20060620135938.GS3206@master.mivlgu.local \
--to=vsu@altlinux.ru \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=kernel@agotnes.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=sergio@sergiomb.no-ip.org \
--cc=stern@rowland.harvard.edu \
/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