Date: Mon, 5 Mar 2007 21:20:15 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: Peter Losher <plosher@plosh.net>, freebsd-stable@freebsd.org Subject: Re: 'panic: bad pte' error on 6.2-RELEASE (amd64) Message-ID: <20070305192015.GL10453@deviant.kiev.zoral.com.ua> In-Reply-To: <20070305182522.P21692@ury.york.ac.uk> References: <45EBCF4C.9000901@plosh.net> <20070305100237.GI10453@deviant.kiev.zoral.com.ua> <20070305182522.P21692@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--QxIEt88oQPsT6QmF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 05, 2007 at 06:28:30PM +0000, Gavin Atkinson wrote: > On Mon, 5 Mar 2007, Kostik Belousov wrote: >=20 > >On Mon, Mar 05, 2007 at 12:05:32AM -0800, Peter Losher wrote: > >>We recently updated one of our dual Opteron systems (w/ 4GB RAM) from > >>5.5 to 6.2 (amd64 wipe and reinstalled) and about once a week, it panics > >>with the below message: > >> > >>-=3D- > >>TPTE at 0xffff8000040028a0 IS ZERO @ VA 800514000 > >>panic: bad pte > >>cpuid =3D 2 > >>KDB: stack backtrace: > >>panic() at 0xffffffff803fdd03 =3D panic+0x253 > >>pmap_remove_pages() at 0xffffffff806072a3 =3D pmap_remove_pages+0x283 > >>exec_new_vmspace() at 0xffffffff803e18e6 =3D exec_new_vmspace+0x216 > >>exec_elf64_imgact() at 0xffffffff803cbb73 =3D exec_elf64_imgact+0x273 > >>kern_execve() at 0xffffffff803e2107 =3D kern_execve+0x457 > >>execve() at 0xffffffff803e2bed =3D execve+0x5d > >>syscall() at 0xffffffff8060d141 =3D syscall+0x4d1 > >>Xfast_syscall() at 0xffffffff805f8128 =3D Xfast_syscall+0xa8 > >>--- syscall (59, FreeBSD ELF64, execve), rip =3D 0x80069838c, rsp =3D > >>0x7fffffffe7c8, rbp =3D 0x7fffffffecd0 --- > >>Uptime: 4d16h55m46s > >>-=3D- > >> > >>I do have a dump, and can make that available if need be. Has anyone > >>encountered this recently and can shed any light on what might be > >>causing this? > > > >Did rev. 1.516.2.9 of sys/amd64/amd64/pmap.c changed (or even fixed) the > >problem ? (This is the same patch I already sent you). >=20 > Do you know if this patch is likely to fix the other "bad pte" panics tha= t=20 > have been seen (usually during process exit())? e.g. >=20 > http://docs.freebsd.org/cgi/mid.cgi?1148482556.35287.18.camel > http://lists.freebsd.org/pipermail/freebsd-current/2004-August/034909.html Yes, the problem there seems to be fixed by Tor' commit into the i386/pmap.c at the 2006/02/16. My commit is MFi386 of the fix to the amd64. > I have a couple of amd64 machines I'm reluctant to make live until this i= s=20 > sorted... I'll cvsup in the next day or two to see, although it wasn't= =20 > consistantly reproduceable. I am interested in testing results. --QxIEt88oQPsT6QmF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF7G1uC3+MBN1Mb4gRAgk4AKCKcxq22dasjej4bnzdCodwv0L1JQCeIPoJ aji59nYt++5hjT4YFomDx+M= =e+/8 -----END PGP SIGNATURE----- --QxIEt88oQPsT6QmF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070305192015.GL10453>