On 12/09/20 13:18, Eric McCorkle wrote:
> I recently updated my other laptop, and now I'm getting a problem
> loading zfs.ko at boot, relating to the lockstat_enabled symbol not
> being defined (this happens during kernel boot and prevents mounting
> root, so I can't get an exact trace)
>
> Lookin
On 11 Sep 2020, at 19:06, Gleb Smirnoff wrote:
> Kristof,
>
> can you please take a look? IMHO, the problem is that with r360345
> the bridge_ioctl() is fully covered by epoch. IMHO, should be either
> more fine grained covered, or use internal locking, because some of
> the code downstream (driv
On Sat, 12 Sep 2020 18:28:03 +0200, Dimitry Andric wrote:
On 12 Sep 2020, at 17:43, Ronald Klop wrote:
Because I'm tired of hours of compilation of llvm/clang I'm testing
compiling FreeBSD with llvm11 from a pkg.
Setup a jail with 13-CURRENT. Compilation of the installed version went
f
On 12 Sep 2020, at 17:43, Ronald Klop wrote:
>
> Because I'm tired of hours of compilation of llvm/clang I'm testing compiling
> FreeBSD with llvm11 from a pkg.
>
> Setup a jail with 13-CURRENT. Compilation of the installed version went fine.
> Today I svn up'd and compiled and compilation brok
Hi,
Because I'm tired of hours of compilation of llvm/clang I'm testing
compiling FreeBSD with llvm11 from a pkg.
Setup a jail with 13-CURRENT. Compilation of the installed version went
fine.
Today I svn up'd and compiled and compilation broke.
/lib/clang/11.0.0/include -fstack-protector-
On Sat, Sep 12, 2020 at 7:55 AM Mark Murray wrote:
>
> On 12 Sep 2020, at 12:18, Eric McCorkle wrote:
> >
> > I recently updated my other laptop, and now I'm getting a problem
> > loading zfs.ko at boot, relating to the lockstat_enabled symbol not
> > being defined (this happens during kernel boo
On 12 Sep 2020, at 12:18, Eric McCorkle wrote:
>
> I recently updated my other laptop, and now I'm getting a problem
> loading zfs.ko at boot, relating to the lockstat_enabled symbol not
> being defined (this happens during kernel boot and prevents mounting
> root, so I can't get an exact trace)
I recently updated my other laptop, and now I'm getting a problem
loading zfs.ko at boot, relating to the lockstat_enabled symbol not
being defined (this happens during kernel boot and prevents mounting
root, so I can't get an exact trace)
Looking at the new kernel, it seems that only zfs.ko conta
> On 12. Sep 2020, at 11:06, Hartmann, O. wrote:
>
> On Sat, 12 Sep 2020 10:03:18 +0200
> Michael Gmelin wrote:
>
>>> On 12. Sep 2020, at 09:55, Hartmann, O.
>>> wrote:
>>> On Fri, 11 Sep 2020 07:18:33 -0600
>>> Alan Somers wrote:
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> w
Since r365488 (and above until recent) my box breaks with the following
error when starting:
Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xf
Am 12.09.20 um 11:05 schrieb Hartmann, O.:
> On Sat, 12 Sep 2020 10:03:18 +0200
> Michael Gmelin wrote:
>
>>> On 12. Sep 2020, at 09:55, Hartmann, O.
>>> wrote:
>>>
>>> On Fri, 11 Sep 2020 07:18:33 -0600
>>> Alan Somers wrote:
>>>
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> wro
On Sat, 12 Sep 2020 10:03:18 +0200
Michael Gmelin wrote:
> > On 12. Sep 2020, at 09:55, Hartmann, O.
> > wrote:
> >
> > On Fri, 11 Sep 2020 07:18:33 -0600
> > Alan Somers wrote:
> >
> >>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> >>> wrote:
> >>>
> >>> On Thu, 10 Sep 2020 10:44:08 -0
> On 12. Sep 2020, at 09:55, Hartmann, O. wrote:
>
> On Fri, 11 Sep 2020 07:18:33 -0600
> Alan Somers wrote:
>
>>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
>>> wrote:
>>>
>>> On Thu, 10 Sep 2020 10:44:08 -0600
>>> Alan Somers wrote:
>>>
No, it's devfs. I'll fix it.
On
On Fri, 11 Sep 2020 07:18:33 -0600
Alan Somers wrote:
> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann
> wrote:
>
> > On Thu, 10 Sep 2020 10:44:08 -0600
> > Alan Somers wrote:
> >
> > > No, it's devfs. I'll fix it.
> > >
> > > On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone
> > > wrote:
> > > >
Building recent 12-STABLE (revision 365643) for a nanobsd environment
on a CURRENT host fails since a couple of weeks for now with the weird
error shown below. The CURRENT host is running at FreeBSD 13.0-CURRENT
#20 r365382: Fri Sep 11 19:01:26 CEST 2020 amd64. Building 12-STABLE
jails at the very
15 matches
Mail list logo