SUSE 9.2 hangs handling USB memory stick
Hi, I've just purchased 9.2 Pro - it's great, but I have serious problem with mobile USB memory devices. I've sent this post to installation support but it does not cover USB problems. I also reported it as technical feedback, but got no response. However, I found similar problem reports[3]. Registering newly connected device consume a lot of CPU - mostly by hwscan and kdeinit (up to 97%) and the whole system becomes unresponsive for about 10 s. The same for cleanup when device is disconnected. This wasn't happening in 9.0 - does it have something to do with this new, smart, automatic mounting/unmounting ? Is there a way to change that ? This is annoying, but not critical. The more serious is that the whole system usually freezes to death when I connect my 128 MB TwinMos pendrive[1] and perform some operations like file copying. Systems hangs irrecoverably - cold reset is the only solution. That's unbelievable, I've never seens anything like this in Linux before. The first crash happened when I moved mouse cursor over PDF file in Konqueror, so I thought it has something to do with previews in tooltips or other scanning file in background for some attributes. I disabled previews in tooltips in Konqueror settings, but it didn't help - systems still freezes suddenly, mostly during file copying. This happens almost always, but mainly for this pendrive - so far, I am trying to replicate this problem using Sony MS cards with Vantec card reader - so far it works without problems. Mobile disks have vfat filesystems (to be compatible with "leading" platform...) and there are messages in dmesg: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! dmesg after device is connected: usb 1-2: new full speed USB device using address 4 usb 1-2: Product: USB Mobile Disk usb 1-2: Manufacturer: TTI-MSA usb 1-2: SerialNumber: AAAA000021 scsi2 : SCSI emulation for USB Mass Storage devices Vendor: TTI-MSA Model: USB Mobile Disk Rev: 0.0A Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 253120 512-byte hdwr sectors (130 MB) sda: Write Protect is off sda: Mode Sense: 4b 00 00 00 sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0, type 0 Vendor: TTI-MSA Model: USB Mobile Disk Rev: 0.0A Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 2880 512-byte hdwr sectors (1 MB) sdb: Write Protect is off sdb: Mode Sense: 4b 00 00 00 sdb: assuming drive cache: write through sdb: sdb1 Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 1 Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 1, type 0 USB Mass Storage device found at 4 New devices appear: /dev/sda1 and /dev/sdb1 (there are 2 partitions) Opening sda1 in "My computer" triggers 2 messages in dmesg: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! $ mount [...] /dev/sdb1 on /media/usb-AAAA000021:0:0:1p1 type subfs (rw,noexec,nosuid,nodev,sync,procuid,iocharset=utf8) /dev/sda1 on /media/usb-AAAA000021:0:0:0p1 type subfs (rw,noexec,nosuid,nodev,sync,procuid,iocharset=utf8) Removing device: usb 1-2: USB disconnect, address 4 ... but next time it can be: sdb : READ CAPACITY failed. sdb : status=0, message=00, host=7, driver=00 sdb : sense not available. sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 sdb: assuming drive cache: write through usb 1-2: USB disconnect, address 5 sdb : READ CAPACITY failed. sdb : status=0, message=00, host=1, driver=00 sdb : sense not available. sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 sdb: assuming drive cache: write through sdb:<3>Buffer I/O error on device sdb, logical block 0 Buffer I/O error on device sdb, logical block 0 Buffer I/O error on device sdb, logical block 262143 Buffer I/O error on device sdb, logical block 262143 Buffer I/O error on device sdb, logical block 0 ldm_validate_partition_table(): Disk read failed. Buffer I/O error on device sdb, logical block 0 unable to read partition table That's interesting, because I didn't do explicitly anything to /dev/sdb All mentioned equipment works perfectly in SUSE 9.0 (exactly the same hardware[2], another HD). It seems other people have the same problem [3]. Anyone else ? It's almost impossible to reliably use USB sticks. Regards, Jarek PS. One more question: what's the status of POSIX4 message queues in 9.2 ? Is it fully operational or not really ? Call to mq_open always returns -1, errno: 22 (Invalid argument). All arguments seem to be OK, according to [4]. References: [1] USB1.1 Mobile Disk III http://www.twinmos.com/flash/flash_p_usb11_mobile3.htm [2] Hardware Mainboard: ASUS P3BF (bought in 2000) CPU: Celeron Coppermine 1.2GHz (to be more specific, 1 GHZ boosted to 1.2), 512 MB RAM [3] "Suse 9.2 usb memory stick problem, system hangs" http://www.linuxquestions.org/questions/showthread.php? s=&forumid=4&threadid=256832 [4] Bill O. Gallmeister, "POSIX.4: Programming for the real world"
Jarek, On the previous main board I used (from MSI), the BIOS had something called "Legacy USB support" or "Legacy USB emulation" (I cannot recall the exact terminology or check it anymore--the word "legacy" was definitely part of it). When enabled it caused SuSE Linux (then 9.0) to lock up during boot as soon as it performed its USB bus scan, unless there were no devices connected. If no devices were connected and powered during booting, the lock-up would occur as soon as the first device was connected or powered on. This "legacy" mode didn't affect Windows, but disabling it allowed Linux to work fine and it then had no trouble accessing my USB devices, which include a flash RAM disk emulator, an HP printer and an MP3 player. I don't know if this is applicable to your situation, but it might be worthwhile to check out any BIOS settings related to USB devices. Randall Schulz On Saturday 27 November 2004 09:57, Jaroslaw Nozderko wrote:
Hi,
I've just purchased 9.2 Pro - it's great, but I have serious problem with mobile USB memory devices. I've sent this post to installation support but it does not cover USB problems. I also reported it as technical feedback, but got no response. However, I found similar problem reports[3].
Registering newly connected device consume a lot of CPU - mostly by hwscan and kdeinit (up to 97%) and the whole system becomes unresponsive for about 10 s. The same for cleanup when device is disconnected. This wasn't happening in 9.0 - does it have something to do with this new, smart, automatic mounting/unmounting ? Is there a way to change that ?
This is annoying, but not critical. The more serious is that the whole system usually freezes to death when I connect my 128 MB TwinMos pendrive[1] and perform some operations like file copying. Systems hangs irrecoverably - cold reset is the only solution. That's unbelievable, I've never seens anything like this in Linux before.
The first crash happened when I moved mouse cursor over PDF file in Konqueror, so I thought it has something to do with previews in tooltips or other scanning file in background for some attributes. I disabled previews in tooltips in Konqueror settings, but it didn't help - systems still freezes suddenly, mostly during file copying. This happens almost always, but mainly for this pendrive - so far, I am trying to replicate this problem using Sony MS cards with Vantec card reader - so far it works without problems.
Mobile disks have vfat filesystems (to be compatible with "leading" platform...) and there are messages in dmesg:
...
Regards, Jarek
Hi Randall,
Jarek,
On the previous main board I used (from MSI), the BIOS had something called "Legacy USB support" or "Legacy USB emulation" (I cannot recall the exact terminology or check it anymore--the word "legacy" was definitely part of it). When enabled it caused SuSE Linux (then 9.0) to lock up during boot as soon as it performed its USB bus scan, unless there were no devices connected. If no devices were connected and powered during booting, the lock-up would occur as soon as the first device was connected or powered on.
This "legacy" mode didn't affect Windows, but disabling it allowed Linux to work fine and it then had no trouble accessing my USB devices, which include a flash RAM disk emulator, an HP printer and an MP3 player.
I don't know if this is applicable to your situation, but it might be worthwhile to check out any BIOS settings related to USB devices.
thanks a lot for your help. Yes, I have "USB Legacy Support" and it was set to "Default", whatever it means. I tried both "Enabled" and "Disabled" but nothing really changed (it seems to be worse with "Enabled", however). As I said, problem seems to be 9.2-specific - in 9.0 everything works well, system doesn't hang and scanning does not lock it up. Thanks, Jarek
Jarek: You are not alone, sorry but no solution. My motherboard is ASUS A7N266 (AMD Athlon). USB worked OK in 9.0, 9.1 and original 9.2 as out of the box. I made a YOU upgrade and keyboard and mouse (PS2, not USB) freeze when I plug an USB device. Downgraded Kernel and ACPID (and legacy off) and now they dont freeze, but USB devices are not recognized. Not even the light goes on. When (and if) I make some progress I will report. Is yours the same motherboard? Perhaps I will make two partitions, one without upgrading and woring and another with regular upgrading until the problem goes away .... Bye -- Osvaldo Clua Buenos Aires
Osvaldo Clua wrote:
Jarek: You are not alone, sorry but no solution. My motherboard is ASUS A7N266 (AMD Athlon). USB worked OK in 9.0, 9.1 and original 9.2 as out of the box. I made a YOU upgrade and keyboard and mouse (PS2, not USB) freeze when I plug an USB device. Downgraded Kernel and ACPID (and legacy off) and now they dont freeze, but USB devices are not recognized. Not even the light goes on. When (and if) I make some progress I will report. Is yours the same motherboard? Perhaps I will make two partitions, one without upgrading and woring and another with regular upgrading until the problem goes away .... Bye
Give it time, using kernel.org linux-2.6.9 without subfs and I just plugged in my card reader. I also have a 120G IDE HD in an enclosure connected to a USB 2.0 port on my 9.2 x86_64 laptop serving as a backup device for all my boxes, 1 reiserfs partition and 1 swap partition online, running kernel 2.6.10-rc2-mm3-V0.7.31-9. Nov 30 00:18:31 barrabas kernel: hub 2-2:1.0: port 3, status 0101, change 0001, 12 Mb/s Nov 30 00:18:31 barrabas kernel: hub 2-2:1.0: debounce: port 3: total 100ms stable 100ms status 0x101 Nov 30 00:18:31 barrabas kernel: usb 2-2.3: new full speed USB device using address 9 Nov 30 00:18:31 barrabas kernel: usb 2-2.3: not running at top speed; connect to a high speed hub Nov 30 00:18:31 barrabas kernel: usb 2-2.3: new device strings: Mfr=0, Product=3, SerialNumber=4 Nov 30 00:18:31 barrabas kernel: usb 2-2.3: default language 0x0409 Nov 30 00:18:31 barrabas kernel: usb 2-2.3: Product: Flash Reader Nov 30 00:18:31 barrabas kernel: usb 2-2.3: SerialNumber: 52509 Nov 30 00:18:31 barrabas kernel: usb 2-2.3: hotplug Nov 30 00:18:31 barrabas kernel: usb 2-2.3: adding 2-2.3:1.0 (config #1, interface 0) Nov 30 00:18:31 barrabas kernel: usb 2-2.3:1.0: hotplug Nov 30 00:18:37 barrabas kernel: ub: sizeof ub_scsi_cmd 60 ub_dev 924 Nov 30 00:18:37 barrabas kernel: ub 2-2.3:1.0: usb_probe_interface Nov 30 00:18:37 barrabas kernel: ub 2-2.3:1.0: usb_probe_interface - got id Nov 30 00:18:38 barrabas kernel: uba: device 9 capacity nsec 256000 bsize 512 Nov 30 00:18:38 barrabas kernel: uba: was not changed Nov 30 00:18:38 barrabas kernel: uba: uba1 Nov 30 00:18:38 barrabas kernel: usbcore: registered new driver ub Nov 30 00:18:49 barrabas /etc/dev.d/block/50-hwscan.dev[11912]: new block device /block/uba Nov 30 00:18:49 barrabas /etc/dev.d/block/50-hwscan.dev[11911]: new block device /block/uba/uba1 Nov 30 00:18:49 barrabas /etc/dev.d/block/51-subfs.dev[11933]: mount block device /block/uba/uba1 Nov 30 00:18:49 barrabas /etc/dev.d/block/51-subfs.dev[11922]: mount block device /block/uba Nov 30 00:18:51 barrabas kernel: uba: was not changed barrabas:/usr/src/linux-2.6.10-rc2-mm3 # mount /dev/uba1 /data2 barrabas:/usr/src/linux-2.6.10-rc2-mm3 # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 148251276 57053688 91197588 39% / tmpfs 257280 0 257280 0% /dev/shm /dev/hdc1 118491736 48602208 69889528 42% /data1 /disk-image 204788 33796 170992 17% /DI /dev/uba1 123931 184 117349 1% /data2 Boycie:/usr/src/linux-2.6.10-rc2-mm3-V0.7.31-9 # df -h Filesystem Size Used Avail Use% Mounted on /dev/hda1 36G 28G 8.1G 78% / tmpfs 250M 4.0K 250M 1% /dev/shm /dev/uba1 114G 6.7G 107G 6% /UBA1 Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
On Tuesday 30 November 2004 01:26, Osvaldo Clua wrote:
Jarek: You are not alone, sorry but no solution. My motherboard is ASUS A7N266 (AMD Athlon). USB worked OK in 9.0, 9.1 and original 9.2 as out of the box.
JFTR: Asus A7N8X-VM/400: No Pen Drive (tm) USB Flash Hard Drive This worked in 9.1. (SuSE 9.2 LiveDVD->HD + current updates) Cheers, Leen
Hi Osvaldo,
Jarek: You are not alone, sorry but no solution. My motherboard is ASUS A7N266 (AMD Athlon). USB worked OK in 9.0, 9.1 and original 9.2 as out of the box. I made a YOU upgrade and keyboard and mouse (PS2, not USB) freeze when I plug an USB device. Downgraded Kernel and ACPID (and legacy off) and now they dont freeze, but USB devices are not recognized. Not even the light goes on. When (and if) I make some progress I will report. Is yours the same motherboard?
No, I have ASUS P3BF. Regards, Jarek
I have problem with USB Flash Drive 2.0, but not with USB 1.1. My solution was change in BIOS the IRQ of USB 2.0 from IRQ 5 to IRQ 11, that is the IRQ used by USB 1.1. Cheers Thadeu On Tuesday 30 November 2004 12:16, Leendert Meyer wrote:
Asus A7N8X-VM/400: No Pen Drive (tm) USB Flash Hard Drive
This worked in 9.1.
(SuSE 9.2 LiveDVD->HD + current updates)
Cheers,
Leen
If anyone is still interested, I've found acceptable workaround. I've submitted feedback report and decided to disable subfs, following recommended link: http://portal.suse.com/sdb/en/2004/05/hmeyer_91_revert_from_subfs.html In /etc/sysconfig/hotplug, I changed HOTPLUG_DO_MOUNT=yes HOTPLUG_MOUNT_TYPE="subfs" to HOTPLUG_DO_MOUNT=no HOTPLUG_MOUNT_TYPE="fstab" and added new entries to /etc/fstab: /dev/sda1 /media/sda1 auto noauto,user,sync 0 0 /dev/sdb1 /media/sdb1 auto noauto,user,sync 0 0 /dev/sdc1 /media/sdc1 auto noauto,user,sync 0 0 /dev/sdd1 /media/sdd1 auto noauto,user,sync 0 0 /dev/sde1 /media/sde1 auto noauto,user,sync 0 0 /dev/sdf1 /media/sdf1 auto noauto,user,sync 0 0 Restarting hotplug: # rchotplug restart disabling Hotplug done enabling Hotplug done Devices are not automatically mounted now, but it's easy to use application like kdf (KDiskFree) to do it. System does not hang - everything works without problems so far (although system is still loaded by hwscan and kdeinit when device is connected and disconnected). Regards, Jarek
participants (6)
-
Jaroslaw Nozderko -
Jose Thadeu Cavalcante -
Leendert Meyer -
Osvaldo Clua -
Randall R Schulz -
Sid Boyce