Re: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Masachika ISHIZUKA
>> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. > > Yea, it seems to be the same issue for both of you, now have some work to do > to

Re: List test, please ignore.

2017-04-11 Thread Eric Joyner
Never! On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote: > ignore > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

List test, please ignore.

2017-04-11 Thread Sean Bruno
ignore signature.asc Description: OpenPGP digital signature

Re: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Toomas Soome
> On 11. apr 2017, at 17:42, Masachika ISHIZUKA wrote: > >> replaced /boot/loader with /boot/loader.old (which was from end of >> March) >> >> copied /boot/loader.efi from the r315864 snapshot USB image >> into /boot/loader.efi of the broken systems. >> >> Aprt from

Re: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Masachika ISHIZUKA
> replaced /boot/loader with /boot/loader.old (which was from end of > March) > > copied /boot/loader.efi from the r315864 snapshot USB image > into /boot/loader.efi of the broken systems. > > Aprt from the fact that I don't know which one is broken, the boxes are > booting again. > >

Re: VNET branch destiny

2017-04-11 Thread peter . blok
Hi Kristof, I’m prety sure it is the same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213673 . It is unrelated to epair or ng_eiface (my case). I’ll dig some more. Peter > On 11 Apr 2017, at 08:47, Kristof Provost

Re: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Hartmann, O.
On Mon, 10 Apr 2017 21:04:04 +0200 "O. Hartmann" wrote: > Am Mon, 10 Apr 2017 21:59:00 +0300 > Toomas Soome schrieb: > > > > On 10. apr 2017, at 21:04, O. Hartmann > > > wrote: > > > > > > Am Mon, 10 Apr 2017 16:14:21 +0300 > >

Re: VNET branch destiny

2017-04-11 Thread Kristof Provost
On 10 Apr 2017, at 12:10, peter.b...@bsd4all.org wrote: There have been issues with pf if I recall correctly. I currently have issues with stable, pf and vnet. There is an issue with pf table entries when an interface is moved to a different vnet. Does anyone no if there is a specific fix for