[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2019-10-03 Thread Po-Hsu Lin
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You rec

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2011-05-23 Thread Jeremy Foshee
** Tags removed: regression-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/536814 Title: Corrupted low memory at 88005df0 (5df0 phys) = e477 -- ubuntu-bugs mailing list ub

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-10-11 Thread nutznboltz
Can you please test and report if this works? memory_corruption_check_size=128K in the boot options. The default is memory_corruption_check_size=64K but it seems that's not enough for some systems. Thanks If you don't know how to set BootOptions read https://help.ubuntu.com/community/BootO

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-08 Thread pj81381
Some corrections to my previous comment. My issue might be slightly different: the computer locks up a few minutes after suspend-resume. The logs show the corrupted low memory message on resume. With 10.04, this still occurs regardless of the Nvidia driver (I had found rolling back the Nvidia drive

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-08 Thread pj81381
I think Chase is right. I've had this problem on and off while trying the nvidia 195 drivers. Rolling back to the 173 driver typically has worked for me. I've seen it on Ubuntu 9.10 and Ubuntu 10.04 LTS, AMD64. Here's my dmidecode info: # dmidecode 2.9 SMBIOS 2.4 present. 63 structures occupying

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-03 Thread Manoj Iyer
I will need the dmidecode information to see if this is happening on the same board or if this needs to be quirked by BIOS vendor. So if the originator of this bug and other who are seeing this problem will post their dmidecode information I will be able to supply a quirked kernel that you can try.

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-03 Thread Manoj Iyer
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Manoj Iyer (manjo) -- Corrupted low memory at 88005df0 (5df0 phys) = e477 https://bugs.launchpad.net/bugs/536814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-03 Thread Manoj Iyer
Can you please post BIOS details ? dmidecode information ? -- Corrupted low memory at 88005df0 (5df0 phys) = e477 https://bugs.launchpad.net/bugs/536814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mail

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-05-03 Thread James78
This problem just hit me. Ubuntu 10.04 LTS AMD64, full release. This error popped up, and now my entire kernel is corrupted. It won't even mount the root fs! -- Corrupted low memory at 88005df0 (5df0 phys) = e477 https://bugs.launchpad.net/bugs/536814 You received this bug notific

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-03-10 Thread Chase Douglas
This looks to be a pretty serious corruption. Is it possible for you to try running without the nvidia driver loaded? If you are able to reproduce without the nvidia driver we may be able to help. Otherwise the issue likely has to do with the nvidia driver, and we can't help with that because the n

[Bug 536814] Re: Corrupted low memory at ffff880000005df0 (5df0 phys) = e47700000000

2010-03-10 Thread Chase Douglas
Note that the OopsText.txt has only the last oops message, which is not the most relevant. Check WifiSyslog.txt for previous Oops messages. ** Summary changed: - BUG: unable to handle kernel paging request at 8800ad905000 + Corrupted low memory at 88005df0 (5df0 phys) = e477