Date: Sat, 17 Oct 1998 17:25:21 -0400 (EDT) From: Chuck Robey <chuckr@mat.net> To: Karl Pielorz <kpielorz@tdx.co.uk> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Latest kernel Message-ID: <Pine.BSF.4.05.9810171722430.330-100000@picnic.mat.net> In-Reply-To: <3629098B.14313D94@tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Oct 1998, Karl Pielorz wrote: > > > Chuck Robey wrote: > > > Appreciate the help, I don't know what I might be doing wrong. /etc/rc > > keeps on telling me the same thing I get when I go into single user with > > now (now preciously hoarded) good kernel single-user and try to save the > > kernel dump --- no kernel dump. When I'm in ddb, and call panic, then > > continue, it says it can't get the smp lock, doesn't do the dump at all, > > and goes directly to reset. No dump. > > "Can't get the SMP lock?" - Are you running an SMP system? You say da0s1b is > 96Mb, how much RAM do you have in the machine? I have 192M of swap, in two 96M partitions. I have 64M of memory. That ought to be hoards and hoards more than I need. > If you can get the exact text it comes up with at panic time, in response to > you issuing 'panic' to DDB it might shed some light on things... I posted separately about what I found with the panic problem, at least as much as I could without being able to get the dump. It's not all that useful, without all the context from teh dump itself. I wanted this to concentrate on getting me the dump, not analysis of something I can't get yet. I'm greedily waiting on advice on how to force the dump. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- 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?Pine.BSF.4.05.9810171722430.330-100000>