Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Oct 2013 21:23:06 +1000
From:      John Marshall <john.marshall@riverwillow.com.au>
To:        freebsd-stable@freebsd.org
Subject:   Re: 9.2-RC4 amd64 panic: vm_page_unwire
Message-ID:  <20131001112305.GA8408@rwpc15.gfn.riverwillow.net.au>
In-Reply-To: <20130930095507.GD2813@rwpc15.gfn.riverwillow.net.au>
References:  <20130927000728.GB19167@rwpc15.gfn.riverwillow.net.au> <20130927081221.GK41229@kib.kiev.ua> <20130928023046.GA1428@rwpc15.gfn.riverwillow.net.au> <CAPjTQNF8R8_krK6P0QRmbd9crLZM%2B2uwKZwWUxOFkdANPGC1hw@mail.gmail.com> <20130929212104.GB1370@rwpc15.gfn.riverwillow.net.au> <CAPjTQNGt9BY8pNC=y4om6v3bEfGmGTFZDj57DbjZi=nUzYu=iA@mail.gmail.com> <20130930095507.GD2813@rwpc15.gfn.riverwillow.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help

--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, 30 Sep 2013, 19:55 +1000, John Marshall wrote:
> Another data point: both systems on which I have seen this panic have
> the ipmi driver compiled in.  ipmi makes the BMC's watchdog timer
> available to the system.

So, I decided to revert my source tree to a clean releng/9.2
(9.2-RELEASE) and recompile without the ipmi driver (so there goes the
watchdog timer too), and see how the system behaved.  I was able to stop
and start ntpd without mishap.  If ntpd was not running, the system
would reboot cleanly.  If ntpd was running, the system would panic
during shutdown - vm_page_unwire - while stopping ntpd.

I decided to switch my source tree back to releng/9.1 (9.1-RELEASE-p7),
rebuild, and test.  Booted into the 9.1 kernel in single-user, installed
the 9.1 world, make delete-old, decided to skip mergemaster (why??!!);
reboot; and it wouldn't :-/

  menuset-loadinitial not found
  Consoles: internal video/keyboard
  BIOS drive C: is disk0
  BIOS drive D: is disk1
  BIOS 565kB/3136000kB available memory

  FreeBSD/x86 bootstrap loader, Revision 1.1
  (root@ozsrv04.riverwillow.net.au, Tue Oct  1 18:04:14 AEST 2013)
  Can't work out which disk we are booting from.
  Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0:

  panic: free: guard1 fail @ 0xbf492150 from /kits/src/sys/boot/i386/loader/
  ../../common/module.c:1004

That should keep me entertained until the morning (this is a remote
system).

--=20
John Marshall

--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iEYEARECAAYFAlJKsJkACgkQw/tAaKKahKIDWACgtfm0As41MVGx2RzXdCPZdFw4
pI8AnRHooJ5A0p97cUyPFSl/qLnI/la4
=6uz7
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131001112305.GA8408>