Re: linking to git revisions in bugzilla

2021-05-06 Thread Yuri Pankov
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)

2021-05-05 Thread Yuri Pankov
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

git magic in contrib/bc

2021-04-28 Thread Yuri Pankov
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

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

2021-04-17 Thread Yuri Pankov
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: > &

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

2021-04-17 Thread Yuri Pankov
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 *.*

Re: Trying to build Current

2021-04-15 Thread Yuri Pankov
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

2021-04-12 Thread Yuri Pankov
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

linking to git revisions in bugzilla

2021-04-11 Thread Yuri Pankov
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

Re: ZFS not mount at boot

2021-04-05 Thread Yuri Pankov
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

2021-03-20 Thread Yuri Pankov
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 be r

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

2021-03-19 Thread Yuri Pankov
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

2021-03-19 Thread Yuri Pankov
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

2021-03-19 Thread Yuri Pankov
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

2021-03-19 Thread Yuri Pankov
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:

loader/boot fonts are painfully small (again)

2021-02-11 Thread Yuri Pankov
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

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

2021-02-09 Thread Yuri Pankov
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

2020-12-24 Thread Yuri Pankov
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_wrap

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Yuri Pankov
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

Re: Boot panic on Lenovo P50s since r367998

2020-12-24 Thread Yuri Pankov
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

Re: referencing one commit in another for git

2020-12-24 Thread Yuri Pankov
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

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

2020-12-17 Thread Yuri Pankov
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

2020-12-17 Thread Yuri Pankov
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"

2020-12-16 Thread Yuri Pankov
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

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

2020-12-03 Thread Yuri Pankov
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

Re: acpi_wmi noisy without EC

2020-11-17 Thread Yuri Pankov
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

2020-11-17 Thread Yuri Pankov
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

2020-11-16 Thread Yuri Pankov
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

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

2020-09-01 Thread Yuri Pankov
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...@freebsd.org S

Re: panic in range_tree_seg64_compare()

2020-08-27 Thread Yuri Pankov
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 fault

panic in range_tree_seg64_compare()

2020-08-27 Thread Yuri Pankov
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

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

2020-08-27 Thread Yuri Pankov
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 at addr 6

usbd_setup_device_desc: getting device descriptor at addr 6 failed, USB_ERR_IOERROR

2020-08-27 Thread Yuri Pankov
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:

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

2020-08-27 Thread Yuri Pankov
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 following: http

can't handle raw ops yet!!!

2020-08-27 Thread Yuri Pankov
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

2020-07-15 Thread Yuri Pankov
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

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

2020-07-14 Thread Yuri Pankov
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

2020-07-13 Thread Yuri Pankov
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

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

2020-07-10 Thread Yuri Pankov
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

2020-07-10 Thread Yuri Pankov
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)

2020-07-10 Thread Yuri Pankov
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

2020-07-10 Thread Yuri Pankov
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

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)

2020-07-08 Thread Yuri Pankov
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)

2020-07-08 Thread Yuri Pankov
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

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

2020-06-21 Thread Yuri Pankov
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

uma_zalloc_debug warnings after r362231

2020-06-19 Thread Yuri Pankov
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

2020-05-11 Thread Yuri Pankov
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

Re: nvme on 2019 macbooks

2020-04-30 Thread Yuri Pankov
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/linux

nvme on 2019 macbooks

2020-04-29 Thread Yuri Pankov
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:

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

2020-04-29 Thread Yuri Pankov
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 /usr/src

installkernel ignoring WITHOUT_DEBUG_FILES?

2020-04-28 Thread Yuri Pankov
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

2020-04-18 Thread Yuri Pankov
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,

Re: PCIe NVME drives not detected on Dell R6515

2020-04-17 Thread Yuri Pankov
Scott Long wrote: On Apr 17, 2020, at 3:07 PM, Miroslav Lachman <000.f...@quip.cz> wrote: Scott Long wrote on 04/17/2020 23:04: On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.f...@quip.cz> wrote: Scott Long wrote on 04/17/2020 22:17: On Apr 17, 2020, at 1:47 PM, Miroslav Lachman

Re: buildkernel failure because ctfconvert not installed

2020-04-09 Thread Yuri Pankov
Trond Endrestøl wrote: On Thu, 9 Apr 2020 10:56+0200, Gary Jennejohn wrote: OK, I figured it out. I used to have MK_CTF=no in src.conf, but I recently changed it to WITH_CTF=no. It's either WITH_xxx=yes or WITHOUT_xxx=yes. Or even WITH_xxx= or WITHOUT_xxx=, src.conf(5) explicitly states

Re: CURRENT crashes if loader.conf contains «net.isr.dispatch="direct"»

2020-04-04 Thread Yuri Pankov
Lev Serebryakov wrote: Hello FreeBSD-Current, CURRENT (and64, r359632) crashes very early on boot if `/boot/loader.conf` contains this line: net.isr.dispatch="direct" Stacktrace (manually transcribed from photo of screen, as it is very early stage of boot, so no crashdump possible):

Re: can't build rust -- out of swap space

2020-03-03 Thread Yuri Pankov
On 03.03.2020 15:27, Trond Endrestøl wrote: On Tue, 3 Mar 2020 12:56+0300, Yuri Pankov wrote: On 03.03.2020 12:44, Trond Endrestøl wrote: On Tue, 3 Mar 2020 12:40+0300, Yuri Pankov wrote: On 03.03.2020 11:49, Yuri Pankov wrote: With recent pkg fallout, I'm trying to build rust myself first

Re: can't build rust -- out of swap space

2020-03-03 Thread Yuri Pankov
On 03.03.2020 12:44, Trond Endrestøl wrote: On Tue, 3 Mar 2020 12:40+0300, Yuri Pankov wrote: On 03.03.2020 11:49, Yuri Pankov wrote: With recent pkg fallout, I'm trying to build rust myself first time ever (as far as I can remember), and it's failing running out of swap on the following step

Re: can't build rust -- out of swap space

2020-03-03 Thread Yuri Pankov
On 03.03.2020 11:49, Yuri Pankov wrote: With recent pkg fallout, I'm trying to build rust myself first time ever (as far as I can remember), and it's failing running out of swap on the following step: Building stage0 std artifacts (x86_64-unknown-freebsd -> x86_64-unknown-freebsd) runn

can't build rust -- out of swap space

2020-03-03 Thread Yuri Pankov
With recent pkg fallout, I'm trying to build rust myself first time ever (as far as I can remember), and it's failing running out of swap on the following step: Building stage0 std artifacts (x86_64-unknown-freebsd -> x86_64-unknown-freebsd) running:

Re: 13.0-CURRENT r356767 wanted ZFS

2020-01-16 Thread Yuri Pankov
David Wolfskill wrote: On Fri, Jan 17, 2020 at 12:18:41AM +, Clay Daniels wrote: 13.0-CURRENT r356767 would not take NO for an answer, and kept up a loop until I gave up trying to use UFS. No big deal, seems to work fine... Clay Err...? Is there some additional context that I'm

Re: DRM-current-kmod is still a problem at r353339

2019-10-21 Thread Yuri Pankov
Niclas Zeising wrote: On 2019-10-20 08:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and mjg@'s

Re: DRM-current-kmod is still a problem at r353339

2019-10-20 Thread Yuri Pankov
hat's exactly the patch mjg@ provided and Xin pointed you at. On 2019-10-20 02:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy_acquire(page,

Re: DRM-current-kmod is still a problem at r353339

2019-10-20 Thread Yuri Pankov
On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi")) -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and mjg@'s earlier patch at https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please

Re: memstick installer doesn't install loader.efi into ESP

2019-10-08 Thread Yuri Pankov
On 10/8/2019 9:07 AM, Yuri Pankov wrote: On Mon, Oct 7, 2019, at 5:23 AM, Yuri Pankov wrote: Just tried reinstalling the system on my laptop using the latest available memstick snapshot (https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20191004

Re: memstick installer doesn't install loader.efi into ESP

2019-10-08 Thread Yuri Pankov
On Mon, Oct 7, 2019, at 5:23 AM, Yuri Pankov wrote: > Just tried reinstalling the system on my laptop using the latest > available memstick snapshot > (https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20191004-r353072-memstick.img), &g

memstick installer doesn't install loader.efi into ESP

2019-10-06 Thread Yuri Pankov
Just tried reinstalling the system on my laptop using the latest available memstick snapshot (https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20191004-r353072-memstick.img), using UEFI boot, and default ZFS partitioning, and it didn't boot after

Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO

2019-09-18 Thread Yuri Pankov
Rebecca Cran wrote: On 2019-09-18 09:01, Yuri Pankov wrote: Any hints on debugging this further? Are you running ESXi 6.7 Update 2? Or, what version of ESXi are you using that has the problem? Yes, exactly, sorry for not mentioning it. ESXi version: 6.7.0 ESXi build number: 13006603

Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO

2019-09-18 Thread Yuri Pankov
Toomas Soome wrote: On 18 Sep 2019, at 18:01, Yuri Pankov wrote: I have tested several snapshot ISOs available for download: FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190906-r351901

ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO

2019-09-18 Thread Yuri Pankov
I have tested several snapshot ISOs available for download: FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso -

Re: panic: rcv_start < rcv_end

2019-09-10 Thread Yuri Pankov
Michael Tuexen wrote: On 10. Sep 2019, at 14:37, Yuri Pankov wrote: Just seen this almost immediately after booting the system installed from amd64-20190906-r351901 snapshot, trying to do initial pkg bootstrap. Sadly, I didn't have the swap/dump device configured at the time, so no dump

panic: rcv_start < rcv_end

2019-09-10 Thread Yuri Pankov
Just seen this almost immediately after booting the system installed from amd64-20190906-r351901 snapshot, trying to do initial pkg bootstrap. Sadly, I didn't have the swap/dump device configured at the time, so no dump was saved. But it looks like I'm not alone, seeing the

Re: sysutils/lsof: VOP_FSYNC definition moved?

2019-08-30 Thread Yuri Pankov
Larry Rosenman wrote: > http://home.lerctr.org:/data/live-host-ports/2019-08-30_20h25m06s/logs/errors/lsof-4.93.2_4,8.log > > --- dnode2.o --- > In file included from dnode2.c:56: > In file included from > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zfs_znode.h:33: > In file

Re: Kernel-Crash when working with ubt0

2019-08-26 Thread Yuri Pankov
Warner Losh wrote: > Is it from read_connection_list? If so I have a 'patch' that I'm using but > haven't committed because it's just too gross: drop the lock before the > copyout and pick it up again after... > > Warner > > On Mon, Aug 26, 2019 at 1:23 AM Hans Petter Selasky wrote: > >> Do

memstick images install broken bootx64.efi

2019-01-26 Thread Yuri Pankov
Hi, Looks like installations from snapshot memstick images (tried all available ones for amd64 from http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/) put broken bootx64.efi to ESP -- the system in question simply tries to boot via PXE. Fixing this is simple -- mounting the ESP, and

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-26 Thread Yuri Pankov
Dag-Erling Smørgrav wrote: > Yuri Pankov writes: >> There's apparently a bug in VMware Workstation NAT implementation, >> [...] The patch itself is attached. > > Could you please open a differential and add me as reviewer? https://reviews.freebsd.org/D18636 And

Re: head -r3418363: top -opid process list order is rather odd (top -Saopid example shown)

2018-12-25 Thread Yuri Pankov
Yuri Pankov wrote: > Mark Millard wrote: >> >> >> On 2018-Dec-24, at 13:49, Yuri Pankov wrote: >> >>> Mark Millard wrote: >>>> From my from=source head -r3418363 context, top with -opid does not >>>> seem to sort in a coherent orde

Re: head -r3418363: top -opid process list order is rather odd (top -Saopid example shown)

2018-12-24 Thread Yuri Pankov
Mark Millard wrote: > > > On 2018-Dec-24, at 13:49, Yuri Pankov wrote: > >> Mark Millard wrote: >>> From my from=source head -r3418363 context, top with -opid does not >>> seem to sort in a coherent order, not time of process creation order >>> (

Re: head -r3418363: top -opid process list order is rather odd (top -Saopid example shown)

2018-12-24 Thread Yuri Pankov
Mark Millard wrote: > From my from=source head -r3418363 context, top with -opid does not > seem to sort in a coherent order, not time of process creation order > (either direction) and not in just-PID numeric order (either > direction). For example: > > PID USERNAMETHR PRI NICE SIZE

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Cy Schubert wrote: > In message , Yuri > Pankov write > s: >> This is an OpenPGP/MIME signed message (RFC 4880 and 3156) >> --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH >> Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi"; >>

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Cy Schubert wrote: > In message <913730b6-c6f0-60b8-a589-e89e872b7...@yuripv.net>, Yuri > Pankov write > s: >> Yuri Pankov wrote: >>> In-Reply-To: l.gmail. >>> com> >>> Mark Peek wrote: >>>> On Fri, Dec 21, 2018 at 9:30 PM Enj

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Mark Peek wrote: > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote: > >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >>> >>> Mark Peek wrote: >>>> Thanks for the cc:. I forwarded the original report on to an internal >>>> V

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-21 Thread Yuri Pankov
t 5:10 PM Enji Cooper wrote: >> >>> >>>> On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: >>>> >>>> Hi, >>>> >>>> There's apparently a bug in VMware Workstation NAT implementation, made >>>> visible by

workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-21 Thread Yuri Pankov
Hi, There's apparently a bug in VMware Workstation NAT implementation, made visible by the change to default values of IPQoS in OpenSSH 7.8p1, making all ssh connections from the guest behind the NAT to fail with obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: Broken pipe".

Re: Whine: "Could not open /dev/crypto: No such file or directory"

2018-12-13 Thread Yuri Pankov
David Wolfskill wrote: After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org

Re: cannot build i386 12.0-RELEASE kernel on -current

2018-12-12 Thread Yuri Pankov
Henry Vogt wrote: > Hi, > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for amd64, > world for i386 ok, but fails 'make buildkernel' for i386: > > -- snip > > ... > > --- if_vte.o --- > /usr/src/12/sys/dev/vte/if_vte.c:76:10: fatal error: 'miibus_if.h' file not > found

Re: nda(4) does not work (reliably) in VMware Workstation

2018-12-09 Thread Yuri Pankov
Chuck Tuffli wrote: > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov <mailto:yur...@yuripv.net>> wrote: > > Hi, > > Running -HEAD in VMware Workstation 15.0.2 VM.  Trying to use nda(4) > instead of nvd(4) shows the following list of errors, and eventually &

nda(4) does not work (reliably) in VMware Workstation

2018-12-08 Thread Yuri Pankov
Hi, Running -HEAD in VMware Workstation 15.0.2 VM. Trying to use nda(4) instead of nvd(4) shows the following list of errors, and eventually panics: https://people.freebsd.org/~yuripv/nda1.png https://people.freebsd.org/~yuripv/nda2.png nvd(4) works without issues in this VM. nda(4) works as

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Yuri Pankov
Warner Losh wrote: > On Mon, Dec 3, 2018 at 11:14 AM Yuri Pankov wrote: > >> Warner Losh wrote: >>> On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: >>> >>>> Yuri Pankov wrote: >>>>> Warner Losh wrote: >>>>>> On Mon, De

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Yuri Pankov
Warner Losh wrote: > On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: > >> Yuri Pankov wrote: >>> Warner Losh wrote: >>>> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: >>>> >>>>> >>>>> On Mon, Dec 3, 2018 at 12:24

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Yuri Pankov
Yuri Pankov wrote: > Warner Losh wrote: >> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: >> >>> >>> On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin >>> wrote: >>> >>>> On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrot

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Yuri Pankov
Warner Losh wrote: > On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: > >> >> On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin >> wrote: >> >>> On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrote: >>>> Hi, >>>> >&

WITH_CTF breaks CD loader: "File too big"

2018-12-02 Thread Yuri Pankov
Hi, Building disc1.iso using `make release` and having WITH_CTF set in src.conf leads to "File too big" displayed when booting the image. Would it make sense to build loader and related parts without CTF unconditionally as it doesn't look useful there? signature.asc Description: OpenPGP

Re: SCSI and dmesg

2018-11-26 Thread Yuri Pankov
Yuri Pankov wrote: > Warner Losh wrote: >> Greetings >> >> a few weeks ago I pointed people to the nycbug dmesg service. I said I was >> looking at data to drive SCSI retirement. I've gatherd some preliminary >> data, which I've uploaded to >> https://gi

Re: ACPI Error: No handler for Region [ECOR]

2018-11-26 Thread Yuri Pankov
Renato Botelho wrote: > On 26/11/18 19:32, Florian Limberger wrote: >> Hi, >> >> On 20.11.18 14:46, Charlie Li wrote: >>> Nov 20 09:35:19 ardmore kernel: ACPI Error: No handler for Region [ECOR] >>> (0xf80003662300) [EmbeddedControl] (20181031/evregion-288) >>> Nov 20 09:35:19 ardmore kernel:

Re: SCSI and dmesg

2018-11-24 Thread Yuri Pankov
Warner Losh wrote: > Greetings > > a few weeks ago I pointed people to the nycbug dmesg service. I said I was > looking at data to drive SCSI retirement. I've gatherd some preliminary > data, which I've uploaded to > https://github.com/bsdimp/device-data/blob/master/cam.md along with some >

Re: C.UTF-8 as default locale

2018-11-04 Thread Yuri Pankov
Baptiste Daroussin wrote: > On Sun, Nov 04, 2018 at 09:35:48AM +0300, Yuri Pankov wrote: >> Hi, >> >> Looking through https://wiki.freebsd.org/DevSummit/201810, I noticed the >> following entry: >> >> - Make C.UTF-8 the default locale (conrad, dteske(i

C.UTF-8 as default locale

2018-11-04 Thread Yuri Pankov
Hi, Looking through https://wiki.freebsd.org/DevSummit/201810, I noticed the following entry: - Make C.UTF-8 the default locale (conrad, dteske(installer)) As this sort of change is better done early, I have put togetger a simple change introducing C.UTF-8 locale using the same common LC_CTYPE

installer loader hangs going from 20181026 to 20181101 snapshot with Supermicro virtual IPMI disks

2018-11-01 Thread Yuri Pankov
Hi, Trying to boot latest -current snapshot (20181101) on Supermicro H8DG6 using the IPMI virtual CD hangs after displaying the disks information, however booting the previous one (20181026) works. The difference is that newer one displays the "BIOS drive A:", so it could be related to recent

Re: UEFI boot hangs after loader

2018-10-28 Thread Yuri Pankov
Warner Losh wrote: > On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > >> Jung-uk Kim wrote: >>> On 18. 10. 24., Warner Losh wrote: >>>> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: >>>> >>>>> gryphon# efivar -N --hex $(efiva

Re: UEFI boot hangs after loader

2018-10-28 Thread Yuri Pankov
Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: >> >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) >>> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >>> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >>> 0020:

Re: vm_fault on boot with NVMe/nda

2018-10-15 Thread Yuri Pankov
Daniel Nebdal wrote: > Hi. I have a 12-ALPHA9 / r339331 amd64 system (a HPE ProLiant ML30 G9), > with a Kingston NVMe SSD ("KINGSTON SKC1000480G") on a PCIe card. > > By default, it shows up as /dev/nvd0, and this is how I installed the > system. It has a single large UFS2 (with SJ and TRIM

  1   2   >