This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Unfortunately messages are still here:
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
root=UUID=eae7f0af-7856-4a0b-ba78-55d294270757
ro quiet splash memory_corruption_check_size=128K
[ 361.000244] Corrupted low memory at c0007bd8 (7bd8 phys) = 0033
[ 361
Thanks for respond. Could you do me the small favor of setting
memory_corruption_check_size=128K then suspending/resuming and seeing if
the "Corrupted low memory at" messages are still there? Thanks again.
--
kernel OOPs when working after resume from suspend
https://bugs.launchpad.net/bugs/465
Hi! As i wrote earlier my suspend forks fine starting from 2.6.34, and also
works with maverik kernel.
Anyway, thanks for useful info about low memory corruption checks.
So the workaround for lucid users would be install backported maverik kernel
from kenel-ppa. Should i close this bug now?
--
If your suspend and resume is still broken, 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 r
Yay! With kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.34-lucid/ installed on lucid my laptop can survive
suspend to ram :
And in dmesg again after resume appears errors abut low memory corruption:
[12601.000228] Corrupted low memory at c0007bd8 (7bd8 phys) = 0033
[12601
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
kernel OOPs when working after resume from suspend
https://bugs.launchpad.net/bugs/465339
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hi! Thanks for your attention to this bug!
Unfortunately this happens also with 2.6.32 mainline.
It all started with 2.6.30 mainline packages. Last working mainline packages
were 2.6.29.
In 2.6.29 mainline and stock jaunty kernel there was warning about low memory
corruption just after resume fr
Please, can you check with 2.6.32 kernel which is placed
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/?
If the issue remains, could you run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It
will automatically gather and attach updated de
** Attachment added: "Full dmesg cut from /var/log/messages after reboot"
http://launchpadlibrarian.net/34713011/dmesg.txt
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/34713012/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/
10 matches
Mail list logo
