Matt, On Wed, 2010-04-28 at 23:38 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=15836 (...) > this one definitely looks strange. ok, I am desperate. Maybe its time to just throw out any information I can think of right now, hoping for some educated guess ;). > Have you tried running other diagnostic tools on you SD card, e.g. fsck? Actually, s.th. like "mkfs;fsck --force" was my initial test before I switched to badblocks. As for bad media, the laptop is my working horse. I work on it every day; when I work on it, the sd card is in use. I had no issues with it whatsoever until I switched to 2.6.32, and I continue to have no issues (sticking to a 2.6.30 kernel) with the very same card. And yes, after I found the kernel upgrade broke it, I tested with a different sd card with the same results. So it's definitely not a media problem. > How about on your hard disks or other mass storage devices? Ok, good point (although I booted from the hard disk for the tests). I run the same badblocks test (with a "bad" kernel) on a hard disk partition and on an usb stick without issues. So it's not a general mass storage problem. > Is it always the same block that's reported as bad? Ok, good point. I noted that they seem to be different, but I did not care much yet. Now I have retested on a bad kernel (actually stock 2.6.33.2), running the test 5 times (0-4) in a row, and this three times on three bootups; the number is the first found bad blocks: Boot 0: 0 14144 1-4 64 Boot 1 (warm boot): 0 64 1-4 64 Boot 2 (cold boot): 0 140 1-4 76 Fwiw, read-only badblock tests always work fine. > Were you doing any suspend/hibernation during these tests? No, all tests after fresh reboot. > It might also be an idea to turn on > CONFIG_DEBUG_PAGEALLOC and run badblocks again. > > If you turn off CONFIG_HOTPLUG and CONFIG_HIBERNATION on a recent kernel > does it work then? Ok, later ;). Thx, Stephan -- Stephan Sürken <absurd at olurdix.de> -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
