From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm3 USB ehci IRQ problem
Date: Tue, 06 Jul 2004 18:15:49 +0200 [thread overview]
Message-ID: <1089130549.3160.2.camel@paragon.slim> (raw)
In-Reply-To: <1089062128.15675.122.camel@dhcppc4>
On Mon, 2004-07-05 at 23:15, Len Brown wrote:
> On Mon, 2004-07-05 at 16:33, Jurgen Kramer wrote:
> > On Mon, 2004-07-05 at 22:16, Jurgen Kramer wrote:
> > > On Mon, 2004-07-05 at 21:02, Len Brown wrote:
> > > > On Sun, 2004-06-27 at 08:02, Jurgen Kramer wrote:
>
> > 2.6.7 vanilly results are in. The results are...it works..
>
> great! Now if you can apply this patch to 2.6.7 and tell me if
> it is ACPI that broke EHCI for you in -mm5 or something else:
>
> http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm5/broken-out/bk-acpi.patch
>
Alright, still looks good:
<snip>
ACPI: Subsystem revision 20040615
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
<snip>
ehci_hcd 0000:00:1d.7: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: irq 23, pci mem f881dc00
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v2.2
<snip>
So it doesn't look like a ACPI problem.
Jurgen
next prev parent reply other threads:[~2004-07-06 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FEF3E@hdsmsx403.hd.intel.com>
2004-07-05 19:02 ` 2.6.7-mm3 USB ehci IRQ problem Len Brown
2004-07-05 20:16 ` Jurgen Kramer
2004-07-05 20:33 ` Jurgen Kramer
2004-07-05 21:15 ` Len Brown
2004-07-06 16:15 ` Jurgen Kramer [this message]
2004-07-06 16:27 ` Len Brown
2004-06-27 12:02 Jurgen Kramer
2004-06-27 18:42 ` Andrew Morton
2004-06-27 20:08 ` Jurgen Kramer
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=1089130549.3160.2.camel@paragon.slim \
--to=gtm.kramer@inter.nl.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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