On Tue, Apr 10, 2018, Kristof Provost wrote:
> On 9 Apr 2018, at 13:10, Vladimir Zakharov wrote:
> > On Mon, Apr 09, 2018, Kristof Provost wrote:
> > > On 9 Apr 2018, at 10:50, Vladimir Zakharov wrote:
> > >
> > > For several days buildworld fails for me with the following
> > > error. Cleanin
This was running:
FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #156
r332399M/332400:1200061: Wed Apr 11 04:17:45 PDT 2018
r...@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64
during boot, after updating from:
FreeBSD g1-215.catwhisker.org 12.0
On Thu, Apr 5, 2018 at 7:23 PM, Zaphod Beeblebrox wrote:
> As I said I would, I put the contents of /boot onto the FAT-formated EFI
> partition. This is suboptimal. The default is to use "kernel.old" ... etc
> ... which cannot be done on a FAT partition... at least not with our
> filesystem driv
Hi;
FWIW, I use a very old PC of the type where the processor will not be
fixed by Intel and that still needs support for the traditional BIOS. I
also bought a 3TB HD (they were easier to find that 2T).
If I leave the disk dedicated to FreeBSD it recognizes the complete 3TB
and will happily
On Wed, Apr 11, 2018 at 11:14 AM, Pedro Giffuni wrote:
> Hi;
>
> FWIW, I use a very old PC of the type where the processor will not be fixed
> by Intel and that still needs support for the traditional BIOS. I also
> bought a 3TB HD (they were easier to find that 2T).
>
> If I leave the disk dedica
On 11/04/2018 11:04, Ryan Stone wrote:
On Wed, Apr 11, 2018 at 11:14 AM, Pedro Giffuni wrote:
Hi;
FWIW, I use a very old PC of the type where the processor will not be fixed
by Intel and that still needs support for the traditional BIOS. I also
bought a 3TB HD (they were easier to find that
On Wed, Apr 11, 2018 at 04:39:58AM -0700, David Wolfskill wrote:
> This was running:
>
> FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #156
> r332399M/332400:1200061: Wed Apr 11 04:17:45 PDT 2018
> r...@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY
Machines don’t need to be old to have issues. I have a two year old asus am3+
board that cant boot from gpt without secure boot enabled and is hard coded for
Microsoft keys
Lucas Holt
> On Apr 11, 2018, at 12:04 PM, Ryan Stone wrote:
>
>> On Wed, Apr 11, 2018 at 11:14 AM, Pedro Giffuni wrot
On 11.04.2018 20:02, Mark Johnston wrote:
>> It appears that r332389 is implicated.
>
> I'm seeing this too, under bhyve with e1000 emulation. Reverting r332389
> fixes the problem.
I have this problem too. And reverting r332389 fixes it.
em0@pci0:0:25:0:class=0x02 card=0x20088086 ch
Sorry about that. It looks like my review must have been missing a line.
@@ -4702,8 +4707,8 @@ iflib_register(if_ctx_t ctx)
_iflib_assert(sctx);
- CTX_LOCK_INIT(ctx, device_get_nameunit(ctx->ifc_dev));
-
+ CTX_LOCK_INIT(ctx);
+ STATE_LOCK_INIT(ctx, device_get_nameunit(c
Actually ctx lock is still a mutex. Just add the STATE_LOCK_INIT line.
-M
On Wed, Apr 11, 2018 at 10:24 AM, K. Macy wrote:
> Sorry about that. It looks like my review must have been missing a line.
>
> @@ -4702,8 +4707,8 @@ iflib_register(if_ctx_t ctx)
>
> _iflib_assert(sctx);
>
> -
Chalk another review fail up to shuffling patches between git and phab.
Sorry for the inconvenience.
-M
On Wed, Apr 11, 2018 at 10:26 AM, K. Macy wrote:
> Actually ctx lock is still a mutex. Just add the STATE_LOCK_INIT line.
> -M
>
> On Wed, Apr 11, 2018 at 10:24 AM, K. Macy wrote:
>> Sorry abo
On 11/04/2018 11:53, Lucas Holt wrote:
Machines don’t need to be old to have issues. I have a two year old asus am3+
board that cant boot from gpt without secure boot enabled and is hard coded for
Microsoft keys
Lucas Holt
Interesting. Not sure Clover would help there though, secure boot is
Hi!
Is there any update regarding the rebase or the inclusion to base system?
On 3/28/18, Eric McCorkle wrote:
> I'll do another rebase from head just to be sure
>
> On March 28, 2018 3:23:23 PM EDT, Warner Losh wrote:
>>It's on my list for nexr, finally. I have an alternate patch for
>>loader.e
Still reviewing the code. I'm worried it's too i386 specific and it
conflicts with some work I'm doing. I'll have a list of actionable
critiques this week.
Warner
On Wed, Apr 11, 2018 at 1:03 PM, Oliver Pinter <
oliver.pin...@hardenedbsd.org> wrote:
> Hi!
>
> Is there any update regarding the re
I think the thing to do at this point is to wait for the current work on
loader.efi to land, then adapt my patches to apply against that work.
On 04/11/2018 15:06, Warner Losh wrote:
> Still reviewing the code. I'm worried it's too i386 specific and it
> conflicts with some work I'm doing. I'll ha
OK. I've pushed in the main part of it. The additional work I have
shouldn't affect any of this stuff. I was going to look at what part(s) of
your open reviewed needed to be redone tomorrow and send you feedback, but
if you wanted to get a start before then, I'm happy to answer questions.
All the
I'm in the middle of moving to a new apartment right now. It's going to
be a bit before I can get to this.
On 04/11/2018 20:31, Warner Losh wrote:
> OK. I've pushed in the main part of it. The additional work I have
> shouldn't affect any of this stuff. I was going to look at what part(s)
> of y
18 matches
Mail list logo
