public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <lkml@morethan.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>, Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Null Pointer BUG in uhci_hcd
Date: Wed, 8 Jul 2009 09:43:44 -0500	[thread overview]
Message-ID: <200907080943.47248.lkml@morethan.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0907071513380.8221-100000@iolanthe.rowland.org>

On Tue July 7 2009, Alan Stern wrote:
> On Tue, 7 Jul 2009, Michael S. Zick wrote:
> 
> > On Tue July 7 2009, Alan Stern wrote:
> > > On Tue, 7 Jul 2009, Michael S. Zick wrote:
> > > 
> > > > > It looks like there's a serious problem in your UHCI hardware.  
> > > > > According to the log you posted, it's not working at all.
> > > > > 
> > > > 
> > > > I am using the x86-generic drivers - -
> > > 
> > > Not a problem with the drivers, a problem in the hardware.
> > > 
> > 
> > Or hardware that works as the manufacturer intended, but differently
> > than expected.  Same difference as "broken" when compared to "standard".
> 
> No, hardware that doesn't work at all.  As in "all reads return
> 0xffffffff" -- that's just a guess but something like it would account
> for what you saw.
> 

Scratches head, and other parts. . .

Hmm... Already known about this chipset/cpu combination; there is
something about its hardware timing that is a "primary problem" - -

In addition to the suggested diagnostic and suggest fix - will look
into finding if that is a problem here, also.
It may just be a hardware timing issue - the processor is hitting the
hub before the hub has its act together from the last action.

Most likely will take most of the day - unless something jumps out
and says "I'm broke" during the testing.  ;)

Mike
> For more information enable CONFIG_USB_DEBUG and CONFIG_DEBUG_FS, then 
> see what's sitting in the usb/uhci/* files in debugfs.
> 
> > Let me see if I can find it again;
> > 1106:3038 translates to: PCI_DEVICE_ID_VIA_82C586_2
> > 1106:3104 translates to: PCI_DEVICE_ID_VIA_8235_USB_2
> > 
> > The first appears in (this device is the UHCI hub in the CX700 chipset):
> > arch/powerpc/platforms/85xx/mpc85xx_cds.c:              case PCI_DEVICE_ID_VIA_82C586_2:
> > arch/mips/pci/fixup-lm2e.c:DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_2,
> > include/linux/pci_ids.h:#define PCI_DEVICE_ID_VIA_82C586_2      0x3038
> 
> Those are simple interrupt routing fixups.  Not related.
> 
> > The second appears in:
> > include/linux/pci_ids.h:#define PCI_DEVICE_ID_VIA_8235_USB_2    0x3104
> > <Hmm... Dead?  Not used?  Never used?  Source padding?>
> 
> Probably never used.
> 
> Alan Stern
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 



  parent reply	other threads:[~2009-07-08 14:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 22:20 Null Pointer BUG in uhci_hcd Michael S. Zick
2009-07-07  9:13 ` Jiri Kosina
2009-07-07 14:08   ` Oliver Neukum
2009-07-07 14:32     ` Michael S. Zick
2009-07-07 15:10     ` Alan Stern
2009-07-07 15:23       ` Michael S. Zick
2009-07-07 15:31         ` Alan Stern
2009-07-07 15:43           ` Michael S. Zick
2009-07-07 17:28             ` Alan Stern
2009-07-07 17:56               ` Michael S. Zick
2009-07-07 19:21                 ` Alan Stern
2009-07-07 19:51                   ` Michael S. Zick
2009-07-07 20:00                     ` Alan Stern
2009-07-07 20:52                       ` Michael S. Zick
2009-07-07 21:24                         ` Michael S. Zick
2009-07-08 19:54                           ` Alan Stern
2009-07-08 14:43                   ` Michael S. Zick [this message]
2009-07-08 16:30                     ` Michael S. Zick
2009-07-08 16:38                       ` Michael S. Zick
2009-07-11 19:07                         ` uhci_hcd fails to off-line device/hub on error condition Michael S. Zick
2009-07-12 15:16                           ` Alan Stern
2009-07-08 19:57                       ` Null Pointer BUG in uhci_hcd Alan Stern
2009-07-08 20:22                         ` Michael S. Zick
2009-07-08 21:02                           ` Alan Stern
2009-07-08 22:31                             ` Michael S. Zick
2009-07-09 14:18                               ` Alan Stern
2009-07-08 23:56                         ` Michael S. Zick
2009-07-08 23:59                           ` Michael S. Zick
2009-07-09 14:20                           ` Alan Stern
2009-07-09 14:46                             ` Michael S. Zick
2009-07-09 15:08                               ` Alan Stern
2009-07-09 16:07                                 ` Michael S. Zick
2009-07-09 20:58                                   ` Michael S. Zick

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=200907080943.47248.lkml@morethan.org \
    --to=lkml@morethan.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.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