daily CVS update output

2022-09-04 Thread NetBSD source update


Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/share/man/man9/Makefile
U src/share/man/man9/pktqueue.9
P src/sys/arch/arm/fdt/pcihost_fdt.c
P src/sys/arch/powerpc/fpu/fpu_compare.c
P src/sys/arch/powerpc/fpu/fpu_div.c
P src/sys/arch/powerpc/fpu/fpu_emu.c
P src/sys/arch/powerpc/fpu/fpu_emu.h
P src/sys/arch/powerpc/fpu/fpu_explode.c
P src/sys/arch/powerpc/fpu/fpu_extern.h
P src/sys/arch/powerpc/fpu/fpu_implode.c
P src/sys/arch/powerpc/fpu/fpu_subr.c
P src/sys/arch/xen/xen/xenevt.c
P src/sys/dev/vnd.c
P src/sys/dev/pci/if_bge.c
P src/sys/dev/pci/if_bgevar.h
P src/sys/dev/ppbus/if_plip.c
P src/sys/net/if_loop.c
P src/sys/net/pktqueue.c
P src/usr.bin/make/cond.c
P src/usr.bin/make/unit-tests/cond-cmp-numeric.exp
P src/usr.bin/make/unit-tests/cond-cmp-numeric.mk
P src/usr.bin/make/unit-tests/cond-cmp-string.exp
P src/usr.bin/make/unit-tests/cond-op-parentheses.exp
P src/usr.bin/make/unit-tests/cond-op-parentheses.mk
P src/usr.bin/make/unit-tests/varmod-ifelse.exp
P src/usr.bin/netstat/if.c

Updating xsrc tree:


Killing core files:



Updating release-8 src tree (netbsd-8):

Updating release-8 xsrc tree (netbsd-8):



Updating release-9 src tree (netbsd-9):

Updating release-9 xsrc tree (netbsd-9):




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  38519204 Sep  5 03:10 ls-lRA.gz


Re: Excessive sleep time

2022-09-04 Thread RVP

On Sun, 4 Sep 2022, pin wrote:


On current since amd64 since August 28, I get the following at boot,

[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)



Yeah, I'm seeing this too on my laptop. It's a change in the upstream
ACPICA code (see [1]):

1) ACPICA kernel-resident subsystem:

For the ASL Sleep() operator, issue a warning if the sleep value is
greater than 10 Milliseconds. Quick boottime is important, so warn about
sleeps greater than 10 ms. Distribution Linux kernels reach initrd in 350
ms, so excessive delays should be called out. 10 ms is chosen randomly,
but three of such delays would already make up ten percent of the
boottime.


[1]: https://mail-index.netbsd.org/source-changes/2022/08/27/msg140579.html

-RVP



fsck failing during setinodebuf on medium sized raid

2022-09-04 Thread Stephen M. Jones
Hello, I'm working with a ~50tb RAID.  I currently have small RAIDs running on 
8.x and 9.x servers
which are between 18tb to 24tb and do not see the issue on those.

The RAID is setup just like the smaller raids per NetBSD documentation.   The 
result seems to be
a resource limitation as starting from scratch and recreating the raid and 
partition result with the
same inode number during setinodebuf

This file system is mounted as rw,log and does not to seem to have any 
performance issues, but I
did experience a kernel panic which led me to try a forced fsck.   The panic 
may be completely unrelated.

amanda#newfs -02 -F -s 105468549120 /dev/rld1d

amanda# fsck -f -y /dev/rld1d
** /dev/rld1d
** File system is already clean
** Last Mounted on 
** Phase 1 - Check Blocks and Sizes
[ 2541.7360615] load: 0.99  cmd: fsck 644 [wait] 0.00u 0.00s 0% 1592k
/dev/rld1d: phase 1: cyl group 57321 of 65165 (87%)
bad inode number 18446744071562068992 to setinodebuf

