Re: [hatari-devel] NetBSD loader for Hatari

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

ATARITT and FALCON variants of NetBSD v8.2 do not double bus error with 
the NetBSD loader core, but they still panic before NetBSD outputs any 
text on screen:
- 1. 0x013e8a: db_readline -0x880c4 (cngetc +0x2)
- 2. 0x09c754: db_read_line +0xe
- 3. 0x09b1a0: db_command_loop +0xe2
- 4. 0x09e4f0: db_trap +0xe8
- 5. 0x022046: kdb_trap +0xaa
- 6. 0x0024b0: trap15 +0x4a (Lbrkpt2 +0x8)
- 7. 0x0220b8: db_panic -0x7b03c (cpu_Debugger +0x4)
- 8. 0x1555aa: vpanic +0x15e
- 9. 0x1555c6: panic +0xc
- 10. 0x10d53a: uvm_page_physload +0x5a
- 11. 0x018032: pmap_bootstrap +0xb2
- 12. 0x014894: start_c +0x714
- 13. 0x0028bc: kernel_text +0x28bc (Lend_cpuset +0x18)

Replacing GEMDOS HD with a blank floppy + 64MB IDE drive does not change 
anything.


	- Eero

On 25.8.2022 3.08, Eero Tamminen wrote:
> On 22.8.2022 8.21, Thorsten Otto wrote:
> > On Sonntag, 21. August 2022 18:12:31 CEST Eero Tamminen wrote:
> > > Now that release is done, I could commit your patch series.  Do you have
> > > a newer version of it?
> >
> > No, the 6 patches i posted are still the current ones.
>
> Should they work?
>
> With Hatari v2.4.1 I get double bus error before there's any screen 
> output, i.e. much earlier than by using loadbsd.ttp:
> ------- netbsd.cfg: ----------
> Kernel = netbsd-SMALL030.gz
> Args = -b -D -s
> ------- profile.ini: ---------
> history on
> profile on
> ------------------------------
> $ hatari --parse profile.ini -c netbsd.cfg --netbsd --monitor vga 
> --machine falcon --dsp none --mmu on -s 14 .
> NetBSD: kernel_phdrs[0].p_vaddr  = 0x00000000
> NetBSD: kernel_phdrs[0].p_offset = 0x00000080
> NetBSD: kernel_phdrs[0].p_filesz = 0x0017827c
> NetBSD: kernel_phdrs[0].p_memsz  = 0x00189ec8
> NetBSD: Copying segment 0: 0x00000080,0x0017827c to 0x00002000-0x0017a27c
> NetBSD: Copying symbol strings: 0x001c4d87,0x000000d3 to 
> 0x0018c1cc-0x0018c29f
> NetBSD: Copying symbol table: 0x0017eaf8,0x00024db0 to 
> 0x0018c2a0-0x001b1050
> NetBSD: Copying symbol strings: 0x001a38a8,0x000214df to 
> 0x001b1050-0x001d252f
> Loaded 8880 symbols (6374 TEXT) from 'kernel'.
> Machine info:
> ST-RAM size    :   14680064 bytes
> TT-RAM size    :          0 bytes
> TT-RAM start    : 0x01000000
> Cpu-type    : 0x00001008
> Kernel loadaddr    : 0x00002000
> Kernel size    :    1901872 (0x1d0530) bytes
> Kernel entry    : 0x00002672
> Kernel esym    : 0x001d0530
> Reading debugger commands from 'profile.ini'...
>  > history on
> Re-allocating & zeroing history due to type/limit change.
> History tracking enabled for CPU & DSP (max. 64 instructions).
>  > profile on
> Profiling enabled.
> Allocated CPU profile buffer (113 MB).
> Allocated CPU profile callsite buffer for 6374 symbols.
> WARNING: previous PC for tracked address 0x0 is undefined!
> WARNING: 'invalid' CPU PC profile instruction address 0xe00002!
> WARNING: subroutine call returned through 2 stack frames: 0x12c30 -> 
> 0x102e4!
> WARNING: 'invalid' CPU PC profile instruction address 0xe00000!
> WARNING: 'invalid' CPU PC profile instruction address 0xe00002!
>
> You have entered debug mode. Type c to continue emulation, h for help.
> Finalizing costs for 8 non-returned functions:
> - 1. 0x000004: doboot -0x2adc (kernel_text +0x4)
> - 2. 0x012b22: cpu_reboot +0x84
> - 3. 0x0b82c8: vpanic +0x152
> - 4. 0x0b82da: panic +0xc
> - 5. 0x07bb7a: uvm_page_physload +0x78
> - 6. 0x013910: pmap_bootstrap +0xb0
> - 7. 0x0106a8: start_c +0x488
> - 8. 0x002754: kernel_text +0x2754 (Lend_cpuset +0x18)
> -------------------------------
>
>
>      - Eero