Re: after closing the lid and reopening it the screen remains blank
On 09/09/2010 03:41 PM, Norbert Preining wrote:
Hi all,
running: 2.6.36-rc3+ (from git) on Integrated Graphics Chipset: Intel(R) GM45
(Sony Vaio Z11)
Debian/unstable, so xserver 1.7.7, intel driver: 2.12.0
since some recent kernel I have the following problem: When closing the
lid on power, so the machine does not suspend, the backlight is properly
turned off.
But when I open the lid again the backlight goes on, but there is nothing
to see: No screensaver, no activity, nothing. Switching to Console in
blind didn't work either.
The machine is still responsible (Sysrq, but also CapsLock), and
killing the X process with Ctrl-Alt-Backspace gets me back a working
X.
I am quite sure that it *was* working in former time, but cannot
pinpoint eaxactely when the problems started.
If you need any further information or testing, please let me know.
But it will take some time until I am back somewhere where I can
ssh into my machine (or try if I can ssh into).
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
BELPER
A knob of someone else's chewing gum which you unexpectedly find your
hand resting on under a deck's top, under the passenger seat of your
car or on somebody's thigh under their skirt.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
if you change up kernels and one of them causes this..then I would do a
bisect.. but if changing kernels makes no diff, then it's userpsace
related(but could be wrong) i.e. on my machine I use acpid
/etc/acpi/lid.sh in there its a simple call to s2ram (works fine(with
radeon though))looking at some of the distros scripts(no-offense) theres
loads of stuff in there todo all kinds of calls..
hope this helps.
Justin P. Mattock
--
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful,
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance.
http://p.sf.net/sfu/dell-sfdev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
after closing the lid and reopening it the screen remains blank
Hi all,
running: 2.6.36-rc3+ (from git) on Integrated Graphics Chipset: Intel(R) GM45
(Sony Vaio Z11)
Debian/unstable, so xserver 1.7.7, intel driver: 2.12.0
since some recent kernel I have the following problem: When closing the
lid on power, so the machine does not suspend, the backlight is properly
turned off.
But when I open the lid again the backlight goes on, but there is nothing
to see: No screensaver, no activity, nothing. Switching to Console in
blind didn't work either.
The machine is still responsible (Sysrq, but also CapsLock), and
killing the X process with Ctrl-Alt-Backspace gets me back a working
X.
I am quite sure that it *was* working in former time, but cannot
pinpoint eaxactely when the problems started.
If you need any further information or testing, please let me know.
But it will take some time until I am back somewhere where I can
ssh into my machine (or try if I can ssh into).
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
BELPER
A knob of someone else's chewing gum which you unexpectedly find your
hand resting on under a deck's top, under the passenger seat of your
car or on somebody's thigh under their skirt.
--- Douglas Adams, The Meaning of Liff
--
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful,
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance.
http://p.sf.net/sfu/dell-sfdev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 17692] Intermittent failure to resume from suspend-to-ram in radeon_surface_init with RV515
https://bugzilla.kernel.org/show_bug.cgi?id=17692 Karl Tomlinson bugs+ker...@karlt.net changed: What|Removed |Added Summary|Intermittent failure to |Intermittent failure to |resume from suspend-to-ram |resume from suspend-to-ram |in radeon_resume|in radeon_surface_init with ||RV515 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'master'
Dne 1.9.2010 02:53, Eric Anholt napsal(a): On Tue, 31 Aug 2010 12:17:43 +0200, Zdenek Kabelac zkabe...@redhat.com wrote: Dne 28.8.2010 05:55, Eric Anholt napsal(a): On Fri, 27 Aug 2010 13:16:04 +0200, Zdenek Kabelac zkabe...@redhat.com wrote: On 27.8.2010 12:02, Julien Cristau wrote: On Fri, Aug 27, 2010 at 11:26:59 +0200, Zdenek Kabelac wrote: Why keeping different name for C++ and C ? Because changing the name for C means breaking API for existing users, which is not a nice thing to do. Well if DRM would have very stable API - it would make sence - but from a view of occasional user who needs to compile drm for intel driver - it seems the API is changed so frequently and in such an incompatible way that this change doesn't look all that bad. How many libdrm project users are there - and how often is this variable used outside of libdrm ? Now C++ will use different names for same variables - that IMHO bigger issue... Also - if headers are supposed to be C++ friendly - maybe usage of extern C might be handy for such case ? Uh, you claim the API has changed, but I'm not aware of any circumstance since TTM removal where upgrading libdrm on Intel should have broken either API or ABI for its users. Can you back that up? Ok - I'm remembering this issue: Essentially I've had idea to try to bisect for this problem: https://bugs.freedesktop.org/show_bug.cgi?id=26937 As I'm quite sure, that there were times were I could use fullscreen for flash without fear of having to restart my desktop. So I've tried just some random older git versions of libdrm intel driver - there were some minor compilations issue (I guess some list defines conflicts and few other minor things for compilation). However compiled driver library actually never worked and all I got was usually black screen. It's probably hard to judge if the problem is kernel driver (using usually quite fresh vanilla git tree) or Xorg from Fedora Rawhide can't work with some slightly older libdrm/intel. It probably not reasonable to spend time to detect where exactly is problem - all I want to point out is, that some internal API must changed significantly so while I could usually boot with 2 year old kernel, I cannot use few months old drmintel driver. And back to this issue - if this variable is used a lot by other projects, than this commit is probably ok - though looks ugly. But if there is just one project which uses it, than it's probably better to break API and keep it clean and use same variable for C C++ programs. For bisecting, just hold libdrm at the new version and bisect in 2d, unless your initial test of old+old vs old+new of each component points at libdrm (in which case, hold the 2d driver old and bisect across libdrm). New drivers do require new symbols, but libdrm is API and ABI stable, exactly so that people can bisect successfully. Ok - I made a closer look at the problem - and bisected for a reason my current Xorg server shows black screen for older version of Intel driver. It looks like the key issue is some API change in Xorg related to this Intel driver commit: 8700673157fdd3a87ad5150f2f30823261fec519 (Adapt glyphs for changes in devPrivates API, Jun 7 2010, Chris Wilson) This is effectively the oldest version of Intel driver which currently seems to work with my (recently upgraded) xorg-x11-server-Xorg-1.9.0-7.fc15.x86_64. It seems like cherry-picking to make this usable for older version of Intel git tree seems to be very complicated so doing bisect looks like very hard task in this case. I'm open to some ideas how could I eventually try to resolve/help with my fullscreen bug (id=26937). Anyway this seems to show that keeping API stable at one small library and breaking it in Xorg server itself doesn't make things better after all Is there any other way (except essentially completely reinstalling my whole system and trying to figure out which combination of Xorg and driver still works ok for full screen??) Would it help to post some /sys prints which would show why the screen is locked in 'fullscreen' picture and there is no way to restore it back ? Zdenek -- Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: after closing the lid and reopening it the screen remains blank
On Fri, Sep 10, 2010 at 07:41:17AM +0900, Norbert Preining wrote: running: 2.6.36-rc3+ (from git) on Integrated Graphics Chipset: Intel(R) GM45 (Sony Vaio Z11) Debian/unstable, so xserver 1.7.7, intel driver: 2.12.0 since some recent kernel I have the following problem: When closing the lid on power, so the machine does not suspend, the backlight is properly turned off. But when I open the lid again the backlight goes on, but there is nothing to see: No screensaver, no activity, nothing. Switching to Console in blind didn't work either. The machine is still responsible (Sysrq, but also CapsLock), and killing the X process with Ctrl-Alt-Backspace gets me back a working X. I am quite sure that it *was* working in former time, but cannot pinpoint eaxactely when the problems started. If you need any further information or testing, please let me know. But it will take some time until I am back somewhere where I can ssh into my machine (or try if I can ssh into). FWIW, 2.6.36-rc3-00396-gbe6200a suspend-to-ram works for me on GM45 (Dell E4300). I am running Ubuntu with xorg-edgers from a few months ago: xserver-xorg-core 2:1.6.5+git20091107+server-1.6-branch.2dbcb06a-0ubuntu0sarvatt~karmic xserver-xorg-video-intel 2:2.11.0+git20100415.c374c94e-0ubuntu0sarvatt~karmic There are several regression fixes pulled after 2.6.36-rc3 in merge commit 4eab8a5717f5, can you try current linux-2.6.git ? If it still fails, please post - lspci -vvv - /var/log/Xorg.0.log from after the failure - dmesg -andy -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: after closing the lid and reopening it the screen remains blank
On Sat, Sep 11, 2010 at 08:44:48AM +0900, Norbert Preining wrote: On Fr, 10 Sep 2010, Andy Isaacson wrote: FWIW, 2.6.36-rc3-00396-gbe6200a suspend-to-ram works for me on GM45 I never said that it has anything to do with suspend to ram. Ah, sorry for misunderstanding. My GM45 system is configured to automatically S2R on lid close so I tend to conflate the two... In fact, suspend to ram works perfectly without any problems. I only reboot after I installed a new kernel ... I will try some older kernels and see if it is a kernel or userspace issue. Do try the current tip and/or describe which post-rc3 kernel fails for you, just to verify. Also, is there anything in Xorg.0.log from when it fails to restore the video? Thanks for reporting the regression, it'll be good to get it fixed ASAP. -andy -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
