daily CVS update output
Updating src tree: P src/distrib/sets/lists/tests/mi P src/doc/3RDPARTY P src/sys/dev/pci/pcidevs P src/sys/dev/pci/pcidevs.h P src/sys/dev/pci/pcidevs_data.h P src/sys/dev/pci/sdhc_pci.c P src/sys/net/if_wg.c P src/tests/usr.bin/xlint/lint1/Makefile P src/tests/usr.bin/xlint/lint1/c11_generic_expression.c cvs update: `src/tests/usr.bin/xlint/lint1/d_type_question_colon.c' is no longer in the repository P src/tests/usr.bin/xlint/lint1/expr_promote.c P src/tests/usr.bin/xlint/lint1/expr_promote.exp-ln P src/tests/usr.bin/xlint/lint1/expr_promote_trad.c P src/tests/usr.bin/xlint/lint1/expr_promote_trad.exp-ln P src/tests/usr.bin/xlint/lint1/init.c P src/tests/usr.bin/xlint/lint1/op_colon.c P src/usr.bin/ldd/ldd.c P src/usr.bin/xlint/lint1/tree.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 49314794 Jan 5 03:03 ls-lRA.gz
Re: NetBSD 10.0_BETA envstat hangs
On 4/01/23 23:32, Mayuresh wrote: envstat hangs (doesn't come out with Ctrl-C) on a laptop with following description: # uname -a NetBSD asusn 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Mon Dec 19 14:00:35 UTC 2022 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 # dmesg | grep acpibat0 [ 1.046558] acpibat0 at acpi0 (BAT0, PNP0C0A-0): ACPI Battery [ 1.046558] acpibat0: ACPI 4.0 functionality present [ 2.056386] acpibat0: autoconfiguration error: failed to evaluate _STA: AE_NO_MEMORY [62.666971] acpibat0: workqueue busy: updates stopped Please advise. If I got that on my laptop, I would create 3 PRs. 1) For the autoconfiguration error. 2) For the the fact that the device appears to be getting attached to sysmon_envsys(9) even though device configuration failed. 3) For the fact that the system call envstat appears to use a system call that cannot be interrupted. For #3 run "ps alx" and see if the STAT column for your uninterruptable envstat process has the letter "D" in it. If so, this indicates that the system call is in an uninterruptible state normally associated with short term disk I/O. Cheers, Lloyd
What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
So... I have a PV+PVSHIM DOMU running a pretty recent 9.x on a DOM0 running a 9.99.xx kernel. The DOM0 is not large, a 4 processor E-2224 with 32GB of memory. The DOMU has 2 VCPUs and 8GB of memory. About every day a very particular DOMU tosses the: WARNING: negative runtime; monotonic clock has gone backwards on its console and sort of falls of the network. A reboot "fixes" it, but nothing else does. The DOM0 is running a mostly stock XEN3_DOM0 kernel except that IFQ_MAXLEN is larger than the default and HZ is 2000 (which helped to keep the clocks on the DOMU syncing properly all other things being equal). The DOMU is running a pretty stock XEN3_DOMU, that is, HZ is 100 there. Over the years, this problem has been mentioned from time to time, but I was wondering if anyone has a actual solution to this sort of thing. The DOM0 hosts a small number of guests, all PV+PVSHIM, but this one in particular is the only one with 2 VCPUs, all the rest have only 1 and have never exhibited the problem of the clock going backwards. Nothing much is really going on with the DOMU right now, as it is one of my build guests. It is running ZFS and does backups each day and does a 'cvs update' sort of thing from time to time, but than that is it right now. Any thoughts?? -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
NetBSD 10.0_BETA envstat hangs
envstat hangs (doesn't come out with Ctrl-C) on a laptop with following description: # uname -a NetBSD asusn 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Mon Dec 19 14:00:35 UTC 2022 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 # dmesg | grep acpibat0 [ 1.046558] acpibat0 at acpi0 (BAT0, PNP0C0A-0): ACPI Battery [ 1.046558] acpibat0: ACPI 4.0 functionality present [ 2.056386] acpibat0: autoconfiguration error: failed to evaluate _STA: AE_NO_MEMORY [62.666971] acpibat0: workqueue busy: updates stopped Please advise. -- Mayuresh
