Trouble with IBM RS/6000 43P-140

Jochen Kunz <[email protected]>
Newsgroups gmane.os.netbsd.ports.prep
Message-ID <[email protected]>
Hi.

I have some 43P-140 machines. I tried to netboot one but the machine
refused to load the boot image. I tried the sysinst and the generic
kernel image. The images are build from -current about a week old.

23:38:36.456322 0.0.0.0.68 > 255.255.255.255.67:  xid:0x25a81c secs:2467
[|bootp]
23:38:36.457614 192.168.2.14.67 > 192.168.2.9.68:  xid:0x25a81c
secs:2467 Y:192.168.2.9 S:192.168.2.14 [|bootp] [tos 0x10] 
23:38:36.466266 arp who-has 192.168.2.14 tell 192.168.2.9
23:38:36.466399 arp reply 192.168.2.14 is-at 8:0:20:b3:23:15
23:38:37.060835 192.168.2.9.4698 > 192.168.2.14.69:  24 RRQ
"sysinst_com0.fs"
23:38:37.206240 192.168.2.14.65063 > 192.168.2.9.4698: udp 516
23:38:42.211925 192.168.2.14.65063 > 192.168.2.9.4698: udp 516
23:38:47.221648 192.168.2.14.65063 > 192.168.2.9.4698: udp 516
23:38:52.231422 192.168.2.14.65063 > 192.168.2.9.4698: udp 516

I tried to load the image via floppy but the kernel crashed very early
in startup:
>> NetBSD/prep BOOT, Revision 1.5
>> (build@Zimbo, Wed Nov 17 21:52:37 CET 2004)

Boot: Loading in()
2827048+356524 [170544+153126]=0x358730
start=0x100000

panic: lockmgr: no context
Stopped at      0x2f3e80:       lwz     r0, r1, 0x14
db> bt
0x00462b20: at 0x2652c4
0x00462bb0: at 0x244514
0x00462be0: at 0x2e03e8
0x00462c00: at 0x2df11c
0x00462d30: at 0x2f97e0
0x00462db0: kernel DSI read trap @ 0xfefe0080 by 0x2f137c: srr1=0x1032
            r1=0x462e70 cr=0x42004082 xer=0 ctr=0x336c40
dsisr=0x40000000
0x00462e70: at 0x18ff94
0x00462e80: at 0x1c1ffc
0x00462ea0: at 0x2fb004
0x00462f00: at 0x2fd454
0x00462f30: at 0x100078
db> 

Is someone successfully running NetBSD on a 43P-140?
Any ideas about net booting? It is quite hard to debug a crashing kernel
when I have to write a boot floppy for every boot attempt.
-- 


tschüß,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.