On 17 Jul 2003, Daniel St�ckner wrote:
> With kernel 2.5.70 and kernel 2.6.0-test1 I did exactly the same
> actions. Both kernels have the same (as similar as possible)
> configuration. I tested in both cases directly after booting into
> Runlevel 3 without doing anything before my test.
>
> Here the /proc/bus/usb/devices of kernel 2.5.70 after the disc was connected:
> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.05
> S: Manufacturer=Linux 2.5.70 uhci-hcd
> S: Product=Intel Corp. 82371AB/EB/MB PIIX4
> S: SerialNumber=00:07.2
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>
> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=05e3 ProdID=0702 Rev= 0.02
> S: Manufacturer=Genesyslogic
> S: Product=USB Mass Storage Device
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 4mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>
> Here the /proc/bus/usb/devices of kernel 2.6.0-test1 after connecting the disc:
> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.06
> S: Manufacturer=Linux 2.6.0-test1 uhci-hcd
> S: Product=Intel Corp. 82371AB/EB/MB PIIX4
> S: SerialNumber=0000:00:07.2
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>
> The usb-atapi device wasn�t listed!
>
> /var/log/messages of kernel 2.6.0-test1:
> http://www.stormgarde.com/daniel/messages-2.6.0-test1 (34kB)
>
> In my previous post, I didn�t do exactly the same actions as now with
> the two log, so it should be better to compare only the two logs of
> today...
There was a change made to the SCSI subsystem between 2.5.70 and 2.6.0.
Originally it tried to use a MODE-SENSE(6) command to tell what kind of
cache a disk device has; now it uses a MODE-SENSE(10) command.
The log you included from 2.5.70 shows that your drive rejects the
MODE-SENSE(6) with an error, so everything goes on from there and works
okay. The log on your website from 2.6.0 shows that your drive accepts
the MODE-SENSE(10) command without an error, but then crashes when asked
to send an entire page of data. In fact, it crashed so hard that it
disconnected itself from the USB bus! That's why it wasn't listed in
/proc/bus/usb/devices above.
It might help a little to know exactly how long the entire page is
supposed to be. If you could apply the test patch given below to your
2.6.0 kernel and repeat the test, it will print out the actual length in
the system log. Let us know when you've got the results ready.
Alan Stern
===== sd.c 1.52 vs edited =====
--- 1.52/drivers/scsi/sd.c Tue Jul 1 17:54:19 2003
+++ edited/drivers/scsi/sd.c Thu Jul 17 10:52:10 2003
@@ -1135,6 +1135,7 @@
if (scsi_status_is_good(res)) {
/* that went OK, now ask for the proper length */
len = data.length;
+ printk(KERN_INFO "Mode sense page length = %d\n", len);
if (len > 128)
len = 128;
res = sd_do_mode_sense(SRpnt, dbd, modepage, buffer,
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
