Port-pmax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Is pmax alive?



Am 05.03.2016 um 23:53 schrieb Tobias Nygren:
Boot: 0/rz0/netbsd
4241136+131984 [236752+233661]=0x49ee94
Starting at 0x80030000

segment  0 start 00000000 size 04800000
segment  1 start 06000000 size 00800000
phys segment: 0x4800000 @ 0
adding 0x32f000 @ 0x4d1000 to freelist 1
adding 0x4000000 @ 0x800000 to freelist 0
phys segment: 0x800000 @ 0x6000000
adding 0x800000 @ 0x6000000 to freelist 0
pmap_steal_memory: seg 0: 0x4d1 0x4d1 0x800 0x800
pid 0(system): trap: cpu0, address error (load or I-fetch) in kernel mode
status=0x80010, cause=0x30000010, epc=0x8000001c, vaddr=0xdeadbeef
tf=0x804d0cf0 ksp=0x804d0d90 ra=0x80174df4 ppl=0
kernel: address error (load or I-fetch) trap
Stopped in pid 0.1 (system) at  8000001c:       lw      k1,0(k1)
db>

That is also what I found in the mailing list archive for a 5000/25 and a 5000/240 (screenshot):

http://mail-index.netbsd.org/port-pmax/2014/03/03/msg000158.html
http://mail-index.netbsd.org/port-pmax/2014/05/13/msg000165.html

Following the first thread, it was suggested that pmax is broken since MIPS64 merge (so even NetBSD 6.x was/is broken)...

It would be great if this long-standing issue could be fixed finally, our DEC machines deserve it! :)

Felix


Home | Main Index | Thread Index | Old Index