installkernel succeeds, but old kernel boots

From: Paco Hope (freebsd-stable_at_filter.paco.to)
Date: 04/21/05

  • Next message: Peter Jeremy: "Re: Deadlock in 5.3p5"
    Date: Thu, 21 Apr 2005 02:41:46 -0400 (EDT)
    To: freebsd-stable@freebsd.org
    
    

    I cvsupped the latest RELENG_5 sources and did make buildworld. Then I
    built and installed the kernel using

    make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=PACO
    make -DALWAYS_CHECK_MAKE installkernel KERNCONF=PACO

    Then I rebooted. So far so good. This is all normal. However, after I
    reboot and run 'uname -a' I see:

    FreeBSD www.provisio.net 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Sat Mar
    19 01:28:39 EST 2005 root@www.provisio.net:/usr/obj/data/src/sys/PACO
    i386

    sysctl agrees with uname:

    kern.ostype: FreeBSD
    kern.osrelease: 5.3-RELEASE-p5
    kern.osrevision: 199506
    kern.version: FreeBSD 5.3-RELEASE-p5 #0: Sat Mar 19 01:28:39 EST 2005
        root@www.provisio.net:/usr/obj/data/src/sys/PACO

    That's my old kernel that I was trying to replace. I run 'sysctl
    kern.bootfile' and it says '/boot/kernel/kernel' so I'm a little confused.
    By all indications, the file that's currently in /boot/kernel/kernel is
    5.4-STABLE. I can run 'strings' on /boot/kernel/kernel and see this near
    the bottom:

    FreeBSD 5.4-STABLE #0: Thu Apr 21 00:04:21 EDT 2005
        root@www.provisio.net:/usr/obj/data/src/sys/PACO
    FreeBSD
    5.4-STABLE
    PACO

    It sure looks like I booted my old kernel somehow, but I can't figure out
    how. It seems unlikely that I somehow installed from a stale build tree
    because I newfs'd /usr/obj before building anything.

    Thoughts?

    Thanks,
    Paco

    p.s. the system is in a colo facility 2200 miles from my current location.
    I can't go to the console and watch it boot. I've done remote upgrades
    from source in the past without trouble.
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: Peter Jeremy: "Re: Deadlock in 5.3p5"

    Relevant Pages

    • 6.1 kernel unable to find /dev ?
      ... the previously-good kernel would no longer ... | exec /sbin/oinit: error 20 ... | Automatic reboot in 15 seconds - press a key on the console to abort ... Should I perhaps to a make installkernel installworld ...
      (freebsd-stable)
    • RE: Upgrading 4.11-STABLE to 5.4-STABLE
      ... >> after my installkernel. ... If the kernel boots OK into single-user ... that successfully, then reboot the system and it fails, there is no way ... I just got familiar with portaudit a few weeks ago, ...
      (freebsd-questions)
    • RE: make world : did it fail?
      ... I know from the script output that the buildworld and buildkernel succeeded. ... The only step that is suspect is the installkernel. ... It reported the unpatched kernel. ... When I heard the computer reboot (it's sitting ...
      (freebsd-questions)
    • Re: 6.1 kernel unable to find /dev ?
      ... I saw two types of panics ... | Automatic reboot in 15 seconds - press a key on the console to abort ... Or there is a bad kernel module in the mix that is randomly corrupting data. ... Should I perhaps to a make installkernel installworld ...
      (freebsd-stable)
    • Re:SOLVVED vinum crashes the Box... WRONG POSTING
      ... vinum crashes the Box by using more then ten disks on ... > With this configuration vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger now... ... >> while devfs rules works for those, but they vanish on reboot. ...
      (freebsd-stable)