I have failed in three attempts over the past week to build FreeBSD-current
amd64, error message is about the same each time.
Build host uname -a shows
FreeBSD amelia 11.1-STABLE FreeBSD 11.1-STABLE #4: Sun Jul 30 17:28:39 UTC 2017
root@amelia2:/usr/obj/BETA1/usr/src11/sys/SANDY11NC amd64
On 18/03/2019 17:32, Konstantin Belousov wrote:
> tmpfs, swap-backed (or even memory backed) md, persistent posix shared
> memory, SysV shared memory.
In the end, it was POSIX shared memory.
I put the system into the single-user to clean up the memory as much as possible
and then I panic'ed it
On Wed, May 15, 2019 at 10:02:51AM +1200, Thomas Munro wrote:
> 1. As mentioned, you can't list 'em (unlike Linux, where you can just
> ls /dev/shm). There's a TODO note, but it's not clear whether it's
> best to extend ipcs or create a new userspace tool, and it wasn't
> immediately clear to me
I just ran into this error when updating my 13.0-CURRENT i386 jail to
r347606. I did not run into this problem when I upgraded by amd64 jail,
or when I updated the i386 jail to r347549.
--- lib/libgcc_s__L ---
sh /var/poudriere/jails/13CURRENTi386/usr/src/tools/install.sh -l rs -o root -g
wheel
On Mon, May 13, 2019 at 10:33:05PM +1000, Trev wrote:
> Joel Dahl wrote on 13/05/2019 19:29:
> > On Fri, May 10, 2019 at 06:27:12PM +, Brooks Davis wrote:
> >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers
> >> as previous approved in FCP-101. The following drivers
On Tue, May 14, 2019 at 9:24 PM Bob Bishop wrote:
> > On 14 May 2019, at 07:50, Andriy Gapon wrote:
> > In the end, it was POSIX shared memory.
> > I put the system into the single-user to clean up the memory as much as
> > possible
> > and then I panic'ed it and went through dirty pages and
> On May 14, 2019, at 13:18, Thomas Mueller wrote:
>
> I have failed in three attempts over the past week to build FreeBSD-current
> amd64, error message is about the same each time.
>
> Build host uname -a shows
>
> FreeBSD amelia 11.1-STABLE FreeBSD 11.1-STABLE #4: Sun Jul 30 17:28:39 UTC
Hi,
> On 14 May 2019, at 07:50, Andriy Gapon wrote:
>
> On 18/03/2019 17:32, Konstantin Belousov wrote:
>> tmpfs, swap-backed (or even memory backed) md, persistent posix shared
>> memory, SysV shared memory.
>
> In the end, it was POSIX shared memory.
> I put the system into the single-user
Hi,
I hit the following panic last night on a non-INVARIANTS kernel at
r347549. The workload involves running a number of bhyve VMs with
frequent restarts, during which a tap interface is destroyed and
recreated. I'm a bit short on time to debug this today, so while I
retry with INVARIANTS on I
On Tue, May 14, 2019 at 10:10 AM Mark Johnston wrote:
>
> Hi,
>
> I hit the following panic last night on a non-INVARIANTS kernel at
> r347549. The workload involves running a number of bhyve VMs with
> frequent restarts, during which a tap interface is destroyed and
> recreated. I'm a bit
On Tue, May 14, 2019 at 10:34 AM Kyle Evans wrote:
>
> On Tue, May 14, 2019 at 10:10 AM Mark Johnston wrote:
> >
> > Hi,
> >
> > I hit the following panic last night on a non-INVARIANTS kernel at
> > r347549. The workload involves running a number of bhyve VMs with
> > frequent restarts, during
11 matches
Mail list logo
