Strange USB issue on 6.0.4 : kernel:[1202001.893158] Oops: 0010 [#5] SMP
I have a HP external USB attached disk plugged into a USB port on my system.
Periodically, every eight or twelve hours or so, and without any real pattern
or trigger cause, I see the following message :
root@aster:~#
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893158] Oops: 0010 [#5] SMP
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893165] last sysfs file:
/sys/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1.3/3-1.3:1.0/host8/target8:0:0/8:0:0:0/block/sdc/uevent
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893435] Stack:
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893469] Call Trace:
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893735] Code: Bad RIP value.
Message from syslogd@aster at Mar 26 15:23:02 ...
kernel:[1202001.893754] CR2: 000000fd00000019
The external USB disk is no longer mounted and any attemp to read it ( with a
simple ls ) results in IO errors.
I unplug it.
Wait 30 secs or so.
Plug it back in and then I see in /dev/sd? thus :
root@aster:~# ls -laptr /dev/sd*
brw-rw---- 1 root disk 8, 16 Mar 12 17:29 /dev/sdb
brw-rw---- 1 root disk 8, 0 Mar 12 17:29 /dev/sda
brw-rw---- 1 root disk 8, 17 Mar 12 17:29 /dev/sdb1
brw-rw---- 1 root disk 8, 3 Mar 12 17:29 /dev/sda3
brw-rw---- 1 root disk 8, 2 Mar 12 17:29 /dev/sda2
brw-rw---- 1 root disk 8, 1 Mar 12 17:29 /dev/sda1
brw-rw---- 1 root disk 8, 4 Mar 12 17:29 /dev/sda4
brw-rw---- 1 root floppy 8, 33 Mar 12 17:29 /dev/sdc1
brw-rw---- 1 root floppy 8, 32 Mar 12 17:29 /dev/sdc
brw-rw---- 1 root floppy 8, 96 Mar 27 21:53 /dev/sdg
brw-rw---- 1 root floppy 8, 97 Mar 27 21:53 /dev/sdg1
The last entry there /dev/sdg1 would be my external HP disk which I can now
mount :
root@aster:~# /bin/mount -v -t ext4 -o rw /dev/sdg1 /hp
Now the filesystem is usable with no real issues.
I have to repeat this process daily, once or twice, and the message on the
console are generally the same. More or less.
How would I go about debugging this issue if it is caused by the USB driver ?
Thank you in advance for any insights.
Dennis
--
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke | Solaris and Linux and Open Source |
| dclarke@blastwave.org | Respect for open standards. |
+-------------------------+-----------------------------------+
Reply to: