daily CVS update output
Updating src tree: P src/distrib/sets/lists/tests/mi P src/sys/arch/arm/imx/imx31_intr.h P src/sys/arch/hpcsh/dev/hd64465/hd64465reg.h P src/sys/arch/i386/stand/efiboot/devopen.c P src/sys/arch/i386/stand/lib/biosdisk.c P src/sys/dev/cgd.c P src/sys/dev/i2c/files.i2c P src/sys/external/bsd/common/include/asm/barrier.h P src/sys/external/bsd/common/linux/linux_tasklet.c P src/sys/external/bsd/drm2/dist/drm/i915/i915_request.c P src/sys/external/bsd/drm2/dist/drm/i915/intel_csr.c P src/sys/external/bsd/drm2/include/linux/sched.h P src/usr.bin/make/compat.c P src/usr.bin/make/cond.c P src/usr.bin/make/hash.c P src/usr.bin/make/job.c P src/usr.bin/make/main.c P src/usr.bin/make/make.c P src/usr.bin/make/make.h P src/usr.bin/make/nonints.h P src/usr.bin/make/parse.c P src/usr.bin/make/unit-tests/Makefile P src/usr.bin/make/unit-tests/cond-short.mk P src/usr.bin/make/unit-tests/cond-token-number.exp P src/usr.bin/make/unit-tests/cond-token-number.mk U src/usr.bin/make/unit-tests/opt-debug-file.exp P src/usr.bin/make/unit-tests/opt-debug-file.mk P src/usr.bin/make/unit-tests/var-eval-short.exp P src/usr.bin/make/unit-tests/var-eval-short.mk U src/usr.bin/make/unit-tests/varmod-assign-shell.exp U src/usr.bin/make/unit-tests/varmod-assign-shell.mk P src/usr.bin/make/unit-tests/varname-makeflags.mk Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 41506408 Dec 28 03:03 ls-lRA.gz
Re: HEADS UP: Merging drm update
Hi,
Taylor R Campbell writes:
>> Date: Tue, 28 Dec 2021 08:41:16 +0900
>> From: Ryo ONODERA
>>
>> panic: mutex_vector_enter,518: uninitialized lock (lock=0xd80023501458,
>> from=807c091c)
>> cpu0: Begin traceback...
>> vpanic() at netbsd:vpanic+0x156
>> panic() at netbsd:panic+0x3c
>> lockdebug_wantlock() at netbsd:lockdebug_wantlock+0x180
>> mutex_enter() at netbsd:mutex_enter+0x213
>> intel_rps_mark_interactive() at netbsd:intel_rps_mark_interactive+0x1e
>
> Weird -- can you insert db_stacktrace() into intel_rps_init_early and
> intel_rps_fini? This looks like i915->gt.rps.power.mutex, judging by
> the stack trace, but I don't see how we can get here without first
> initializing the mutex.
Thanks for your suggestion.
With the following patch,
Index: sys/external/bsd/drm2/dist/drm/i915/gt/intel_rps.c
===
RCS file: /cvsroot/src/sys/external/bsd/drm2/dist/drm/i915/gt/intel_rps.c,v
retrieving revision 1.5
diff -u -r1.5 intel_rps.c
--- sys/external/bsd/drm2/dist/drm/i915/gt/intel_rps.c 19 Dec 2021 12:32:15
- 1.5
+++ sys/external/bsd/drm2/dist/drm/i915/gt/intel_rps.c 28 Dec 2021 02:32:37
-
@@ -9,6 +9,10 @@
#include
__KERNEL_RCSID(0, "$NetBSD: intel_rps.c,v 1.5 2021/12/19 12:32:15 riastradh
Exp $");
+#if 1
+#include
+#endif
+
#include "i915_drv.h"
#include "intel_gt.h"
#include "intel_gt_irq.h"
@@ -1618,6 +1622,9 @@
void intel_rps_init_early(struct intel_rps *rps)
{
+#if 1
+ db_stacktrace()
+#endif
mutex_init(>lock);
mutex_init(>power.mutex);
@@ -1679,6 +1686,9 @@
void intel_rps_fini(struct intel_rps *rps)
{
+#if 1
+ db_stacktrace()
+#endif
mutex_destroy(>power.mutex);
mutex_destroy(>lock);
I have gotten dmesg here:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
2018, 2019, 2020, 2021 The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 9.99.93 (LOCKDEBUG) #1: Tue Dec 28 11:26:27 JST 2021
ryoon@brownie:/usr/world/9.99/amd64/obj/sys/arch/amd64/compile/LOCKDEBUG
total memory = 15961 MB
avail memory = 15405 MB
timecounter: Timecounters tick every 10.000 msec
Kernelized RAIDframe activated
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
efi: systbl at pa 5697d018
mainbus0 (root)
ACPI: RSDP 0x63FFE014 24 (v02 DELL )
ACPI: XSDT 0x63F9C188 F4 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: FACP 0x63FF6000 000114 (v06 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: DSDT 0x63FB3000 03F8DE (v02 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: FACS 0x63EDF000 40
ACPI: SSDT 0x63FFB000 001B61 (v02 CpuRef CpuSsdt 3000 INTL
20180927)
ACPI: SSDT 0x63FF7000 003C64 (v02 INTEL DptfTabl 1000 INTL
20180927)
ACPI: HPET 0x63FF5000 38 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: APIC 0x63FF4000 00012C (v03 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: MCFG 0x63FF3000 3C (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: SSDT 0x63FB2000 0008D9 (v02 DELL DellRtd3 1000 INTL
20180927)
ACPI: NHLT 0x63FB1000 2D (v00 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: SSDT 0x63FB 000CB8 (v02 DELL UsbCTabl 1000 INTL
20180927)
ACPI: SSDT 0x63FAF000 000612 (v02 DELL Tpm2Tabl 1000 INTL
20180927)
ACPI: TPM2 0x63FAE000 34 (v04 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: LPIT 0x63FAD000 94 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: SSDT 0x63FAC000 000B75 (v02 DELL PtidDevc 1000 INTL
20180927)
ACPI: SSDT 0x63FAB000 000FBB (v02 DELL TbtTypeC INTL
20180927)
ACPI: DBGP 0x63FAA000 34 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: DBG2 0x63FA9000 54 (v00 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: SLIC 0x63FA8000 000176 (v03 DELL CBX3 06222004 MSFT
00010013)
ACPI: BOOT 0x63FA7000 28 (v01 DELL CBX3 20170001 ??LL
20160422)
ACPI: MSDM 0x63FA6000 55 (v03 DELL CBX3 06222004 AMI
00010013)
ACPI: SSDT 0x63FA4000 001554 (v02 SaSsdt SaSsdt 3000 INTL
20180927)
ACPI: SSDT 0x63F9D000 006C63 (v02 INTEL TcssSsdt 1000 INTL
20180927)
ACPI: DMAR 0x63FFD000 B0 (v02 INTEL Dell Inc 0002
0113)
ACPI: SSDT 0x63F9B000 000BE6 (v02 DELL xh_Dell_ INTL
20180927)
ACPI: SSDT 0x63F9A000 000156 (v02 Dell ADebTabl 1000 INTL
20180927)
ACPI: BGRT 0x63F99000 38 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: FPDT 0x63F98000 34 (v01 DELL Dell Inc 20170001 ??LL
20160422)
ACPI: 12 ACPI AML tables successfully acquired and loaded
Re: HEADS UP: Merging drm update
> Date: Tue, 28 Dec 2021 08:41:16 +0900 > From: Ryo ONODERA > > panic: mutex_vector_enter,518: uninitialized lock (lock=0xd80023501458, > from=807c091c) > cpu0: Begin traceback... > vpanic() at netbsd:vpanic+0x156 > panic() at netbsd:panic+0x3c > lockdebug_wantlock() at netbsd:lockdebug_wantlock+0x180 > mutex_enter() at netbsd:mutex_enter+0x213 > intel_rps_mark_interactive() at netbsd:intel_rps_mark_interactive+0x1e Weird -- can you insert db_stacktrace() into intel_rps_init_early and intel_rps_fini? This looks like i915->gt.rps.power.mutex, judging by the stack trace, but I don't see how we can get here without first initializing the mutex.
re: well-supported card for new DRM?
> I'm looking to upgrade my graphics card. What's the newest generation > that's well supported by NetBSD-current now? > NVidia "Pascal" (e.g. GTX 1050 Ti)? > Radeon "Polaris" (e.g. Radeon RX 550)? > or even something newer? we have reports that 1030 works well. i still haven't gotten a newer nvidia since those are beyond my toy-gpu-card-price :-) the RX 550 mostly works but we are still having some bugs (i have one of these from before they went up about 2x in cost). the two issues i reported before merge: https://github.com/riastradh/netbsd-src/issues/24 https://github.com/riastradh/netbsd-src/issues/28 i don't think we got fixes for these yet. #42 looks like the same issue as my #24, and #34 is a panic i've never seen but on the next generation card (5500.) HTH. .mrg.
Re: HEADS UP: Merging drm update
> Date: Mon, 27 Dec 2021 12:34:10 +0900 > From: Ryo ONODERA > > panic: kernel diagnostic assertion "!(!i915_request_completed(rq))" failed: > file "/usr/src/sys/external/bsd/drm2/dist/drm/i915/gt/intel_gt.c", line 475 I committed a change that I think will fix the particular bug leading to this assertion, but I suspect it won't fix the underlying issue. Nevertheless, can you cvs up and try again?
well-supported card for new DRM?
Hi! I'm looking to upgrade my graphics card. What's the newest generation that's well supported by NetBSD-current now? NVidia "Pascal" (e.g. GTX 1050 Ti)? Radeon "Polaris" (e.g. Radeon RX 550)? or even something newer? Thanks, Thomas
Serious crashes on 9.99.93
Hi all, I've upgraded my amd64 machine to NetBSD-9.99.93 yesterday and I'm experience serious crashes which were not happening on 9.99.92. dmesg, https://pastebin.com/8WJeUJDj Xorg-log, https://pastebin.com/xTAmUZPU The backtraces from the coredumps aren't really useful, https://pastebin.com/eaXYEC0Z I've managed to reproduce the crashes by launching lariza or badwolf web browsers. The system runs without issues if I don't use a web browser. Also, I've noticed the following while booting after a crash panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file "/usr/src/sys/kern/uipc_usrreq.c", line 525 Finally, unsure if related, console resolution doesn't scale after loading i915drmkms0, it used to in 9.99.92. Although, resolution after startx is correct. I've hosted the core-dumps in case, netbsd.2.core.gz, https://ufile.io/d00lfx4f netbsd.2.gz, https://ufile.io/4yvklq5w Thank you for any hints. Best, pin Sent with ProtonMail Secure Email.
Re: HEADS UP: Merging drm update
On Mon, Dec 27, 2021 at 06:58:34PM +0900, Ryo ONODERA wrote: > Hi, > > My previous dmesg is confusing. > Two messages are accidentally concatenated. The former message has no newline. > They should be splitted as follows. > > panic: i915drmkms0: notice: DMC firmware homepage: > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 Yeah, I get the same. I downloaded the firmware blob from that git repo, but now am not sure where to put it on the machine so the driver would find it. Since it talks about i915/skl_dmc_ver1_27.bin I thought putting it into /libdata/firmware/i915/skl_dmc_ver1_27.bin should work - but it doesn't. Martin
Re: HEADS UP: Merging drm update
Hi, My previous dmesg is confusing. Two messages are accidentally concatenated. The former message has no newline. They should be splitted as follows. panic: i915drmkms0: notice: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 kernel diagnostic assertion "!(!i915_request_completed(rq))" failed: file "/usr/src/sys/external/bsd/drm2/dist/drm/i915/gt/intel_gt.c", line 475 Thank you. On Mon, Dec 27, 2021 at 4:26 PM Martin Husemann wrote: > > On Mon, Dec 27, 2021 at 12:34:10PM +0900, Ryo ONODERA wrote: > > "panic: i915drmkms0: notice: DMC firmware homepage: > > Where would the firmware need to be? > > /libdata/firmware/i915/skl_dmc_ver1_27.bin > > obviously is not the right place. > > Martin
