The kernel is trying to access the primary (block 3) and secondary
(block 22) IDE interface, then trying to access the floppy. And it
thinks there is something in the floppy drive. You have some user code
that is trying to access these devices, the kernel will not do it on
its own. Are you running automount or something similar?
>VFS: Disk change detected on device fd(2,0)
>end_request: I/O error, dev 02:00 (floppy), sector 0
>VFS: Disk change detected on device fd(2,0)
>end_request: I/O error, dev 02:00 (floppy), sector 0
>VFS: Disk change detected on device fd(2,0)
>end_request: I/O error, dev 02:00 (floppy), sector 0
>VFS: Disk change detected on device fd(2,0)
>end_request: I/O error, dev 02:00 (floppy), sector 0
>
>And no, there's nothing in the floppy drive. I don't think we've ever
>actually used it...
The kernel is getting interrupts from the floppy. If there is nothing
loaded, you probably have a hardware or cable problem.
-
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/