From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 7 13:52:47 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B34C71065673 for ; Fri, 7 Jan 2011 13:52:47 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8E68FC0A for ; Fri, 7 Jan 2011 13:52:46 +0000 (UTC) Received: by mail-wy0-f182.google.com with SMTP id 19so17574260wyf.13 for ; Fri, 07 Jan 2011 05:52:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=78iYKx/7+eBBeko9sUkrMjBnReINCmTMx4tJPSyXwb4=; b=eFRRPLRhUAGe6AHrJMm+WEwKHjBJ98gmrZb2CeEZ+GLE7QOp1rddemcwjBx+ZA8vc9 nPHwAiFdPM1gfItbVCW6GAK5kMGDd5n86yZlVhw79XJYpxECeU2wTYk06mrqbxgKe+8w v77Eb1TTpdfYF/hXStmp5lf1Ylk7BYFTbQqCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i63zv1UtBw7QBwsD02zjX7Adg8PEvV+Cd1Z4/Wz02AED6yaezjCv9yQfVnIVY/abvX C5x1XX8bQ6aDPxu+AhGFXYMddXZxGmgmNHtvIorlf5kDrJCrQvDjonJrpNIhAvX6UWY/ zf1+UyfkprUURRXuRsJB0O7G3DsFktzTBi6bk= MIME-Version: 1.0 Received: by 10.227.146.149 with SMTP id h21mr15424184wbv.43.1294406645377; Fri, 07 Jan 2011 05:24:05 -0800 (PST) Received: by 10.227.59.3 with HTTP; Fri, 7 Jan 2011 05:24:05 -0800 (PST) In-Reply-To: References: <201101062245.p06MjFSW019165@red.freebsd.org> Date: Fri, 7 Jan 2011 14:24:05 +0100 Message-ID: From: Oliver Pinter To: fbsdmail@dnswatch.com Content-Type: text/plain; charset=ISO-8859-1 Cc: patrick@spacesurfer.com, freebsd-amd64@freebsd.org Subject: Re: amd64/153746: kernel crash with 2 X11 sessions on amd64 with radeon drm X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 13:52:47 -0000 http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html http://old.nabble.com/freebsd7,-radeon,-xorg-server-->-deadlock-or-so-td27524122.html On 1/7/11, fbsdmail@dnswatch.com wrote: > > On Thu, January 6, 2011 2:45 pm, Patrick Mackinlay wrote: >> > >>> Number: 153746 >>> Category: amd64 >>> Synopsis: kernel crash with 2 X11 sessions on amd64 with radeon >>> drm >>> Confidential: no >>> Severity: non-critical >>> Priority: medium >>> Responsible: freebsd-amd64 >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Thu Jan 06 22:50:07 UTC 2011 >>> Closed-Date: >>> Last-Modified: >>> Originator: Patrick Mackinlay >>> Release: 8.1-RELEASE-p2 (affects 8.0 as well) >>> Organization: >>> Environment: >>> >> FreeBSD patrick.uknet.spacesurfer.com 8.1-RELEASE-p2 FreeBSD >> 8.1-RELEASE-p2 #3: Thu Jan 6 21:40:18 GMT 2011 >> root@patrick.uknet.spacesurfer.com:/usr/obj/usr/src/sys/PATRICK amd64 >> >>> Description: >>> >> If I start 2 X11 sessions (startx and start -- :1). The close the >> sessions on display :1, when I switch to the session on display :0 the >> system reboots. I have an amd64 with a ATI radeon card: >> >> drm0: on vgapci0 >> >> >> Note that if I never close either X11 session there is no problem with >> stability (weeks uptime), however the only graphics intensive app I use >> is mplayer. mplayer is the only reason I need drm, however the bug will >> be triggered even if I havn't used mplayer in my X11 session. > Greetings, > Fact is, Mplayer has nothing to do with when/how drm is loaded. 2 > possibilities exist for loading; @boot via loader.conf(5), or when > starting X via xorg.conf(5). > If you're loading it via xorg.conf(5), and suspect drm to be the culprit. > The easiest solution would be to comment the line that loads it in your > xorg.conf(5) file. Then startx(1), and see if there's any difference in > behavior. FWIW I haven't been able to use HALd on _any_ 64bit box. So > against the suggested entries in rc.conf(8): > dbus_enable="YES" > hald_enable="YES" > > I need to use > > hald_enable="NO" > or I have big problems running X. I only mention it, in case this > might also apply to your situation. > > HTH > > --Chris > >> >> I will attach the output from dmesg with my full system setup and the >> output from the two xorg log files. >>> How-To-Repeat: >>> >> >>> Fix: >>> >> >> >>> Release-Note: >>> Audit-Trail: >>> Unformatted: >>> >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >> >> > > > -- > kern: > FreeBSD 8.1-RELEASE amd64 > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >