9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cblack1@uiuc.edu
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Alpha bootloader "kernel stack not valid"
Date: Thu, 23 Feb 2006 01:30:07 -0600	[thread overview]
Message-ID: <20060223073007.GA32767@slash.bytex64.net> (raw)
In-Reply-To: <a7e95fe7b48ffdfb3bc9718c2055018c@collyer.net>

On Wed, Feb 22, 2006 at 10:57:10PM -0800, geoff@collyer.net wrote:
> There are several memmoves in that vicinity; could you show us the
> line and some surrounding context?

Sure. From /sys/src/boot/alphapc/bootp.c, in bootp(), near the bottom:

	addr = (uchar*)entry;
	p = tftpb.data+sizeof(Exec);
	dlen -= sizeof(Exec);
	segsize = text;
	for(;;){
		if(dlen == 0){
			if((dlen = tftpread(fd, &server, &tftpb, sizeof(tftpb.data))) < 0)
				return -1;
			p = tftpb.data;
		}
		if(segsize <= dlen)
			i = segsize;
		else
			i = dlen;
		//print("addr: %lux p: %lux i: %d\n", addr, p, i);
		//print("addr[0]: ");
		//print("%x\n",addr[0]);
		memmove(addr, p, i);

That last one is the offending memmove. With those print()'s
uncommented, the first two show up, but the third doesn't.

> "kernel stack not valid halt" is coming from SRM, right?

Yep. Looks like this:

yomiko (10.0.0.12!67): /alpha/conf/10.0.0.14.../alpha/9apc
659416
halted CPU 0

halt code = 2
kernel stack not valid halt
PC = 283bebeb8dfb08cc
>>>

Yomiko is running the tftp server, and I've successfully used tftp to
start up the netbsd net loader and the debian install image.

> I'm surprised that your alpha didn't come with a 2114x, and that SRM's
> bootp/tftp loader can drive any other kind of ethernet card.  Does
> your 82559 have PXE enabled or have the additional chip added with
> bootp and tftp boot burned into it (there's a socket for it on most
> ethernet cards)?

Well, it wasn't actually an alpha *machine*. I found the mobo/CPU in a
box of other dilapidated hardware a few years ago, and recently came
upon some RAM that works with it. Much to my surprise, it booted. I was
completely surprised that the Intel card worked with it, too. I'm not
sure about the PXE or netboot rom; I'm not sure I've ever tried this
card elsewhere. It has no socket, but does have an Atmel chip soldered
to it. (None of that would work with SRM, anyway, would it?) It shows up
as eia0 instead of ewa0, but works the same. It looks like this:

http://www.pluto.ai.kyutech.ac.jp/plt/matumoto/bench/oldpc/fxp.jpg

~chip


  reply	other threads:[~2006-02-23  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  4:55 cblack1
2006-02-23  6:57 ` geoff
2006-02-23  7:30   ` cblack1 [this message]
2006-02-23  8:15     ` geoff
2006-02-23  9:19       ` cblack1
2006-02-23  9:40         ` geoff
2006-02-23  9:48           ` cblack1
2006-02-23 16:25       ` LiteStar numnums

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060223073007.GA32767@slash.bytex64.net \
    --to=cblack1@uiuc.edu \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).