Re: recently updated -current fatal trap at boot

2012-09-12 Thread Kim Culhan
On Wed, Sep 12, 2012 at 11:53 AM, Michael Butler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 09/12/12 11:48, Kim Culhan wrote: >> FreeBSD -current r240360 has a fatal trap at boot. > > SVN r240367 reverts the troublesome change, > > imb On Wed, Sep 12, 2012 at 11:57 AM

Re: recently updated -current fatal trap at boot

2012-09-12 Thread David Wolfskill
On Wed, Sep 12, 2012 at 11:48:45AM -0400, Kim Culhan wrote: > FreeBSD -current r240360 has a fatal trap at boot. > ... As noted yesterday, yes. You need to either revert r240344 or apply r240367 (which reverts r240344). FWIW, I had no trouble at r240388. Peace, david -- David H. Wolfskill

Re: recently updated -current fatal trap at boot

2012-09-12 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/12/12 11:48, Kim Culhan wrote: > FreeBSD -current r240360 has a fatal trap at boot. SVN r240367 reverts the troublesome change, imb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlBQr+IACgkQQv9rrgRC1JKkSQ

recently updated -current fatal trap at boot

2012-09-12 Thread Kim Culhan
FreeBSD -current r240360 has a fatal trap at boot. This has been noted on two machines running -current which were updated using the recommended buildworld update procedure. Booting in single-user mode is possible and booting with the previous kernel, r240327M from ~ 09-10-12, is also possible an