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

Re: Does FreeBSD have an assigned Internet OID?

2020-08-27 Thread Poul-Henning Kamp
Rick Macklem writes: > For the NFS over TLS work, I have a need for an Internet OID. > (I understand that IETF assigns ones for things like SNMP under > 1.3.6.1.4.1...) See: /usr/share/snmp/mibs/FREEBSD-MIB.txt -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20

Re: Does FreeBSD have an assigned Internet OID?

2020-08-27 Thread Kurt Jaeger
Hi! > For the NFS over TLS work, I have a need for an Internet OID. > (I understand that IETF assigns ones for things like SNMP under > 1.3.6.1.4.1...) > > I'm referring to the long strings of numbers separated by "."s, > where each number is a subtree administered by someone.

Does FreeBSD have an assigned Internet OID?

2020-08-27 Thread Rick Macklem
For the NFS over TLS work, I have a need for an Internet OID. (I understand that IETF assigns ones for things like SNMP under 1.3.6.1.4.1...) I'm referring to the long strings of numbers separated by "."s, where each number is a subtree administered by someone. If either the project or

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

2020-08-27 Thread Matthew Macy
https://github.com/openzfs/zfs/pull/10836 On Thu, Aug 27, 2020 at 11:37 AM Yuri Pankov wrote: > > 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: > >> >

Re: panic in range_tree_seg64_compare()

2020-08-27 Thread Matthew Macy
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 code

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: buildkernel fais with option ZFS in kernel configuration

2020-08-27 Thread Scott Kenney
On Thu, Aug 27, 2020 at 11:36:56AM -0700, Matthew Macy wrote: > Need zstdio option when linking statically Thank you. It should probably be added as a requirement to the NOTES file. > On Thu, Aug 27, 2020 at 8:23 AM Scott Kenney wrote: > > > > Hello, > > > > Just noticed that buildkernel

Re: FreeBSD-head-i386-build - Build #17845 (r364891) - Failure

2020-08-27 Thread Glen Barber
Well, this was unexpected. I have pinged jenkins-admin@. Glen On Thu, Aug 27, 2020 at 09:59:47PM +, jenkins-ad...@freebsd.org wrote: > FreeBSD-head-i386-build - Build #17845 (r364891) - Failure > > Build information: https://ci.FreeBSD.org/job/FreeBSD-head-i386-build/17845/ > Full change

buildkernel fais with option ZFS in kernel configuration

2020-08-27 Thread Scott Kenney
Hello, Just noticed that buildkernel fails with "options ZFS" in the kernel configuration file, the modules build without error. Source is at revision 364870 FreeBSD datura.rmta.org 13.0-CURRENT FreeBSD 13.0-CURRENT #3 r364525: Sun Aug 23 23:14:23 EDT 2020

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

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

2020-08-27 Thread bob prohaska
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 failed, >

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:

Re: buildkernel fais with option ZFS in kernel configuration

2020-08-27 Thread Matthew Macy
Need zstdio option when linking statically On Thu, Aug 27, 2020 at 8:23 AM Scott Kenney wrote: > > Hello, > > Just noticed that buildkernel fails with "options ZFS" in the kernel > configuration file, the modules build without error. > > Source is at revision 364870 > > FreeBSD datura.rmta.org

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

2020-08-27 Thread Matthew Macy
Expected. I'm working on it. It's just a friendly reminder when INVARIANTS is enabled. 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: > >

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: Strange USB loop

2020-08-27 Thread bob prohaska
On Tue, Aug 25, 2020 at 11:29:16AM -0700, bob prohaska wrote: > With a _different_ FT232 plugged in it also came up normally. > > Both are thought to be genuine, but they are of different age > and produce different recognition messages: > > The FT232 that causes trouble reports > ugen1.4: at

Re: the state of amd64 ports on -CURRENT as of 20200827

2020-08-27 Thread Mark Linimon
I forgot to include the following statistic: repojail% grep duplicate_symbol regresslogs.out.wanted | wc -l 613 mcl ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

the state of amd64 ports on -CURRENT as of 20200827

2020-08-27 Thread Mark Linimon
The latest build of amd64-CURRENT ports has just completed: http://beefy18.nyi.freebsd.org/build.html?mastername=head-amd64-default=p546132_s364744 The number of build failures is now 740. This is an slight drop from the initial post-clang11 commit of 830. This is due to diligent work by a