KM266/VT8235, USB2.0 and problems

KM266/VT8235, USB2.0 and problems

[lk]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1085 bytes --]

Hi.  I've noticed that intermittently in the past with some devices, and 
now every time with my new USB2.0 thumb drive (aka pen drive, aka flash 
memory thing) that there are errors with the USB on my motherboard.  It's 
a M7VIG-PRO, which has a KM266/VT8235 chipset.

Using kernel 2.6.0, I can only access my flash drive several times before 
getting an error about not being able to access the device.  The dmesg 
output is below.  When I try on my laptop, which has an EHCI USB2.0 
controller, the device works flawlessly.  There are no errors, etc.

I am using a USB keyboard and a USB mouse.  Both work fine.

I've tried several combinations of connecting the device, with and without 
the "noapic" kernel option while booting.  I've connected the device to 
the motherboard's USB sockets (ie the ones soldered to the board, not via 
wires to the case), through a USB2.0 hub, etc.  I get the same result 
every time.

I've included the relevant parts of "dmesg" and "dmidecode".  Please cc: 
me on responses, since I'm not subscribed, and let me know what to try 
next.

Thanks.

[-- Attachment #2: Type: TEXT/PLAIN, Size: 489 bytes --]

# dmidecode 1.8
SMBIOS 2.3 present.
DMI 2.3 present.
38 structures occupying 1083 bytes.
DMI table at 0x000F0800.
Handle 0x0000
	DMI type 0, 20 bytes.
	BIOS Information Block
		Vendor: Phoenix Technologies, LTD
		Version: 6.00 PG
		Release: 02/24/2003
		BIOS base: 0xE0000
		ROM size: 256K
		Capabilities:
			Flags: 0x000000007FCBDE90
...
Handle 0x0002
	DMI type 2, 8 bytes.
	Board Information Block
		Vendor:  
		Product: KM266-8235
		Version:  
		Serial Number:  

[-- Attachment #3: Type: TEXT/PLAIN, Size: 4673 bytes --]

Linux version 2.6.0 (root@axp.isacolor) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)) #18 Sun Jan 4 17:26:03 CST 2004
...
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: irq 5, pci mem e1812000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-13
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: irq 11, io base 0000d000
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: irq 12, io base 0000d400
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: irq 10, io base 0000d800
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
...
hub 1-0:1.0: new USB device on port 3, assigned address 4
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor: MicroAdv  Model: QuickiDrive128M   Rev: 2.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
sda: Unit Not Ready, sense:
Current : sense = 70  6
ASC=28 ASCQ= 0
Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=08 
Current sd: sense = 70  6
ASC=28 ASCQ= 0
Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00 
sda: test WP failed, assume Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: Mode Sense: 00 26 94 00
sda: assuming drive cache: write through
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: Mode Sense: 00 26 94 00
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0: p1
 /dev/scsi/host0/bus0/target0/lun0: p1
devfs_mk_bdev: could not append to parent for scsi/host0/bus0/target0/lun0/part1
kobject_register failed for sda1 (-17)
Call Trace:
 [<c01da272>] kobject_register+0x52/0x60
 [<c017abc9>] add_partition+0xb9/0xd0
 [<c017ad7e>] register_disk+0x13e/0x170
 [<c022825a>] add_disk+0x4a/0x60
 [<c02281e0>] exact_match+0x0/0x10
 [<c02281f0>] exact_lock+0x0/0x20
 [<c02548dd>] sd_probe+0x1bd/0x270
 [<c017c355>] sysfs_add_file+0xa5/0xb0
 [<c02213ef>] bus_match+0x3f/0x70
 [<c0221461>] device_attach+0x41/0xa0
 [<c022164b>] bus_add_device+0x5b/0xa0
 [<c0220535>] device_add+0xb5/0x120
 [<c0251be8>] scsi_sysfs_add_sdev+0x58/0x170
 [<c025082d>] scsi_add_lun+0x2bd/0x390
 [<c0250a20>] scsi_probe_and_add_lun+0x120/0x1b0
 [<c0251091>] scsi_scan_target+0xa1/0x120
 [<c0251169>] scsi_scan_channel+0x59/0xa0
 [<c0251275>] scsi_scan_host_selected+0xc5/0xd0
 [<c02512af>] scsi_scan_host+0x2f/0x40
 [<c028d688>] storage_probe+0x158/0x1d0
 [<c0271803>] usb_probe_interface+0x73/0xa0
 [<c02213ef>] bus_match+0x3f/0x70
 [<c0221461>] device_attach+0x41/0xa0
 [<c022164b>] bus_add_device+0x5b/0xa0
 [<c0220535>] device_add+0xb5/0x120
 [<c0277d98>] usb_set_configuration+0x1c8/0x240
 [<c02725fc>] usb_new_device+0x28c/0x410
 [<c027467a>] hub_port_connect_change+0x1ca/0x330
 [<c0274aea>] hub_events+0x30a/0x350
 [<c0274b5d>] hub_thread+0x2d/0xf0
 [<c010b182>] ret_from_fork+0x6/0x14
 [<c011ab10>] default_wake_function+0x0/0x20
 [<c0274b30>] hub_thread+0x0/0xf0
 [<c01092c9>] kernel_thread_helper+0x5/0xc

Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 7440
Buffer I/O error on device sda, logical block 930

Re: KM266/VT8235, USB2.0 and problems

[Greg KH]

On Sun, Jan 04, 2004 at 11:30:51PM -0600, lk@rekl.yi.org wrote:
> Hi.  I've noticed that intermittently in the past with some devices, and 
> now every time with my new USB2.0 thumb drive (aka pen drive, aka flash 
> memory thing) that there are errors with the USB on my motherboard.  It's 
> a M7VIG-PRO, which has a KM266/VT8235 chipset.
> 
> Using kernel 2.6.0, I can only access my flash drive several times before 
> getting an error about not being able to access the device.  The dmesg 
> output is below.  When I try on my laptop, which has an EHCI USB2.0 
> controller, the device works flawlessly.  There are no errors, etc.
> 
> I am using a USB keyboard and a USB mouse.  Both work fine.
> 
> I've tried several combinations of connecting the device, with and without 
> the "noapic" kernel option while booting.  I've connected the device to 
> the motherboard's USB sockets (ie the ones soldered to the board, not via 
> wires to the case), through a USB2.0 hub, etc.  I get the same result 
> every time.
> 
> I've included the relevant parts of "dmesg" and "dmidecode".  Please cc: 
> me on responses, since I'm not subscribed, and let me know what to try 
> next.

Do the errors go away if you stop using devfs?

thanks,

greg k-h

Re: KM266/VT8235, USB2.0 and problems

[lk]

On Mon, 5 Jan 2004, Greg KH wrote:

> Do the errors go away if you stop using devfs?


Since Gentoo requires devfs, no.  I only have Gentoo installed on the 
machine.

I suppose that I could get an install CD from another distribution or a 
rescue CD, boot from it, and test out the device.  Are there any CD's or 
boot images that are based on 2.6 that don't use devfs?

Re: KM266/VT8235, USB2.0 and problems

[Greg KH]

On Mon, Jan 05, 2004 at 10:48:41AM -0600, lk@rekl.yi.org wrote:
> On Mon, 5 Jan 2004, Greg KH wrote:
> 
> > Do the errors go away if you stop using devfs?
> 
> 
> Since Gentoo requires devfs, no.  I only have Gentoo installed on the 
> machine.

Gentoo does not require devfs anymore, or so the Gentoo developers tell
me.

greg k-h

Re: KM266/VT8235, USB2.0 and problems

[lk]

On Mon, 5 Jan 2004, Greg KH wrote:

> Gentoo does not require devfs anymore, or so the Gentoo developers tell
> me.
> 


Apparently, udev can be used.  I will try it.

Re: KM266/VT8235, USB2.0 and problems

[lk]

> > > Do the errors go away if you stop using devfs?
> > 

Ok, I removed devfs support from the kernel, and installed udev on the 
machine.  I get the same error:

SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 7552
Buffer I/O error on device sda, logical block 944



I migrated my laptop to use udev, also.  The USB stick still works 
perfectly on it.

Any other suggestions?

Re: KM266/VT8235, USB2.0 and problems

[Peter Lieverdink]

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

