WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0()

[vnieto]

Before a restart with kerneloops

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
DistroRelease: Ubuntu 9.04
Failure: oops
MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcCmdLine: root=UUID=38814f2f-9f17-43c2-8b1b-73b474164ed4 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0()

[Antonio Sánchez (antoniosanchez)]

This also affects me but under i386 architecture.

[Paul Dufresne (paulduf)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
Is this reproducible?
If so, what specific steps should we take to recreate this bug?
Is this only on resume (after suspend-to-ram or suspend-to-disk)?
How does your BIOS identify itself (mark and version)?

According to:
http://lkml.indiana.edu/hypermail/linux/kernel/0808.3/1869.html
this check was added to check for BIOS corruption, but I am unsure how much abnormal it is on a resume.

Just a note about an other bug with similar warning:
https://bugs.launchpad.net/bugs/350192

[Antonio Sánchez (antoniosanchez)]

Is this reproducible?

Yes

If so, what specific steps should we take to recreate this bug?

1. Start system
2. Suspend system
3. Restore system
4. Enter your user password
5. Kernel Failure windows popup show next message:

Kernel failure message 1:
------------[ cut here ]------------
WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xc8/0xd0()
Memory corruption detected in low memory
Modules linked in: aes_i586 aes_generic iptable_mangle xt_DSCP ip_tables xt_owner xt_dscp x_tables binfmt_misc i915 drm bridge stp bnep video output input_polldev quota_v2 lp arc4 snd_hda_intel ecb snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss ath5k snd_seq_midi mac80211 snd_rawmidi iTCO_wdt led_class snd_seq_midi_event iTCO_vendor_support snd_seq cfg80211 snd_timer snd_seq_device intel_agp agpgart snd soundcore snd_page_alloc pcspkr ppdev parport_pc parport usbhid r8169 mii fbcon tileblit font bitblit softcursor
Pid: 0, comm: swapper Not tainted 2.6.28-11-generic #35-Ubuntu
Call Trace:
 [<c0139a60>] warn_slowpath+0x60/0x80
 [<c013a2a9>] ? release_console_sem+0x1c9/0x200
 [<c0128e90>] ? __wake_up_common+0x40/0x70
 [<c0500ab1>] ? printk+0x18/0x1f
 [<c01079b8>] check_for_bios_corruption+0xc8/0xd0
 [<c01079c8>] periodic_check_for_corruption+0x8/0x30
 [<c0143aa0>] run_timer_softirq+0x130/0x200
 [<c01079c0>] ? periodic_check_for_corruption+0x0/0x30
 [<c01079c0>] ? periodic_check_for_corruption+0x0/0x30
 [<c013f147>] __do_softirq+0x97/0x170
 [<c0152c36>] ? hrtimer_interrupt+0x186/0x1b0
 [<c0152a89>] ? ktime_get+0x19/0x40
 [<c013f27d>] do_softirq+0x5d/0x60
 [<c013f3f5>] irq_exit+0x55/0x90
 [<c011a0ab>] smp_apic_timer_interrupt+0x5b/0x90
 [<c0105318>] apic_timer_interrupt+0x28/0x30
 [<c010b002>] ? mwait_idle+0x42/0x50
 [<c010285d>] cpu_idle+0x6d/0xd0
 [<c04f11ee>] rest_init+0x4e/0x60
---[ end trace 61c3c3f62b33e069 ]---

Is this only on resume (after suspend-to-ram or suspend-to-disk)?

By now, I only have this issue after suspend-to-disk. I'll try to reproduce it under other situations.

How does your BIOS identify itself (mark and version)?

Award Modular BIOS v6.00PG

[Antonio Sánchez (antoniosanchez)]

I've just done a dist-upgrade in Jaunty and now I can't reproduce this issue.

I think this issue is solved now.

[Antonio Sánchez (antoniosanchez)]

We can't reproduce this issue with latest package upgrade.

[donggonghua (gonghua-dong)]

I'm having the same problem, I just did a apt-get upgrade and after reboot, this error msg pops up.

I'm using a Hewlett-Packard nc6400 x86/x64, and I'm using i386 build.

I'm getting this Kernel Failure every time i start the computer.

Kernel failure message 1:
------------[ cut here ]------------
WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xc8/0xd0()
Memory corruption detected in low memory
Modules linked in: binfmt_misc radeon drm bridge stp bnep vboxnetflt vboxdrv input_polldev lp snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi snd_rawmidi iwl3945 snd_seq_midi_event snd_seq snd_timer snd_seq_device pcmcia leds_hp_disk mac80211 iTCO_wdt iTCO_vendor_support snd ppdev video tifm_7xx1 sdhci_pci led_class soundcore psmouse intel_agp parport_pc parport tpm_infineon tpm joydev yenta_socket rsrc_nonstatic pcmcia_core output tifm_core cfg80211 sdhci snd_page_alloc pcspkr serio_raw agpgart tpm_bios lis3lv02d usbhid tg3 fbcon tileblit font bitblit softcursor
Pid: 0, comm: swapper Not tainted 2.6.28-11-generic #42-Ubuntu
Call Trace:
 [<c0139ab0>] warn_slowpath+0x60/0x80
 [<c013a2f9>] ? release_console_sem+0x1c9/0x200
 [<c015aee3>] ? tick_dev_program_event+0x33/0xc0
 [<c0500ac6>] ? printk+0x18/0x1a
 [<c01079c8>] check_for_bios_corruption+0xc8/0xd0
 [<c01079d8>] periodic_check_for_corruption+0x8/0x30
 [<c0143b00>] run_timer_softirq+0x130/0x200
 [<c01079d0>] ? periodic_check_for_corruption+0x0/0x30
 [<c01079d0>] ? periodic_check_for_corruption+0x0/0x30
 [<c013f197>] __do_softirq+0x97/0x170
 [<c0106f30>] ? timer_interrupt+0x30/0x80
 [<c013f2cd>] do_softirq+0x5d/0x60
 [<c013f445>] irq_exit+0x55/0x90
 [<c0106853>] do_IRQ+0x83/0xa0
 [<c01051f3>] common_interrupt+0x23/0x30
 [<c03195b9>] ? acpi_idle_enter_simple+0x153/0x18e
 [<c040f4df>] cpuidle_idle_call+0x6f/0xd0
 [<c010285d>] cpu_idle+0x6d/0xd0
 [<c04f110e>] rest_init+0x4e/0x60
---[ end trace c26aba27896c9fb8 ]---

[Paul Dufresne (paulduf)]

>I'm getting this Kernel Failure every time i start the computer.
Even on normal boot (not after suspend, or hibernate)?

The computer continue to works fine after that?

Could you do a "dmesg | grep Corrupted" after the oops
and copy the result here?

Also, please attach the minimum requested information by
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies:

As a last resort, you may manually file your kernel bug, but at a minimum it should contain the output of the following commands:

$ uname -a > uname-a.log
$ cat /proc/version_signature > version.log
$ dmesg > dmesg.log
$ sudo lspci -vvnn > lspci-vvnn.log

These four files should be attached separately to the bug report (not pasted into comments or tar and zipped, as it makes things harder to read, and formatting is completely broken). Please note the comment about dmesg output below.

In this particular case, I guess it could be usefull to attache the result file of:
$ sudo dmidecode > dmidecode.log

But you may want to erase the serial numbers, and/or UUID before attaching the file.

[aquino (aquino-dong)]

Thanks for replying.

I didn't get anything by using "dmesg | grep Corrupted", I was trying "dmesg
| grep -i corr" and got below info:

*gonghua@thinkatmsft:~$ dmesg | grep -i corr
[ 0.000000] Scanning 2 areas for low memory corruption
[ 0.004000] Scanning for low memory corruption every 60 seconds
gonghua@thinkatmsft:~$ *

also attached four files per your instructions.

Thanks!

Gonghua

On Mon, Apr 20, 2009 at 9:14 AM, Paul Dufresne <email address hidden> wrote:

> >I'm getting this Kernel Failure every time i start the computer.
> Even on normal boot (not after suspend, or hibernate)?
>
> The computer continue to works fine after that?
>
> Could you do a "dmesg | grep Corrupted" after the oops
> and copy the result here?
>
> Also, please attach the minimum requested information by
> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies:
>
> As a last resort, you may manually file your kernel bug, but at a
> minimum it should contain the output of the following commands:
>
> $ uname -a > uname-a.log
> $ cat /proc/version_signature > version.log
> $ dmesg > dmesg.log
> $ sudo lspci -vvnn > lspci-vvnn.log
>
> These four files should be attached separately to the bug report (not
> pasted into comments or tar and zipped, as it makes things harder to
> read, and formatting is completely broken). Please note the comment
> about dmesg output below.
>
> In this particular case, I guess it could be usefull to attache the result
> file of:
> $ sudo dmidecode > dmidecode.log
>
> But you may want to erase the serial numbers, and/or UUID before
> attaching the file.
>
> --
> WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
> check_for_bios_corruption+0xdd/0xe0()
> https://bugs.launchpad.net/bugs/350704
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Confirmed
> Status in “linux” source package in Guadalinex Edu: Fix Released
>
> Bug description:
> Before a restart with kerneloops
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> Failure: oops
> MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-11-generic 2.6.28-11.38
> ProcCmdLine: root=UUID=38814f2f-9f17-43c2-8b1b-73b474164ed4 ro quiet splash
> ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
> SourcePackage: linux
> Title: WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
> check_for_bios_corruption+0xdd/0xe0()
>

--
Regards

Dong Gonghua

[aquino (aquino-dong)]

Hi There, forget to answer your question, the system seems working fine even
I'm getting this kernel failure.

Gonghua

On Mon, Apr 20, 2009 at 2:21 PM, Dong <email address hidden> wrote:

> Thanks for replying.
>
> I didn't get anything by using "dmesg | grep Corrupted", I was trying
> "dmesg | grep -i corr" and got below info:
>
> *gonghua@thinkatmsft:~$ dmesg | grep -i corr
> [ 0.000000] Scanning 2 areas for low memory corruption
> [ 0.004000] Scanning for low memory corruption every 60 seconds
> gonghua@thinkatmsft:~$ *
>
> also attached four files per your instructions.
>
> Thanks!
>
> Gonghua
>
>
>
> On Mon, Apr 20, 2009 at 9:14 AM, Paul Dufresne <email address hidden>wrote:
>
>> >I'm getting this Kernel Failure every time i start the computer.
>> Even on normal boot (not after suspend, or hibernate)?
>>
>> The computer continue to works fine after that?
>>
>> Could you do a "dmesg | grep Corrupted" after the oops
>> and copy the result here?
>>
>> Also, please attach the minimum requested information by
>> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies:
>>
>> As a last resort, you may manually file your kernel bug, but at a
>> minimum it should contain the output of the following commands:
>>
>> $ uname -a > uname-a.log
>> $ cat /proc/version_signature > version.log
>> $ dmesg > dmesg.log
>> $ sudo lspci -vvnn > lspci-vvnn.log
>>
>> These four files should be attached separately to the bug report (not
>> pasted into comments or tar and zipped, as it makes things harder to
>> read, and formatting is completely broken). Please note the comment
>> about dmesg output below.
>>
>> In this particular case, I guess it could be usefull to attache the result
>> file of:
>> $ sudo dmidecode > dmidecode.log
>>
>> But you may want to erase the serial numbers, and/or UUID before
>> attaching the file.
>>
>> --
>> WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
>> check_for_bios_corruption+0xdd/0xe0()
>> https://bugs.launchpad.net/bugs/350704
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in “linux” source package in Ubuntu: Confirmed
>> Status in “linux” source package in Guadalinex Edu: Fix Released
>>
>> Bug description:
>> Before a restart with kerneloops
>>
>> ProblemType: KernelOops
>> Annotation: Your system might become unstable now and might need to be
>> restarted.
>> Architecture: amd64
>> DistroRelease: Ubuntu 9.04
>> Failure: oops
>> MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
>> NonfreeKernelModules: nvidia
>> Package: linux-image-2.6.28-11-generic 2.6.28-11.38
>> ProcCmdLine: root=UUID=38814f2f-9f17-43c2-8b1b-73b474164ed4 ro quiet
>> splash
>> ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
>> SourcePackage: linux
>> Title: WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
>> check_for_bios_corruption+0xdd/0xe0()
>>
>
>
>
> --
> Regards
>
> Dong Gonghua
>
>

--
Regards

Dong Gonghua

[Paul Dufresne (paulduf)]

Thanks Gonghua for all these infos.
I was hoping to see the WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() in the dmesg.log file.

I can only guess that this is because you get this message when resuming from suspend or hibernate, and that this time you were not resuming from suspend.

Could you try to suspend (or hibernate if this occurs on hibernate), and then after resume, retry the:
"dmesg | grep Corrupted", please?

[aquino (aquino-dong)]

Hi there, I tried both suspend & hibernate, but I'm still not getting what u
said.

*gonghua@thinkatmsft:~$ dmesg | grep Corr (wake up from suspend)
gonghua@thinkatmsft:~$ dmesg | grep -i corr
[ 0.000000] Scanning 2 areas for low memory corruption
[ 0.004000] Scanning for low memory corruption every 60 seconds
gonghua@thinkatmsft:~$ dmesg | grep Corr (wake up from hibernate)
gonghua@thinkatmsft:~$ *

Also I was facing a computer freeze 1 minute after wakeup from hibernate,
and had to force shutdown.

Thanks!

Gonghua

On Mon, Apr 20, 2009 at 11:40 PM, Paul Dufresne <email address hidden> wrote:

> Thanks Gonghua for all these infos.
> I was hoping to see the WARNING: at
> /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
> check_for_bios_corruption+0xdd/0xe0() in the dmesg.log file.
>
> I can only guess that this is because you get this message when resuming
> from suspend or hibernate, and that this time you were not resuming from
> suspend.
>
> Could you try to suspend (or hibernate if this occurs on hibernate), and
> then after resume, retry the:
> "dmesg | grep Corrupted", please?
>
> --
> WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
> check_for_bios_corruption+0xdd/0xe0()
> https://bugs.launchpad.net/bugs/350704
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Confirmed
> Status in “linux” source package in Guadalinex Edu: Fix Released
>
> Bug description:
> Before a restart with kerneloops
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> Failure: oops
> MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-11-generic 2.6.28-11.38
> ProcCmdLine: root=UUID=38814f2f-9f17-43c2-8b1b-73b474164ed4 ro quiet splash
> ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
> SourcePackage: linux
> Title: WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719
> check_for_bios_corruption+0xdd/0xe0()
>

--
Regards

Dong Gonghua

[gokrix (gokrix-yahoo)]

I was also running into this issue, but seems like installing linux-backports-modules-jaunty-generic has fixed this one too. I installed linux-backports-modules-jaunty-generic as a fix for Bug #350370.