hdaa: uma_zalloc_debug: zone "malloc-{32,64}" with the following non-sleepable locks held

Getting the following debug notifications: hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 uma_zalloc_debug: zone "malloc-32" with the following non-sleepable locks held: exclusive sleep mutex hdac0 (HDA driver mutex) r = 0 (0xf80107cb7aa0) locked @ /usr/src/sys/dev/sound/pci/hda/hdaa.c:

Re: Not bootstrapping a cross-compiler

Jochen Neumeister wrote: > Alloah ML, > > I have a problem here after I just wanted to update CURRENT: > > After a “git pull” in /usr/src I get this error at buildworld: > > > make -j12 buildworld > --- buildworld --- > make[1]: "/usr/src/Makefile.inc1" line 362: SYSTEM_COMPILER: Determined > t

Re: pax(1) looping infinitely

Ganael Laplanche wrote: > > > Le 21/06/2024 à 18:58, Warner Losh a écrit : > >> My apologies...  I didn't check, but. it's in your sig so I should >> have. > > Hey, no pb :) > >> There's a mapping file that can be updated for cases like this. > > Hmmm, I could add my address there. Can you p

Re: revision not displayed in a2440348eed7

KIRIYAMA Kazuhiko wrote: > Hi, list > > I updated to a2440348eed7, but could not display revision: > > admin@tbedfc:~ % uname -a > FreeBSD tbedfc 15.0-CURRENT FreeBSD 15.0-CURRENT #0: Tue Sep 26 00:15:10 JST > 2023 root@tbedfc:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > admin@tbedfc:~ %

sed in CURRENT fails in textproc/jq

/logs/jq-1.7.log Yuri

Re: Jail compile error on CURRENT?

James Gritton wrote: > On 2023-08-07 13:29, Dimitry Andric wrote: >> On 7 Aug 2023, at 04:50, Yoshihiro Ota wrote: >>> >>> Am I the only one seeing this error? >>> I'm on 12.4-RELEASE amd64 and building CURRENT as of now. >>> >>> jaillex.c:2228:43: error: unused parameter 'yyscanner' >>> [-Werror,

panic: Segment size is not aligned (smartpqi related)

Hi, I'm getting the panic below trying to install latest current snapshot (20230720) on HPE Proliant 380 Gen10. There don't seem to be any recent changes to smartpqi driver itself so it's likely something else changed as this HBA didn't have *this* specific problem previously on this system. The

Re: HST time zone

David Cornejo wrote: > On Tue, Jul 25, 2023 at 11:01 AM Dimitry Andric > wrote: > > On 25 Jul 2023, at 22:26, David Cornejo > wrote: > > > > One thing that has bothered me for a long time is that the > Pacific/Honolulu timezon

Re: problems on new -current install with pkg/ssl

void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use > pkg for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping p

motivation for iconv versions of mbrtocXX functions

