We got the following panic on a 6.1_STABLE/amd64 server while restarting ipf:
fatal page fault in supervisor mode
trap type 6 code 0 rip 8023e7f4 cs 8 rflags 10212 cr2 ad0 cpl 4 rsp
fe8001005970
kernel: page fault trap, code=0
Stopped in pid 0.3 (system) at
On Thu, Jul 14, 2016 at 08:51:45PM +, Michael van Elst wrote:
> dholland-t...@netbsd.org (David Holland) writes:
>
> >Is there any reason lfs is using a global (rather than per-volume)
> >lock? ad@ seems to have introduced it but as usual there's little in
> >the way of reasoning or
On Fri, Jul 15, 2016 at 06:30:23PM +0900, Masanobu SAITOH wrote:
> Or enclose with #ifdef DIAGNOSTIC?
Assuming we do not use aprint_error when there is no "error", hiding it for
non-DIAGNOSTIC kernels does not make sense to me (at least in the !silent
or !quiet case).
I wonder if we should make
On 2016/07/15 16:45, Masanobu SAITOH wrote:
Hi.
aprint_error*() increments aprint_error_count.
At the end of config_finalize():
KERNEL_UNLOCK_ONE(NULL);
errcnt = aprint_get_error_count();
if ((boothowto & (AB_QUIET|AB_SILENT)) != 0 &&
(boothowto & AB_VERBOSE) == 0) {
On Fri, Jul 15, 2016 at 09:51:09AM +0900, Ryota Ozaki wrote:
> Does NFS root matter?
Not sure, Nick says his ERLITE still boots (where NFS root would be the
only obvious difference), but his Cobalt is not using NFS root.
I do not see the issue on ARM machines with NFS root.
Martin
Hi.
aprint_error*() increments aprint_error_count.
At the end of config_finalize():
KERNEL_UNLOCK_ONE(NULL);
errcnt = aprint_get_error_count();
if ((boothowto & (AB_QUIET|AB_SILENT)) != 0 &&
(boothowto & AB_VERBOSE) == 0) {
