Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: amd64 kernel doesn't boot
On Fri, Oct 02, 2009 at 08:04:05AM +0100, Nick Hudson wrote:
> On Thursday 01 October 2009 23:22:12 Kurt Schreiner wrote:
> > Hi,
> >
> > kernels compiled from -current sources updated an hour or so ago don't
> > boot. Just print "123456-" (don't have the exact numbers) and than just sit
> > there doing nothing (install-kernel tried in newest VirtualBox - yes,
> > NetBSD runs as guest in VB 3.0.6 on 64bit-Solaris!) or reboot the system
> > (custom kernel tried on Sun Ultra40).
>
> Did you do used build.sh or re-run config to build the kernel that doesn't
> boot? Can you post the link line?
Used build.sh on both machines with cleaned out obj,dest,TOOLS, first rebuild
TOOLS and distribution. Then compiled a new kernel:
===> build.sh command: ./build.sh -u -N 1 -j 12 -x -U -m amd64 -O
/u/NetBSD/arch/amd64/obj -D /u/Net
BSD/arch/amd64/dest -T /u/NetBSD/arch/amd64/TOOLS kernel=/var/home/ks/NBconf/U40
===> build.sh started: Thu Oct 1 18:17:48 MEST 2009
===> NetBSD version: 5.99.19
===> MACHINE: amd64
===> MACHINE_ARCH: x86_64
===> Build platform: NetBSD 5.99.16 amd64
===> HOST_SH: /bin/sh
===> TOOLDIR path: /u/NetBSD/arch/amd64/TOOLS
===> DESTDIR path: /u/NetBSD/arch/amd64/dest
===> RELEASEDIR path: /u/NetBSD/arch/amd64/obj/releasedir
===> makewrapper: /u/NetBSD/arch/amd64/TOOLS/bin/nbmake-amd64
===> Updated /u/NetBSD/arch/amd64/TOOLS/bin/nbmake-amd64
===> Building kernel without building new tools
===> Building kernel: /var/home/ks/NBconf/U40
===> Build directory: /u/NetBSD/arch/amd64/obj/sys/arch/amd64/compile/U40
Build directory is /u/NetBSD/arch/amd64/obj/sys/arch/amd64/compile/U40
> What's the output of readelf -l of that kernel?
>-1014: readelf -l /netbsd
Elf file type is EXEC (Executable file)
Entry point 0xffffffff80100000
There are 1 program headers, starting at offset 64
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000000 0xffffffff80000000 0xffffffff80000000
0x00000000005c79c0 0x00000000006545a0 RWE 200000
Section to Segment mapping:
Segment Sections...
00 .text .rodata .eh_frame link_set_malloc_types link_set_modules
link_set_sysctl_funcs link_set_bufq_strats link_set_evcnts
link_set_dkwedge_methods link_set_domains link_set_prop_linkpools .data .bss
And here's the readelf -l from the old kernel running now:
>-1013: readelf -l /onetbsd
Elf file type is EXEC (Executable file)
Entry point 0xffffffff80100000
There are 2 program headers, starting at offset 64
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000100000 0xffffffff80100000 0xffffffff80100000
0x00000000003a0d00 0x00000000003a0d00 R E 100000
LOAD 0x00000000004a1000 0xffffffff805a1000 0xffffffff805a1000
0x000000000001b7a0 0x00000000000a80e0 RW 100000
Section to Segment mapping:
Segment Sections...
00 .text .rodata .eh_frame link_set_malloc_types link_set_modules
link_set_sysctl_funcs link_set_pools link_set_bufq_strats link_set_evcnts
link_set_dkwedge_methods link_set_domains
01 .data .bss
Just looked at the other older kernels lying around: All have two "LOAD"s,
like the running one...
Thanks
Kurt
Home |
Main Index |
Thread Index |
Old Index