[ 69786.3416697] uvm_fault(0x83e37a369478, 0x89ff35bad000, 1) -> e
[ 69786.4239488] fatal page fault in supervisor mode
[ 69786.4801091] trap type 6 code 0 rip 0x808dd271 cs 0x8 rflags 
0x10287 cr2 0x89ff35badf68 ilevel 0 rsp 0x8a01cd3dea90
[ 69786.6225918] curlwp 0x83e379cb8ac0 pid 342.1 lowest kstack 
0x8a01cd3dc2c0
[ 69786.7130745] panic: trap
[ 69786.7421952] cpu0: Begin traceback...
[ 69786.7889954] vpanic() at netbsd:vpanic+0x160
[ 69786.8326774] snprintf() at netbsd:snprintf
[ 69786.375] startlwp() at netbsd:startlwp
[ 69786.9387596] alltraps() at netbsd:alltraps+0xbb
[ 69786.9938801] ffs_hashalloc() at netbsd:ffs_hashalloc+0x40
[ 69787.0620328] ffs_valloc() at netbsd:ffs_valloc+0xdd
[ 69787.1134827] ffs_newvnode() at netbsd:ffs_newvnode+0x57
[ 69787.1821239] vcache_new() at netbsd:vcache_new+0xa9
[ 69787.2434861] ufs_mkdir() at netbsd:ufs_mkdir+0x6c
[ 69787.2934069] VOP_MKDIR() at netbsd:VOP_MKDIR+0x54
[ 69787.3558079] do_sys_mkdirat.isra.8() at netbsd:do_sys_mkdirat.isra.8+0x144
[ 69787.4422238] syscall() at netbsd:syscall+0x157
[ 69787.4936104] --- syscall (number 136) ---
[ 69787.5445717] 7c5c2af6282a:
[ 69787.5747325] cpu0: End traceback...

[ 69787.6204930] dumping to dev 19,1 (offset=15, size=6289150):
[ 69787.6204930] dump i/o error

Excessive sleep time

2022-09-04 Thread pin
Hi,

On current since amd64 since August 28, I get the following at boot,

[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x0064 ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x0064 ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x0064 ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x0064 ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)
[ 1.037893] ACPI Warning: Firmware issue: Excessive sleep time 
(0x005A ms > 10 ms) in ACPI Control Method (20220331/exsystem-239)

The system works fine but, these were not there before. I usually upgrade the 
base system once a week.
Right now,

~ > uname -v
NetBSD 9.99.99 (GENERIC) #0: Fri Sep  2 06:51:24 UTC 2022  
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

Any clues?
Thanks!

Sent with Proton Mail secure email.


Automated report: NetBSD-current/i386 test failure

2022-09-04 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the
NetBSD test suite.

The newly failing test cases are:

fs/nfs/t_rquotad:get_nfs_be_1_both
fs/nfs/t_rquotad:get_nfs_be_1_group
fs/nfs/t_rquotad:get_nfs_be_1_user
fs/nfs/t_rquotad:get_nfs_le_1_both
fs/nfs/t_rquotad:get_nfs_le_1_group
fs/nfs/t_rquotad:get_nfs_le_1_user
lib/libc/net/t_hostent:dnsbyaddrlookup4
lib/libc/net/t_hostent:dnsbyaddrlookup6
lib/libc/net/t_hostent:dnsbynamelookup4
lib/libc/net/t_hostent:dnsbynamelookup6
lib/libc/net/t_hostent:gethostbyaddr4
lib/libc/net/t_hostent:gethostbyaddr6
lib/libc/net/t_hostent:gethostbyname4
lib/libc/net/t_hostent:gethostbyname6
lib/librumpclient/t_fd:sigio
lib/librumphijack/t_tcpip:http
lib/librumphijack/t_tcpip:nfs
lib/librumphijack/t_tcpip:ssh
net/icmp/t_ping2:basic
net/if_loop/t_pr:loopmtu
net/if_loop/t_pr:loopmtu_csum
net/if_vlan/t_vlan:vlan_basic6
net/net/t_ipv6address:linklocal
net/net/t_pktinfo_send:pktinfo_send_bindaddr
net/net/t_pktinfo_send:pktinfo_send_bindaddrport
net/net/t_pktinfo_send:pktinfo_send_bindany
net/net/t_pktinfo_send:pktinfo_send_bindother
net/net/t_pktinfo_send:pktinfo_send_bindport
net/net/t_pktinfo_send:pktinfo_send_invalidarg
net/net/t_pktinfo_send:pktinfo_send_multicast
net/net/t_pktinfo_send:pktinfo_send_rawip
net/net/t_pktinfo_send:pktinfo_send_unbound

The above tests failed in each of the last 4 test runs, and passed in
at least 26 consecutive runs before that.

The following commits were made between the last successful test and
the failed test:

