tags 523964 moreinfo stop On Fri, 29 Jan 2010, Kushal Koolwal wrote:
> > Hi Moritz, > > Sorry for not seeing your message earlier. Actually I have not been checking > this email address any more but just happen to log in. > > > Does this error still occur with the 2.6.30 kernel from unstable? > I had to disable the following option in 2.6.28-1-486 in order to get rid of > the error: > # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set egrep CONFIG_X86_CHECK_BIOS_CORRUPTION /boot/config-2.6.* /boot/config-2.6.28-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.30-2-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.31-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set /boot/config-2.6.32-1-amd64:# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set seems to have been never set. > Let me know if you need more information. I have bookmarked the BUG > report page so I will know if there is any new reply from you. yes please boot 2.6.32 linux image from squeeze / unstable (preferably latest version in unstable) and tell us if you can still repdouce mem corruption with it. squeeze will be released with 2.6.32 so it's a worthwile exercise to see if acpi improved since 2.6.28 for you. thanks. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
