Date: Fri, 14 Dec 2012 00:39:36 +0200 From: Artyom Mirgorodskiy <artyom@ijminteractive.net> To: freebsd-current@freebsd.org Cc: Johannes Dieterich <dieterich.joh@gmail.com>, Dimitry Andric <dim@freebsd.org> Subject: Re: new xorg segfault 11 with KMS Message-ID: <150606223.2PmcIlS4ld@home.alkar.net> In-Reply-To: <50CA4A58.7070109@FreeBSD.org> References: <CABquGzXefGp%2BD0qmaAboYQSGip-4A3XwQUT7M%2BMfVqSZjQ6i9Q@mail.gmail.com> <50CA4A58.7070109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I have recompile xorg-server with WITH_DEBUG=yes and did not get crash On Thursday 13 December 2012 22:36:24 Dimitry Andric wrote: > On 2012-12-13 21:49, Johannes Dieterich wrote: > > I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and > > WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly > > causes the segfault (log attached), gnome survives a bit longer but > > starting any bigger application (e.g. firefox) causes it to crash with the > > same log. > > > > I have a Xorg.core file, but since it is without debug symbols the > > backtrace makes little sense to me. > > Please post the backtrace anyway. :-) Or recompile xorg-server with > WITH_DEBUG=yes in your environment, and reproduce the crash. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- This message is for the person(s) named above only and may contain privileged, proprietary, or otherwise private information. If you received this transmission in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. From owner-freebsd-current@FreeBSD.ORG Thu Dec 13 22:49:31 2012 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 155C2CC6; Thu, 13 Dec 2012 22:49:31 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 875F08FC0A; Thu, 13 Dec 2012 22:49:27 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so2888007oag.13 for <multiple recipients>; Thu, 13 Dec 2012 14:49:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CzqNvgdAAQkLBrBZS4cS3q7nzJcKRsoxNJWDG9Vac04=; b=zNFwbC9USSNscEBwrcYuIX+RGHmF+F1KFHAGdfz1cyTRTEWD26ROW2SrH17tl1gTbn GCYAizPbr8hlJBs6e+C2s4nz1tioxQELZupQw4r1FThDgicQqrlmU9Hk6Wg/kiKWfNLj 6xsnmhxqV1zCKWQnwXy+n5h+VHh6iHu3w/xxNDkOM3rFQ3RNQpVlTw7Y62q6cWbDkEdd Tm3y0NJKz3d9ZNhbTEjI6ypH4bMXLmkCS83oQyz+DdlO0sa5g0pAtRdrmP39EC34gyCM JYepyVE9T09lNP20nRCQtXf1N8u9N+5OlEFFJPjUZYumVtDGrQtLl/g3uQ14XN9NYpRR tSvg== MIME-Version: 1.0 Received: by 10.182.172.74 with SMTP id ba10mr2972754obc.83.1355438966744; Thu, 13 Dec 2012 14:49:26 -0800 (PST) Received: by 10.76.143.33 with HTTP; Thu, 13 Dec 2012 14:49:26 -0800 (PST) In-Reply-To: <50C9BA19.4040504@FreeBSD.org> References: <50B6598B.20200@FreeBSD.org> <CAGH67wRGfO6KMe8u54FHRkpv=bBXNxPwtm79edZAM4nUUsS=QA@mail.gmail.com> <CAGH67wSz0Lycp7+F-v=p-XrOLCFSGM6xzEySr6rRsxwqwdBjxw@mail.gmail.com> <50C9BA19.4040504@FreeBSD.org> Date: Thu, 13 Dec 2012 14:49:26 -0800 Message-ID: <CAGH67wRV0nTaka+W34BMHV90Lu9UdMOyKzQCZ+8kgV_mgESG8Q@mail.gmail.com> Subject: Re: [HEADSUP] zfs root pool mounting From: Garrett Cooper <yanegomi@gmail.com> To: Andriy Gapon <avg@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current <freebsd-current@freebsd.org>, freebsd-zfs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 13 Dec 2012 22:49:31 -0000 On Thu, Dec 13, 2012 at 3:20 AM, Andriy Gapon <avg@freebsd.org> wrote: ... > One thing that I recommend to all ZFS users is to make use of boot environments. > They are very easy, very convenient and may save a lot of trouble. > Use either any of the tool available in ports (e.g. sysutils/beadm) or just "do > boot environments" in an ad hoc fashion: snapshot and clone your current / known > good boot+root filesystem and you have a safe environment to fall back to. Looks interesting (this page has a slightly more in-depth description of what beadm tries to achieve for the layman like me that doesn't use *Solaris: http://www.linuxquestions.org/questions/*bsd-17/howto-zfs-madness-beadm-on-freebsd-4175412036/ ). > Proper zdb -l usage was described in the "HEADSUP" posting. > It's also available in zdb(8). zdb -l should be used with disks/partitions/etc, > not with pool names. I realized that mistake after the fact :/. >> I'm running into the same behavior before and after I upgraded sac/sac2. >> My git branch is a lightly modified version of FreeBSD, but >> doesn't contain any ZFS specific changes (I can point you to it if you >> like to look at it). >> Would appreciate some pointers on what to do next. > > Try to get a working environment (using livecd, another disk, backups, etc), try > to follow the original instructions. Ok. That's sort of what I'm trying. Given that I didn't do a *ton* of customizations, I might just tar up the root pool's contents and basic configuration, wipe it out, and try creating a new one from scratch and restore the contents after the fact. However, thinking back I could turn on terse debugging in ZFS after building it with that (I've done it once before -- forgot about it until now). That would probably be the best way to get the official "story" from ZFS as to what it thinks is going south when importing the pool. Thanks! -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?150606223.2PmcIlS4ld>