Re: Kernel Memory corruption error messages
On 2009-04-16, Kushal Koolwal <kushalkoolwal@hotmail.com> wrote:
>
> Has any lately seen the following memory error messages (from dmesg) after resuming from Suspend to Ram (S3). I am using Debian Lenny with 2.6.28 kernel.
>
> ************************************************************************
> [ 179.822885] Corrupted low memory at c0007ffc (7ffc phys) = 82ea0000
> [ 179.834294] ------------[ cut here ]------------
> [ 179.834310] WARNING: at arch/x86/kernel/setup.c:718 check_for_bios_corruption+0xa0/0xaa()
> [ 179.834326] Memory corruption detected in low memory
> [ 179.845435] Modules linked in: snd_pcm_oss snd_mixer_oss dme1737 hwmon_vid lm90 snd_cs5535audio snd_ac97_codec pcspkr ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc evdev
> [ 179.845505] Pid: 0, comm: swapper Not tainted 2.6.28-1-epm15-test1 #1
> [ 179.845519] Call Trace:
> [ 179.845904] [] warn_slowpath+0x5a/0x78
> [ 179.845927] [] handle_fasteoi_irq+0x8a/0xbc
> [ 179.845947] [] do_IRQ+0x5a/0x6c
> [ 179.845966] [] common_interrupt+0x23/0x28
> [ 179.845988] [] vprintk+0x22b/0x24a
> [ 179.846008] [] vprintk+0x240/0x24a
> [ 179.846029] [] read_tsc+0x6/0x22
> [ 179.846053] [] getnstimeofday+0x4a/0xc5
> [ 179.846078] [] mfgpt_start_timer+0x4b/0x5b
> [ 179.846103] [] printk+0xe/0x11
> [ 179.846124] [] check_for_bios_corruption+0xa0/0xaa
> [ 179.846146] [] periodic_check_for_corruption+0x0/0x28
> [ 179.846169] [] periodic_check_for_corruption+0x5/0x28
> [ 179.846194] [] run_timer_softirq+0x12a/0x18e
> [ 179.846214] [] __do_softirq+0x4a/0xbc
> [ 179.846232] [] do_softirq+0x22/0x26
> [ 179.846249] [] irq_exit+0x25/0x5f
> [ 179.846267] [] do_IRQ+0x5a/0x6c
> [ 179.846285] [] common_interrupt+0x23/0x28
> [ 179.846308] [] default_idle+0x25/0x38
> [ 179.846326] [] cpu_idle+0x41/0x6f
> [ 179.846339] ---[ end trace 5f499d87af471ce2 ]---
> debian:~#
> ************************************************************************
> The system does seem to work fine even after the kernel panic but I am little bit nervous that in the long run it might hurt.
>
> Also does anybody know how to debug this issue like -
> - Is it a module that is causing the problem or
It seems the sound related modules cause the problem, like snd_pcm_oss.
Try not to load them at startup, and then you load them by hand one bye one,
and you can find which module causes this issue.
> - Is it a core kernel issue or
I don't thinks so.
> - A Hardware/BIOS issue.
Only if you upgrade your BIOS recently.
>
> I also filed a bug report few days back:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523964
>
> Kushal Koolwal
>
> I do blog at http://blogs.koolwal.net/
> _________________________________________________________________
> Windows Live™: Life without walls.
> http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1b_explore_042009
>
Reply to: