From owner-freebsd-stable@FreeBSD.ORG Fri Jul 27 00:51:30 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93C36106566B for ; Fri, 27 Jul 2012 00:51:30 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 4B37B8FC12 for ; Fri, 27 Jul 2012 00:51:30 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q6R0oddT018121 for ; Thu, 26 Jul 2012 17:50:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1343350240; bh=IyIiMcbMu40he5LmMk4qpulRhRmHzot6AVaTl2uYPEc=; h=Subject:From:Reply-To:To:Content-Type:Date:Message-ID: Mime-Version:Content-Transfer-Encoding; b=cvVuVD8W6/M73dduFPL58k/zQ8RtOfFm07sj0KzSmE8mdmqAVqBLCNV8tc0ccHtNI howoEc7ojPqNwxKI2Yinzkc8YcHAxIzg0GDxPQplVvvLalLP4DsyQBelJwIi8fmCAx tmK103Y7WO0YGB07RJxXlZl4EziMjT6QNmbRlTDA= From: Sean Bruno To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Thu, 26 Jul 2012 17:50:38 -0700 Message-ID: <1343350238.12294.10.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 350239001 Subject: dell r420/r320 stable/9 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2012 00:51:30 -0000 For the time being I had to revert the following from my stable/9 tree. Otherwise I would get a kernel panic on shutdown from ipmi(4). http://svnweb.freebsd.org/base?view=revision&revision=237839 http://svnweb.freebsd.org/base?view=revision&revision=221121 I suspect that the ipmi device isn't detatching early or properly in this configuration, but I have only just now discovered these changesets as a clue to what's going on here. The panic looks like this when you see it: Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc sleepq_wait() at sleepq_wait+0x4d _sleep() at _sleep+0x3f6 ipmi_submit_driver_request() at ipmi_submit_driver_request+0x97 ipmi_set_watchdog() at ipmi_set_watchdog+0xb1 ipmi_wd_event() at ipmi_wd_event+0xaa kern_do_pat() at kern_do_pat+0x10f sched_sync() at sched_sync+0x1ea fork_exit() at fork_exit+0x135 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff869b177bb0, rbp = 0 ---