For what it's worth, I seem to have found a way to work around this bug. Here are the details.
I have an MSI (Micro Star) MS-6712 (KT4V) motherboard. It was running version 2.6.32-35 of package linux-image-2.6.32-5-686 in squeeze. I wanted to upgrade its RAM from about half a gigabyte on two sticks, to three gigabytes on three sticks. I bought three used and unmatched one gigabyte memory sticks, pulled out the old small ones, and put in the new. After rebooting, this Debian bug (#582487) happened. Then I tried upgrading linux to the latest version in stable (squeeze), 2.6.32-39. That failed too. Then I upgraded linux to the version in debian-backports, 2.6.39+35. Still no luck. Then I pulled out the memory stick nearest to the CPU. That worked. I rebooted twice more, and saw no more stack traces in dmesg or /var/log/messages. I suspect bad or mismatched RAM caused the error, but I'm not sure. ~K -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