(also CC'ed current@ in case anyone else knows the answer) Hi Ed, Looking at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272293, I noticed that non-iconv implementations of mbrtoc16/32 work correctly for the provided test case, and before digging deeper into the issue with iconv ones, I wou

Re: CURRRENT snapshot won't boot due missing ZFS feature

Yuri wrote: > Michael Gmelin wrote: >> Hi, >> >> I didn't dig into this yet. >> >> After installing the current 14-snapshot (June 1st) in a bhyve-vm, I >> get this on boot: >> >> ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 >&

Re: CURRRENT snapshot won't boot due missing ZFS feature

Michael Gmelin wrote: > Hi, > > I didn't dig into this yet. > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > get this on boot: > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > (booting stops at this point) > > Seems like the boot loader is missing thi

Re: Surprise null root password

bob prohaska wrote: > On Fri, May 26, 2023 at 07:48:04PM +0100, Ben Laurie wrote: >> -T on ls will give you full time resolution... >> > More's the wonder: > root@www:/usr/src # ls -lT /etc/*p*wd* > -rw--- 1 root wheel 2099 May 10 17:20:33 2023 /etc/master.passwd > -rw-r--r-- 1 root wheel

Re: Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e

David Wolfskill wrote: > This is from an in-place source update from main-n263073-634a770a5e16 to > main-n263112-ad513b4dba3e: > > ... > Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test > Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o > Building

Re: FreeBSD wont boot on AMD Ryzen 9 7950X

Mike Jakubik wrote: > Hello, > > Thanks for the info. At least I know it's not specific to my parts. Is > there any knob one can turn in the BIOS to enable/disable this feature? > iirc UART is old school serial ports? Wonder if removing UART support > from the kernel would be a workaround. Try th

Re: photo/video on tty console with the new VT/framebuffer

Tomek CEDRO wrote: > On Fri, May 19, 2023 at 1:44 PM Alastair Hogge wrote: >> On 2023-05-19 11:30, Tomek CEDRO wrote: >>> On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote: As long as those packages support DRMKMS and does your GPU, you can to a degree. I noticed video works for mpv an

Re: Delay in 14.0-RELEASE cycle and blocking items

Yuri wrote: > Michael Osipov wrote: >> Am 2023-05-15 um 22:19 schrieb Yuri: >>> Michael Osipov wrote: >>>> Am 2023-05-15 um 21:37 schrieb Glen Barber: >>>>> On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: >>>>>> Glen,

Re: Delay in 14.0-RELEASE cycle and blocking items

Michael Osipov wrote: > Am 2023-05-15 um 22:19 schrieb Yuri: >> Michael Osipov wrote: >>> Am 2023-05-15 um 21:37 schrieb Glen Barber: >>>> On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: >>>>> Glen, >>>>> >>

Re: Delay in 14.0-RELEASE cycle and blocking items

Michael Osipov wrote: > Am 2023-05-15 um 21:37 schrieb Glen Barber: >> On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: >>> Glen, >>> >>> do you see any chance to get this finally merged: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236204 ? >>> >>> It seriously affects peop

Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support

Warner Losh wrote: > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes > mailto:freebsd-...@gndrsh.dnsmgr.net>> > wrote: > > > On Thu, May 11, 2023, 2:16 PM Yuri <mailto:y...@aetern.org>> wrote: > > > > > Warner Losh wrot

Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support

Warner Losh wrote: > The branch main has been updated by imp: > > URL: > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > Author: Warner Losh > AuthorDate: 2023-05-11 20:04:12 + > Commit: Warner Lo

Re: adopting zone1970.tab changes in tzsetup

Yuri wrote: > Hi, > > After tzsetup was switched to use zone1970.tab in 513419f4047 it mostly > works, but there are some content changes compared to zone.tab that was > used previously which need to be taken care of (would like to do so > before 14.0). If you have spare time,

Re: github CI failures related to tzsetup

Yuri wrote: > Looking at the CI jobs on github, all seem to fail in tzsetup while > making kernel-toolchain target. Obviously this build for me locally, > FreeBSD's CI is fine with it, it's only ubuntu and macos jobs reporting > the errors, and I don't see why; any hin

github CI failures related to tzsetup

Looking at the CI jobs on github, all seem to fail in tzsetup while making kernel-toolchain target. Obviously this build for me locally, FreeBSD's CI is fine with it, it's only ubuntu and macos jobs reporting the errors, and I don't see why; any hints? https://github.com/freebsd/freebsd-src/actio

Re: find(1): I18N gone wild? [[:alpha:]] not a substitute to refer 26 English letters A-Z

Yuri wrote: > parv/FreeBSD wrote: >> Wrote Dimitry Andric on Fri, 21 Apr 2023 10:38:05 UTC >> (via >> https://lists.freebsd.org/archives/freebsd-current/2023-April/003556.html >> <https://lists.freebsd.org/archives/freebsd-current/2023-April/003556.html> ) >

Re: find(1): I18N gone wild? [[:alpha:]] not a substitute to refer 26 English letters A-Z

parv/FreeBSD wrote: > Wrote Dimitry Andric on Fri, 21 Apr 2023 10:38:05 UTC > (via > https://lists.freebsd.org/archives/freebsd-current/2023-April/003556.html > ) >> >> ... However, I have read that with unicode, you shoul

Re: find(1): I18N gone wild ?

Jamie Landeg-Jones wrote: > Yuri wrote: > >> No, find "-name" works with pattern rules in the first link, please see: >> >> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/find.html > > Yeah. *blush* Sorry about that. I had thought characte

Re: find(1): I18N gone wild ?

Jamie Landeg-Jones wrote: > Yuri wrote: > >>> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13 >>> >>> ...which in turn refers to the following link for bracket expressions: >>> >>> https://pubs.opengrou

Re: find(1): I18N gone wild ?

Yuri wrote: > Mark Millard wrote: >> Dimitry Andric wrote on >> Date: Fri, 21 Apr 2023 10:38:05 UTC : >> >>> On 21 Apr 2023, at 12:01, Ronald Klop wrote: >>>> Van: Poul-Henning Kamp >>>> Datum: maandag, 17 april 2023 23:06 >>>>

Re: find(1): I18N gone wild ?

Mark Millard wrote: > Dimitry Andric wrote on > Date: Fri, 21 Apr 2023 10:38:05 UTC : > >> On 21 Apr 2023, at 12:01, Ronald Klop wrote: >>> Van: Poul-Henning Kamp >>> Datum: maandag, 17 april 2023 23:06 >>> Aan: curr...@freebsd.org >>> Onderwerp: find(1): I18N gone wild ? >>> This surprised me:

adopting zone1970.tab changes in tzsetup

Hi, After tzsetup was switched to use zone1970.tab in 513419f4047 it mostly works, but there are some content changes compared to zone.tab that was used previously which need to be taken care of (would like to do so before 14.0). If you have spare time, please take a look at the reviews below. h

Re: find(1): I18N gone wild ?

Xin LI wrote: > This is expected behavior (in en_US.UTF-8 the ordering is AaBb, not > ABab).  You might want to set LC_COLLATE to C if C behavior is desirable. > > On Mon, Apr 17, 2023 at 2:06 PM Poul-Henning Kamp > wrote: > > This surprised me: > >         #

Re: byteswap.h not found on 12 and 13

Nuno Teixeira wrote: > Hello Warner, > > My poudriere jails: > --- > 124amd64   12.4-RELEASE-p2      amd64         http         2023-03-17 > 08:04:15 /usr/local/poudriere/jails/124amd64 > 124i386    12.4-RELEASE-p2      i386          http         2023-03-17 > 08:04:38 /usr/local/poudriere/jails/12

dangling symlinks in openzfs import

These have been in there for quite some time now, and every time I try to grep something I see this (I know about -s option, but it's there in opengrok and other tools output as well): grep: sys/contrib/openzfs/contrib/debian/openzfs-zfsutils.zfs-load-key.init: No such file or directory grep: sys/

Re: Infinite loop with d_write_t

Goran Mekić wrote: > Hello, > > I'm trying to assemble a minimal kernel module and user space program as > a skeleton, and no matter what I do I get infinite loop. The code for > kernel is > https://github.com/mekanix/freebsd-project/blob/master/kernel/main.c. > The way to test: > # make > # sudo

Re: vt and keyboard accents

Hans Petter Selasky wrote: > On 1/29/23 09:48, Yuri wrote: >> Hans Petter Selasky wrote: >>> On 1/29/23 01:54, Yuri wrote: >>>> Looking into an issue with accents input for vt and cz (so >>>> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accen

Re: vt and keyboard accents

Hans Petter Selasky wrote: > On 1/29/23 01:54, Yuri wrote: >> Looking into an issue with accents input for vt and cz (so >> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are >> working and other result weird unrelated characters output. >> >> Che

vt and keyboard accents

Looking into an issue with accents input for vt and cz (so /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are working and other result weird unrelated characters output. Checking kbdcontrol -d output, there is an obvious difference with keymap contents -- all mappings are trimmed

Re: ld error (undefined symbol) while compiling sqlite3

Archimedes Gaviola wrote: > Hi, > > For some reason, I am compiling sqlite3 from the > /usr/src/contrib/sqlite3 source using > FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20221027-769b884e2e2-258837. I > created a /usr/src/usr.bin/sqlite3 directory and created a Makefile file > with content referred to

Re: buildkernel doesn't respect PORTSDIR with PORTS_MODULES

Juraj Lutter wrote: > > >> On 24 Nov 2022, at 15:16, Juraj Lutter wrote: >>> >>> bsd.port.mk and bsd.port.subdir.mk use _PORTSDIR. You could try adding >>> that to your list. >>> >> >> PORTS_MODULES are being built from within kern.post.mk. I’d put PORTSDIR >> into src-env.conf instead of /etc

emulated nvme on vmware workstation whines

I started seeing the following whines from emulated nvme on vmware workstation some time ago, and it seems to happen almost exclusively during the nightly periodic run: Jul 3 03:01:47 titan kernel: nvme0: RECOVERY_START 48053105730250 vs 48051555254036 Jul 3 03:01:47 titan kernel: nvme0: timeout

panic: make_dev_alias_v: bad si_name

Getting the following panic on HPE system with HPE enclosure: panic: make_dev_alias_v: bad si_name (error=22, si_name=enc@n../type@0/slot@1/elmdesc@{"Name":"DriveBay1"}/pass4) db_trace_self_wrapper() vpanic() panic() make_dev_alias_v() make_dev_alias_p() make_dev_physpath_alias() pass_add_phy

smartpqi: panic: malloc(M_WAITOK) with sleeping prohibited

Got this panic after booting GENERIC kernel: panic: malloc(M_WAITOK) with sleeping prohibited cpuid = 3 time = 1643658859 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00c7b20ae0 vpanic() at vpanic+0x17f/frame 0xfe00c7b20b30 panic() at panic+0x43/fra

Re: Deprecating smbfs(5) and removing it before FreeBSD 14

Ed Maste wrote: > The smbfs(5) filesystem supports only the obsolete SMBv1 protocol, and > I propose removing it for FreeBSD 14. I know the CHERI folks have been > using it but they plan to migrate away from it. It was broken for > months before they fixed it, so I suspect nobody is using it on > c

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

Thanx very much Цитирую "Alexander V. Chernikov" : On 12 Sep 2021, at 11:51, Yuri Tcherkasov wrote: ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports Looks pretty close to https://reviews.freebsd.org/D23450 <https://reviews.freebsd.org/D23450> I gues

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

The command is root@gw:/home/tyv # ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports ipfw nat 1 config ip 195.138.73.206 same_ports unreg_only reset root@gw:/home/tyv # Цитирую "Alexander V. Chernikov" : On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: Hi

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

Thanx, i try. Цитирую "Alexander V. Chernikov" : On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: Hi I'm binary upgrade FreeBSD from 10.2 to 13.0 After upgrate all workin well, but I need add one more routing table. So add to GENERIC kernel You can add 'net.fibs=2

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

Thanx, i try. Цитирую "Alexander V. Chernikov" : On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: Hi I'm binary upgrade FreeBSD from 10.2 to 13.0 After upgrate all workin well, but I need add one more routing table. So add to GENERIC kernel You can add 'net.fibs=2

ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

44_XCONFIG): Invalid argument Returning original kernel instataling with upgrade resolve problem with nat but multiple route I can't use. Anybody can help me? Thanx! -- -- Yuri Tcherkasov E-Mail: t...@uats.od.ua

Re: linking to git revisions in bugzilla

Oleksandr Tymoshenko wrote: > Kubilay Kocak (ko...@freebsd.org) wrote: >> On 12/04/2021 9:02 am, Yuri Pankov wrote: >>> While filing a bug, I noticed that the help only mentions svn revision >>> numbers, and "Preview" tab had no output when I tried putting

Re: zpool list -p 's FREE vs. zfs list -p's AVAIL ? FREE-AVAIL == 6_675_374_080 (199G zroot pool)

Mark Millard via freebsd-current wrote: > Context: > > # gpart show -pl da0 > => 40 468862048da0 GPT (224G) > 40 532480 da0p1 efiboot0 (260M) > 532520 2008 - free - (1.0M) > 534528 25165824 da0p2 swp12a (12G) >25700352 25165824 da0p

git magic in contrib/bc

Not sure if it's just me, but I'm seeing a bit of git weirdness in contrib/bc: $ cd freebsd-src $ git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean $ cd .. $ cp -a freebsd-src freebsd-src-copy $ cd freebsd-src-copy $ git status On branch

Re: catch-all daemon.info entry in syslog.conf is a bit unhelpful

Yuri Pankov wrote: > I understand it's been quite some time since it was added, but I have > been bitten by it just now. I am adding per-daemon .conf files for > ports in /usr/local/etc/syslog.d/ and noticed that none of them were > working. > > An example entry is: &g

catch-all daemon.info entry in syslog.conf is a bit unhelpful

I understand it's been quite some time since it was added, but I have been bitten by it just now. I am adding per-daemon .conf files for ports in /usr/local/etc/syslog.d/ and noticed that none of them were working. An example entry is: $ cat /usr/local/etc/syslog.d/dhcpd.conf !dhcpd *.* /var

Re: Trying to build Current

Willem Jan Withagen via freebsd-current wrote: > On 15-4-2021 11:47, Gary Jennejohn wrote: >> On Thu, 15 Apr 2021 10:51:39 +0200 >> Willem Jan Withagen via freebsd-current >> wrote: >> >>> Hi, >>> >>> I actually went completely back to the basic setup with directories >>> /usr/src and /usr/obj >>>

"ahci0: AHCI v1.30 with 6 6Gbps ports" while only 2 of those are SATA3

That is on somewhat older Supermicro X9DRI-LN4F+ board: ahci0: port 0x9050-0x9057,0x9040-0x9043,0x9030-0x9037,0x9020-0x9023,0x9000-0x901f mem 0xdfa21000-0xdfa217ff irq 18 at device 31.2 numa-domain 0 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported and then I was confu

linking to git revisions in bugzilla

While filing a bug, I noticed that the help only mentions svn revision numbers, and "Preview" tab had no output when I tried putting "base ", so I'm wondering how do you link to git revisions? ___ freebsd-current@freebsd.org mailing list https://lists.f

Re: ZFS not mount at boot

beepc.ch wrote: > Dear list, > > I've freshly installed FreeBSD 13-RC5 following this wiki for ZFS manual > configuration: > > https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot > > After restart, the ZFS datasets aren't mount at boot: > > # mount > zroot/ROOT/default on / (zfs, local, nfsv4acls) >

Re: no time selection screen in installer anymore

Yuri Pankov wrote: > Installing from > FreeBSD-14.0-CURRENT-amd64-20210318-a771bf748f9-245511-disc1.iso, I > noticed that there's no time selection screen anymore; TZ is there, date > is there, and only time is missing. > > Not that I miss it much, but it does not seem to

Re: [Bug 254395] bsdinstall: fail script install after BETA3

Chris wrote: > On 2021-03-19 13:06, bugzilla-nore...@freebsd.org wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 >> >> Nathan Whitehorn changed: >> >>    What    |Removed |Added >> --

no time selection screen in installer anymore

Installing from FreeBSD-14.0-CURRENT-amd64-20210318-a771bf748f9-245511-disc1.iso, I noticed that there's no time selection screen anymore; TZ is there, date is there, and only time is missing. Not that I miss it much, but it does not seem to be removed from source, so I'm wondering if it's recent

Re: panic: malloc(M_WAITOK) with sleeping prohibited

Yuri Pankov wrote: > H/W: Supermicro X9DRI-LN4F+, booting from IPMI Virtual CD-ROM using > FreeBSD-14.0-CURRENT-amd64-20210311-15565e0a217-257277-disc1.iso. Somehow I missed that it was already reported (a lot) and seems to be already fixed with FreeBSD-14.0-CURRENT-amd64-20210318-a771b

panic: malloc(M_WAITOK) with sleeping prohibited

H/W: Supermicro X9DRI-LN4F+, booting from IPMI Virtual CD-ROM using FreeBSD-14.0-CURRENT-amd64-20210311-15565e0a217-257277-disc1.iso. Root mount waiting for: usbus0 ugen0.4: at usbus0 umass0 numa-domain 0 on uhub2 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0xc101 umass0:7:0: Attache

loader/boot fonts are painfully small (again)

Lenovo P51 laptop, 15'' 4k (3840x2160) display. Booting from the latest available current snapshot (20210107), fonts were at least readable; updating to the latest bits (manually installing new loader as well) made them really small -- terminal size reported by stty is 480x135. I have also notice

Re: regression in /etc/rc.d/linux

Sergey V. Dyatko wrote: Hi, Subj was introduced in e40787f900f3c262d5134d342e5a16757dd2193c compat.linux.emul_path isn't defined before kldload`ing linux/linux64 kernel. Looks like it's already fixed: https://cgit.freebsd.org/src/commit/?id=07cac176fba947381c8111b8e02e8067e7fa542a _

Re: Boot panic on Lenovo P50s since r367998

Yuri Pankov wrote: Tomoaki AOKI wrote: On Thu, 24 Dec 2020 10:34:49 +0100 Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper()

Re: Boot panic on Lenovo P50s since r367998

Tomoaki AOKI wrote: On Thu, 24 Dec 2020 10:34:49 +0100 Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/fr

Re: Boot panic on Lenovo P50s since r367998

Marc Veldman wrote: Hello, since r367998 my Lenovo P50s panics on boot: mmc0: detached panic: Bad link elm 0xf80003a73300 next->prep != elm cupid=3 time=2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x8299a9c0 vpanic() at vpanic+0x181/frame 0xff

Re: referencing one commit in another for git

Warner Losh wrote: On Wed, Dec 23, 2020 at 6:22 PM Jan Beich wrote: Warner Losh writes: On Wed, Dec 23, 2020, 3:21 PM Alan Somers wrote: On Wed, Dec 23, 2020 at 3:16 PM Rick Macklem wrote: Hi, So I just did my first git commit. Pretty scary, but it looks ok. Now, how do I referenc

Re: installation on pvscsi fails with "The request was too large for this host"

Andriy Gapon wrote: On 17/12/2020 07:02, Yuri Pankov wrote: Trying to install latest snapshot (20201210) on a VMware ESXi/Workstation VMs with pvscsi fails on bootloader step, and the following is in dmesg: pvscsi0: pvscsi_execute_ccb error 27 pvscsi0: pvscsi_execute_ccb error 27 (da0:pvscsi0

Re: acpi_wmi noisy without EC

Yuri Pankov wrote: On Tue, Nov 17, 2020, at 4:00 PM, Vladimir Kondratyev wrote: On 2020-11-17 15:29, Yuri Pankov wrote: On Tue, Nov 17, 2020, at 11:07 AM, Vladimir Kondratyev wrote: On 2020-11-17 10:57, Vladimir Kondratyev wrote: On 2020-11-17 03:00, Yuri Pankov wrote: I have started seeing

installation on pvscsi fails with "The request was too large for this host"

Trying to install latest snapshot (20201210) on a VMware ESXi/Workstation VMs with pvscsi fails on bootloader step, and the following is in dmesg: pvscsi0: pvscsi_execute_ccb error 27 pvscsi0: pvscsi_execute_ccb error 27 (da0:pvscsi0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 28 00 04 00 (da0:pvscs

Re: port build fails with missing sys/smr_types.h

Alan Somers wrote: On Thu, Dec 3, 2020 at 2:09 PM Chuck Tuffli wrote: Hi I'm trying to fix the build of qemu-utils but am seeing failures on CURRENT (13.0-HEAD-9e082d278b9) like: In file included from util/oslib-posix.c:50: In file included from /usr/include/sys/user.h:51: In file included f

Re: acpi_wmi noisy without EC

On Tue, Nov 17, 2020, at 4:00 PM, Vladimir Kondratyev wrote: > On 2020-11-17 15:29, Yuri Pankov wrote: > > On Tue, Nov 17, 2020, at 11:07 AM, Vladimir Kondratyev wrote: > >> On 2020-11-17 10:57, Vladimir Kondratyev wrote: > >> > On 2020-11-17 03:00, Yuri Pankov wrote:

Re: acpi_wmi noisy without EC

On Tue, Nov 17, 2020, at 11:07 AM, Vladimir Kondratyev wrote: > On 2020-11-17 10:57, Vladimir Kondratyev wrote: > > On 2020-11-17 03:00, Yuri Pankov wrote: > >> I have started seeing the following on boot since some time: > >> > >> acpi_wmi0: on acpi0 &

acpi_wmi noisy without EC

I have started seeing the following on boot since some time: acpi_wmi0: on acpi0 acpi_wmi0: cannot find EC device device_attach: acpi_wmi0 attach returned 6 acpi_wmi0: on acpi0 acpi_wmi0: cannot find EC device device_attach: acpi_wmi0 attach returned 6 acpi_wmi0: on acpi0 acpi_wmi0: cannot find

Re: usbd_setup_device_desc: getting device descriptor at addr 6 failed, USB_ERR_IOERROR

spamming console with netgraph warnings; didn't notice its absence as I'm not using bluetooth at the moment. -Original Message- From: owner-freebsd-curr...@freebsd.org On Behalf Of Yuri Pankov Sent: Thursday, 27 August 2020 21:18 To: bob prohaska Cc: curr...@fre

Re: panic in range_tree_seg64_compare()

Matthew Macy wrote: On Thu, Aug 27, 2020 at 6:34 PM Yuri Pankov wrote: Yet another issue I'm seeing after last update (currently running r364870), hit it 2 times today: Fatal trap 12: page fault while in kernel mode cpuid = 19; apic id = 0d fault virtual address = 0xf819e2ecdc40

panic in range_tree_seg64_compare()

Yet another issue I'm seeing after last update (currently running r364870), hit it 2 times today: Fatal trap 12: page fault while in kernel mode cpuid = 19; apic id = 0d fault virtual address = 0xf819e2ecdc40 fault code = supervisor read data, page not present instruction poin

Re: usbd_setup_device_desc: getting device descriptor at addr 6 failed, USB_ERR_IOERROR

bob prohaska wrote: On Thu, Aug 27, 2020 at 09:41:16PM +0300, Yuri Pankov wrote: Another issue that I started seeing lately, didn't try finding out when exactly in case someone knows what it's about: Root mount waiting for: usbus0 usbd_setup_device_desc: getting device descriptor

usbd_setup_device_desc: getting device descriptor at addr 6 failed, USB_ERR_IOERROR

Another issue that I started seeing lately, didn't try finding out when exactly in case someone knows what it's about: Root mount waiting for: usbus0 usbd_setup_device_desc: getting device descriptor at addr 6 failed, USB_ERR_IOERROR Root mount waiting for: usbus0 usbd_setup_device_desc: getti

Re: can't handle raw ops yet!!!

Matthew Macy wrote: Expected. I'm working on it. It's just a friendly reminder when INVARIANTS is enabled. Good, thanks. On Thu, Aug 27, 2020 at 11:17 AM Yuri Pankov wrote: After OpenZFS merge, during boot I'm getting several occurrences of what seems to be the f

can't handle raw ops yet!!!

After OpenZFS merge, during boot I'm getting several occurrences of what seems to be the following: http://src.illumos.org/source/xref/freebsd-head/sys/contrib/openzfs/module/os/freebsd/spl/spl_kstat.c#207 And, yes, I'm running GENERIC, so with INVARIANTS. Should I be worried?

Re: FreeBSD Quarterly Status Report - Second Quarter 2020

Daniel Ebdrup Jensen wrote: [nothing] At least in Thunderbird the text is not inline, and rather shows as attachment. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail

Re: svn commit: r352558 - head/usr.bin/top

Steve Wills wrote: Hi, On 7/10/20 7:12 PM, Yuri Pankov wrote: Thanks. The attached diff seems to take care of the issue for me, adding VIS_TAB and removing VIS_SAFE, which can be blamed for passing through the following: VIS_SAFE   Currently this form allows space, tab, newline

Re: Current panics on connecting disks to a LSI-3108 controller

Willem Jan Withagen wrote: Hi, I have this Supermicro SUPERSERVER®2028TP Which hold four nodes each with a X10DRT-PT motherboard and a LSI-3108 SAS controller connecting to 6 disks. Trying to run the most recent current snapshot on it. # uname -a FreeBSD quadbox-d.digiware.nl 13.0-CURRENT FreeB

Re: svn commit: r352558 - head/usr.bin/top

Mark Millard wrote: On 2020-Jul-10, at 16:12, Yuri Pankov wrote: Mark Millard wrote: On 2020-Jul-10, at 11:05, Yuri Pankov wrote: Steve Wills wrote: On 11/28/19 4:08 PM, Mark Millard via svn-src-head wrote: Author: daichi Date: Fri Sep 20 17:37:23 2019 New Revision: 352558 URL: https

Re: svn commit: r352558 - head/usr.bin/top

Mark Millard wrote: On 2020-Jul-10, at 11:05, Yuri Pankov wrote: Steve Wills wrote: On 11/28/19 4:08 PM, Mark Millard via svn-src-head wrote: Author: daichi Date: Fri Sep 20 17:37:23 2019 New Revision: 352558 URL: https://svnweb.freebsd.org/changeset/base/352558 Log: top(1): support

Re: DRM Project report (week of July 6th)

Emmanuel Vadot wrote: [...] Hi Emmanuel, Sorry for somewhat hijacking the thread, but as you mentioned (IIRC) testing the vmwgfx in one of the previous mails, I'd like to ask if any work/fixes is done for that. Currently I don't have a VM with X11 installed as all my attempts didn't succeed

Re: svn commit: r352558 - head/usr.bin/top

Steve Wills wrote: On 11/28/19 4:08 PM, Mark Millard via svn-src-head wrote: Author: daichi Date: Fri Sep 20 17:37:23 2019 New Revision: 352558 URL: https://svnweb.freebsd.org/changeset/base/352558 Log:    top(1): support multibyte characters in command names (ARGV array)    depending on local

Re: svn commit: r363031 - in head: contrib/bmake contrib/bmake/lst.lib contrib/bmake/mk contrib/bmake/mk/sys contrib/bmake/unit-tests usr.bin/bmake (make now broken)

Mark Millard wrote: On 2020-Jul-8, at 20:35, Yuri Pankov wrote: Mark Millard wrote: This seems to have broken doing buildworld buildkernel and other things using make: make[2]: "/usr/src/share/mk/bsd.compiler.mk" line 197: warning: String comparison operator should be either ==

Re: svn commit: r363031 - in head: contrib/bmake contrib/bmake/lst.lib contrib/bmake/mk contrib/bmake/mk/sys contrib/bmake/unit-tests usr.bin/bmake (make now broken)

Mark Millard wrote: This seems to have broken doing buildworld buildkernel and other things using make: make[2]: "/usr/src/share/mk/bsd.compiler.mk" line 197: warning: String comparison operator should be either == or != make[2]: "/usr/src/share/mk/bsd.compiler.mk" line 197: warning: String co

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

Olivier Cochard-Labbé wrote: On Thu, Jun 18, 2020 at 10:26 PM Yasuhiro KIMURA wrote: I have VirtualBox VM running 13-CURRENT. In order to switch from legacy BIOS to UEFI I reinstalled OS by using FreeBSD-13.0-CURRENT-amd64-20200611-r362037-disc1.iso. After that `shutdow -p now` (or select 'ACP

uma_zalloc_debug warnings after r362231

I've started getting the following after r362231 (I think) when plugging USB drive, not seeing any real issues though: ugen0.9: at usbus0 umass0 numa-domain 0 on uhub4 umass0: 10> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0xc101 umass0:2:0: Attached to scbus2 uma_zalloc_debug: zone

Re: lockups on lenovo p43s under current

Pete Wright wrote: hello, i have a lenovo thinkpad P43s that exhibits lockups under CURRENT but behaves fine when running STABLE.  i've tried to find a fully reproducible situation to get this system to lockup but haven't found anything yet.  i am starting to suspect that the changes implement

Re: nvme on 2019 macbooks

Yuri Pankov wrote: I have tried booting latest -current snapshot on 2019 macbook pro 16, and noticed that nvme driver didn't attach, as class reported is 0x018002 and not 0x010802 that we expect in nvme_pci.c. The following linux changes seem to be related: https://github.com/torvalds/

nvme on 2019 macbooks

I have tried booting latest -current snapshot on 2019 macbook pro 16, and noticed that nvme driver didn't attach, as class reported is 0x018002 and not 0x010802 that we expect in nvme_pci.c. The following linux changes seem to be related: https://github.com/torvalds/linux/commit/66341331ba0d2de

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

Mark Johnston wrote: On Wed, Apr 29, 2020 at 08:49:00AM +0300, Yuri Pankov wrote: I'm trying to replace the kernel on memstick image with the help of mdconfig, and installkernel runs out of space despite WITHOUT_DEBUG_FILES= added to /etc/src.conf. /usr/src$ make -V MK_DEBUG_FILES no /us

installkernel ignoring WITHOUT_DEBUG_FILES?

I'm trying to replace the kernel on memstick image with the help of mdconfig, and installkernel runs out of space despite WITHOUT_DEBUG_FILES= added to /etc/src.conf. /usr/src$ make -V MK_DEBUG_FILES no /usr/src$ sudo rm -rf /mnt/usr/lib/debug /usr/src$ sudo make DESTDIR=/mnt installkernel

Re: Outdated jemalloc in CURRENT

Gordon Bergling wrote: I am not sure, that this info is correct. As far as I remember the update for jemalloc was reverted due to build problems, on some architecture. An updated revision has still to be commited to -CURRENT. That's exactly what the commit log says, yes? On Sat, Apr 18, 202

  1   2   3   >