[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Killer floppy



Dale Scheetz wrote:
> 
> I appear to have a floppy that is destructive to my system. When I try to
> mount it, I get the following:
> 
> Unable to handle kernel paging request at virtual address d0c2af14
> current->tss.cr3 = 00fbc000, %cr3 = 00fbc000
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<0015f359>]
> EFLAGS: 00010202
> eax: 10c2af10   ebx: 00000010   ecx: 00003a00   edx: 021e5218
> esi: 001c387c   edi: 02373000   ebp: 10c2af10   esp: 00fbde3c
> ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
> Process mount (pid: 191, process nr: 28, stackpage=00fbd000)
> Stack: 001c387c 00000200 001aafd8 08050200 001bafd8 00000030 00000000
> 002b4f00
>        002bfe98 002b4f00 002bfe98 00000006 021e3001 002bfe98 00000001
> 00000000
>        00002074 021e5218 00000000 00000200 00000000 00000006 002b88d4
> 0000ef32
> Call Trace: [<0012c196>] [<0012c204>] [<0012c3e7>] [<00161033>]
> [<00128a29>] [<00128e6b>] [<001293a0>]
>        [<0010ab25>]
> Code: 8b 4d 04 81 f9 72 72 41 61 74 10 51 68 8f 9a 19 00 e8 9d 52
> /usr/local/bin/qm: line 4:   191 Segmentation fault      mount -t msdos
> /dev/fd0 /floppy
> 
> At this point, until I reboot, I have lost the floppy drive. If I try to
> unmount it, I am told it is busy. If I try to mount it, I am told no such
> device on /dev/fd0.
> 
> Any idea of how to protect from this occurance (aside from throwing the
> floppy away)?

Notice how similar this is to when you remove a floppy that's mounted...
maybe a real error caused mount to get to a halfway point.  Have you
tried to dd the floppy?  I'd expect the same kernel error, and I'd think
you could repeat it without rebooting.

							- Tom


Reply to: