From owner-freebsd-current Wed Feb 26 7:27:48 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B18BC37B405 for ; Wed, 26 Feb 2003 07:27:42 -0800 (PST) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76A4943F93 for ; Wed, 26 Feb 2003 07:27:39 -0800 (PST) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (localhost.dlib.vt.edu [127.0.0.1]) by gromit.dlib.vt.edu (8.12.7/8.12.7) with ESMTP id h1QFRcV6027510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 26 Feb 2003 10:27:38 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by gromit.dlib.vt.edu (8.12.7/8.12.7/Submit) id h1QFRcOE027509 for freebsd-current@freebsd.org; Wed, 26 Feb 2003 10:27:38 -0500 (EST) Date: Wed, 26 Feb 2003 10:27:38 -0500 From: Paul Mather To: freebsd-current@freebsd.org Subject: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENT upgrade Message-ID: <20030226152738.GA27326@gromit.dlib.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-No-Archive: yes X-Operating-System: FreeBSD/i386 4.8-PRERELEASE User-Agent: Mutt/1.5.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yesterday evening I upgraded a Gateway 450 laptop from 5.0-RELEASE-p3 to 5.0-CURRENT. Unfortunately, as a byproduct of that upgrade, I can no longer start X. Instead, it now aborts with Signal 10. :-( Here is the end of the XFree86 log file: >>>>> [[...]] (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) RADEON(0): VESA BIOS detected (II) RADEON(0): VESA VBE Version 2.0 (II) RADEON(0): VESA VBE Total Mem: 32768 kB (II) RADEON(0): VESA VBE OEM: ATI MOBILITY RADEON (II) RADEON(0): VESA VBE OEM Software Rev: 1.0 (II) RADEON(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) RADEON(0): VESA VBE OEM Product: P6 (II) RADEON(0): VESA VBE OEM Product Rev: 01.00 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) RADEON(0): VESA VBE DDC supported (II) RADEON(0): VESA VBE DDC Level none (II) RADEON(0): VESA VBE DDC transfer in appr. 2 sec. (II) RADEON(0): VESA VBE DDC read failed (==) RADEON(0): Write-combining range (0xe8100000,0x80000) was already clear (==) RADEON(0): Write-combining range (0xf0000000,0x2000000) (II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=16600 (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) Fatal server error: Caught signal 10. Server aborting [[...]] <<<<< Comparing the XFree86 log to an older one in which XFree86 was working, it seems that the current server is choking reading the virtual display size. Here is the output from when it was still working under 5.0-RELEASE-p3: >>>>> [[...]] (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) RADEON(0): VESA BIOS detected (II) RADEON(0): VESA VBE Version 2.0 (II) RADEON(0): VESA VBE Total Mem: 32768 kB (II) RADEON(0): VESA VBE OEM: ATI MOBILITY RADEON (II) RADEON(0): VESA VBE OEM Software Rev: 1.0 (II) RADEON(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) RADEON(0): VESA VBE OEM Product: P6 (II) RADEON(0): VESA VBE OEM Product Rev: 01.00 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) RADEON(0): VESA VBE DDC supported (II) RADEON(0): VESA VBE DDC Level none (II) RADEON(0): VESA VBE DDC transfer in appr. 2 sec. (II) RADEON(0): VESA VBE DDC read failed (==) RADEON(0): Write-combining range (0xe8100000,0x80000) was already clear (==) RADEON(0): Write-combining range (0xf0000000,0x2000000) (II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=16600 (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) (--) RADEON(0): Virtual size is 1024x768 (pitch 1152) (**) RADEON(0): Mode "1024x768" (==) RADEON(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" [[...]] <<<<< (Note the probe of the card for the virtual size succeeds in 5.0-RELEASE, but fails in 5.0-CURRENT.) At boot, the graphics card is probed as: >>>>> pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xec000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0x3000-0x30ff mem 0xe8100000-0xe810f fff,0xf0000000-0xf7ffffff irq 10 at device 0.0 on pci1 info: [drm] AGP at 0xec000000 64MB info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 <<<<< Finally, here is the output from gdb on the resultant XFree86 core file: >>>>> GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... (no debugging symbols found)... Core was generated by `XFree86'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libz.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.2 Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libm.so.2 Reading symbols from /usr/lib/libc.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)... done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 0x28243853 in kill () from /usr/lib/libc.so.5 (gdb) bt #0 0x28243853 in kill () from /usr/lib/libc.so.5 #1 0x282a6e5c in abort () from /usr/lib/libc.so.5 #2 0x0806bce1 in ddxGiveUp () #3 0x0806bd95 in AbortDDX () #4 0x080dee90 in GiveUp () #5 0x080e0368 in FatalError () #6 0x0807fd21 in xf86SigHandler () #7 #8 0x28220575 in vsscanf () from /usr/lib/libc.so.5 #9 0x0809678f in xf86sscanf () #10 0x0884d67a in ?? () #11 0x0884dddf in ?? () #12 0x0884ec44 in ?? () #13 0x0806b09b in InitOutput () #14 0x080c7703 in main () #15 0x0806a815 in _start () (gdb) <<<<< Has anyone else experienced problems with X ceasing to work after a 5.0-RELEASE -> 5.0-CURRENT upgrade?? I did not change X at all during the upgrade. All I did was rebuilt world and kernel, as per /usr/src/UPDATING. After discovering X no longer worked, I rebuilt my X server and X libraries ports via portupgrade -f, but still have the same problem. I notice the drm device has remained fairly dormant, although according to the CVS logs there was a change to a header file (drm_vm.h) yesterday. Could this be the problem? I can post full XFree86 startup log, boot log, XF86Config, etc. if desired. Any help is appreciated, as this leaves the laptop pretty useless right now for the kind of work for which it's used. :-( If all else fails, I will have to try and regress back to 5.0-RELEASE. :-( (Please Cc: me on any replies to the list.) Cheers, Paul. e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message