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: <Pine.LNX.4.44L0.0905241035380.7718-100000@netrider.rowland.org>
Date:	Sun, 24 May 2009 10:40:10 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Rogério Brito <rbrito@....usp.br>
cc:	Robert Hancock <hancockrwd@...il.com>,
	<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>
Subject: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error

On Sun, 24 May 2009, [utf-8] Rogério Brito wrote:

> Resuming our earlier discussion, I got another case of weird USB
> messages here with kernel 2.6.30-rc5 (sorry, I have not yet had time to
> use anything newer).
> 
> My father has a USB (1.1, I would say, which matches what the logs say)
> stick/pen drive that, when I connect to my ECHI controller on my machine
> with an ICH5 chipset, I get:

> [ 2291.280525] sd 0:0:0:0: [sda] 256000 512-byte hardware sectors: (131 MB/125 MiB)
> [ 2291.283532] sd 0:0:0:0: [sda] Write Protect is off
> [ 2291.283539] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
> [ 2291.283543] sd 0:0:0:0: [sda] Assuming drive cache: write through
> [ 2291.283603] PM: Adding info for No Bus:sda
> [ 2291.290517] sd 0:0:0:0: ioctl_internal_command return code = 8000002
> [ 2291.290523]    : Sense Key : 0x0 [current] 
> [ 2291.290529]    : ASC=0x0 ASCQ=0x0
> [ 2291.298513] sd 0:0:0:0: [sda] Assuming drive cache: write through
> [ 2291.298520]  sda: sda1
> [ 2291.304573] PM: Adding info for No Bus:sda1
> [ 2291.309522] sd 0:0:0:0: ioctl_internal_command return code = 8000002
> [ 2291.309527]    : Sense Key : 0x0 [current] 
> [ 2291.309533]    : ASC=0x0 ASCQ=0x0
...

> In particular, those ioctl_internal_command return code messages seem
> strange, regarding other USB devices that I have. Are they being shown
> because I have some debugging information in my kernel or are they
> abnormal?

It is abnormal, but I can't tell what the reason is without more 
information.  You should try using usbmon (see 
Documentation/usb/usbmon.txt) to trace these events.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