NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

USB regression in 10.1



I notice a smallish but annoying regression in 10.1 compared to 10.0.

I keep an external disk connected but powered off.
Previously, when powering the disk on (while already plugged in), it
would come online by itself.  First there would be this:

umass0 at uhub0 port 1 configuration 1 interface 0
umass0: Western Digital (0x1058) Elements 25A3 (0x25a3), rev 3.10/10.21, addr 5
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <WD, Elements 25A3, 1021> disk fixed
sd0(umass0:0:0:0):  Check Condition on CDB: 0x00 00 00 00 00 00
    SENSE KEY:  Not Ready
     ASC/ASCQ:  Logical Unit Is In Process Of Becoming Ready
sd0: drive offline

and then after a short time

sd0: fabricating a geometry
sd0: 9313 GB, 9537504 cyl, 64 head, 32 sec, 512 bytes/sect x 19532808192 sectors (this line isn't logged to /var/log/messages but I presume it's there)
sd0: GPT GUID: xxxxxxxx-xxxx-xxxx-xxxc-xxxxxxxxxxxx
dk14 at sd0: "yyyyyyyy", zzzzzz blocks at 4096, type: etc etc

but with 10.1 this doesn't happen any more.

The only thing I found so far was to unplug and replug the USB cable.
This is kind of annoying since I don't want to mess with the side of the
cable that is plugged into the spinning disk, so I have to get to the
back of the computer on the floor to unplug and replug there.

Then this happens:

sd0: detached
scsibus0: detached
umass0: detached
umass0: at uhub0 port 1 (addr 5) disconnected
umass0 at uhub0 port 1 configuration 1 interface 0
umass0: Western Digital (0x1058) Elements 25A3 (0x25a3), rev 3.10/10.21, addr 6
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <WD, Elements 25A3, 1021> disk fixed
sd0: fabricating a geometry
sd0: 9313 GB, 9537504 cyl, 64 head, 32 sec, 512 bytes/sect x 19532808192 sectors
sd0: fabricating a geometry
dk14 at sd0: "yyyyyyyy", zzzzzz blocks at 4096, type: etc etc

I note it says "sd0: fabricating a geometry" twice now.

Does anyone else see this?

I can add that with this USB controller and NetBSD's driver many USB
thumb drives don't work. The same thumb drives work fine in another
machine with the same version of NetBSD (but apparently some other USB
controller). Maybe this factors in as well.

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert                            <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work.           --I. Rose

Attachment: signature.asc
Description: PGP signature



Home | Main Index | Thread Index | Old Index