Any idea why an usb-storage device registers sdb twice? Its a 2.6.9rc2 based kernel for SuSE 9.2-x86_64. I havent seen this before, havent asked if current Linus tree works any better.
...
ohci_hcd 0000:03:00.0: wakeup
usb 1-2: new full speed USB device using address 2
usb 1-2: Product: Flash Disk
usb 1-2: Manufacturer: USB
usb 1-2: SerialNumber: 106C1141AD2C8C03
Initializing USB Mass Storage driver...
scsi5 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB Flash Disk Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
sdb: Unit Not Ready, sense:
Current : sense key Unit Attention
Additional sense: Not ready to ready change, medium may have changed
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
Current sd: sense key Unit Attention
Additional sense: Not ready to ready change, medium may have changed
sdb: test WP failed, assume Write Enabled
sdb: assuming drive cache: write through
SCSI device sdb: 4095488 512-byte hdwr sectors (2097 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 4095488 512-byte hdwr sectors (2097 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sdb: sdb1
kobject_register failed for sdb1 (-17)
Call Trace:<ffffffff80210ad6>{kobject_register+70}
<ffffffff801b6d4f>{add_partition+255}
...
dmesg.gz
Description: application/gunzip
