Repeatable X lockups

Paul B. Mahol

2009-05-13 19:01:44 UTC

When using the xv output driver for vlc or mplayer, X will lockup, crash
instantly, trashing the screen and forcing a reboot
http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg

I have experienced the same problem, but I didn't see any suggestions
or answers to your posting. Have you had any success yet with this?
Have you tried any other output drivers? This is something I plan to
try in the next few days.
My system is i386 with Intel 915 graphics on the motherboard. Xorg 7.4
runs fine. When I run mplayer from the command line, in an xterm under
open-motif, the X Windows session dies and I am tossed back to the vty.

Halp? The x11 output driver sucks when trying to watch something full
screen.
With the latest (in ports) xf86-video-intel-2.7.1, first time with xv it
was fine, flipped to a console then back to X, and ran mplayer with xv,
lockup/Xcrash,
ssh'd into my box, and for the hell of it, ran startx, and it worked, I
was back in X, but the console was still buggered as the picture in the
link above shows.
I could kill X, but the console was buggered, locked, ssh would allow me
to restart X as many times as I wished.

One thing to note, I dont switch to console while DRI is active
otherwise panic could happen(last time when I tested it with 915GM).

Post by Jimmie James
pid 65663 (Xorg), uid 0: exited on signal 6
Unfortunatly, Xorg log doesn't have anything, as I restarted X over ssh
several times, the only thing there, is when trying to startx a lot of
times, the first attempt can't find any screens with a usable
configuration, ^c then startx again works just fine.
(WW) intel(0): drmDropMaster failed: Unknown error: -1
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xc5819000 at 0x2884f000
(II) intel(0): [drm] Closed DRM master.
xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1600
VGA connected 1600x1200+0+0 (normal left inverted right x axis y axis)
306mm x 230mm
1600x1200 65.0*
rev=0x04 hdr=0x00
vendor = 'Intel Corporation'
device = '82915G/GV/GL, 82910GL Integrated Graphics Device'
class = display
subclass = VGA
grep vga /var/run/dmesg.boot
vgapci0: <VGA-compatible display> port 0x6800-0x6807 mem
0xcfd80000-0xcfdfffff,0xd0000000-0xdfffffff,0xcfe80000-0xcfebffff at
device 2.0 on pci0
agp0: <Intel 82915G (915G GMCH) SVGA controller> on vgapci0
drm0: <Intel i915G> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
vgapci1: <VGA-compatible display> mem 0xcfe00000-0xcfe7ffff at device
2.1 on pci0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
vgapci0: <VGA-compatible display> port 0x6800-0x6807 mem
0xcfd80000-0xcfdfffff,0xd0000000-0xdfffffff,0xcfe80000-0xcfebffff at
device 2.0 on pci0
agp0: <Intel 82915G (915G GMCH) SVGA controller> on vgapci0
drm0: <Intel i915G> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
vgapci1: <VGA-compatible display> mem 0xcfe00000-0xcfe7ffff at device
2.1 on pci0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
--
Over the years I've come to regard you as people I've met.
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia
To unsubscribe, send any mail to

That is same corrupted screen output I was experiencing with older server and
mesa. And only when zapping Xorg.

Somehow small change somewhere "fixed" that problem for me, actually
everything points to some timeing issue.

It's hard to say if this is FreeBSD DRM issue or X11(mesa or server) problem.

I could put console into somehow not perfect but still usable conditon
if I started X11 again using vesa driver.

--
Paul