Date: Thu, 21 Jul 2005 11:19:22 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Eirik =?iso-8859-1?Q?=D8verby?= <ltning@anduin.net> Cc: marcolz@stack.nl Subject: Re: Serious issue with serial console in 5.4 Message-ID: <20050721091922.GB52120@stack.nl> Resent-Message-ID: <20050721094458.GD52120@stack.nl> In-Reply-To: <00DD4399-4317-4579-82C4-5B64AC3F800B@anduin.net> References: <20050721050048.GU22430@xor.obsecurity.org> <00DD4399-4317-4579-82C4-5B64AC3F800B@anduin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--jho1yZJdad60DJr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2005 at 10:56:54AM +0200, Eirik verby wrote: > >>>Fatal trap 12: page fault while in kernel mode > >>>cpuid =3D 1; apic id =3D 00 > >>>fault virtual address =3D 0x1c > >>>fault code =3D supervisor write, page not present > >>>instruction pointer =3D 0x8:0xc0620b5f > >>>stack pointer =3D 0x10:0xdadbd988 > >>>frame pointer =3D 0x10:0xdadbd994 > >>>code segment =3D base 0x0, limit 0xfffff, type 0x1b > >>> =3D DPL 0, pres 1, def32 1, gran 1 > >>>processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > >>>current process =3D 51999 (getty) > >>>trap number =3D 12 > >>>panic: page fault > >>>cpuid =3D 1 > >>>boot() called on cpu#0 > >>>Uptime: 66d11h24m50s > >>> > >> > >>The above panic will show up occasionally when logging out from a > >>serial console (i.e. ctrl-D, logout, exit, whatever). This is > >>EXTREMELY BAD, as it will crash an otherwise perfectly healthy box at > >>random - and renders the serial console useless. > >> > >>Robert Watson confirmed this to be an issue on the 10th of April. > >> > >>Anyone?? > >> > > > >You might have to wait until 6.0-R since fixing it seems to require > >infrastructure changes that cannot easily be backported to 5.x. >=20 > With all due respect - if this is (and I'm assuming it is, because it =20 > happens on all the servers I'm serial-controlling) an omnipresent =20 > problem on 5.x, I daresay it should warrant some more attention. =20 > Having unsafe serial terminal support that can bring down your system =20 > like that defies much of the point of having serial terminal support =20 > in the first place. >=20 > However, since I seem to be the only one who has noticed this, =20 > perhaps I'm the last person on earth to routinely use serial terminal =20 > switches instead of KVM switches to do my admin work? Nope, I use them a lot as well, but only if there are problems. Why would you login on a serial console if there's ssh ;-) So that would explain why I haven't seen the issue yet. Do you have a debugger trace ? It seems very similar to my last remaining issue (http://www.stack.nl/~marcolz/FreeBSD/showstoppers.html), namely http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/83375 i.e. someting going wrong in pty cloning and cleanup... Marc --jho1yZJdad60DJr+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC32iaezjnobFOgrERAho7AJ4z6glZr8heXPaEG92rcJGQNhkxCwCeKiPV OxV0Zar4ThpR9edLs7YAzVo= =mqfV -----END PGP SIGNATURE----- --jho1yZJdad60DJr+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050721091922.GB52120>