Date: Fri, 28 Feb 2003 22:11:15 -0800 (PST) From: "nate" <freebsd@aphroland.org> To: <freebsd-questions@freebsd.org> Subject: Re: kernel panic question Message-ID: <49136.10.10.10.7.1046499075.squirrel@webmail.linuxpowered.net> In-Reply-To: <20030228190303.1d5490e4.kitbsdlists@HotPOP.com> References: <20030228160755.4e34ba4b.kitbsdlists@HotPOP.com> <20030301044805.GE41962@wantadilla.lemis.com> <20030228180031.36d416ab.kitbsdlists@HotPOP.com> <20030301051231.GG41962@wantadilla.lemis.com> <20030228190303.1d5490e4.kitbsdlists@HotPOP.com>
next in thread | previous in thread | raw e-mail | index | archive | help
kitsune said: > Any ways since ye wanted proof, why I would care to fake it I do not know, > I am inserting the out put from dmesg... and after looking into kernel > dumps, afaik that would be useless to me since from what little info I > found has told me there is a nice chance I won't understant it. I reccomend setting up a serial console. you'll need a null modem cable and another system to connect the console to. capturing kernel panics via log files is tricky, I've never been able to on linux or free/open bsd, maybe my panics have just been too severe. on the flip side the kernel panics i've had on solaris managed to get logged to the syslog server :) nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49136.10.10.10.7.1046499075.squirrel>