Hi *,
I had a problem with 2.3.99-pre9-2 (.config available at request). The
error is quite verbose, so I hope it can help. The story: I put a
floopy in, there was some read error. So I removed the floppy, and
forgot to put a new one. The floppy is mounted by autofs:
floppy -fstype=vfat,owner,uid=500,gid=500 :/dev/fd0
After the entry had expired, I tried to do shell completion
on /rem/floppy/st[TAB]:
hazel automount[411]: attempting to mount entry /rem/floppy
hazel kernel: Trying to lock fdc while usage count=0
hazel kernel: floppy0: fractionary current count b=0 s=0
hazel kernel: addr=0, length=0
hazel kernel: st=0 ast=0 mse=18 msi=18
hazel kernel: ssize=1 SIZECODE=2
hazel kernel: command=e6 SECTOR=1 HEAD=0, TRACK=0
hazel kernel: buffer drive=0
hazel kernel: buffer track=-1
hazel kernel: buffer_min=0
hazel kernel: buffer_max=0
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel automount[3261]: >> mount: /dev/fd0 is not a valid block device
hazel automount[3261]: mount(generic): failed to mount /dev/fd0 (type vfat) on /rem/floppy
hazel automount[411]: attempting to mount entry /rem/floppy
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel automount[3263]: >> mount: /dev/fd0 is not a valid block device
hazel automount[3263]: mount(generic): failed to mount /dev/fd0 (type vfat) on /rem/floppy
Then, I put a floppy in, tried again:
hazel automount[411]: attempting to mount entry /rem/floppy
hazel kernel: Trying to lock fdc while usage count=0
hazel kernel: warning: usage count=0, CURRENT=c02c4690 exiting
hazel kernel: sect=0 cmd=0
hazel kernel: floppy0: fractionary current count b=0 s=0
hazel kernel: addr=0, length=0
hazel kernel: st=0 ast=0 mse=18 msi=18
hazel kernel: ssize=1 SIZECODE=2
hazel kernel: command=e6 SECTOR=1 HEAD=0, TRACK=0
hazel kernel: buffer drive=0
hazel kernel: buffer track=-1
hazel kernel: buffer_min=0
hazel kernel: buffer_max=0
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel kernel: floppy0: FDC access conflict!
hazel kernel: floppy0: Floppy io-port 0x03f0 in use
hazel kernel: motor off timer 0 still active
hazel kernel: Trying to lock fdc while usage count=0
hazel kernel: warning: usage count=0, CURRENT=c02c4690 exiting
hazel kernel: sect=0 cmd=0
hazel kernel: floppy0: Floppy io-port 0x03f0 in use
hazel kernel: motor off timer 0 still active
hazel kernel:
hazel kernel: floppy driver state
hazel kernel: -------------------
hazel kernel: now=98229 last interrupt=96754 diff=1475 last called handler=c0170500
hazel kernel: timeout_message=redo fd request
hazel kernel: last output bytes:
hazel kernel: 3 80 96746
hazel kernel: c1 90 96746
hazel kernel: 10 90 96746
hazel kernel: 7 80 96746
hazel kernel: 0 90 96746
hazel kernel: 8 81 96746
hazel kernel: f 80 96746
hazel kernel: 0 90 96746
hazel kernel: 1 91 96746
hazel kernel: 8 81 96747
hazel kernel: 4 80 96751
hazel kernel: 0 90 96751
hazel kernel: f 80 96751
hazel kernel: 0 90 96751
hazel kernel: 0 91 96751
hazel kernel: 8 81 96752
hazel kernel: f 80 96754
hazel kernel: 0 90 96754
hazel kernel: 1 91 96754
hazel kernel: 8 81 96754
hazel kernel: last result at 96754
hazel kernel: last redo_fd_request at 97929
hazel kernel: 20 1
hazel kernel: status=0
hazel kernel: fdc_busy=0
hazel kernel: DEVICE_INTR=c0170cd0
hazel kernel: cont=c026baec
hazel kernel: CURRENT=c02c4690
hazel kernel: command_status=-1
hazel kernel:
hazel kernel: floppy0: floppy timeout called
hazel kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
hazel kernel: floppy0: FDC access conflict!
hazel kernel: bad fdc value
hazel kernel: floppy0: Floppy io-port 0x03f0 in use
hazel kernel: motor off timer 0 still active
hazel kernel: floppy timer still active:lock fdc
hazel automount[3274]: >> mount: wrong fs type, bad option, bad superblock on /dev/fd0,
hazel automount[3274]: >> or too many mounted file systems
hazel automount[3274]: mount(generic): failed to mount /dev/fd0 (type vfat) on /rem/floppy
And this repeats various times.... the floppy is not usable anymore.
Restarting automount didn't help. Rebooting did help :-), so the
floppy was good and readable. The problem is quite well reproducible:
put a floppy, read from it, wait for the entry expire, remove the
floppy, try to access (I think completion is doing a readdir()), and
look at the problem. It may be hardware, but it's a quite new
behaviour. Never seen it before (my previous kernel was a 99pre4), but
it is possible it's just an old problem that I happened to trigger
only now.
Hey, this oddity apart, pre9-2 works like a charm for me. Good work!
Romano
-- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:14 EST