Lately I've started to wonder if there isn't more than one bug at work here. The main barrier to my getting information about this is that I can't save any files after the problem pops up. The logs just stop and then start up again when I restart the machine.
Have you noticed any strange activity by any of your programs BEFORE your hard-drive goes read-only? Also, what other programs does top show eating up your CPU, besides dd, klogd and ksoftirqd? Mostly, the three procs that are always there are usually accompanied by firefox, though at least once I saw evince instead. Lately the pattern is that firefox suddenly starts thrashing, hopping from one core to the other (I have a Core 2 Duo in this machine), and then after it stops, I get the read-only file system and the deadlock with dd/klogd/ksoftirqd and company. I, sadly enough, don't have any USB keys or anything like that, but it recently occurred to me that if I had one mounted, I could save the output of dmesg or other programs on that, and sift through it for clues later. I just have to be sure that the programs I need (mount, umount, sudo, dmesg, cp, df...) have been used recently, so they'll still be paged into memory instead of on the hard disk where you only get input/output errors. Let me know if you find out anything. I'd love to get to the bottom of this too. ~jdacronym -- Hardy: ksoftirqd, dd, klogd use 100% CPU, Disk https://bugs.launchpad.net/bugs/368324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
