https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #60 from Theodore Tso <tytso@xxxxxxx> 2011-04-22 10:13:05 --- One of the problems which has made this hard to debug is (a) the kernel oops/panic messages are inconsistent (they're not all the same, and some of them don't have anything file system related at all), and (b) mant of them are incomplete. Note that we need more than just the stack traces, too. We also need the beginning of the oops message, complete with the IP/RIP information. At least one of these systems looks like it's using some kind of network console? Can you set up a simple serial console, and then do some experiments where you yank out the USB drive, and tell us whether it happens reliably 100% of the time? 50% of the time? 10% of the time? If you run sync first and the system is idle, does that make it more or less likely to happen? If you then start writing to the now-disappeared file system with a single command, does it crash right away? Does it crash 30 seconds later? I've done a simple experiment where I've mounted a USB stick, written to it, typed sync, but then without typing umount, yanked the stick out, and then tried writing to the file system. It didn't crash for me. So some explicit instructions of what you can do that causes reliable crashes would be very useful, and then if you can set up a serial console so we can get complete and reliably crash logs, that would also be very useful. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
