From owner-freebsd-ia64 Wed Apr 18 7:36:50 2001 Delivered-To: freebsd-ia64@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 8B97137B422; Wed, 18 Apr 2001 07:36:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 14pt4U-000KPj-0Y; Wed, 18 Apr 2001 15:36:42 +0100 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f3IEZQ785580; Wed, 18 Apr 2001 15:35:26 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 18 Apr 2001 15:35:26 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: John Baldwin , , Subject: RE: Need some help w/ia64 :) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Apr 2001, John Baldwin wrote: > > On 13-Apr-01 John Baldwin wrote: > > At the moment ia64 kernels on -current panic in the pmap code. I'd like to > > get > > a backtrace in ddb, but I can't seem to be able to send input to the console. > > I was curious if that worked at all or is known to be broken. I also recall > > Dough saying that ski engaged in some Linux stupidness with respect to the > > tty's that he had to work around. Unfortunately, I can't seem to find an > > e-mail with the actual workaround in it, so I'd appreciate any pointers > > people > > have. Also, I've noticed that once I start the kernel going, ski is > > basically > > unresponsive after the kernel panics. None of the windows update if I move > > them around, no mouse events, etc. Also, if anyone knows how to fix this > > panic > > (dmesg below) that would be great as well. :) > > Well, I've managed to do enough quirky things to kick the console into a usable > mode, but trying to do a 'trace' gives a SSC breakpoint. At this point I > checked the code to discover: > > void > db_stack_trace_cmd(db_expr_t addr, boolean_t have_addr, db_expr_t count, char *m > odif) > { > } > > Hmm, guess that still needs to be implemented. :-P I just committed something. The linux bootloader doesn't load symbols (big surprise) but you can make pretty good sense of the stack frame. I might even be able to figure out how to print the arguments too. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message