2.2.14 USB problem

2.2.14 USB problem

[Roeland Th. Jansen]

I recently bought a fujifilm finepix 1300. Cool stuff and works with
minimal effort with USB.

However, after a few days, I was not able tomount the usb mass storage
of the cam anymore. It reposted at mount :

mount: /dev/sdb1 is not a valid block device

checked the process table and saw several usb processes in Z state. I
killed their paret and that went away. still usb-storage was loaded.
Tried to remove it -- oops process in D state. Note that khubd also was
in a Z state. All was not recoverable so a restart was needed.


USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         8  0.0  0.0     0    0 ?        Z    Nov16   0:00 [khubd <defunct>]
root     18297  0.0  0.0  1568  496 ?        D    11:13   0:00 rmmod usb-storage

when going singel user I saw :

pci_pool_destroy 00:07.2/uhci_desc e851ec000 busy
                                   d5d4c0000 busy


also in the logs stuff :

kernel: usbdevfs: USBDEVFS_CONTROL failed dev 29 rqt 128 rq 6 len 4 ret -6 
kernel: usb-uhci.c: ENXIO 80001d80, flags 0, urb c94880c0, burb c9488dc0 
kernel: scsi3 : SCSI emulation for USB Mass Storage devices
kernel:   Vendor: Fujifilm  Model: FinePix 1400Zoom  Rev: 1000
kernel:   Type:   Direct-Access ANSI SCSI revision: 02
kernel: Attached scsi removable disk sdc at scsi3, channel 0, id 0, lun 0
kernel: usb-uhci.c: ENXIO 80001d80, flags 0, urb c9488dc0, burb c94880c0
last message repeated 2 times
kernel: SCSI device sdc: 16000 512-byte hdwr sectors (8 MB)
kernel: sdc: Write Protect is off
kernel:  sdc: sdc1


note that the initial sdb1 now all over sudden was changed into sdc1.

hoe somebody has some use for this info.

-- 
Grobbebol's Home                        |  Don't give in to spammers.   -o)
http://www.xs4all.nl/~bengel            | Use your real e-mail address   /\
Linux 2.4.14 (noapic) SMP 466MHz/768 MB |        on Usenet.             _\_v  

Re: 2.2.14 USB problem

[Greg KH]

On Wed, Dec 05, 2001 at 01:35:51PM +0000, Roeland Th. Jansen wrote:
> 
> hoe somebody has some use for this info.

You might want to let the driver's author know about this.  His email
address is in the usb-storage.c and the MAINTAINER files.

thanks,

greg k-h

2.4.14 USB oops

[Roeland Th. Jansen]

ksymoops 2.4.2 on i686 2.4.14.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.14/ (default)
     -m /boot/System.map-2.4.14 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Oops: 0000
CPU:    0
EIP:    0010:[<f0a79652>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000   ebx: e4233000   ecx: 00000000   edx: 00000010
esi: dfd97fcc   edi: dfd97fec   ebp: f0a85497   esp: dfd97f7c
ds: 0018   es: 0018   ss: 0018
Process usb-storage-0 (pid: 2877, stackpage=dfd97000)
Stack: e4233000 f0a85711 dfd97ff0 e4233004 c02f7747 00000246 00000024
e4233000
       f0a79a24 e4233000 dfd97fcc 00000024 f0a85720 00000100 e006fdc8
e4233000
       e4233000 e4233194 e4233180 00000001 02028000 0000001f 696a7546
6d6c6966
Call Trace: [<f0a85711>] [<f0a79a24>] [<f0a85720>] [<c0105594>]
[<f0a8d3ac>]
Code: 0f b7 80 cc 00 00 00 66 c1 e8 0c 0c 30 88 46 20 8b 43 18 8a

>>EIP; f0a79652 <[usb-storage]fill_inquiry_response+e2/274>   <=====
Trace; f0a85710 <[usb-storage]__module_usb_device_size+660/828e>
Trace; f0a79a24 <[usb-storage]usb_stor_control_thread+240/3fc>
Trace; f0a85720 <[usb-storage]__module_usb_device_size+670/828e>
Trace; c0105594 <kernel_thread+28/38>
Trace; f0a8d3ac <[usb-storage]usb_stor_sense_notready+0/14>
Code;  f0a79652 <[usb-storage]fill_inquiry_response+e2/274>
00000000 <_EIP>:
Code;  f0a79652 <[usb-storage]fill_inquiry_response+e2/274>   <=====
   0:   0f b7 80 cc 00 00 00      movzwl 0xcc(%eax),%eax   <=====
Code;  f0a79658 <[usb-storage]fill_inquiry_response+e8/274>
   7:   66 c1 e8 0c               shr    $0xc,%ax
Code;  f0a7965c <[usb-storage]fill_inquiry_response+ec/274>
   b:   0c 30                     or     $0x30,%al
Code;  f0a7965e <[usb-storage]fill_inquiry_response+ee/274>
   d:   88 46 20                  mov    %al,0x20(%esi)
Code;  f0a79662 <[usb-storage]fill_inquiry_response+f2/274>
  10:   8b 43 18                  mov    0x18(%ebx),%eax
Code;  f0a79664 <[usb-storage]fill_inquiry_response+f4/274>
  13:   8a 00                     mov    (%eax),%al


1 warning issued.  Results may not be reliable.
-- 
Grobbebol's Home                        |  Don't give in to spammers.   -o)
http://www.xs4all.nl/~bengel            | Use your real e-mail address   /\
Linux 2.4.14 (noapic) SMP 466MHz/768 MB |        on Usenet.             _\_v