2.6.28-11 Oops - resume from suspend, blank monitor

[Jeremy Sequoia]

I am choosing "I don't know" for the package because this tool seems broken. I selected "linux-image-2.6-amd64-generic" from the "Choose..." list, but it still complains!

kernel is 2.6.28-11 generic

echo "mem" > /sys/power/state
press power to resume.

The screen does not restore its state after the resume, but I can connect remotely. dmesg reports this oops:

[ 140.206229] ------------[ cut here ]------------
[ 140.206231] WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80()
[ 140.206233] Component: resume devices
[ 140.206234] Modules linked in: binfmt_misc ppdev bridge stp bnep video output input_polldev lp parport snd_via82xx gameport snd_via82xx_modem snd_ac97_codec snd_mpu401_uart ac97_bus snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device k8temp pcspkr usbhid snd snd_page_alloc soundcore psmouse i2c_viapro serio_raw shpchp skge ohci1394 ieee1394 floppy fbcon tileblit font bitblit softcursor
[ 140.206260] Pid: 3379, comm: bash Not tainted 2.6.28-11-generic #42-Ubuntu
[ 140.206262] Call Trace:
[ 140.206268] [<ffffffff80250927>] warn_slowpath+0xb7/0xf0
[ 140.206272] [<ffffffff8026d478>] ? down_trylock+0x38/0x50
[ 140.206275] [<ffffffff80251040>] ? try_acquire_console_sem+0x10/0x40
[ 140.206280] [<ffffffff8025c676>] ? lock_timer_base+0x36/0x70
[ 140.206283] [<ffffffff80531f4f>] ? usb_suspend_both+0x26f/0x310
[ 140.206288] [<ffffffff8069bf36>] ? printk+0x67/0x69
[ 140.206291] [<ffffffff80418877>] ? kobject_put+0x27/0x60
[ 140.206296] [<ffffffff804b6045>] ? put_device+0x15/0x20
[ 140.206301] [<ffffffff804be06a>] ? dpm_complete+0x18a/0x1a0
[ 140.206304] [<ffffffff8028003c>] suspend_test_finish+0x7c/0x80
[ 140.206307] [<ffffffff80280124>] suspend_devices_and_enter+0xe4/0x180
[ 140.206310] [<ffffffff802803d9>] enter_state+0xe9/0x120
[ 140.206313] [<ffffffff802804ca>] state_store+0xba/0x100
[ 140.206316] [<ffffffff80418717>] kobj_attr_store+0x17/0x20
[ 140.206319] [<ffffffff80347675>] sysfs_write_file+0xc5/0x140
[ 140.206324] [<ffffffff802e7eeb>] vfs_write+0xcb/0x130
[ 140.206327] [<ffffffff802e8040>] sys_write+0x50/0x90
[ 140.206330] [<ffffffff8021253a>] system_call_fastpath+0x16/0x1b
[ 140.206333] ---[ end trace 24f663bc54a09208 ]---
[ 140.206578] PM: Finishing wakeup.

root@sephiroth:~# uname -a
Linux sephiroth 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
root@sephiroth:~# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
 Subsystem: ASUSTeK Computer Inc. Device 80a3
 Flags: bus master, 66MHz, medium devsel, latency 64
 Memory at <ignored> (32-bit, prefetchable)
 Capabilities: [80] AGP version 3.5
 Capabilities: [c0] HyperTransport: Slave or Primary Interface
 Capabilities: [68] Power Management version 2
 Capabilities: [58] HyperTransport: Interrupt Discovery and Configuration
 Kernel driver in use: agpgart-amd64

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
 Flags: bus master, 66MHz, medium devsel, latency 0
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Memory behind bridge: f9100000-fd2fffff
 Prefetchable memory behind bridge: d1000000-f0ffffff
 Capabilities: [80] Power Management version 2
 Kernel modules: shpchp

00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 80) (prog-if 10)
 Subsystem: ASUSTeK Computer Inc. Device 808a
 Flags: bus master, medium devsel, latency 64, IRQ 11
 Memory at fdd00000 (32-bit, non-prefetchable) [size=2K]
 I/O ports at bc00 [size=128]
 Capabilities: [50] Power Management version 2
 Kernel driver in use: ohci1394
 Kernel modules: firewire-ohci, ohci1394