On Tue, 2004-01-06 at 14:52, lk@rekl.yi.org wrote:
> > > > Do the errors go away if you stop using devfs?
> > > 
> 
> Ok, I removed devfs support from the kernel, and installed udev on the 
> machine.  I get the same error:
> 
> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 7552
> Buffer I/O error on device sda, logical block 944

I get the same thing using USB2 on a KT400/VT8235 mobo. I have a 20Gb
USB2 HDD (fat32), which produces this when accessed:

SCSI error : <1 0 0 0> return code = 0x8000000
Current sdb: sense key No Sense
end_request: I/O error, dev sdb, sector 19159735
Buffer I/O error on device sdb1, logical block 19159672

The drive works flawlessly with Windows and MacOS. A 128Mb USB key via
USB1.1 causes no problems. Not using udev, not using devfs. The USB2
drive works fine under 2.4.X as well.

- Peter.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: KM266/VT8235, USB2.0 and problems

[Greg KH]

On Mon, Jan 05, 2004 at 09:52:04PM -0600, lk@rekl.yi.org wrote:
> > > > Do the errors go away if you stop using devfs?
> > > 
> 
> Ok, I removed devfs support from the kernel, and installed udev on the 
> machine.  I get the same error:

You don't get the oops anymore, which is good.

> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 7552
> Buffer I/O error on device sda, logical block 944

Can you enable CONFIG_USB_STORAGE_DEBUG and send the debug log to the
linux-usb-devel mailing list for when this happens?  The people there
should be able to help you out.

thanks,

greg k-h

Re: KM266/VT8235, USB2.0 and problems

[lk]

On Tue, 6 Jan 2004, Greg KH wrote:

> Can you enable CONFIG_USB_STORAGE_DEBUG and send the debug log to the
> linux-usb-devel mailing list for when this happens?  The people there
> should be able to help you out.
> 

Ok, I enabled that and the SCSI option.  Here's what I get:

Jan  7 09:04:10 axp kernel: hub 1-0:1.0: new USB device on port 3, 
assigned address 6
Jan  7 09:04:10 axp usb.agent[4754]: ... no modules for USB product 
ea0/2168/200
Jan  7 09:04:10 axp kernel: scsi0 : SCSI emulation for USB Mass Storage 
devices
Jan  7 09:04:10 axp kernel:   Vendor: MicroAdv  Model: QuickiDrive128M   
Rev: 2.00
Jan  7 09:04:10 axp kernel:   Type:   Direct-Access                      
ANSI SCSI revision: 02
Jan  7 09:04:10 axp scsi.agent[4788]: how to add device type= at 
/devices/pci0000:00/0000:00:10.3/usb1/1-3/1-3:1.0/host0/0:0:0:0 ??
Jan  7 09:04:10 axp kernel: sda: Unit Not Ready, sense:
Jan  7 09:04:10 axp kernel: Current : sense key Unit Attention
Jan  7 09:04:10 axp kernel: Additional sense: Not ready to ready change, 
medium may have changed
Jan  7 09:04:10 axp kernel: sda : READ CAPACITY failed.
Jan  7 09:04:10 axp kernel: sda : status=1, message=00, host=0, driver=08
Jan  7 09:04:10 axp kernel: Current sd: sense key Unit Attention
Jan  7 09:04:10 axp kernel: Additional sense: Not ready to ready change, 
medium may have changed
Jan  7 09:04:11 axp kernel: sda: Write Protect is off
Jan  7 09:04:11 axp kernel:  sda:<7>usb-storage: queuecommand called
Jan  7 09:04:11 axp kernel:  sda1
Jan  7 09:04:11 axp kernel: Attached scsi removable disk sda at scsi0, 
channel 0, id 0, lun 0
Jan  7 09:04:11 axp kernel: Attached scsi generic sg0 at scsi0, channel 0, 
id 0, lun 0,  type 0
Jan  7 09:09:05 axp kernel: SCSI error : <0 0 0 0> return code = 0x70000
Jan  7 09:09:05 axp kernel: end_request: I/O error, dev sda, sector 7552


Also, the full dmesg and .config are available at 
http://rekl.no-ip.org/~lk/

The problem is that the USB2.0 flash drive doesn't work after a few 
accesses on my KM266/8235 based machine.  It works fine on my laptop, 
which also has USB2.0.

Any suggestions?

Thanks.