Thanks. There are lots of errors in your logs that look like this, so
I'm assigning to the kernel for now:
Dec 7 18:52:02 Satellite kernel: [ 9524.689322] Pid: 8852, comm: pm-suspend
Tainted: P 2.6.27-9-generic #1
Dec 7 18:52:02 Satellite kernel: [ 9524.689326] [<c037c4b6>] ?
printk+0x1d/0x1f
Dec 7 18:52:02 Satellite kernel: [ 9524.689338] [<c018a477>]
__alloc_pages_internal+0x387/0x490
Dec 7 18:52:02 Satellite kernel: [ 9524.689371] [<c018a5e9>]
__get_free_pages+0x29/0x40
Dec 7 18:52:02 Satellite kernel: [ 9524.689375] [<c01ad6f6>]
__kmalloc+0xf6/0x100
Dec 7 18:52:02 Satellite kernel: [ 9524.689385] [<dcc65de5>]
__ke_malloc_atomic+0x15/0x20 [fglrx]
Dec 7 18:52:02 Satellite kernel: [ 9524.689479] [<dcc985d8>]
firegl_cmmqs_save_fb+0xa8/0x280 [fglrx]
Dec 7 18:52:02 Satellite kernel: [ 9524.689553] [<dcc7aec6>] ?
firegl_pm_save_framebuffer+0x66/0x70 [fglrx]
Dec 7 18:52:02 Satellite kernel: [ 9524.689607] [<dcc7cd2a>] ?
firegl_cail_powerdown+0xaa/0x150 [fglrx]
Dec 7 18:52:02 Satellite kernel: [ 9524.689672] [<dcc68f0b>] ?
fglrx_pci_suspend+0x8b/0x150 [fglrx]
Dec 7 18:52:02 Satellite kernel: [ 9524.689732] [<c0262e7b>] ?
pci_legacy_suspend+0x2b/0x70
Dec 7 18:52:02 Satellite kernel: [ 9524.689743] [<c026305a>] ?
pci_pm_suspend+0x7a/0xa0
Dec 7 18:52:02 Satellite kernel: [ 9524.689746] [<c02c73ca>] ?
pm_op+0x11a/0x150
Dec 7 18:52:02 Satellite kernel: [ 9524.689752] [<c02c788c>] ?
suspend_device+0x8c/0x140
Dec 7 18:52:02 Satellite kernel: [ 9524.689756] [<c02c79f1>] ?
dpm_suspend+0xb1/0x110
Dec 7 18:52:02 Satellite kernel: [ 9524.689759] [<c02c7a72>] ?
device_suspend+0x22/0x30
Dec 7 18:52:02 Satellite kernel: [ 9524.689763] [<c015d279>] ?
suspend_devices_and_enter+0x69/0x190
Dec 7 18:52:02 Satellite kernel: [ 9524.689770] [<c015d571>] ?
enter_state+0xd1/0x100
Dec 7 18:52:02 Satellite kernel: [ 9524.689773] [<c015d625>] ?
state_store+0x85/0xd0
Dec 7 18:52:02 Satellite kernel: [ 9524.689776] [<c015d5a0>] ?
state_store+0x0/0xd0
Dec 7 18:52:02 Satellite kernel: [ 9524.689779] [<c024e444>] ?
kobj_attr_store+0x24/0x30
Dec 7 18:52:02 Satellite kernel: [ 9524.689784] [<c01ff4c7>] ?
sysfs_write_file+0x97/0x100
Dec 7 18:52:02 Satellite kernel: [ 9524.689788] [<c01b24c0>] ?
vfs_write+0xa0/0x110
Dec 7 18:52:02 Satellite kernel: [ 9524.689792] [<c01ff430>] ?
sysfs_write_file+0x0/0x100
Dec 7 18:52:02 Satellite kernel: [ 9524.689796] [<c01b2602>] ?
sys_write+0x42/0x70
Dec 7 18:52:02 Satellite kernel: [ 9524.689799] [<c0103f7b>] ?
sysenter_do_call+0x12/0x2f
Dec 7 18:52:02 Satellite kernel: [ 9524.689803] [<c0370000>] ?
netdev_exit+0x10/0x20
Dec 7 18:52:02 Satellite kernel: [ 9524.689807] =======================
This problem might have already been reported though, and I need to
check that first before triaging it.
Thanks
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Resume/Thaw takes ~20 minutes or longer, hdd activity excessive
https://bugs.launchpad.net/bugs/307384
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
