linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: "Trever L. Adams" <tadams-lists@myrealbox.com>,
	arjanv@redhat.com, Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [More Info] Re: 2.6.0test 1 fails on eth0 up (arjanv RPM's - all needed rpms installed)
Date: Tue, 15 Jul 2003 16:15:48 -0700	[thread overview]
Message-ID: <3F148B24.8080408@pacbell.net> (raw)
In-Reply-To: <20030715210240.GA5345@kroah.com>

Greg KH wrote:

> Hm, but usb_hcd_irq() reports back the proper interrupt return value.  I
> don't see how this could happen, unless the ehci driver was somehow
> halted...
> 
> David, any ideas?

It's getting an IRQ before the driver expects them,
I suspect.  I think the HCD glue needs a new entry,
forcing hardware reset before the rest of hcd init.
Easy/simple to do; and IMO reasonable too.

Of course, it's also strange that leaving ACPI on
causes problems at this level.  And that it only
happens for EHCI.

- Dave



  parent reply	other threads:[~2003-07-15 22:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 18:56 Trever L. Adams
2003-07-14 19:06 ` Jeff Garzik
2003-07-14 19:15   ` Arjan van de Ven
2003-07-14 21:20     ` Trever L. Adams
2003-07-15 20:10       ` [More Info] " Trever L. Adams
2003-07-15 21:02         ` Greg KH
2003-07-15 20:55           ` jds
2003-07-15 23:15           ` David Brownell [this message]
2003-07-26  0:06           ` David Brownell
2003-07-31  6:42             ` Trever L. Adams
2003-07-31 17:15               ` David Brownell
2003-07-16 18:59 ` Zwane Mwaikambo
2003-07-17  3:11   ` Trever L. Adams
     [not found]     ` <Pine.LNX.4.53.0307170254500.32541@montezuma.mastecende.com>
2003-07-17 14:46       ` Trever L. Adams

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=3F148B24.8080408@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=arjanv@redhat.com \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tadams-lists@myrealbox.com \
    --subject='Re: [More Info] Re: 2.6.0test 1 fails on eth0 up (arjanv RPM'\''s - all needed rpms installed)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).