public inbox for linux-kernel@vger.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: Fri, 17 Oct 2008 08:20:45 -0700	[thread overview]
Message-ID: <48F8AD4D.30706@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810171046530.2178-100000@iolanthe.rowland.org>

Alan Stern wrote:
>> ------------[ cut here ]------------
>> WARNING: at /home/jeremy/hg/xen/paravirt/linux/drivers/usb/host/uhci-q.c:1744 uhci_scan_schedule+0xb7/0x9a3()
>> uhci->skelqh[1]->node.next is NULL
>>     
>
> Odd.  Is skelqh[1] the only entry whose node.next is NULL?  Not 
> skelqh[2] or others?
>   

No, the others too, but all the WARN_ON backtraces got very verbose and 
I had to rush home at the end of the day.

> The node is initialized during uhci_start() in uhci-hcd.c -- there's a
> loop which initializes all the uhci->skelqh[i] entries by calling
> uhci_alloc_qh().  You should check inside that loop to see whether
> uhci->skelqh[i]->node.next is NULL to begin with.  If it is then
> something about the DMA-coherent memory is funny; if not then the
> linked list pointer gets corrupted somewhere.
>   

OK, will check it out.

    J

  reply	other threads:[~2008-10-17 15:20 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 [this message]
2008-10-21 20:02         ` Alan Stern
2008-10-21 20:41           ` Jeremy Fitzhardinge
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=48F8AD4D.30706@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox