Re: 715/50 experience

Hi,

have not found a solution yet, but I have some questions below.

> sti: hpa=f4000000, rom=f4000000
> sti: romh=f4000000
> sti: devtype=1
> sti0 at mainbus0 offset 4000000 irq 11sti: hpa=f4000000, rom=f4000000
> sti: ioh=f4000000, romh=f4000000
> dd:
> devtype=1, rev=82;10, altt=0, gid=9299000000000000, font=ff50, mss=a0
> end=1efd4, regions=fef0, msto=0, timo=100, mont=0, user=0[0]
> memrq=0, pwr=0, bus=0, ebus=0, cfb=0
> code=300,3650,5b00,8970,9f40,ef10,f840,fef0,0,0,0,0,0,0,0,0
> code=0xc8566000[3efc]

AFAIKT, these values make sense. The code that reads the values nicely
follows the sti manual.

A question: in most cases the byte rom is read with a
bus_space_read_1(), and sometimes (when copying the code from the rom)
with a bus_space_read_4() and throwing away the three upper
bytes. Why?

> stiregions @0xfef0:
> 3f000 @ 0xf4000000
> 1000000 @ 0xf5000000 btlb
> already mapped region
> 280000 @ 0xf4100000
> already mapped region
> 1000 @ 0xf403f000
> already mapped region
> 1000 @ 0xf4380000 sys last
> already mapped region

These values correspond to a log mickey@ sent me. But note the last
regions's address and size.

> sti0: init,0xc8566000(86000000, 0x4af910, 0x4af918, 0xc012412c)
> panic: trap: uvm_fault(0x40df98, f4380004, 0, 1): 14

The fault address is f4380004, which is within the last region. So my
hypothesis is that the init code accesses the last region, which isn't
mapped correctly for some reason.

Does this analysis make any sense?


	 -Otto

> Stopped at      Debugger+0x18:  break   0,5
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> ddb> trace
> Debugger(2d7a80,f0823800,5,468000) at Debugger+0x18
> panic(31da78,40df98,f4380004,0) at panic+0xf8
> panic(3008dc,1,5,4677b0) at panic+0xdc
> trap(0,0,ffffffff,64) at trap+0x7dc
> -- trap #15
> end(2a52b8,4af708,2ced80,467ef8) at 0xc8566054
> sti_init(panic: trap: uvm_fault(0x40df98, 85ffffdc, 0, 1): 14
> Stopped at     Debugger+0x18:  break   0,5