From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 1 01:54:46 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EB79106566B; Wed, 1 Dec 2010 01:54:46 +0000 (UTC) (envelope-from oxyd.oxyd@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id DDE9C8FC1B; Wed, 1 Dec 2010 01:54:45 +0000 (UTC) Received: by qyk8 with SMTP id 8so1877576qyk.13 for ; Tue, 30 Nov 2010 17:54:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Nvcj2n+Rv79zUZz70jL7MZ4HTkFXsQGen6Ro08NptpU=; b=X94GZl7h18W0ZZ1RkX0N72IVQ8Imx30tzLz2jurB37olKzxGEN8FZWQKf+pe7wtNnX Dz2WsrqtmyFrNUf2DS3C8bZ8f0AXwX9CSDR5nC9jdan5YpbvIR65SSMg1GjDvJq2n5lz K+uIWd9nejd5acvVl/n9JkCBPQkEyIhG9049s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mocaa88Xcm+KM8H+ikARgCQ1bTYep60rzfMG1lizOJnaqPe25C791J36TcT3ecIRfm /t2aNb2RR1YBeqGCfnjnQHtVvUjwsGzIauXkASKJrf1hWtliYJg9fnjodGApe/N6tD5q OJl94Xr5cuOLPFUnV07j3v7zC1BC75lF0o5pA= MIME-Version: 1.0 Received: by 10.229.100.20 with SMTP id w20mr6730551qcn.233.1291166599659; Tue, 30 Nov 2010 17:23:19 -0800 (PST) Received: by 10.229.183.19 with HTTP; Tue, 30 Nov 2010 17:23:19 -0800 (PST) Date: Wed, 1 Dec 2010 02:23:19 +0100 Message-ID: From: =?UTF-8?Q?Ond=C5=99ej_Majerech?= To: FreeBSD Mailing List , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: 8.1-RELEASE hangs on reboot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2010 01:54:46 -0000 Hello, my 8.1-R system has just started hanging on reboot. Specifically after I svn up'd my source and updated from 8.1-R-p1 to -p2. Some kind of hang occurs on every reboot attempt. Usually it hangs at the "Rebooting..." message, but sometimes the thing just locks up before it even syncs disks. shutdown -p now seems to shutdown the system successfully each time. So I booted into single-user mode, executed "reboot" and during the "Syncing disks" I pressed Ctrl-Alt-Escape to break into the debugger. There I single-stepped with the "s" command until the thing simply stopped doing anything. (Even if I pressed NumLock, the LED on the keyboard wouldn't turn off.) The screen content at the moment of hang is (dutifully typed over as the thing is dead and I don't have a serial cable): [thread pid 12 tid 100017 ] Stopped at sckbdevent+0x5f: call _mtx_unlock_flags db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags: pushq %rbp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x1: movq %rsp,%rbp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unloock_flags+0x4: subq $0x20,%rsp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x8: movq %rbx,(%rsp) db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0xc: movq %r12,0x8(%rsp) db> [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x11: movq %rdi,%rbx db> [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x14: movq %r13,0x10(%rsp) db> E Including that "E" at the end. As I said, it's 8.1-RELEASE-p2; it's on AMD64. I'm using custom kernel which only differs from GENERIC by addition of the debugging options: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC I tried rebooting with ACPI disabled, but the thing paniced on boot with panic: Duplicate free of item 0xffffff00025e0000 from zone 0xffffff00bfdcc2a0(1024) cpuid = 0 KDB: enter: panic [thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3d: movq $0, 0x6b2d20(%rip) db> bt Tracing pid 0 tid 100000 td 0xffffffff80c63fc0 kdb_enter() at kdb_enter+0x3d panic() at panic+0x17b uma_dbg_free() at uma_dbg_free+0x171 uma_zfree_arg() at uma_zfree_arg+0x68 free() at free+0xcd device_set_driver() at device_set_driver+0x7c device_attach() at device_attach+0x19b bus_generic_attach() at bus_generic_attach+0x1a pci_attach() at pci_attach+0xf1 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_pcib_attach() at legacy_pcib_attach+0x70 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_attach() at legacy_attach+0x19 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a nexus_attach() at nexus_attach+0x68 device_attach() at device_attach+0x69 bus_generic_new_pass() at bus_generic_new_pass+0xd6 bus_set_pass() at bus_set_pass+0x7a configure() at configure+0xa mi_startup() at mi_startup+0x59 btext() at btext+0x2c db> reboot That panic is 100% repeatable -- every time I try booting with ACPI disabled, I get exactly the same panic. So -- what can I do about it? I'll gladly provide more information of course. Ondra