Date: Sat, 16 May 2009 10:05:25 -0400 From: Jimmie James <jimmiejaz@gmail.com> To: Robert Noland <rnoland@FreeBSD.org> Cc: freebsd-x11@freebsd.org Subject: Re: Repeatable X lockups Message-ID: <4A0EC825.7010102@gmail.com>
next in thread | raw e-mail | index | archive | help
On Fri, 15 May 2009 08:53:24 -0500 Robert Noland said: >On Thu, 2009-05-14 at 18:37 -0400, Albert Vest wrote: >> Paul B. Mahol wrote: >> > On 5/13/09, Jimmie James <jimmiejaz@gmail.com> wrote: >=20 > >> 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). >>=20 >> I've been experiencing something similar, not a panic but, whenever I=20 >> switch to console (ctrl-f1?) and come back to X (ctrl-f9), my session=20 >> goes away and a new XDM screen presents itself for a fresh login. >This sounds like the xserver is crashing. This is a crash of the xserver, usually a sig.6 in /var/log/messages is pid 65663 (Xorg), uid 0: exited on signal 6, (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. leaving the console looking like http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg . While you can ssh in, restart X, the console stays corrupted like that. Memory heap 0x2867e260: Offset:0002a000, Size:00100000, F. Free list: FREE Offset:0002a000, Size:00100000, F. End of memory blocks (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. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=291042+0+archive/2009/freebsd-x11/20090503.freebsd-x11 >> Might it have to do with my hardware? I started using one of those=20 >> "wide screen" displays (1440 x 900), about the same time my updates=20 >> started showing "7.2-PRERELEASE" as version number, and it still happens=20 >> with "7.2-STABLE". All ports current (except OOO 3.0.0). >=20 >> Still using the same Radeon 9100 "IGP" forced to PCI mode, if that might=20 >> matter. >Does it detect as AGP natively? display bits from dmesg: 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 drm0: <Intel i915G> on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xd0000000 256MB info: [drm] Initialized i915 1.6.0 20080730 drm0: [ITHREAD] agp0: <Intel 82915G (915G GMCH) SVGA controller> on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M info: [drm] AGP at 0xd0000000 256MB -- Over the years I've come to regard you as people I've met.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0EC825.7010102>