From: AsterixTheGaul <asterixthegaul@gmail.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Moritz Muehlenhoff <jmm@inutil.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.12-rc2
Date: Fri, 8 Apr 2005 12:30:42 +0530 [thread overview]
Message-ID: <54b5dbf5050408000016e02601@mail.gmail.com> (raw)
In-Reply-To: <54b5dbf505040723392f29b18c@mail.gmail.com>
Ok this time I did with radeontool and it works good :)) (2.6.12-rc2 on T41).
1. I have "radeontool regs" before susp to ram (presusp)
2. turn off LCD with "radeontool light off"
3. Suspend to RAM and wake up. (same backtrace)
4. LCD is back on (no problem)
5. regs in postsusp
only diff is
< RADEON_CRTC_GEN_CNTL=03200600
---
> RADEON_CRTC_GEN_CNTL=03000600
presusp
---------------
RADEON_DAC_CNTL=ff002102
RADEON_DAC_CNTL2=00000000
RADEON_TV_DAC_CNTL=07680142
RADEON_DISP_OUTPUT_CNTL=10000002
RADEON_CONFIG_MEMSIZE=02000000
RADEON_AUX_SC_CNTL=00000000
RADEON_CRTC_EXT_CNTL=00008048
RADEON_CRTC_GEN_CNTL=03200600
RADEON_CRTC2_GEN_CNTL=00800000
RADEON_DEVICE_ID=00004c66
RADEON_DISP_MISC_CNTL=5b300600
RADEON_GPIO_MONID=00000000
RADEON_GPIO_MONIDB=00000300
RADEON_GPIO_CRT2_DDC=00000300
RADEON_GPIO_DVI_DDC=00130000
RADEON_GPIO_VGA_DDC=00030000
RADEON_LVDS_GEN_CNTL=003dffa1
postsusp
---------------
RADEON_DAC_CNTL=ff002102
RADEON_DAC_CNTL2=00000000
RADEON_TV_DAC_CNTL=07680142
RADEON_DISP_OUTPUT_CNTL=10000002
RADEON_CONFIG_MEMSIZE=02000000
RADEON_AUX_SC_CNTL=00000000
RADEON_CRTC_EXT_CNTL=00008048
RADEON_CRTC_GEN_CNTL=03000600
RADEON_CRTC2_GEN_CNTL=00800000
RADEON_DEVICE_ID=00004c66
RADEON_DISP_MISC_CNTL=5b300600
RADEON_GPIO_MONID=00000000
RADEON_GPIO_MONIDB=00000300
RADEON_GPIO_CRT2_DDC=00000300
RADEON_GPIO_DVI_DDC=00130000
RADEON_GPIO_VGA_DDC=00030000
RADEON_LVDS_GEN_CNTL=003dffa1
On Apr 8, 2005 12:09 PM, AsterixTheGaul <asterixthegaul@gmail.com> wrote:
> Err... never mind... I was not doing any radeon control.
>
> On Apr 8, 2005 11:58 AM, AsterixTheGaul <asterixthegaul@gmail.com> wrote:
> > > 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
> > >
> > >
> > >
> >
>
next prev parent reply other threads:[~2005-04-08 7:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0504040945100.32180@ppc970.osdl.org>
2005-04-04 21:32 ` Linux 2.6.12-rc2 Linus Torvalds
2005-04-04 22:58 ` Andres Salomon
2005-04-04 23:04 ` Andres Salomon
2005-04-04 23:07 ` Andres Salomon
2005-04-04 23:24 ` Al Viro
2005-04-04 23:49 ` Russell King
2005-04-04 23:54 ` Al Viro
2005-04-04 23:37 ` Stephen Rothwell
2005-04-04 23:54 ` Al Viro
2005-04-05 4:54 ` Gene Heskett
2005-04-06 17:14 ` Moritz Muehlenhoff
2005-04-06 22:42 ` Benjamin Herrenschmidt
2005-04-07 17:50 ` Moritz Muehlenhoff
2005-04-07 18:54 ` Nish Aravamudan
2005-04-07 22:45 ` Benjamin Herrenschmidt
2005-04-08 0:44 ` Nish Aravamudan
2005-04-08 6:28 ` AsterixTheGaul
2005-04-08 6:39 ` AsterixTheGaul
2005-04-08 7:00 ` AsterixTheGaul [this message]
2005-04-08 15:39 ` Nish Aravamudan
2005-04-08 18:14 ` AsterixTheGaul
2005-04-07 22:43 ` Benjamin Herrenschmidt
2005-04-05 7:29 Oleg Nesterov
2005-04-05 8:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 14:56 Hubert Tonneau
2005-04-06 23:20 Bob Gill
2005-04-06 23:25 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54b5dbf5050408000016e02601@mail.gmail.com \
--to=asterixthegaul@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=jmm@inutil.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox