https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #67 from Theodore Tso <tytso@xxxxxxx> 2011-04-23 19:31:45 --- Just because *I* don't like desktops that initiate I/O at random times when I don't request doesn't mean that other users shouldn't use it. It's just that if we're talking about making a reliable test case, it's much better if it doesn't depend on random I/O initiated by a desktop. The test case should do whatever I/O is needed, so that it is complete reproducible, even by people who don't necessarily use the same desktop as you. Thinking about this some more, *very* recently (as in the most recent merge window) there have been some hanges recently to avoid deadlock in ext3/4 on when freezing and unfreezing file systems for snapshots, and that code path is also used on suspend/resume. Those changes came in way after 2.6.36-rc1, so yes, if they are also causing some issues with 2.6.39-rc2+ systems, it's very likely that there are different bugs involved. Which is why I insist on getting full and accurate OOPS logs, so we can see if they are different crashes that happen to have apparently the same symptoms caused by the same event (i.e. USB keys getting rudely yanked out of the system). By the way, for years and years and years USB disks just didn't work at all across suspend/reusmes. Which is why I have scripts into my suspend/resume framework to automatically unmount removeable disks at suspend-time.... -- 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
