Re: Someone broke diskless booting

It's not obvious to me how this happened, but binary searching narrows
down the cause to the following commit:

jhb         2007-02-23 19:46:59 UTC

  FreeBSD src repository

  Modified files:
    sys/kern             kern_linker.c
  Log:
  Drop the global kernel linker lock while executing the sysinit's for a
  freshly-loaded kernel module.  To avoid various unload races, hide linker
  files whose sysinit's are being run from userland so that they can't be
  kldunloaded until after all the sysinit's have finished.

  Tested by:      gallatin

  Revision  Changes    Path
  1.145     +21 -15    src/sys/kern/kern_linker.c

Kris

On Sun, Feb 25, 2007 at 06:33:33PM -0500, Kris Kennaway wrote:
> Some time in the past week or so someone committed a change to the
> kernel that broke diskless booting:
> 
> Trying to mount root from nfs:
> fxp0: link state changed to UP
> NFS ROOT: 69.147.83.43:/a/nfs/7.dir1
> Interface fxp0 IP-Address 69.147.83.96 Broadcast 69.147.83.127
> mdmfs: mdconfig (attach) exited with error code 1
> cp: /etc/gss/mech: Read-only file system
> cp: /etc/gss/qop: Read-only file system
> cp: utimes: /etc/gss: Read-only file system
> cp: /etc/ppp/ppp.conf: Read-only file system
> ...
> nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
> nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
> nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
> 
> Kris
>