Date: Wed, 30 Jan 2002 07:34:50 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Sergey Gershtein <sg@ur.ru> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange lock-ups during backup over nfs after adding 1024M RAM Message-ID: <20020130073449.B78919@gsmx07.alcatel.com.au> In-Reply-To: <1931130530386.20020128130947@ur.ru>; from sg@ur.ru on Mon, Jan 28, 2002 at 01:09:47PM %2B0500 References: <20020126204941.H17540-100000@resnet.uoregon.edu> <1931130530386.20020128130947@ur.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-Jan-28 13:09:47 +0500, Sergey Gershtein <sg@ur.ru> wrote: > It was surprising to me that when >everything is locked-up you can still type on the keyboard, switch >consoles (alt-F1..Alt-Fn), but not log in or even reboot the system >with ctrl-alt-del. It just ignores ctrl-alt-del, but allowes to type, >scroll the console with arrow keys after pressing scrollLock, etc. That suggests that the kernel is still running happily but something has deadlocked. Compile and run a kernel with "options DDB". When it locks up, use Ctrl-Alt-Esc to enter DDB and try "ps" - this will tell you what processes are running/blocked. (Read ddb(4) for more details). >It was nmbd that continued to answer its queries and was able to write >to log file. All other log files including /var/log/cron and web >server logs stopped at the time of lock-up. nmbd writes direct to files. cron writes via syslogd. Apache writes direct, but other WEB servers may differ. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020130073449.B78919>