Date: Wed, 1 Dec 2010 02:23:19 +0100 From: =?UTF-8?Q?Ond=C5=99ej_Majerech?= <oxyd.oxyd@gmail.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org>, freebsd-hackers@freebsd.org Subject: 8.1-RELEASE hangs on reboot Message-ID: <AANLkTi=mxpjY%2BdhjRWsG1hUnnA=4J%2BLybcOw=is81rQH@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=mxpjY%2BdhjRWsG1hUnnA=4J%2BLybcOw=is81rQH>