Re: Which kernel for Lemote Yeeloong?

On Thu, Dec 01, 2011 at 06:41:33PM -0600, John D. Baker wrote:
> On Fri, 18 Nov 2011, Manuel Bouyer wrote:
> 
> >The first thing to do is to try a kernel built with
> >options LOW_DEBUG
> 
> I built a kernel with the following config:
> 
> ----------
> # YEELOONG - debug kernel for Lemote YeeLoong 8101b netbook
> 
> include 	"arch/evbmips/conf/LOONGSON"
> no options 	INCLUDE_CONFIG_FILE
> options 	INCLUDE_JUST_CONFIG
> 
> #ident YEELOONG - JDB 30 Nov 2011
> 
> options 	LOW_DEBUG
> ----------
> 
> And booted as follows (hand-transcribed from YeeLoong LCD console):
> 
> ----------
> BEV in SR set to zero.
> PMON> ifaddr rtl0 192.168.17.30
> bootp=8000b968
>  100Mbps FULL-DUPLEX.
> PMON> boot -k tftp://192.168.17.43/netbsd-YEELOONG
> Loading file: tftp://192.168.17.43/netbsd-YEELOONG (elf)
> (elf)
> 0x80200000/4034576 + 0x805d9010/158504(z) + 13974 syms\
> Kernel debugger symbols ELF hdr @ 0x805ffb40
> pmon hello
> hello 0x8009c2b8 2 0xaff7fd30 0xaff7fd3c 0x0 stack 0xffffffff801fff60
> ssym 0xffffffff805ffb40 esym 0xffffffff80689908
> mips_vector_init uvm_setpagesize
> Found Lemote Yeeloong, setting up.
> memlo 256memhi 768
> bonito_pci_init bonito_bus_init bonito_bus_mem_init
> sys_platform->setup 0x0
> comconsrate 0
> dev 0 class 0xffffffff id 0xffffffff; dev 1 class 0xffffffff id 0xffffffff; dev 2 class 0xffffffff id 0xffffffff; dev 3 class 0xffffffff id 0xffffffff; dev 4 class 0xffffffff id 0xffffffff; dev 5 class 0xffffffff id 0xffffffff; dev 6 class 0xffffffff id 0xffffffff; dev 7 class 0x2000010 id 0x813910ec; dev 8 class 0x30000b0 id 0x712126f; dev 9 class 0xc0e1044 id 0x351033; dev 10 class 0xffffffff id 0xffffffff; dev 11 class 0xffffffff id 0xffffffff; dev 12 class 0xffffffff id 0xffffffff; dev 13 class 0xffffffff id 0xffffffff; dev 14 class 0xff000003 id 0x208f1022;
> search cpuclock got 796980000 cpuclock 796980000
> phys segment: 0x3f974000 @ 0x8068c000
> adding 0x3f974000 @ 0x8068c000 to freelist 0
> mips_init_msgbuf
> pmap_bootstrap
> pmap_steal_memory: seg 0: 0x201a3 0x201a3 0x2ffff 0x2ffff
> curlwp 0xffffffff805cb2a0 curlwp stack 0x0
> pmap_steal_memory: seg 0: 0x201b8 0x201b8 0x2ffff 0x2ffff
> curlwp 0xffffffff805cb2a0 curlwp stack 0x98000000806e0000
> return
> * <- random garbage character, (small circle over center bar in this case).
> [hung]

At this point is should have called main().
The next step would be to add printf() calls in main() (sys/kern/init_main.c)
to see exactly where it hangs (and if main() is called at all).

-- 
Manuel Bouyer <[email protected]>
     NetBSD: 26 ans d'experience feront toujours la difference
--