All of lore.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: Thu, 9 Jul 2009 11:07:28 -0500	[thread overview]
Message-ID: <200907091107.31446.lkml@morethan.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0907091106050.5823-100000@iolanthe.rowland.org>

On Thu July 9 2009, Alan Stern wrote:
> On Thu, 9 Jul 2009, Michael S. Zick wrote:
> 

Going to have to mark this thread as "suspended" -
Have a 1Mbyte per minute memory leak that needs finding first.  ;)

Mike
> > In case you missed it - this is the CX700 integrated chipset in a NetBook.
> > No all USB devices are removable in the sense of being physically impossible.
> 
> Do the best you can.
> 
> > The documentation for the CX700 has been released from NDA and is available
> > at the VIA Linux portal - just in case you don't already have your copy.
> > 
> > More testing today - including trying some of the many kernel options available
> > for dealing with funky irq, bios, and acpi implementations.
> > 
> > On the subject of irq's:
> > 
> > root@cb01:~# biosdecode
> > # biosdecode 2.9
> > SMBIOS 2.4 present.
> >         Structure Table Length: 1556 bytes
> >         Structure Table Address: 0x000DC010
> >         Number Of Structures: 47
> >         Maximum Structure Size: 119 bytes
> > BIOS32 Service Directory present.
> >         Revision: 0
> >         Calling Interface Address: 0x000FDD64
> > ACPI 1.0 present.
> >         OEM Identifier: PTLTD
> >         RSD Table 32-bit Address: 0x1BEE5663
> > PNP BIOS 1.0 present.
> >         Event Notification: Not Supported
> >         Real Mode 16-bit Code Address: E923:768E
> >         Real Mode 16-bit Data Address: 0040:0000
> >         16-bit Protected Mode Code Address: 0x00015FCF
> >         16-bit Protected Mode Data Address: 0x00000400
> > PCI Interrupt Routing 1.0 present.
> >         Router ID: 00:11.0
> >         Exclusive IRQs: None
> >         Compatible Router: 1106:8324
> >         Slot Entry 1: ID 00:00, on-board
> >         Slot Entry 2: ID 00:11, on-board
> >         Slot Entry 3: ID 00:10, on-board
> >         Slot Entry 4: ID 00:0f, on-board
> >         Slot Entry 5: ID 04:09, slot number 9
> >         Slot Entry 6: ID 00:01, on-board
> >         Slot Entry 7: ID 01:00, on-board
> >         Slot Entry 8: ID 00:13, on-board
> >         Slot Entry 9: ID 02:01, on-board
> >         Slot Entry 10: ID 00:13, on-board
> >         Slot Entry 11: ID 03:03, slot number 49
> >         Slot Entry 12: ID 03:04, slot number 50
> >         Slot Entry 13: ID 03:05, slot number 51
> >         Slot Entry 14: ID 03:06, slot number 52
> >         Slot Entry 15: ID 03:07, slot number 53
> 
> Means nothing to me.  I'm no ACPI or chipset expert.
> 
> > Whatever a VIA 8324 router happens to be - - -
> > 
> > All four of the different brands of "Nano-book reference design"
> > machines have the same, or very similar, BIOS (all the VIA demo
> > board BIOS).  That interrupt table is the same in all machines.
> > Only one of the manufacturer's even bothered to change the serial
> > number of the machine (1234567890) - they are that "similar".
> 
> Alan Stern
> 
> 
> 



  reply	other threads:[~2009-07-09 16:07 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
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 [this message]
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=200907091107.31446.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 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.