Re: Repeatable X lockups
On 5/13/09, Jimmie James wrote: > Jimmie James wrote: >>> When using the xv output driver for vlc or mplayer, X will lockup, crash >>> instantly, trashing the screen and forcing a reboot >>> Image of screen corruption: >>> http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg > > William Bulley wrote: >>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). > All that's in /var/log/messages is May 13 11:19:35 jimmiejaz kernel: > 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* > > vgap...@pci0:0:2:0: class=0x03 card=0x25821043 chip=0x25828086 > 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: port 0x6800-0x6807 mem > 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at > device 2.0 on pci0 > agp0: on vgapci0 > drm0: on vgapci0 > vgapci0: child drm0 requested pci_enable_busmaster > vgapci1: mem 0xcfe0-0xcfe7 at device > 2.1 on pci0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > vgapci0: port 0x6800-0x6807 mem > 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at > device 2.0 on pci0 > agp0: on vgapci0 > drm0: on vgapci0 > vgapci0: child drm0 requested pci_enable_busmaster > vgapci1: mem 0xcfe0-0xcfe7 at device > 2.1 on pci0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > > > > -- > Over the years I've come to regard you as people I've met. > > ___ > freebsd-multime...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to > "freebsd-multimedia-unsubscr...@freebsd.org" > 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Repeatable X lockups
Jimmie James wrote: When using the xv output driver for vlc or mplayer, X will lockup, crash instantly, trashing the screen and forcing a reboot Image of screen corruption: http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg William Bulley wrote: 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. All that's in /var/log/messages is May 13 11:19:35 jimmiejaz kernel: 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* vgap...@pci0:0:2:0: class=0x03 card=0x25821043 chip=0x25828086 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: port 0x6800-0x6807 mem 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at device 2.0 on pci0 agp0: on vgapci0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster vgapci1: mem 0xcfe0-0xcfe7 at device 2.1 on pci0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 vgapci0: port 0x6800-0x6807 mem 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at device 2.0 on pci0 agp0: on vgapci0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster vgapci1: mem 0xcfe0-0xcfe7 at device 2.1 on pci0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 -- Over the years I've come to regard you as people I've met. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Repeatable X lockups
According to Jimmie James on Sat, 05/02/09 at 15:46: > > When using the xv output driver for vlc or mplayer, X will lockup, crash > instantly, trashing the screen and forcing a reboot > Image of screen corruption: > http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg > > This just started manifesting in the past week or so. 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. When I similarly run vlc from the command line, the screen is locked in an even worse state than your above URL. I am forced to ssh(1) in from another FreeBSD workstation to reboot. Before the reboot, ps(1) reports no processes running xorg or any of its child processes, it seems as if my video hardware has been left in some ugly, locked-up, unusable state. What is interesting to me is that the same flash file that causes vlc and mplayer to crash runs just fine in ffplay(1) (part of ffmpeg port). Yet at least vlc uses ffmpeg, while it doesn't look like mplayer does. This is 7.2-PRERELEASE built on 24 Apr 2009 with the ports of mplayer and vlc built on 2 May 2009 following a csup(1) of complete ports tree on either 24 Apr or 25 Apr - so approximately the same timeframe as you. Regards, web... -- William Bulley Email: w...@umich.edu The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately, and delete this message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Repeatable X lockups
When using the xv output driver for vlc or mplayer, X will lockup, crash instantly, trashing the screen and forcing a reboot Image of screen corruption: http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg This just started manifesting in the past week or so. HW/SW details All that's printed to Xorg.0.log (II) intel(0): EDID vendor "NEC", prod id 17450 Memory heap 0x2867e260: Offset:0002a000, Size:0010, F. Free list: FREE Offset:0002a000, Size:0010, F. End of memory blocks pciconf -lv vgap...@pci0:0:2:0: class=0x03 card=0x25821043 chip=0x25828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82915G/GV/GL, 82910GL Integrated Graphics Device' class = display subclass = VGA vgap...@pci0:0:2:1: class=0x038000 card=0x25821043 chip=0x27828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82915G Graphics device: 82915G/GV/910GL Express Chipset Family' class = display display bits from dmesg: vgapci0: port 0x6800-0x6807 mem 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at device 2.0 on pci0 agp0: on vgapci0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster vgapci1: mem 0xcfe0-0xcfe7 at device 2.1 on pci0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xd000 256MB info: [drm] Initialized i915 1.6.0 20080730 drm0: [ITHREAD] dmesg: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-PRERELEASE #0: Sat Mar 21 22:34:18 EDT 2009 jim...@jimmiejaz.org:/usr/obj/usr/src/sys/FORTYTWO Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3192.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x441d AMD Features=0x10 Logical CPUs per core: 2 real memory = 1065091072 (1015 MB) avail memory = 1032073216 (984 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3f70 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x6800-0x6807 mem 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xd000 256MB info: [drm] Initialized i915 1.6.0 20080730 vgapci1: mem 0xcfe0-0xcfe7 at device 2.1 on pci0 hdac0: mem 0xcfef8000-0xcfefbfff irq 16 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090316_0130 hdac0: [ITHREAD] pcib1: irq 16 at device 28.0 on pci0 pci5: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci4: on pcib2 pcib3: irq 18 at device 28.2 on pci0 pci3: on pcib3 pcib4: irq 19 at device 28.3 on pci0 pci2: on pcib4 uhci0: port 0x7000-0x701f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x7400-0x741f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x7800-0x781f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x8000-0x801f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xcfeffc00-0xcfef irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib5: at device 30.0 on pci0 pci1: on pcib5 fxp0: port 0xa000-0xa03f mem 0xcfffe000-0xcfffefff irq 20 at device 8.0 on pci1 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:11:d8:11:b7:4e fxp0: [ITHREAD] rl0: port 0xa400-0xa4ff mem 0xc800-0xc8ff irq 22 at device 10.0 on pci1 miibus1: on rl0 rlphy0: PHY 0 on miibus1 rlphy0: 10ba
