FLOPPY SEGFAULT !?!?

Kernel Related Emails (kernel@penguin.linuxhardware.org)
Tue, 27 Jun 2000 01:30:09 -0400 (EDT)


Well here it is the kernel error that I'd never thought I'd
see. Everytime I umount /dev/fd0 I segfault? Where's the error
here? Here's the stack trace:

invalid operand: 0000
CPU: 1
EIP: 0010:[<c013866c>]
EFLAGS: 00010286
eax: 0000001d ebx: cb7611a0 ecx: 00000097 edx: 00000001
esi: c13671bc edi: 00000000 ebp: c1367124 esp: c191fedc
ds: 0018 es: 0018 ss: 0018
Process umount (pid: 167, stackpage=c191f000)
Stack: c0238a04 c0238dda 000005b3 c1367124 c13671bc 00000000 c1ab0a24
c191ff3c
cb7611a0 c0128226 c1367124 c1ab0960 c191ff3c 00000000 c191ff98
c014c776
c1ab0a24 cfb62c40 c191ff3c c014c894 c191ff3c cfb62c00 cfb62c00
00000000
Call Trace: [<c0238a04>] [<c0238dda>] [<c0128226>] [<c014c776>]
[<c014c894>] [<c013c19d>] [<c013c559>]
[<c013c6b3>] [<c0127687>] [<c013c76c>] [<c010b428>]
Code: 0f 0b 83 c4 0c 8d 76 00 8b 4b 28 89 4c 24 10 53 e8 cf fe ff
Segmentation fault

Running 2.4.0-test2-ac1 on SMP i840 motherboard.

Thanks,
Kris Kersey

-
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/