On Mon, Apr 13, 2009 at 03:30:53PM -0700, Kushal Koolwal wrote:
> Package: linux-image-2.6.28-1-486
> Version: 2.6.28-1
> Severity: normal
> 
> I get the following memory corruption error message after my system wakes up 
> from Suspend-to-ram. This happens from console and from X too.
> I have tried to use the following methods to suspend by computer and I get 
> the error messages with all of them:
> echo mem > /sys/power/state
> s2ram -f
> pm-hibernate
> 
> [  239.816522] ------------[ cut here ]------------
> [  239.816538] WARNING: at arch/x86/kernel/setup.c:718 
> check_for_bios_corruption+0xa0/0xaa()
> [  239.816554] Memory corruption detected in low memory
> [  239.816566] Modules linked in: pcspkr snd_cs5535audio snd_ac97_codec 
> ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc evdev
> [  239.816617] Pid: 4351, comm: grep Not tainted 2.6.28-1-acpi #1
> [  239.816630] Call Trace:
> [  239.816654]  [<c0119312>] warn_slowpath+0x5a/0x78
> [  239.816678]  [<c02cf705>] vt_console_print+0x0/0x27f
> [  239.816700]  [<c0119551>] __call_console_drivers+0x34/0x40
> [  239.816724]  [<c0107968>] read_tsc+0x6/0x22
> [  239.816747]  [<c012d7af>] getnstimeofday+0x4a/0xc5
> [  239.816769]  [<c03de252>] printk+0xe/0x11
> [  239.816789]  [<c0106241>] check_for_bios_corruption+0xa0/0xaa
> [  239.816812]  [<c010624b>] periodic_check_for_corruption+0x0/0x28
> [  239.816834]  [<c0106250>] periodic_check_for_corruption+0x5/0x28
> [  239.816858]  [<c012038f>] run_timer_softirq+0x12a/0x18e
> [  239.816878]  [<c011cf0d>] __do_softirq+0x4a/0xbc
> [  239.816896]  [<c011cfa1>] do_softirq+0x22/0x26
> [  239.816913]  [<c011d0ba>] irq_exit+0x25/0x5f
> [  239.816931]  [<c010534e>] do_IRQ+0x5a/0x6c
> [  239.816949]  [<c0104377>] common_interrupt+0x23/0x28
> [  239.816972]  [<c03d0000>] sta_apply_parameters+0x12e/0x14e
> [  239.816987] ---[ end trace 1c9338d4c6e94f6c ]---
> [  362.200042] Hangcheck: hangcheck value past margin!
> 
> I am using software suspend method in kernel (CONFIG_SUSPEND=y). Please let 
> me know if you need more information on this.

Does this error still occur with the 2.6.30 kernel from unstable?

Cheers,
        Moritz



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to