ozak...@netbsd.org (Ryota Ozaki) writes:
>I've committed a possible fix. Could you try it?
>Thanks,
> ozaki-r
I just got a NULL pointer dereference in tcp_ctloutput where
the previous check for inp == NULL is also missing.
[ 24837.756043] fp c0016794db70 tcp_ctloutput() at c02ec4
Updating src tree:
P src/bin/sh/jobs.c
P src/bin/sh/sh.1
P src/distrib/sets/lists/xcomp/mi
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/etc/etc.evbarm/Makefile.inc
P src/external/mit/xorg/lib/libXext/Makefile
P src/external/mit/xorg/lib/libXmu/Makefile
P src/external/mit/xorg/lib/libXpresent/Makefi
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2022.10.30.01.19.08.
An extract from the build.sh output follows:
./usr/share/zoneinfo/America/Rainy_River
./usr
Hi,
I've committed a possible fix. Could you try it?
Thanks,
ozaki-r
On Sun, Oct 30, 2022 at 12:17 AM Thomas Klausner wrote:
>
> Hi!
>
> A couple hours later, my shell was in an NFS mounted directory (probably idle
> for some time) and I tried tab-completing an entry, and it panicked again.
Hi!
A couple hours later, my shell was in an NFS mounted directory (probably idle
for some time) and I tried tab-completing an entry, and it panicked again.
Same location as below.
Hand copied:
tcp_shutdown_wrapper+0x20
nfs_disconnect+0x69
nfs_reconnect+0x1a
nfs_request+0x7fb
nfs_access+0x1ed
VO
Hi!
I’ve upgraded from 9.99.100 (stable) to 9.99.104 this morning (kernel + user
land, but packages still the old ones built on 9.99.100 in case it matters).
A couple hours later I started transmission-gtk and the machine immediately
panicked.
Hand copied:
uvm_fault(0xf8b04ab6d8f0, 0x0, 1)
