All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-usb <linux-usb@vger.kernel.org>
Subject: Re: Oops in UHCI when encountering "host controller process error"
Date: Tue, 21 Oct 2008 13:41:12 -0700	[thread overview]
Message-ID: <48FE3E68.5080908@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810211601340.2353-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Thu, 16 Oct 2008, Jeremy Fitzhardinge wrote:
>
>   
>> Looks like this is the relevent detail: "uhci->skelqh[1]->node.next is 
>> NULL" for all the queues.  Haven't looked into it yet.
>>     
>
> Any news?
>   

They're being initialized properly (which is what I'd expect, since the 
driver works fine when booting native).  They're being trashed at some 
later point, likely when handing the hardware error.  But I haven't had 
a chance to pick through it in any more detail than that.

    J

  reply	other threads:[~2008-10-21 20:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 23:42 Oops in UHCI when encountering "host controller process error" Jeremy Fitzhardinge
2008-10-16 14:03 ` Alan Stern
2008-10-16 22:02   ` Jeremy Fitzhardinge
2008-10-16 23:34     ` Alan Stern
2008-10-17  1:00       ` Jeremy Fitzhardinge
2008-10-17 14:58         ` Alan Stern
2008-10-17 15:20           ` Jeremy Fitzhardinge
2008-10-21 20:02         ` Alan Stern
2008-10-21 20:41           ` Jeremy Fitzhardinge [this message]
2008-12-09  0:04           ` Jeremy Fitzhardinge
2008-12-09  1:04             ` Jeremy Fitzhardinge
2008-12-09  2:13               ` Alan Stern
2008-12-09 18:24                 ` Jeremy Fitzhardinge
2008-12-09 18:43                   ` Alan Stern
2008-12-09 22:49                     ` Jeremy Fitzhardinge
2008-12-10 15:10                       ` Alan Stern
2008-12-10 19:15                         ` Jeremy Fitzhardinge

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=48FE3E68.5080908@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.