x3100 resume results in black screen (2.6.25 kernel)

[Khashayar Naderehvandi]

On Fri, May 9, 2008 at 11:23 PM, Jesse Barnes <jbarnes at virtuousgeek.org>
wrote:

> On Friday, May 09, 2008 1:14 pm Khashayar Naderehvandi wrote:
> > On Fri, May 9, 2008 at 10:03 PM, Jesse Barnes <jbarnes at virtuousgeek.org>
> >
> > wrote:
> > > On Friday, May 09, 2008 12:41 pm Khashayar Naderehvandi wrote:
> > > > On 5/9/08, Jesse Barnes <jbarnes at virtuousgeek.org> wrote:
> > > > > On Friday, May 09, 2008 10:05 am Khashayar Naderehvandi wrote:
> > > > > > Running ubuntu hardy with a 2.6.25 kernel causes the backlight of
> > > > > > my
> > > > >
> > > > > laptop
> > > > >
> > > > > > to remain black after resume. Switching VTs does not help.
> > > > > >
> > > > > > Hardy ships with a 2.6.24 kernel which works just fine, I
> installed
> > > > > > a 2.6.25 kernel since it causes far fewer wakeups (as observed
> with
> > > > > > powertop).
> > > > > >
> > > > > > I have also tried the 2.6.24 kernel with drm modules from git.
> This
> > > > > > also fails on resume.
> > > > > >
> > > > > > The laptop is a dell xps m1330 with an x3100 chipset.
> > > > >
> > > > > Does a suspend/resume from the console after loading the i915 DRM
> > >
> > > driver
> > >
> > > > > fail
> > > > > in the same way?
> > > > >
> > > > >
> > > > > No, that works just fine.
> > >
> > > Ok, so the console always comes back correctly if you suspend from the
> > > console... that's a start.  Are you using vesafb, intelfb, uvesafb or
> any
> > > other framebuffer drivers?
> >
> > Not as far as I know, but here's an output of lsmod | grep fb
> >
> > fbcon                  42912  0
> > tileblit                3456  1 fbcon
> > font                    9472  1 fbcon
> > bitblit                 6784  1 fbcon
> >
> > > > In fact, resume works fine sometimes (well, it worked at least once),
> > > > but most of the time it fails. I tried to get it working some more
> > > > using the 2.6.24 kernel with updated drm and i915 modules. What
> > > > happens, more exactly, is that upon resume the only thing that comes
> > > > back is the
> > >
> > > cursor.
> > >
> > > > I can move the cursor around but I can't change VTs, neither can I
> > >
> > > restart
> > >
> > > > the X server with ctrl-alt-backspace. I managed to suspend the laptop
> > >
> > > once
> > >
> > > > more in this state (by closing the lid). Upon opening the lid again,
> > >
> > > ubuntu
> > >
> > > > threw me in a low resolution mode running their display-config
> utility.
> > > > I could still not change VTs to a console. At this point I restarted
> > > > the laptop.
> > > >
> > > > Should I post any log files?
> > > >
> > > > By the way, this is a long shot, but I know the uvcvideo module has
> > >
> > > caused
> > >
> > > > problems in the past, could it do so again? This is a long shot,
> > > > because the only thing changed when I tried the above with the 2.6.24
> > > > kernel is updated i915 and drm modules.
> > >
> > > Well, if console suspend/resume is working, it's probably not a
> uvcvideo
> > > issue, since that would probably prevent the kernel from suspending or
> > > resuming altogether.
> >
> > I'm also 99.9% certain it's not. Just wanted to mention it. And also, it
> is
> > possible that the module wasn't loaded when Isuspended in console (I can
> > double check this later if need be). In any event, the suspend script is
> > supposed to unload the module before suspend.
> >
> > > What X driver are you using?
> > >
> > > Everything else is plain ubuntu hardy: intel version: 2.2.1-1ubuntu13.
> > > And
> >
> > the xorg.conf is just minimal.
> > By the way, the logs I caught revealed nothing. I can try to get more
> > verbose logs later if that's needed.
>
> What if you suspend w/o using the scripts?  I.e. from X just open an xterm
> or
> something as root and do 'echo mem > /sys/power/state'?
>
> I've narrowed down the problem to compiz.
For what it's worth, suspending directly under X worked fine as far as
suspending and resuming is concerned. For some reason I was thrown back at
the login screen though, but that's probably not related to this.

I tried suspending (using gnome-power-manager which uses hal) multiple times
while compiz was not running, and that worked perfectly. After a few rounds,
I fired up compiz and tried again, only to be greeted with the old cursor
above a small rectangle of my desktop. After that, sysrq magic got me out.

Khashayar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20080510/b80971e7/attachment.html>