Date: Wed, 16 Sep 1998 17:08:54 -0700 From: Mike Smith <mike@smith.net.au> To: Ben Smithurst <ben@scientia.demon.co.uk> Cc: FreeBSD Current <freebsd-current@FreeBSD.ORG> Subject: Re: system hangs with soft updates Message-ID: <199809170008.RAA00894@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 16 Sep 1998 23:08:21 BST." <19980916230821.A282@scientia.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hmm... when it hung as it did before, pressing ctrl-alt-esc and typing > trace gave: > > _scgetc(flags=2) at _scgetc+0x7 [../../i386/isa/syscons.c:3299] > _scintr(unit=0) at _scintr+0x17 [../../i386/isa/syscons.c:847] > Xresume1() at Xresume1+0x2b > --- interrupt, eip=0xf01bfef7, esp=0xf3a22e4c, ebp=0xf3a2de88 --- This is the interrupt that got you into DDB, so > _wdstart(ctrlr=1) at _wdstart+0x4af [../../i386/isa/wd.c:332] This is where you were when the interrupt occurred. Unfortunately the line number above is wrong; wdstart() begins around line 900. Did you see any "dummy wdunwedge" messages before you dropped into DDB, or any other messages at all? If you can reproduce the situation again, it would be useful if you could drop into DDB, copy the trace output, then use 'c' to continue and repeat the process a couple of times. This would clarify whether you're stuck in the IDE driver, or whether you just happened to catch it there on a chance. > _wdintr(unit=1) at _wdintr+0x5de [../../i386/isa/wd.c:1284] > Xresume15() at Xresume15+0x2b > --- interrupt, eip=0xf01913ce, esp=0xf3a2defc, ebp=0xf3a2df68 --- > vec15(f3a2df88) at vec15+0x2 > _sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] > _kproc_start(udata=f01d8888) at _kproc_start+0x32 [../../kern/init_main.c:248] > _fork_trampoline(e5641589,c766f01f,1fe56605,800008f0,1fe56825) at _fork_trampoline+0x30 > > I hope I copied it all correctly. If any of that makes no sense at all, > or if anyone needs more info, I'll do anything else that's needed > (within reason <g>). 8) > When I typed `panic', it wouldn't reboot: kept complaining about > interrupt timeout on wd2, I think, and then assumed I was running a > laptop because of too many timeouts. It never got as far as saving the > core image, so I can't get that, unless someone's got some other bright > idea... That's fairly normal if you're inside the drive's interrupt handler; dump routines rarely perform a full controller reset before dumping. Thanks for the feedback. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809170008.RAA00894>