Re: Linux 2.6.12-rc2

AsterixTheGaul
2005-04-08T06:28:43Z

> FWIW, I have the same problem on a T41p with 2.6.11 and 2.6.12-rc2,
> except that neither returns from suspend-to-ram with video restored on
> the LCD. I believe I was able to get video restored on an external CRT
> in either 2.6.12-rc2 or 2.6.12-rc2-mm1, but the LCD still didn't
> restore (can verify later today, if you'd like). I had dumped out the
> radeontool regs values before & after the sleep, in case they help.
> They are attached.

Hmm... I have 2.6.12-rc2 on a T41 and "suspend to ram" works good (well
except for a backtrace complaining about __might_sleep but otherwise ok).

Apr 7 23:17:10 localhost kernel: Debug: sleeping function called from
invalid context at mm/slab.c:2090
Apr 7 23:17:10 localhost kernel: in_atomic():0, irqs_disabled():1
Apr 7 23:17:10 localhost kernel: [<c011d9e3>] __might_sleep+0xa3/0xc0
Apr 7 23:17:10 localhost kernel: [<c015beb0>] kmem_cache_alloc+0x50/0x60
Apr 7 23:17:10 localhost kernel: [<c0269750>] acpi_pci_link_set+0x4a/0x1a2
Apr 7 23:17:10 localhost kernel: [<c0269bc9>] irqrouter_resume+0x1c/0x24
Apr 7 23:17:10 localhost kernel: [<c02b70f6>] sysdev_resume+0x66/0xc4
Apr 7 23:17:10 localhost kernel: [<c02bbcc5>] device_power_up+0x5/0xa
Apr 7 23:17:10 localhost kernel: [<c014a426>] suspend_enter+0x36/0x60
Apr 7 23:17:10 localhost kernel: [<c014a3a3>] suspend_prepare+0x63/0xb0
Apr 7 23:17:10 localhost kernel: [<c014a4ec>] enter_state+0x5c/0x70
Apr 7 23:17:10 localhost kernel: [<c014a639>] state_store+0xa9/0xbc
Apr 7 23:17:10 localhost kernel: [<c014a590>] state_store+0x0/0xbc
Apr 7 23:17:10 localhost kernel: [<c01d27c6>] subsys_attr_store+0x36/0x50
Apr 7 23:17:10 localhost kernel: [<c01d2a6e>] flush_write_buffer+0x2e/0x40
Apr 7 23:17:10 localhost kernel: [<c01d2ace>] sysfs_write_file+0x4e/0x80
Apr 7 23:17:10 localhost kernel: [<c017bdee>] vfs_write+0x12e/0x130
Apr 7 23:17:10 localhost kernel: [<c017bea1>] sys_write+0x41/0x70
Apr 7 23:17:10 localhost kernel: [<c01039ff>] sysenter_past_esp+0x54/0x75

>
> I posted these problems in the "Call for help S3" thread, but no one responded.
>
> Thanks,
> Nish
>
>
>