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

-- 
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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to