Re: panic: kernel diagnostic assertion VOP_ISLOCKET(vp) == LK_EXCLUSIVE

2022-04-23 Thread Takahiro Kambe
In message on Sat, 23 Apr 2022 18:24:00 +0200, "J. Hannken-Illjes" wrote: >> In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org> >> on Sat, 23 Apr 2022 10:22:13 +0200, >> "J. Hannken-Illjes" wrote: On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote: >>>

daily CVS update output

2022-04-23 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/tests/mi P src/doc/3RDPARTY P src/lib/libutil/parsedate.y P src/sbin/fsck_msdos/boot.c P src/sys/compat/netbsd32/netbsd32.h P src/sys/compat/netbsd32/netbsd32_fs.c P src/sys/dev/audio/audio.c P src/sys/dev/audio/audiodef.h P src/sys/dev/dkwedge/dk.c P

Automated report: NetBSD-current/i386 build failure

2022-04-23 Thread NetBSD Test Fixture
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.04.23.22.40.28. An extract from the build.sh output follows:

Re: Non-HDMI audio

2022-04-23 Thread Michael van Elst
r...@fdy2.co.uk (Robert Swindells) writes: >What do I need to do to get non-HDMI audio to work again? >% mixerctl -a -v >outputs.dacsel=HDMI00 { HDMI00 } You havve audio0 (HDMI) and audio1 (Speaker, etc..) and need to select. audiocfg list shows the devices. audiocfg default NUM selects

Re: Non-HDMI audio

2022-04-23 Thread RVP
On Sat, 23 Apr 2022, Robert Swindells wrote: What do I need to do to get non-HDMI audio to work again? % mixerctl -a -v outputs.dacsel=HDMI00 { HDMI00 } Try: audiocfg default 1 -RVP

Non-HDMI audio

2022-04-23 Thread Robert Swindells
What do I need to do to get non-HDMI audio to work again? % mixerctl -a -v outputs.dacsel=HDMI00 { HDMI00 } radeon0 at pci1 dev 0 function 0: vendor 1002 product 68f9 (rev. 0x00) hdaudio0 at pci1 dev 0 function 1: HD Audio Controller hdaudio0: interrupting at ioapic0 pin 19 hdaudio0: HDA ver.

Re: panic: kernel diagnostic assertion VOP_ISLOCKET(vp) == LK_EXCLUSIVE

2022-04-23 Thread J. Hannken-Illjes
> On 23. Apr 2022, at 14:45, Takahiro Kambe wrote: > > Hi, > > In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org> > on Sat, 23 Apr 2022 10:22:13 +0200, > "J. Hannken-Illjes" wrote: >>> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote: >> >>> Please try the attached

Re: panic: kernel diagnostic assertion VOP_ISLOCKET(vp) == LK_EXCLUSIVE

2022-04-23 Thread Takahiro Kambe
Hi, In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org> on Sat, 23 Apr 2022 10:22:13 +0200, "J. Hannken-Illjes" wrote: >> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote: > >> Please try the attached diff (with mount option "discard"). > > ... and remove the

Re: panic: kernel diagnostic assertion VOP_ISLOCKET(vp) == LK_EXCLUSIVE

2022-04-23 Thread J. Hannken-Illjes
> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote: > Please try the attached diff (with mount option "discard"). ... and remove the "#define TRIMDEBUG" from the top of ffs_alloc.c first ... -- J. Hannken-Illjes - hann...@mailbox.org signature.asc Description: Message signed with OpenPGP

Re: panic: kernel diagnostic assertion VOP_ISLOCKET(vp) == LK_EXCLUSIVE

2022-04-23 Thread J. Hannken-Illjes
> On 23. Apr 2022, at 05:17, Takahiro Kambe wrote: > > Hi, > > In message <15bebcc1-4756-46ad-a424-e5232065b...@mailbox.org> > on Fri, 22 Apr 2022 19:39:35 +0200, > "J. Hannken-Illjes" wrote: >>> #5 0x80e69314 in VOP_FDISCARD (vp=0x879fb253da40, >>> pos=, len=) >>>