The most pertinent part of the dmesg for me seems to be the sections that follows. It is also present in Wouter's submission.
[ 1039.792506] ------------[ cut here ]------------ [ 1039.792513] WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90() [ 1039.792515] Hardware name: Studio 1537 [ 1039.792517] Component: resume devices, time: 12350 [ 1039.792518] Modules linked in: binfmt_misc rfcomm ppdev sco bridge stp bnep l2cap snd_hda_codec_atihdmi btusb bluetooth snd_hda_codec_idt joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi lib80211_crypt_tkip snd_seq_midi_event snd_seq snd_timer snd_seq_device dell_wmi uvcvideo sdhci_pci sdhci dell_laptop dcdbas snd psmouse ricoh_mmc serio_raw led_class videodev v4l1_compat v4l2_compat_ioctl32 wl(P) lib80211 lp parport soundcore snd_page_alloc radeonfb fb_ddc fbcon tileblit font bitblit softcursor vga16fb vgastate usbhid radeon ttm drm_kms_helper ohci1394 video output ieee1394 drm i2c_algo_bit tg3 intel_agp [ 1039.792566] Pid: 2939, comm: pm-suspend Tainted: P 2.6.32-11-generic #15-Ubuntu [ 1039.792568] Call Trace: [ 1039.792574] [<ffffffff81064f4b>] warn_slowpath_common+0x7b/0xc0 [ 1039.792577] [<ffffffff81064ff1>] warn_slowpath_fmt+0x41/0x50 [ 1039.792580] [<ffffffff810a1458>] suspend_test_finish+0x88/0x90 [ 1039.792583] [<ffffffff810a1201>] suspend_devices_and_enter+0xb1/0xe0 [ 1039.792586] [<ffffffff810a1308>] enter_state+0xd8/0x110 [ 1039.792588] [<ffffffff810a08aa>] state_store+0x9a/0x100 [ 1039.792593] [<ffffffff812ae4f7>] kobj_attr_store+0x17/0x20 [ 1039.792597] [<ffffffff811aa035>] sysfs_write_file+0xe5/0x170 [ 1039.792601] [<ffffffff811401d8>] vfs_write+0xb8/0x1a0 [ 1039.792606] [<ffffffff815628c4>] ? do_page_fault+0x194/0x370 [ 1039.792609] [<ffffffff81140c91>] sys_write+0x51/0x90 [ 1039.792613] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b [ 1039.792616] ---[ end trace 97aeee2497f9bd26 ]--- It seems we both use radeon, and I suspect that is part of the problem. Though it may not be related, I've always found that the GPU runs much hotter under the radeon driver than fglrx, and so this bug is especially worrying, as it makes the computer even more likely to overheat. I tested the 2.6.33-999.201001221151 kernel, and that exacerbated the problem: plymouth didn't work, and KMS seemed dodgy. Further, when resuming, I had to issue a SysRq+K command before the display would be restarted. The thermal problem still existed. I will attach the dmesg from that session shortly. Lastly, I am using the xorg-edgers PPA. It's very exciting to see the progress that the free drivers are making. -- Thermal control broken after resume https://bugs.launchpad.net/bugs/508369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
