On Jun 29, 2023 at 11:36 AM -0500, FreeBSD User , wrote:
> Am Thu, 29 Jun 2023 16:41:51 +0200
> Guido Falsi schrieb:
>
> > On 29/06/23 16:35, FreeBSD User wrote:
> > > Hello,
> > >
> > > running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu
> > > Jun 29 05:26:55
> > > CEST
Just updated my -CURRENT box from a build almost exactly 14 days ago
to one just about an hour old. When a VNET jail starts, I'm seeing a
lock reversal:
lock order reversal:
1st 0x81e893a8 allprison (allprison, sx) @
/usr/src/sys/kern/kern_jail.c:1378
2nd 0x81f99fe8
On Thu, Dec 9, 2021 at 12:35 PM Shawn Webb wrote:
>
> On Thu, Dec 09, 2021 at 12:05:30PM -0500, Mark Johnston wrote:
> > On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote:
> > > Hey all,
> > >
> > > It looks like there's a potential deadlock in some networking code,
> > > specifically
Just a quick update..
A kernel built from today boots just fine, so whatever the problem
was, it's already fixed :).
-Dustin
On Thu, Nov 18, 2021 at 3:54 PM Dustin Marquess wrote:
>
> It was 16 days ago, so just a tad over 2 weeks :).
>
> Indeed, I'll start a bisect here in a
It was 16 days ago, so just a tad over 2 weeks :).
Indeed, I'll start a bisect here in a few and I'll update as soon as I
know. I figured I'd ask ahead of time before I did the work :).
Thanks!
-Dustin
On Thu, Nov 18, 2021 at 12:29 PM Juraj Lutter wrote:
>
>
>
> On 18 Nov 2021, at 18:46, Karel
I just updated a machine from a build that was ~2 weeks old. The
latest commit when I built it was 2e946f87055.
The system boots using UEFI, if that matters. The system is panicking
pretty early in the boot, however:
real memory = 137438953472 (131072 MB)
avail memory = 133651496960 (127460 MB)
On Tue, Aug 31, 2021 at 2:06 AM Konstantin Belousov
wrote:
> On Tue, Aug 31, 2021 at 01:29:27AM -0500, Dustin Marquess wrote:
> > On Mon, Aug 30, 2021 at 4:33 AM Konstantin Belousov
> wrote:
> >
> > > On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wr
On Mon, Aug 30, 2021 at 4:33 AM Konstantin Belousov wrote:
> On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wrote:
> > I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
> > one I built about 2 hours ago. After installkernel I updated t
I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
one I built about 2 hours ago. After installkernel I updated the bootloader
the same way I normally do:
# mount_msdosfs /dev/da8p1 /mnt
# cp /mnt/EFI/BOOT/BOOTX64.efi /mnt/EFI/BOOT/BOOTX64.bak
# cp loader_lua.efi
I upgraded a 14-CURRENT system from a build about 2 months old to current.
In my /etc/rc.conf, I have:
cloned_interfaces="lagg0 lagg1 tap0 tap1 tap2 bridge0 bridge1 bridge2
vlan1 vlan2"
ifconfig_cxl0="txcsum txcsum6 lso mtu 9000 up"
ifconfig_cxl1="txcsum txcsum6 lso mtu 9000 up"
So I stupidly did a 'zpool add' instead of a 'zpool attach'. Luckily
I was able to 'zpool remove' the device thanks to the remove work done
a while back.
However, now I can't for the life of me get this part of the 'zpool
status' output to go away:
pool: zroot
state: ONLINE
scan: scrub
On Sat, Oct 3, 2020 at 2:54 PM Felix Kronlage-Dammers
wrote:
>
> Alexander Leidinger wrote on 03.10.20 17:37:
>
> > Quoting Kristof Provost (from Sat, 03 Oct 2020 16:06:43
> > +0200):
>
> >> Okay, let’s abandon that patch. It’s ugly and it doesn’t work.
> >>
> >> Here’s a different approach
On Tue, Sep 29, 2020 at 4:21 PM Kristof Provost wrote:
>
> On 28 Sep 2020, at 16:44, Alexander Leidinger wrote:
>
> > Quoting Kristof Provost (from Mon, 28 Sep 2020
> > 13:53:16 +0200):
> >
> >> On 28 Sep 2020, at 12:45, Alexander Leidinger wrote:
> >>> Quoting Kristof Provost (from Sun, 27 Sep
There seems to be a problem with OpenZFS when shutting down a machine
that boots from USB.
My machine has two SD cards in an adapter board that plugs into an
internal USB port on the motherboard. On these two cards I have the
UEFI loader and a mirror zpool containing just the bare minimum to
On Tue, Aug 18, 2020 at 3:19 PM Michael Butler
wrote:
>
> Any thoughts as to why this is happening when I build a (custom) kernel?
>
> kldxref: /boot/kernel/kernel: too many segments
I'm seeing this too. I haven't tried actually booting the kernel
because of this.
-Dustin
On Mon, Mar 2, 2020 at 6:55 PM Ryan Libby wrote:
>
> On Sun, Mar 1, 2020 at 8:07 PM Dustin Marquess wrote:
> >
> > So I've been fighting with any current from the last month or so
> > instantly crashing when I boot it. I did notice that kernels in the
> > variou
So I've been fighting with any current from the last month or so
instantly crashing when I boot it. I did notice that kernels in the
various snapshot images were working, however, so I was trying to
figure out why. At first I thought it was because I had INVARIANTS
and such disabled, but no, I
On Mon, Feb 10, 2020 at 6:53 AM David Wolfskill wrote:
>
> Looks as if the same thing affected both my laptop and my build machine
> -- each updated from r357688 (built yesterday & smoke-tested without
> incident). While I got some screenshots for the laptop, I have a serial
> console for the
All,
I have a couple of Lenovo ThinkServer RD450 servers booting in pure
UEFI mode. I'm using serial console redirection over IPMI with these
and a fresh install from r298793.
When it boots it picks up the right serial settings and I get the menu:
>> FreeBSD EFI boot block
Loader path:
then change.
>
>
>
> On 31/03/2016 07:15, Allan Jude wrote:
>
>> On 2016-03-31 02:13, Dustin Marquess wrote:
>>
>>> I have what I think is a pretty normal setup.. a bunch of HDDs plus 2
>>> SSDs
>>> (one ZIL, one SLOG).
>>>
>>
I have what I think is a pretty normal setup.. a bunch of HDDs plus 2 SSDs
(one ZIL, one SLOG).
The HDDs are standard 512 byte sector drives. The SSDs have 8k page sizes.
In Illumos I added the SSDs to sd.conf and created the zpool and it shows
the HDDs as ashift 9 and the SSDs as ashift 13,
21 matches
Mail list logo