2022.09.02.16.24.31 sjg src/usr.bin/make/cond.c,v 1.335
2022.09.02.16.24.31 sjg src/usr.bin/make/for.c,v 1.169
2022.09.02.16.24.31 sjg src/usr.bin/make/make.1,v 1.331
2022.09.02.16.24.31 sjg src/usr.bin/make/make.h,v 1.304
2022.09.02.16.24.31 sjg src/usr.bin/make/parse.c,v 1.682
2022.09.02.16.24.31 sjg src/usr.bin/make/unit-tests/Makefile,v 1.322
2022.09.02.16.24.31 sjg 
src/usr.bin/make/unit-tests/directive-for-break.exp,v 1.1
2022.09.02.16.24.31 sjg 
src/usr.bin/make/unit-tests/directive-for-break.mk,v 1.1
2022.09.02.18.54.25 sjg src/distrib/sets/lists/tests/mi,v 1.1221
2022.09.02.18.54.25 sjg src/usr.bin/make/unit-tests/Makefile,v 1.323
2022.09.02.23.48.10 thorpej src/sys/arch/hppa/hppa/trap.c,v 1.121
2022.09.02.23.48.10 thorpej src/sys/arch/sun68k/sun68k/isr.c,v 1.27
2022.09.02.23.48.10 thorpej src/sys/arch/vax/vax/intvec.S,v 1.23
2022.09.02.23.48.10 thorpej src/sys/arch/xen/xen/xennetback_xenbus.c,v 1.108
2022.09.02.23.48.10 thorpej src/sys/dev/pci/if_jme.c,v 1.55
2022.09.02.23.48.10 thorpej src/sys/dev/pci/if_tl.c,v 1.125
2022.09.02.23.48.10 thorpej src/sys/dev/ppbus/if_plip.c,v 1.37
2022.09.02.23.48.10 thorpej src/sys/dev/qbus/if_qt.c,v 1.27
2022.09.02.23.48.10 thorpej src/sys/dev/sbus/be.c,v 1.97
2022.09.02.23.48.11 thorpej src/sys/dev/sbus/qe.c,v 1.78
2022.09.02.23.48.11 thorpej src/sys/external/bsd/ipf/netinet/ip_auth.c,v 1.7
2022.09.02.23.48.11 thorpej src/sys/net/raw_usrreq.c,v 1.65
2022.09.02.23.48.11 thorpej src/sys/netinet/ip_carp.c,v 1.117
2022.09.02.23.48.11 thorpej src/sys/netipsec/ipsec_netbsd.c,v 1.55
2022.09.03.00.31.02 thorpej src/sys/net/if_ethersubr.c,v 1.316
2022.09.03.00.31.02 thorpej src/sys/net/if_spppsubr.c,v 1.265
2022.09.03.00.50.07 rillig src/usr.bin/make/for.c,v 1.170
2022.09.03.00.50.07 rillig src/usr.bin/make/make.1,v 1.332
2022.09.03.00.50.07 rillig src/usr.bin/make/parse.c,v 1.683
2022.09.03.00.50.07 rillig 
src/usr.bin/make/unit-tests/directive-for-break.exp,v 1.2
2022.09.03.00.50.07 rillig 
src/usr.bin/make/unit-tests/directive-for-break.mk,v 1.2
2022.09.03.01.35.03 thorpej src/sys/net/Attic/netisr_dispatch.h,v 1.21
2022.09.03.01.35.03 thorpej src/sys/net/if_arcsubr.c,v 1.84
2022.09.03.01.35.03 thorpej src/sys/net/if_ethersubr.c,v 1.317
2022.09.03.01.35.03 thorpej src/sys/net/if_ieee1394subr.c,v 1.68
2022.09.03.01.35.03 thorpej src/sys/net/netisr_dispatch.h,v 1.21
2022.09.03.01.35.03 thorpej src/sys/netinet/if_arp.c,v 1.308
2022.09.03.01.35.03 thorpej src/sys/netinet/if_inarp.h,v 1.53
2022.09.03.01.35.03 thorpej 
src/sys/rump/net/lib/libnetinet/netinet_component.c,v 1.12
2022.09.03.01.48.22 thorpej src/sys/net/Attic/netisr_dispatch.h,v 1.22
2022.09.03.01.48.22 thorpej src/sys/net/if_ethersubr.c,v 1.318
2022.09.03.01.48.22 thorpej src/sys/net/if_gre.c,v 1.182
2022.09.03.01.48.22 thorpej src/sys/net/if_loop.c,v 1.115
2022.09.03.01.48.22 thorpej src/sys/net/netisr_dispatch.h,v 1.22
2022.09.03.01.48.22 thorpej src/sys/netatalk/at_extern.h,v 1.21
2022.09.03.01.48.22 thorpej src/sys/netatalk/at_proto.c,v 1.23
2022.09.03.01.48.22 thorpej src/sys/netatalk/at_var.h,v 1.10
2022.09.03.01.48.22 thorpej src/sys/netatalk/ddp_input.c,v 1.32
2022.09.03.01.48.22 thorpej 

Re: legacy DRM UMS vs. "options DRM_LEGACY"

2022-09-04 Thread Robert Swindells


"John D. Baker"  wrote:
> Well, 3 out of 4 kernels built when the above procedure was followed.
> the following config still fails when the old DRM drivers are enabled:

Your RACKMOUNT config builds fine for me (apart from plip but I will fix
that), are you sure that the link errors you are seeing are from the
kernel and not from a module?