00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
 Subsystem: ASUSTeK Computer Inc. Device 80f5
 Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 5
 I/O ports at ec00 [size=64]
 I/O ports at dc00 [size=16]
 I/O ports at cc00 [size=128]
 Memory at fdf00000 (32-bit, non-prefetchable) [size=4K]
 Memory at fde00000 (32-bit, non-prefetchable) [size=128K]
 Capabilities: [60] Power Management version 2
 Kernel driver in use: sata_promise

00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
 Subsystem: ASUSTeK Computer Inc. Device 811a
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
 Memory at fdb00000 (32-bit, non-prefetchable) [size=16K]
 I/O ports at b000 [size=256]
 Expansion ROM at fda00000 [disabled] [size=128K]
 Capabilities: [48] Power Management version 2
 Capabilities: [50] Vital Product Data <?>
 Kernel driver in use: skge
 Kernel modules: skge

00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 10
 I/O ports at e800 [size=8]
 I/O ports at e400 [size=4]
 I/O ports at e000 [size=8]
 I/O ports at d800 [size=4]
 I/O ports at d400 [size=16]
 I/O ports at d000 [size=256]
 Capabilities: [c0] Power Management version 2
 Kernel driver in use: sata_via

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 32, IRQ 11
 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
 [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
 [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
 [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
 I/O ports at fc00 [size=16]
 Capabilities: [c0] Power Management version 2
 Kernel driver in use: pata_via

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 11
 I/O ports at b400 [size=32]
 Capabilities: [80] Power Management version 2
 Kernel driver in use: uhci_hcd

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 11
 I/O ports at b800 [size=32]
 Capabilities: [80] Power Management version 2
 Kernel driver in use: uhci_hcd

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 10
 I/O ports at c000 [size=32]
 Capabilities: [80] Power Management version 2
 Kernel driver in use: uhci_hcd

00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 10
 I/O ports at c400 [size=32]
 Capabilities: [80] Power Management version 2
 Kernel driver in use: uhci_hcd

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20)
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, medium devsel, latency 64, IRQ 5
 Memory at fd900000 (32-bit, non-prefetchable) [size=256]
 Capabilities: [80] Power Management version 2
 Kernel driver in use: ehci_hcd

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
 Subsystem: ASUSTeK Computer Inc. Device 80ed
 Flags: bus master, stepping, medium devsel, latency 0
 Capabilities: [c0] Power Management version 2
 Kernel modules: i2c-viapro

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
 Subsystem: ASUSTeK Computer Inc. Device 80b0
 Flags: medium devsel, IRQ 5
 I/O ports at c800 [size=256]
 Capabilities: [c0] Power Management version 2
 Kernel driver in use: VIA 82xx Audio
 Kernel modules: snd-via82xx

00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
 Flags: medium devsel, IRQ 5
 I/O ports at 1000 [size=256]
 Capabilities: [d0] Power Management version 2
 Kernel modules: snd-via82xx-modem

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
 Flags: fast devsel
 Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
 Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
 Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
 Flags: fast devsel
 Kernel driver in use: k8temp
 Kernel modules: k8temp

01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
 Subsystem: Device 196e:02f1
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
 Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
 Memory at e0000000 (32-bit, prefetchable) [size=256M]
 Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
 Expansion ROM at fd200000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
 Capabilities: [44] AGP version 3.0
 Kernel modules: nvidiafb

root@sephiroth:~# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 4
model name : AMD Athlon(tm) 64 Processor 2800+
stepping : 8
cpu MHz : 1802.080
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up rep_good
bogomips : 3604.16
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp

This is with 9.04

[Jeremy Sequoia (jeremyhu)]

The screen state restore is problematic, and I think there are multiple issues at work here. When I boot my kernel with 'test_suspend=standby no_console_suspend', I still get the following:

[ 14.176212] ------------[ cut here ]------------
[ 14.176277] WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80()
[ 14.176358] Component: resume devices
[ 14.176421] Modules linked in:
[ 14.176532] Pid: 1, comm: swapper Not tainted 2.6.28-11-generic #42-Ubuntu
[ 14.176600] Call Trace:
[ 14.176667] [<ffffffff80250927>] warn_slowpath+0xb7/0xf0
[ 14.176736] [<ffffffff8025c676>] ? lock_timer_base+0x36/0x70
[ 14.176804] [<ffffffff80531f4f>] ? usb_suspend_both+0x26f/0x310
[ 14.176873] [<ffffffff8069bf36>] ? printk+0x67/0x69
[ 14.176940] [<ffffffff80418877>] ? kobject_put+0x27/0x60
[ 14.177009] [<ffffffff804b6045>] ? put_device+0x15/0x20
[ 14.177078] [<ffffffff804be06a>] ? dpm_complete+0x18a/0x1a0
[ 14.177145] [<ffffffff8028003c>] suspend_test_finish+0x7c/0x80
[ 14.177213] [<ffffffff80280124>] suspend_devices_and_enter+0xe4/0x180
[ 14.177282] [<ffffffff802803d9>] enter_state+0xe9/0x120
[ 14.177348] [<ffffffff80280526>] pm_suspend+0x16/0x20
[ 14.177416] [<ffffffff80a076ab>] test_wakealarm+0x113/0x149
[ 14.177483] [<ffffffff80a076e1>] ? test_suspend+0x0/0xb8
[ 14.177549] [<ffffffff80a0778f>] test_suspend+0xae/0xb8
[ 14.177615] [<ffffffff80a06fbd>] ? pm_qos_power_init+0xa2/0xe5
[ 14.177683] [<ffffffff8020a03b>] do_one_initcall+0x3b/0x170
[ 14.177750] [<ffffffff80417e7f>] ? idr_pre_get+0x4f/0x90
[ 14.177817] [<ffffffff8069e569>] ? _spin_lock+0x9/0x10
[ 14.177885] [<ffffffff8033c2e4>] ? proc_register+0x144/0x220
[ 14.177952] [<ffffffff8033c4e9>] ? create_proc_entry+0x59/0xb0
[ 14.178020] [<ffffffff802a1e58>] ? register_irq_proc+0xb8/0xe0
[ 14.178088] [<ffffffff80330000>] ? dquot_mark_dquot_dirty+0x20/0x80
[ 14.178157] [<ffffffff809e97cb>] kernel_init+0xc8/0x11e
[ 14.178224] [<ffffffff80246917>] ? schedule_tail+0x27/0x70
[ 14.178291] [<ffffffff80213979>] child_rip+0xa/0x11
[ 14.178357] [<ffffffff809e9703>] ? kernel_init+0x0/0x11e
[ 14.178424] [<ffffffff8021396f>] ? child_rip+0x0/0x11
[ 14.178489] ---[ end trace c1b40c1d8d0f0309 ]---

[Jeremy Sequoia (jeremyhu)]

After looking at the kernel source, I realized that wasn't an oops... it
was just a stack trace warning that was triggered by the resume taking
too long (but it unfortunately doesn't identify exactly WHAT made it
take so long). This occurs with test_suspend=standby on boot, so it's
not related to a specific module.

[Jeremy Sequoia (jeremyhu)]

The title needs to be changed since this is not an oops, but I don't see where to do that...

I used the pm trace functionality described here:
https://wiki.ubuntu.com/DebuggingKernelSuspend

but I did not get anywhere with that. On the next boot, dmesg showed:
Magic number: 5:435:547

but there was no hash match.

With X11 running using nvidia drivers and without X11 running, S1/standby works successfully (I did not test standby/nv)

With X11 running using nv or nvidia and without X11 running, S3/mem fails. I have periodically been able to get a network connection after the resume, and each time that I have, I've noticed that either Xorg was consuming 100% CPU (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/363672) or vbetool post was consuming 100% CPU (see https://bugs.launchpad.net/ubuntu/+source/vbetool/+bug/130979).

Using test_suspend=mem on boot (to eliminate possible bugs in modules), my video does not come back, and I can successfully interact blindly with the machine or connect via network.

My BIOS has an option to re-POST the vide card after S3 resume. Having this option on, I have never been able to connect via network or successfully interact blindly with the machine, so I assume the machine is hung with that option, so I've been debugging with it off.

[Jeremy Sequoia (jeremyhu)]

My guess is that this is a hardware bug... unless someone else can reproduce it and knows a workaround, I suggest we close the bug.

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

I just upgraded to this kernel, and suspend/resume was broken