linux-kernel - Re: Null Pointer BUG in uhci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200907081522.22026.lkml@morethan.org>
Date:	Wed, 8 Jul 2009 15:22:19 -0500
From:	"Michael S. Zick" <lkml@...ethan.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Oliver Neukum <oliver@...kum.org>, Jiri Kosina <jkosina@...e.cz>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: Null Pointer BUG in uhci_hcd

On Wed July 8 2009, Alan Stern wrote:
> On Wed, 8 Jul 2009, Michael S. Zick wrote:
> 
> > But, then again, we might just get lucky:
> > ehci_hcd 0000:00:10.4: Unlink after no-IRQ?  Controller is probably using the wrong IRQ.
> > usb 1-5: khubd timed out on ep0in len=18/64
> 
> Like I've been telling you all along, the hardware isn't working.  
>

That sounds very fragile.

> I suspect it's worse than a simple interrupt-routing mistake.
> 

I would not object to your removing that one mistake - that is one less
to contend with.

> > > > For more information enable CONFIG_USB_DEBUG and CONFIG_DEBUG_FS, then 
> > > > see what's sitting in the usb/uhci/* files in debugfs.
> > > > 
> > 

Fours up-time - nothing written to dmesg since boot -
Just the usual hard-lockup.

Also - something in the combined fix/diagnostic patch
disable any sensing of external usb events.
So I couldn't very well poke devices at it.  ;)

> > Anything in particular to look for/at?
> 
> Just post the contents of those files.
> 

Will capture that information during this afternoon's testing.

Mike
> Alan Stern
> 
> 
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/