After a suspend-to-ram cycle every usage of the XV extension leads to instant crash of the X-server. The X-server then remains in the restart loop and does not come up anymore. Framebuffer console is just black. System itself is fine (can login via ssh) I am using 2.6.13-rc3 vanilla sources and xorg 6.8.99.15 with an intel i915 graphics adapter. 0000:00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) Subsystem: Hewlett-Packard Company: Unknown device 099c Flags: bus master, fast devsel, latency 0 Memory at d0500000 (32-bit, non-prefetchable) Capabilities: [d0] Power Management version 2 Xorg log after resume: ynaptics DeviceOff called (WW) I810(0): Successfully set original devices (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (WW) I810(0): Successfully set original devices (2) (II) No APM support in BIOS or kernel (II) I810(0): xf86BindGARTMemory: bind key 4 at 0x007bf000 (pgoffset 1983) (II) I810(0): xf86BindGARTMemory: bind key 0 at 0x0ffff000 (pgoffset 65535) (II) I810(0): xf86BindGARTMemory: bind key 1 at 0x0fffb000 (pgoffset 65531) (II) I810(0): xf86BindGARTMemory: bind key 3 at 0x0ffea000 (pgoffset 65514) (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x0fffa000 (pgoffset 65530) (WW) I810(0): PGTBL_ER is 0x00000003 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/lib/modules/libddc.a (II) I810(0): VESA VBE DDC supported (II) I810(0): VESA VBE DDC Level 2 (II) I810(0): VESA VBE DDC transfer in appr. 1 sec. (II) I810(0): VESA VBE DDC read successfully (II) I810(0): Display plane A is disabled and connected to Pipe A. (II) I810(0): Display plane B is enabled and connected to Pipe B. (II) I810(0): Enabling plane B. (II) I810(0): Display plane A is now disabled and connected to Pipe A. (II) I810(0): Display plane B is now enabled and connected to Pipe B. (II) I810(0): PIPEACONF is 0x00000000 (II) I810(0): PIPEBCONF is 0x80000000 (II) I810(0): Mode bandwidth is 47 Mpixel/s (II) I810(0): maxBandwidth is 1152 Mbyte/s, pipe bandwidths are 252 Mbyte/s, 0 Mbyte/s (II) Mouse1: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) touchpad touchpad found Now using XV Error in I830WaitLpRing(), now is 3087873, start is 3085872 pgetbl_ctl: 0x2ffc0001 pgetbl_err: 0x3 ipeir: 0 iphdr: 1810000 LP ring tail: 15a88 head: 15a74 len: 1f801 start 0 eir: 0 esr: 10 emr: ffff instdone: ffc0 instpm: 0 memmode: 108 instps: f0000 hwstam: ffff ier: 0 imr: ffff iir: 0 space: 131044 wanted 131064 Fatal server error: lockup Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. Error in I830WaitLpRing(), now is 3089887, start is 3087886 pgetbl_ctl: 0x2ffc0001 pgetbl_err: 0x3 ipeir: 0 iphdr: 1810000 LP ring tail: 15ac8 head: 15a74 len: 1f801 start 0 eir: 0 esr: 10 emr: ffff instdone: ffc0 instpm: 0 memmode: 108 instps: f0000 hwstam: ffff ier: 0 imr: ffff iir: 0 space: 130980 wanted 131064 FatalError re-entered, aborting lockup Broadcast message from root (pts/0) (Sun Jul 24 10:33:40 2005): The system is going down for reboot NOW!
Can you try my test driver from http://www.fairlite.demon.co.uk/intel.html
I did - the X server still shows the same behavior and before the suspend cycle the colors in XV are messed up (everything is some kind of blue and white ?!) I appreciate your work on the intel driver however I am missing a history/changelog on your site (no offence - just a suggestion). (In reply to comment #1) > Can you try my test driver from http://www.fairlite.demon.co.uk/intel.html
Can you upload a complete log from the test with my driver.
Created attachment 3131 [details] xorg.conf
That log isn't from my driver. Can you submit another log with that driver. Thanks.
Sorry to hear that. Unfortunately I do not have access to the machine this week. I will post the log as soon as I can. (In reply to comment #5) > That log isn't from my driver. Can you submit another log with that driver. Thanks.
Maybe I can jump in at this point, I think I'm having similar problems. Here is how to reproduce: Start X. Switch console to text mode, switch back to X (I think this does the same as Dominics suspend to RAM). Play video (mplayer or xine using Xv), X almost always locks up. If it doesn't switch video to fullscreen, now X definitly locks up. If you don't do the console switch thing but play the video right after starting the X server everything works fine, even in fullscreen mode (besides X killing my /var/ due to excessive debugging :-) I'll attach the log from the X server. I have full access to my laptop, feel free to ask for more information or letting me try other testing versions of the driver.
Created attachment 3209 [details] GPG Key for Adam Jocksch Started X. Switched to console. Switched back to X. Played video. *bang*
Does Xvideo work before you do the switch ??
I've just uploaded another test driver to try as well. Can you upload another log once you've tested that.
> Does Xvideo work before you do the switch ?? Yes, works fine.
Created attachment 3219 [details] short lsb-test-vsw4 journal with just cpyar tests Same behaviour as .137, still locks up after switching to console and back.
Mmm, the last log you uploaded seems to suggest that you didn't do a suspend/resume. Can you explain in a little detail of what occurred for the last log ??
Whoops, seems I uploaded the wrong log file :-(. After the original lockup the X server restarts and crashes over and over again and the original log got overwritten. I'll upload the correct log soon, sorry for the confusion.
Created attachment 3224 [details] [review] updated patch for fbSetBuffer remove X is starting. [... lots of log lines] (--) Mouse[1] touchpad found (II) Mouse[3]: ps2EnableDataReporting: succeeded Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from l ist! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from lis t! Now I press Ctrl-Alt-F6 to switch to the text console [... lots of log lines] (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (WW) I810(0): Successfully set original devices (2) Now I Switch Ctrl-Alt-F7 to go back to X [...lots of log lines] (II) I810(0): Enabling Xvideo one-line mode (II) Mouse[3]: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Mouse[1] touchpad found X is back again, I start the video -> lockup
I've uploaded 1.5.139 - can you try that and upload another log ?
Created attachment 3225 [details] The PDF in question Here it is, still no change in the behaviour.
1.5.140 is up. I can see that you are running your panel at 1280x1024 but it's native resolution is 1400x1050. Can you also try adding Option "ForceBIOS" "1280x1024=1400x1050" And also make sure you have Modes "1400x1050" selected first in your mode list. Can you get two logs 1. From the past tests that you've done 2. From the new config with a 1400x1050 mode.
Good news :-) a) The new driver 1.5.140 in 1280 resolution does not lock up any more b) The new driver 1.5.140 in 1400 resolution does not lock up, too and(!) c) my old driver (1.3.0) in the 1400 resolution with the ForceBios-Option does not lock up either. Thanks a lot.
Created attachment 3269 [details] [review] fixes to remove alignment code in EXA, fix one pixmapPitchAlign, and do some cleanup Just in case you're still interested in the log though the bug is fixed.
Created attachment 3270 [details] [review] check-for-xvmc.patch
Thanks for testing. Closing.
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.