Date: Wed, 25 Sep 2002 13:48:09 -0700 From: Gordon Tetlow <gordont@gnf.org> To: stable@freebsd.org Subject: Re: Panic on 4.6.1-RELEASE-p10 with a Crusoe processors Message-ID: <20020925204809.GR41477@roark.gnf.org> In-Reply-To: <20020920220916.GA41477@roark.gnf.org> References: <20020920220916.GA41477@roark.gnf.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Sep 20, 2002 at 03:09:16PM -0700, Gordon Tetlow wrote: > I have a *very* reproducable panic from my RLX Transmeta Blade when I try > to do a sysctl -a. It hits hw.crusoe.longrun and crashes the box. Since this > is in production I didn't get a core dump (I don't have a debug kernel around > since this is on a production server). Here's the info from the console: > > stack pointer = 0x10:0xc874cdfc > frame pointer = 0x10:0xc874ce0c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 174 (sysctl) > interrupt mask = none > trap number = 9 > panic: general protection fault > > I don't know if that helps, but there it is. > > If you want to look at the code that pertains, > src/sys/i386/i386/identcpu.c:1138 The problem turns out to be the fact that this CPU doesn't have longrun on it. I think there is a CPU flag that indicates longrun capability or not. I'm not sure what it is, or what it looks like, but I can provide some code (from a Linux package) that does the detection. -gordon [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9kiEJRu2t9DV9ZfsRAiR4AJ9yQEeimO8C3A4rL6WEotmt+hyCHACcCzyo fhtaVeYlmK4mQz1xxCHpIYs= =4NbG -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020925204809.GR41477>