| Summary: | kernel panic writing to floppy | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Mikael Eklund <miek> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.3-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Mikael Eklund
1999-10-29 15:00:00 UTC
State Changed From-To: open->suspended This is no longer a problem for since block devices now act as char devices. I am not sure however, if this problem would also manifest itself if the faulty floppy was mounted as a filesystem, therefore the "suspend" state. Using 3.4-RELEASE: The dd command using the char device (rfd0) works fine (no panic), but using the block device (fd0) panics. On to the open->suspend rationale: Mounting a writeable floppy, pulling the disk, write-protecting it, replacing it, and then writing to the FS results in a console message complaining about writing to a write-protected media (expected), but when the FS is unmounted, a kernel panic occurs. Jul 17 19:02:33 styx /kernel: panic: vinvalbuf: dirty bufs Jul 17 19:02:33 styx /kernel: Jul 17 19:02:33 styx /kernel: syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up [ 1 1 1... may be replaced by 2 2 2...] State Changed From-To: suspended->closed So then we're back to a known problem. Duplicate of kern/11808 and kern/10870 . |