Commit 6ad696d2cf535772dff659298ec7e7260e344595 breaks my SD card reader [197b:2381]

Matt,

(...)

ok, I am desperate. Maybe its time to just throw out any information I can think of right now, hoping for some educated guess ;).

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.

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.

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.

No, all tests after fresh reboot.

Ok, later ;).

Thx,

Stephan

Stephan Sürken <absurd at olurdix.de>