From owner-freebsd-alpha Tue May 18 2:11:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from gate.keisu.t.u-tokyo.ac.jp (ns06.t.u-tokyo.ac.jp [133.11.68.1]) by hub.freebsd.org (Postfix) with SMTP id 429E4155AB for ; Tue, 18 May 1999 02:11:23 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: (qmail 12326 invoked from network); 18 May 1999 09:11:22 -0000 Received: from sylph.sat.t.u-tokyo.ac.jp (10.6.1.20) by ns06.t.u-tokyo.ac.jp with SMTP; 18 May 1999 09:11:22 -0000 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by sylph.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id C64312DAAA; Tue, 18 May 1999 18:11:21 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp by ett.sat.t.u-tokyo.ac.jp (8.9.3/sat-V0.6) id SAA09204; Tue, 18 May 1999 18:11:20 +0900 (JST) Date: Tue, 18 May 1999 18:11:19 +0900 Message-ID: <14145.11959.719375.15587A@ett.sat.t.u-tokyo.ac.jp> From: Hidetoshi Shimokawa To: dfr@nlsystems.com Cc: jdp@polstra.com, alpha@freebsd.org Subject: Re: Panic: warning: pmap_changebit didn't. In-Reply-To: In your message of "Tue, 18 May 1999 09:30:14 +0100 (BST)" References: <14144.54192.153726.48298X@ett.sat.t.u-tokyo.ac.jp> User-Agent: Wanderlust/0.10.0 (Got My Mind Set On You) SEMI/1.13.2 (Mikawa) FLIM/1.12.5 (Hirahata) MULE XEmacs/21.2 (beta13) (Demeter) (i386-unknown-freebsd3.1) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX wrote: > > On Tue, 18 May 1999, Hidetoshi Shimokawa wrote: > > > I get same panic now (current of yesterday). > > > > panic: warning: pmap_changebit didn't. > > panic > > Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe000ce0bbe0> > > > > db> trace > > Debugger() at Debugger+0x2c > > panic() at panic+0xfc > > pmap_emulate_reference() at pmap_emulate_reference+0x120 > > trap() at trap+0x2b0 > > XentMM() at XentMM+0x20 > > swapout_procs() at swapout_procs+0x174 > > (null)() at 0 > > > > I can generate crash dump, but it must be more than 500MB. > > I'll leave it in DDB for while. If you have something to examine, > > let me know. > > It would be useful to find out the values of pa, *pte and faultoff. > Unfortunately I cannot use gdb now. db> gdb No gdb port enabled. Set flag 0x80 on desired port in your configuration file (currently sio only). Last time, I was able to use gdb with the flag 0x50. I found the following code in /sys/isa/sio.c #ifdef __i386__ #if DDB > 0 gdbdev = makedev(CDEV_MAJOR, unit); gdb_getc = siocngetc; gdb_putc = siocnputc; #endif #endif Can I use gdb on alpha with flag 0x80? I give up to use gdb via serial and get the crash dump. But stock gdb seems not to understand crash dump yet. root@achat:/export/home/crash# gdb kernel.debug.13 vmcore.13 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd"... "/export/home/crash/vmcore.13" is not a core dump: File format not recognized (gdb) -- /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message