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>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Oops in UHCI when encountering "host controller process error"
Date: Tue, 09 Dec 2008 10:24:47 -0800	[thread overview]
Message-ID: <493EB7EF.7040309@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0812082105170.30007-100000@netrider.rowland.org>

Alan Stern wrote:
> The hardware starts running right at the end of uhci_start(), in the
> call to start_rh().  However according to those debugging lines you
> added to uhci_alloc_qh(), the DMA pool allocations are all messed up.  
> Those initial allocations all occur within uhci_start(), in the
>
> 	for (i = 0; i < UHCI_NUM_SKELQH; ++i)
>
> loop.  It sure looks like the DMA pool memory management needs 
> attention.
>
>   

Yep, there's something very odd going on in there.  By contrast, does 
this look OK?  The allocations are fine, but I'm wondering if the 
skeleton QH stuff is all correct; it seems to work OK in this state.

uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4000 handle=7e212000
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4080 handle=7e212080
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4100 handle=7e212100
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4180 handle=7e212180
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4200 handle=7e212200
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4280 handle=7e212280
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4300 handle=7e212300
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4380 handle=7e212380
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4400 handle=7e212400
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4480 handle=7e212480
uhci_alloc_qh: uhci=ffff88002e5de3d0 qh=ffff88002e5f4500 handle=7e212500
Root-hub state: reset   FSBR: 0
HC status
  usbcmd    =     0000   Maxp32 
  usbstat   =     0020   HCHalted 
  usbint    =     0000
  usbfrnum  =   (0)000
  flbaseadd = 7ffd5000
  sof       =       40
  stat1     =     0080  
  stat2     =     0080  
Most recent frame: 0 (0)   Last ISO frame: 0 (0)
Periodic load table
        0       0       0       0       0       0       0       0
        0       0       0       0       0       0       0       0
        0       0       0       0       0       0       0       0
        0       0       0       0       0       0       0       0
Total: 0, #INT: 0, #ISO: 0
Frame List
Skeleton QHs
- skel_unlink_qh
    [ffff88002e5f4000] Skel QH link (00000001) element (00000001)
      queue is empty
- skel_iso_qh
    [ffff88002e5f4080] Skel QH link (00000001) element (00000001)
      queue is empty
- skel_int128_qh
    [ffff88002e5f4100] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int64_qh
    [ffff88002e5f4180] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int32_qh
    [ffff88002e5f4200] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int16_qh
    [ffff88002e5f4280] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int8_qh
    [ffff88002e5f4300] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int4_qh
    [ffff88002e5f4380] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_int2_qh
    [ffff88002e5f4400] Skel QH link (7e212482) element (00000001)
      queue is empty
- skel_async_qh
    [ffff88002e5f4480] Skel QH link (00000001) element (7e215000)
      queue is empty
[ffff88002e5f3000] link (00000001) e0 Length=0 MaxLen=7ff DT0 EndPt=0 Dev=7f, PID=69(IN) (buf=00000000)
- skel_term_qh
    [ffff88002e5f4500] Skel QH link (7e212502) element (7e215000)
      queue is empty


Thanks,
    J

  reply	other threads:[~2008-12-09 18:25 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
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 [this message]
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=493EB7EF.7040309@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --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