From owner-freebsd-stable@FreeBSD.ORG Thu Jun 20 16:59:54 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 7CD51139 for ; Thu, 20 Jun 2013 16:59:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 4595316DD for ; Thu, 20 Jun 2013 16:59:54 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id xn12so7569408obc.34 for ; Thu, 20 Jun 2013 09:59:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DJLq6NRm19i9a0uZH1wepI844MBifMCSHhCez51+Nk0=; b=bCtX4/o7kI71u3o+GE+orWC5vR5adhiQfCyDMuR4BfWFjRsg1/MRZizEulhYJ6dOa5 QiSrZWO62JzZtw7ZWo+7FJ5G0C3pLFNcnivxmCWpEgOATwcae2OGgsZ3aPZxDLueNvvT sUxu54dBUjELEEzQDdAdY9Jui4a50QcvV7bCWuXU2n/Mt+iHeRgtQ8TZcGoHyjwupb6Q mNQuvWASbyK9t0QJoaBmq1D5cLLJK+F+nTCTfW2L/bH4cQ9046CcbwRctpZ3o+HJyWjG 3kWqtSHuDhm3T6mZV7T8N8Su8T2+cEUSN0Ll1exOitb12jAZ9Xi90K9zs89oo+TDX2Yd /OEQ== MIME-Version: 1.0 X-Received: by 10.60.146.242 with SMTP id tf18mr4599183oeb.115.1371747593891; Thu, 20 Jun 2013 09:59:53 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Thu, 20 Jun 2013 09:59:53 -0700 (PDT) In-Reply-To: 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 09:59:53 -0700 X-Google-Sender-Auth: mU0pUHfzuxS5gozX1nQI3WrEojg Message-ID: Subject: Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG From: Kevin Oberman To: Javad Kouhi Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Jeremy Chadwick , Michiel Boland , "freebsd-stable@freebsd.org Stable" 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 16:59:54 -0000 On Thu, Jun 20, 2013 at 1:23 AM, Javad Kouhi wrote: > 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, > Please note that head was just patched to fix the moused issue. The fix is also applicable to 9, but I don't know when it might be MFCed. Several people have reported that it does resolve the problem (which is an infinite loop in the kernel) and my first test seems to indicate that it works for me, but I can't be sure as the problem was sporadic. And, yes, I would LOVE to have a serial console back when Intel KMS is used! -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com