Re: USB sound devices with FreeBSD-CURRENT

On 2020-09-13 16:30, Hans Petter Selasky wrote: On 2020-09-13 16:13, Graham Perrin wrote: pcm3: (rec) pcm4: (play/rec) Or: -R /dev/dsp4 -P /dev/dsp4 -f /dev/dsp4 You can also add these parameters run-time via the GUI for virtual_oss. As a follow up to this discussion I've lowered the d

[2 WEEKS LEFT REMINDER] Call for 2020Q3 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is October, 1st 2020 for work done since the last round of Quarterly Reports: July 2020 - September 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report s

Re: Panic with wifi + usb in latest FreeBSD-current

Small correction... My rtwn is running at 1 MB, not Mb. I have two tools watching the network, one does bits and the other bytes. Still, performance is really bad. Can't say whether it's the driver or something else, but I'll be gathering data as I can between reboots of my current system. Sorry f

FreeBSD CI Weekly Report 2020-09-13

FreeBSD CI Weekly Report 2020-09-13 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2020-09-07 to 2020-09-13. During this period, we have: * 2533 builds (94.0% (+2.0) passed, 6.0% (-2.0) failed) of buildworld and buildkern

Re: Undefined symbol "lzc_remap"

On 9/14/20 1:00 PM, Kyle Evans wrote: On Mon, Sep 14, 2020 at 2:56 PM Pete Wright wrote: Hello, I have a system running current that is acting a little odd after a rebuild from last night (sept 13th). After reboot my root zfs pool mountd fine, but my second datavol "tank0" didn't auto-impor

Re: Undefined symbol "lzc_remap"

On Mon, Sep 14, 2020 at 2:56 PM Pete Wright wrote: > > Hello, > I have a system running current that is acting a little odd after a > rebuild from last night (sept 13th). After reboot my root zfs pool > mountd fine, but my second datavol "tank0" didn't auto-import/mount. A > manual "zpool import

Undefined symbol "lzc_remap"

Hello, I have a system running current that is acting a little odd after a rebuild from last night (sept 13th).  After reboot my root zfs pool mountd fine, but my second datavol "tank0" didn't auto-import/mount.  A manual "zpool import" then "zfs mount -a" got everything back where it should b

Re: ioctl argument type [Was Re: svn commit: r359968 - head/sys/kern]

Sorry for top posting. I think that https://reviews.freebsd.org/D26423 is the proper fix to catchup to NetBSD/4.4BSD Lite-2. Warner On Mon, Sep 14, 2020 at 3:58 AM Warner Losh wrote: > > > On Mon, Sep 14, 2020 at 1:45 AM Xin LI wrote: > >> Hi, >> >> I have seen Chromium trigger the warning (I

Re: Panic with wifi + usb in latest FreeBSD-current

On Sun, Sep 13, 2020 at 11:31 PM Adrian Chadd wrote: > On Sun, 13 Sep 2020 at 22:34, Warner Losh wrote: > > > > > > > On Sun, Sep 13, 2020, 11:29 PM Adrian Chadd > > wrote: > > > >> Yeah, this was also reported in #freebsd-wireless today. > >> > >> Is there a lock being held in the rtwn path th

Re: compiling with ports llvm11 breaks on mman.h: struct shm_larg epage_conf

On 13 Sep 2020, at 20:56, Dimitry Andric wrote: > > On 12 Sep 2020, at 23:00, Ronald Klop wrote: >> >> On Sat, 12 Sep 2020 18:28:03 +0200, Dimitry Andric wrote: >>> On 12 Sep 2020, at 17:43, Ronald Klop wrote: Because I'm tired of hours of compilation of llvm/clang I'm testing >>>

Re: ioctl argument type [Was Re: svn commit: r359968 - head/sys/kern]

On Mon, Sep 14, 2020 at 1:45 AM Xin LI wrote: > Hi, > > I have seen Chromium trigger the warning (I run -CURRENT with INVARIANTS) > and looked into the code history a little bit. > > It seems that the command was changed to u_long in r36846 >

Re: ioctl argument type [Was Re: svn commit: r359968 - head/sys/kern]

On 2020-09-14 09:44, Xin LI wrote: Hi, I have seen Chromium trigger the warning (I run -CURRENT with INVARIANTS) and looked into the code history a little bit. It seems that the command was changed to u_long in r36846 with a follow

ioctl argument type [Was Re: svn commit: r359968 - head/sys/kern]

Hi, I have seen Chromium trigger the warning (I run -CURRENT with INVARIANTS) and looked into the code history a little bit. It seems that the command was changed to u_long in r36846 with a follow up commit of r38517