Re: System crash

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Sat, 8 Aug 2020 at 18:07, Robert Nestor <rnestor%mac.com@localhost> wrote:
>
> My NFS is on a DS218+ Synology NAS which I believe is based on a version of Linux.  FreeNAS is based on FreeBSD I think, if that makes any difference.
>
> Could be something I haven’t configured properly on my NAS, but everything else has been working fine for the last couple of years and it’s where I have /home mounted which works for accessing files from Mac, Linux and NetBSD.

I haven't got a Synology hardware, but I have an xpenology VirtualBox
guest with a very recent version of DSM - 6.2.3. I am happy to report
I get exactly the same panic if I place the iso file on a NFS share
there:


# crash -M netbsd.27.core -N netbsd.27
Crash version 9.99.69, image version 9.99.69.
crash: _kvm_kvatop(0)
Kernel compiled without options LOCKDEBUG.
System panicked: nfs physio/async
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
?() at ffff8d05670b2440
sys_reboot() at sys_reboot
vpanic() at vpanic+0x15b
snprintf() at snprintf
nfs_pathconf() at nfs_pathconf
VOP_STRATEGY() at VOP_STRATEGY+0x64
vndthread() at vndthread+0x81e

The nfs parameter definitions on the server are the default ones.

>
> -bo
>
> On Aug 8, 2020, at 11:01 AM, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> > On Sat, 8 Aug 2020 at 17:52, Robert Nestor <rnestor%mac.com@localhost> wrote:
> >>
> >> I didn’t realize at the time that the iso file I was using for this was on an NFS share.  It crashes there, but if I move the file to a local disk then I don’t see any crash and get the same output you got.  This is the BT for attempting this when the file is on an NFS share:
> >>
> >> cpu1: Begin traceback…
> >> vpanic() at netbsd:vpanic+0x152
> >> snprintf() at netbsd:snprinf
> >> nfs_pathconf() at netbsd:nfs_pathconf
> >> VOP_STRATEGY() at netbsd:VOP_STRATEGY+0x64
> >> vndthread() at netbsd:vndthread+0x81e
> >> cpu1: End traceback…
> >
> > It sure is worth a pr, but I tested the same, placing the iso file on
> > a FreeNAS NFS share and did not get the panic.
> >
> >>
> >>
> >> On Aug 8, 2020, at 10:42 AM, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> >>
> >>> On Sat, 8 Aug 2020 at 16:51, Robert Nestor <rnestor%mac.com@localhost> wrote:
> >>>>
> >>>> Done but I may have put it into the wrong category - PR kern/55550
> >>>>
> >>>> On Aug 8, 2020, at 8:55 AM, Paul Goyette <paul%whooppee.com@localhost> wrote:
> >>>>
> >>>>> On Sat, 8 Aug 2020, Robert Nestor wrote:
> >>>>>
> >>>>>> Stumbled over this trying to check on the format of a NetBSD CD.  This
> >>>>>> is a newly installed system of 9.99.69 downloaded two days ago with
> >>>>>> all the installed packages rebuilt and installed under it, so
> >>>>>> everything is pretty much up to date.
> >>>>>>
> >>>>>>    vndconfig -c vnd0 NetBSD-9.99.69-amd64.iso
> >>>>>>    gpt show vnd0
> >>>
> >>> I don't get any panic with today's -current:
> >>>
> >>> $ vnconfig -c vnd0 /home/sysbuild/release/images/NetBSD-9.99.69-amd64.iso
> >>> $ dkctl vnd0 listwedges
> >>> /dev/rvnd0: no wedges configured
> >>> $ gpt show vnd0
> >>> GPT not found, displaying data from MBR.
> >>>
> >>>  start    size  index  contents
> >>>      0  962560         Unused
> >>> $ uname -a
> >>> NetBSD ymir 9.99.69 NetBSD 9.99.69 (GENERIC) #3: Sat Aug  8 13:47:29
> >>> BST 2020  sysbuild@ymir:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC
> >>> amd64
> >>>
> >>>
> >>>>>>
> >>>>>> And the system immediately crashed.  Now maybe what I tried doing
> >>>>>> isn't permitted, but should the system crash just from trying to do
> >>>>>> it?
> >>>>>
> >>>>> No it should not crash.
> >>>>>
> >>>>> Please file a PR
> >>>>>
> >>>>>
> >>>>> +--------------------+--------------------------+-----------------------+
> >>>>> | Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
> >>>>> | (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
> >>>>> | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
> >>>>> +--------------------+--------------------------+-----------------------+
> >>>>
> >>>
> >>>
> >>> --
> >>> ----
> >>
> >
> >
> > --
> > ----
>


-- 
----