Created attachment 36466 [details] Xorg log After S3 resume, backlight is not enabled. chipset: i915 Arrandale Integrated Graphics (8086:0046) system architecture: i686 mesa: 7.7.1-1ubuntu3 xserver: 1.7.6 glx client version: 1.4 (from glxinfo) libdrm: 2.5.18-1ubuntu3 kernel version: 2.6.32-23-generic Linux distrubtion: Ubuntu Lucid (i386, generic) Machine: Dell Latitude E4310, BIOS: A02, 05/28/2010 Display: LCD laptop screen Steps to reproduce: 1. Boot machine 2. Suspend (from desktop, or using pm-suspend) 3. Resume (hit power buttom, machine resumes) 4. Backlight does not turn on 100% reproducible. Attachments:
Created attachment 36468 [details] dmesg log
Created attachment 36469 [details] output from intel-reg-dumper
Created attachment 36470 [details] output from xrandr
Is it just the backlight that fails to turn on or does the panel not come back on at all? Sometimes when it's just the backlight you can see something displayed on the screen if you look closely it's just really dim.
(In reply to comment #4) > Is it just the backlight that fails to turn on or does the panel not come back > on at all? Sometimes when it's just the backlight you can see something > displayed on the screen if you look closely it's just really dim. Jesse, it's hard to tell. The screen is totally off - no illumination, no sign of any image at all. It's equivalent to me doing xset dpms force off.
Also, did you do a bare bones test? Just boot into a kernel console (no X), do "echo mem > /sys/power/state" then try to resume. If that comes back it tells us something is wrong with the X part of it. Otherwise we have a more fundamental problem.
(In reply to comment #6) > Also, did you do a bare bones test? Just boot into a kernel console (no X), do > "echo mem > /sys/power/state" then try to resume. If that comes back it tells > us something is wrong with the X part of it. Otherwise we have a more > fundamental problem. Done some testing from just the console with X totally disabled: 1. pm-suspend + resume, resumes fine, can ssh back into the machine, no display, totally blank laptop screen. 2. echo mem > /sys/power/state, resume, cannot ssh back into machine, no display, total blank laptop screen. I bascially need a bunch of the pm scripts to resume the device into a working state so I can ssh back into it after resume, but that's another issue.
Interesting... I wonder if your PM scripts are running "vbetool post" at some point. Can you set up netconsole and see if you get any useful info out of the machine at resume time?
*** This bug has been marked as a duplicate of bug 28739 ***
(In reply to comment #8) > Interesting... I wonder if your PM scripts are running "vbetool post" at some > point. Can you set up netconsole and see if you get any useful info out of the > machine at resume time? What kind of "useful info" do you require?
On Sat, 10 Jul 2010 09:16:40 -0700 (PDT) bugzilla-daemon@freedesktop.org wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=28744 > > --- Comment #10 from Colin Ian King <colin.king@canonical.com> 2010-07-10 09:16:40 PDT --- > (In reply to comment #8) > > Interesting... I wonder if your PM scripts are running "vbetool post" at some > > point. Can you set up netconsole and see if you get any useful info out of the > > machine at resume time? > > What kind of "useful info" do you require? Well I was hoping to see a panic, oops, or some DRM modesetting related error message.
Assuming closed - like https://bugs.freedesktop.org/show_bug.cgi?id=28739
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.