Date: Thu, 20 Oct 2005 19:37:48 +0000 (GMT) From: wpaul@FreeBSD.ORG (Bill Paul) To: Emanuel.strobl@gmx.net (Emanuel Strobl) Cc: freebsd-current@freebsd.org Subject: Re: PANIC (watchdog) Message-ID: <20051020193748.3E80B16A420@hub.freebsd.org> In-Reply-To: <200510200906.19239@harrymail> from Emanuel Strobl at "Oct 20, 2005 09:05:58 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello,
>
> after I had switched into single user mode I ran installworld where my box
> paniced. I have ZERO_COPY_SOCKETS with two not committed patches but I
> think this is unrelated.
>
> Thanks,
>
> -Harry
I'm waiting for the part where you explain why you have software
watchdog support in kern_clock.c turned on. As far as I know, it's
not enabled by default in the GENERIC kernel config, and even if
it is, you have to twiddle debug.watchdog_enable in order to make
it trigger.
I can only conclude that you turned on watchdog support for some
reason, set up a watchdog app to reset the watchdog timeout every
so often, and then forgot about it (or else it was enabled as part
of some other change you made and you weren't aware of it -- maybe one
of those unrelated things you foolishly chose not to tell us about).
Presumeably the watchdog app crashed while you were doing your
installworkd. If that's the case, you shouldn't be surprised when
the watchdog expiration occurs and dumps you into ddb.
-Bill
> cd /usr/include/cam/scsi; for h in *.h; do if [ -L $h ]; then rm -f $h;
> fi; done
> interrupt total
> irq4: sio0 1421
> irq13: npx0 1
> irq20: em0 acpi0 118586
> irq21: fwohci0 1
> irq22: twe0 204149
> cpu0: timer 71692220
> Total 72016378
> KDB: stack backtrace:
> kdb_backtrace(c073ede1,44ae1fa,0,c079a9a7,c079a498) at kdb_backtrace+0x2e
> watchdog_fire(c07a7f00,2,c073ed22,10c,c0813300) at watchdog_fire+0xb5
> hardclock(d13d39f4,d13d3a08,41ed,d13d3a4c,c06e6720) at hardclock+0xfd
> lapic_handle_timer(0) at lapic_handle_timer+0x56
> Xtimerint(2,41ed,0,0,40) at Xtimerint+0x30
> ufs_access(d13d3ae4,c07a6f6c,22d,c17b9bb0,d13d3b10) at ufs_access+0x20e
> VOP_ACCESS_APV(c078f120,d13d3ae4,c0741d1e,c1810300,c14d5d00) at
> VOP_ACCESS_APV+0xac
> vfs_cache_lookup(d13d3b7c,d13d3b7c,c17b9bb0,c17b9bb0,d13d3c60) at
> vfs_cache_lookup+0x95
> VOP_LOOKUP_APV(c078f120,d13d3b7c,c1810300,246,1) at VOP_LOOKUP_APV+0xb4
> lookup(d13d3c38,0,c074b04e,c5,c19b1830) at lookup+0x468
> namei(d13d3c38,d13d3c20,246,c07ac8e0,d13d3c3c) at namei+0x438
> kern_readlink(c1810300,281975f7,0,bfbfe310,0) at kern_readlink+0x3d
> readlink(c1810300,d13d3d04,c,4,3) at readlink+0x38
> syscall(3b,3b,3b,0,bfbfe310) at syscall+0x290
> Xint0x80_syscall() at Xint0x80_syscall+0x1f
> --- syscall (58, FreeBSD ELF32, readlink), eip = 0x28121333, esp =
> 0xbfbfe2ac, ebp = 0xbfbfe368 ---
> KDB: enter: watchdog timeout
> [thread pid 69367 tid 100095 ]
> Stopped at kdb_enter+0x30: leave
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051020193748.3E80B16A420>