Re: Hang while PXE booting todays -current

On Fri, 2 May 2003, Blaz Zupan wrote:

> Is anybody else having trouble PXE booting -current as of today? I had a
> working test setup where my laptop was PXE booted off of my -current
> desktop box. The test setup was running yesterdays -current. Then I made
> world today and now it hangs at the point it should start executing
> /sbin/init. 

I seem to be booting OK, but I need to check to see which PXE boxes are
using which kernels.

<...>
> And here it hangs forever. I tried breaking into DDB. Doing a "trace" shows
> this:
> 
> Debugger(c051dd90,4,1,0,1) at Debugger+0x54
> scgetc(c05f5120,2,80296,c05a49e8,c2635280) at scgetc+0x445
> sckbdevent(c05f900,0,c05f5120,c059faa0,8) at sckbdevent+0x1e0
> atkbd_intr(c05cf900,0,cccaad0c,c0305ba2,c05cf900) at atkbd_intr+0x2c
> atkbd_isa_intr(c05cf900,0,c050409c,218,c26381e0) at atkbd_isa_intr+0x21
> ithread_loop(c25e5180,cccaad48,c0503f4f,310,70020400) at ithread_loop+0x182
> fork_exit(c0305a20,c25e5180,cccaad48) at fork_exit+0xc0
> fork_trampoline() at fork_trampoline+0x1a
> --- trap 0x1, eip = 0, esp = 0xcccaad7c, ebp = 0 ---

This is the stack trace of the interrupt thread for the keyboard handler. 
What you want to do is type in "trace 1" to see what init is doing.  Also,
the output of the ddb ps command would be useful.

> Also, earlier in the boot, I see this:
> 
> malloc() of "4096" with following non-sleepablelock held:
> exclusive sleep mutex ifnet r = 0 (0xc05c79c0) locked _at_ nfsclient/bootp_subr.c:1696
> 
> The kernel is GENERIC with options BOOTP, BOOTP_NFSROOT and BOOTP_COMPAT
> added.

I can do PXE using GENERIC without any special options -- do you need the
options?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert_at_fledge.watson.org      Network Associates Laboratories