From owner-freebsd-stable@FreeBSD.ORG Thu Jun 20 08:26:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 143FFE9F for ; Thu, 20 Jun 2013 08:26:03 +0000 (UTC) (envelope-from javad.kouhi@gmail.com) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1101295 for ; Thu, 20 Jun 2013 08:26:02 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id eb20so5412017lab.1 for ; Thu, 20 Jun 2013 01:26:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=R9IZ1rzaFOrN7Ee3B4/pHRd36IxCzbdv7ODDeEJ2c0s=; b=hLIi9dVn+A5w8d4c8oZcuKC9L9wmGOCzF01OhpHanh+A81I22058Z3aALf+cXg6GwH 3mxXcbFXX3996k/fNWEbWpd2/GSUDfvjuwmrDG6wrovpOFy7MJnNuSfz9BzHnvgm3QKs pw7T3TONq/CMdSAmciGFjFvtwd75vg0VNf0oLNeW7Wjb6JuivbS0/Gc/QKUYwH/iL32V BoOU1jEN4yIH9vcBi/LeSwJzggtox+oU2/D/pREJfDLKdEgz+D+J2WwlFt6KCRsOGCVc HT48F3un2GasPpB1+aQI5PwwHiBRC4/IrvYNBQzIvM1Th+y43wAwhtHffPX4HrQaRF4c yizw== X-Received: by 10.112.125.199 with SMTP id ms7mr5003759lbb.29.1371716761475; Thu, 20 Jun 2013 01:26:01 -0700 (PDT) Received: from localhost ([2.181.105.241]) by mx.google.com with ESMTPSA id m1sm10676742lag.3.2013.06.20.01.25.56 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 20 Jun 2013 01:26:00 -0700 (PDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Jeremy Chadwick" Subject: Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG References: <51BDD593.5000102@xs4all.nl> <51BF60A8.6000503@xs4all.nl> <20130617193726.GR91021@kib.kiev.ua> <51C06AD2.5030404@xs4all.nl> <20130618144722.GA3446@icarus.home.lan> <20130618182538.GA3380@icarus.home.lan> <20130618212818.GA58803@icarus.home.lan> Date: Thu, 20 Jun 2013 12:53:03 +0430 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Javad Kouhi" Message-ID: In-Reply-To: <20130618212818.GA58803@icarus.home.lan> User-Agent: Opera Mail/12.15 (FreeBSD) Cc: Michiel Boland , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jun 2013 08:26:03 -0000 On Wed, 19 Jun 2013 01:58:18 +0430, Jeremy Chadwick wrote: > On Wed, Jun 19, 2013 at 01:41:10AM +0430, Javad Kouhi wrote: >> I've read the posts again. Although the issue looks same as Michiel >> Boland (first link) but I'm not sure if the root of the issue is same >> as Michiel's too (second link). Anyway, it should be discussed in >> another thread as you said. > > Let me be more clear: > > I have seen repeated reports from people complaining about "lockups when > shutting down" many times over the years. The ones I remember: > > - Certain oddities with SCSI/SATA storage drivers and disks (many of > these have been fixed) > - ACPI-based reboot not working correctly on some motherboards > (depends on hw.acpi.handle_reboot and sometimes > hw.acpi.disable_on_reboot) -- not sure if this still pops up > - USB layer causing issues, or possibly some USB CAM integration > problem (this is still an ongoing one) > - Now some sort of weird Intel graphics driver (and DRM?) quirk > involving moused(8) and Vsync (the issue reported by Michiel) > > And I'm certain I'm forgetting others. > > What Kevin Oberman said also applies -- these are painful to debug > because the system is already in a "shutting down" state where usability > and accessibility becomes bare minimal, and you're kind of at your > wits end. > > Booting verbose can help -- there are other messages printed to the VGA > (and/or serial) console during the shutdown phase when verbose. > > All you can hope for is that the kernel is still alive and Ctrl-Alt-Esc > to force a drop to DDB (assuming all of this is enabled in your kernel) > works and that someone familiar with the FreeBSD kernel can help you > debug it (possibly it's just easier to do that, type "panic", then > issue "call doadump" to force a dump to swap at that point -- kib@ > might have better recommendations). > > Serial console can also greatly help, because quite often there are > pages upon pages of debugging information that are useful, otherwise you > have to hope the VGA console keyboard is functional (even more tricky > with USB) and that Scroll Lock + Page Up/Down function along with taking > photos of the screen; doing it this way is stressful and painful for > everyone involved. > > I hope this sheds some light on why I said what I did. :-) > Ok, I will compile a new kernel with DDB option. I will submit the crash info and dmesg output the next time it happens. (in a new thread) Thanks for your help. Regards,