linux-kernel - Re: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351

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]

Date:	Wed, 22 Aug 2007 08:22:00 -0500
From:	Florin Iucha <florin@...ha.net>
To:	Jiri Kosina <jikos@...os.cz>
Cc:	linux-usb-devel@...ts.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	trond.myklebust@....uio.no
Subject: Re: [linux-usb-devel] USB-related oops in sysfs with linux
	v2.6.23-rc3-50-g28e8351

On Tue, Aug 21, 2007 at 03:42:26PM +0200, Jiri Kosina wrote:
> On Tue, 21 Aug 2007, Florin Iucha wrote:
> 
> > There is another interesting angle to this: in the past, every time I 
> > had keyboard problems, it used to be caused by the VFS and/or NFS... 
> > after much wrangling, a bunch of bugs were fixed (Hi Trond, Peter, 
> > Alan!). Now, after the keyboard "locked up", I used the mouse to close 
> > the gnome session, then I logged-in remotely to reboot.  The reboot 
> > process locked up and I need to use the reset button!  The second time 
> > the keyboard "locked up" I listed my processes, and I noticed that I had 
> > a couple of bash processes and a ssh process in "D" state. Something is 
> > fishy again in the VFS ;)
> 
> Yes, there were some NFS updates in between -rc2 and 
> 28e8351ac22de25034e048c680014ad824323c65. I'd be now even more curious 
> what are you going to find by bisect, please let us know.
> 
> I added Trond to CC, full thread to be found at 
> http://lkml.org/lkml/2007/8/21/151 for reference.
> 
> Florin, it also might be useful to capture the states of stuck processess 
> via alt-sysrq-T (or better by echo t > /proc/sysrq-trigger), so that we 
> know better where are they stuck.

This morning it took a bit longer to hang, but it happened.  The
backtraces are at http://iucha.net/2.6.23-rc3/backtraces.gz .

I'll try a bisect session this weekend.

Cheers,
florin

-- 
Bruce Schneier expects the Spanish Inquisition.
      http://geekz.co.uk/schneierfacts/fact/163

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)