From owner-freebsd-stable@freebsd.org Sun Feb 9 11:25:17 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 77B0E2356D9 for ; Sun, 9 Feb 2020 11:25:17 +0000 (UTC) (envelope-from joe@truespeed.com) Received: from mail.truespeed.com (mail.truespeed.com [31.210.26.210]) by mx1.freebsd.org (Postfix) with ESMTP id 48Fmt43X7Cz41hW for ; Sun, 9 Feb 2020 11:25:16 +0000 (UTC) (envelope-from joe@truespeed.com) Received: from dspam.truespeed.com (localhost [127.0.0.1]) by mail.truespeed.com (Postfix) with SMTP id 6FC125212E8 for ; Sun, 9 Feb 2020 11:25:15 +0000 (UTC) Received: from wormhole.home (host86-161-111-19.range86-161.btcentralplus.com [86.161.111.19]) (Authenticated sender: joe@truespeed.com) by mail.truespeed.com (Postfix) with ESMTPSA id A2F9C5212D8; Sun, 9 Feb 2020 11:25:13 +0000 (UTC) From: Dr Josef Karthauser Message-Id: <1F45763E-08A1-4308-A77A-B5CA30CF3909@truespeed.com> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Date: Sun, 9 Feb 2020 11:25:12 +0000 Subject: PAM modules; pthreads not reliably dispatching background threads :(. References: <9E850062-AA7F-4A0F-98B2-7FBE8B58AE76@truespeed.com> Cc: Richard Smith To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3608.40.2.2.4) X-Rspamd-Queue-Id: 48Fmt43X7Cz41hW X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of joe@truespeed.com designates 31.210.26.210 as permitted sender) smtp.mailfrom=joe@truespeed.com X-Spamd-Result: default: False [-0.18 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.935,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:31.210.26.210/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[truespeed.com]; NEURAL_HAM_LONG(-0.53)[-0.533,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_NAME_HAS_TITLE(1.00)[dr]; IP_SCORE(-0.02)[country: GB(-0.08)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:51048, ipnet:31.210.24.0/21, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[19.111.161.86.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 11:25:17 -0000 Hi Folks, Has anyone got any experience with PAM and pthreads? We=E2=80=99re using a 2FA module (pam_yubico = https://www.freebsd.org/cgi/man.cgi?query=3Dpam_yubico&sektion=3D8 = ). It=E2=80=99s proving unreliable. Digging deeper it uses libcurl to = communication to an HTTP endpoint, and libcurl is using pthreads for to = make asynchronous DNS lookup requests.=20 It seems that the pthreads are not being handled reliably within the PAM = runtime context - the background threads do not complete or dispatch. = It=E2=80=99s very strange. The problem doesn=E2=80=99t happen if we use the same code running from = a user land process. The pthreads are reliably in this context. Is there a known issue with PAM and pthreads? Hints are that there are = (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214540 = ). But that = problem was reported 3 years ago! HELP! If you know something I=E2=80=99d really appreciate a steer! Many thanks, Joe =E2=80=94=20 Dr Josef Karthauser Chief Technical Officer=20 (01225) 300371 / (07703) 596893=20 www.truespeed.com = From owner-freebsd-stable@freebsd.org Sun Feb 9 17:05:53 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 485FD23D54A for ; Sun, 9 Feb 2020 17:05:53 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48FwR42KcDz4Kxn for ; Sun, 9 Feb 2020 17:05:51 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 019H5inD006142 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 9 Feb 2020 11:05:44 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 019H5iTm006141; Sun, 9 Feb 2020 11:05:44 -0600 (CST) (envelope-from bob) Date: Sun, 9 Feb 2020 11:05:44 -0600 From: Bob Willcox To: Phil Norman Cc: freebsd-stable@freebsd.org Subject: Re: USB trouble on Ryzen 3/AsRock mobo. Message-ID: <20200209170544.GB932@rancor.immure.com> Reply-To: Bob Willcox References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 48FwR42KcDz4Kxn X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [2.84 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.40)[ip: (0.21), ipnet: 108.64.0.0/11(0.10), asn: 7018(1.74), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.25)[0.248,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.99)[0.995,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 17:05:53 -0000 Hi Phil, Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors you were getting? I just installed a recent 12.1 snapshot on a system with a Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT errors with this MB. The errors on this system appear to be continuing forever as they have been going on for over 30 minutes so far with no end in sight. On this system the initial dmesg messages for the usb errors looks strikingly similar to yours: Feb 9 18:46:57 han kernel: xhci0: Resetting controller Feb 9 18:46:57 han kernel: usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignored) Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han syslogd: last message repeated 1 times Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han syslogd: last message repeated 1 times Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han syslogd: last message repeated 1 times Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Feb 9 18:46:57 han syslogd: last message repeated 1 times Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 Anyone have any advice on what I can do the get this to stop? The system is fundamentally unusable as it is. Thanks, Bob On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote: > Hi. > > I've recently converted to FreeBSD, fleeing the Windowsification of Ubuntu. > I've been having some trouble with the USB system, which seems strange as > FreeBSD's USB stack is, according to a friend, rock solid. I'd like to > narrow down if this is a hardware (CPU or mobo) or software issue. > > I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac" > motherboard (chosen because it supports ECC RAM and fits in an ITX case). > > On a cold boot (ie starting by flipping the physical PSU power switch), BSD > boots up nice and quickly, without errors, and then runs for days without a > single USB-related error on dmesg. However, any other kind of reboot which > doesn't interrupt the electricity supply yields a large number of USB > errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of > the xhci0 controller. > > On occasion, I also get problems with my keyboard randomly stopping working > (but then, if the USB subsystem is continuously resetting, that's only to > be expected). I also seem to get slow USB storage device read throughput > (2MB/s from a USB3 SSD), although I can't rule out that being caused by the > fuse ext4fs driver. > > Here's what I see in dmesg when the USB system's in spam mode: > > ---------------- > xhci0: Resetting controller > usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > igb0: link state changed to UP > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > uhid0 on uhub3 > uhid0: on > usbus1 > uhid1 on uhub3 > uhid1: 1.10/1.22, addr 4> on usbus1 > ums0 on uhub2 > ums0: on > usbus1 > ums0: 3 buttons and [XYZ] coordinates ID=0 > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > ugen0.2: at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > uhub1: at usbus0, port 1, addr 1 (disconnected) > uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > uhub1: 22 ports with 22 removable, self powered > xhci0: Resetting controller > ----------------- > > > Here's the start of dmesg: > > ----------------- > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.2-PRERELEASE #0 r335198: Fri Jun 15 20:55:02 CEST 2018 > phil@bob:/usr/obj/usr/src/sys/BOB amd64 > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM > 6.0.0) > VT(efifb): resolution 1024x768 > CPU: AMD Ryzen 3 1200 Quad-Core Processor (3094.26-MHz K8-class > CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > Features=0x178bfbff > > Features2=0x7ed8320b > AMD Features=0x2e500800 > AMD > Features2=0x35c233ff > Structured Extended > Features=0x209c01a9 > XSAVE Features=0xf > AMD Extended Feature Extensions ID EBX=0x1007 > SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 > TSC: P-state invariant, performance statistics > real memory = 17179869184 (16384 MB) > avail memory = 16519221248 (15753 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > random: unblocking device. > Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid > Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-55 on motherboard > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #1 Launched! > Timecounter "TSC-low" frequency 1547130097 Hz quality 1000 > random: entropy device external interface > kbd0 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff80a3bd40, 0) error 19 > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX > platforms 390.59 Wed May 9 21:54:48 PDT 2018 > nexus0 > cryptosoft0: on motherboard > aesni0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x71 on acpi0 > atrtc0: registered as a time-of-day clock, resolution 1.000000s > Event timer "RTC" frequency 32768 Hz quality 0 > hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 950 > Event timer "HPET" frequency 14318180 Hz quality 450 > Event timer "HPET1" frequency 14318180 Hz quality 450 > Event timer "HPET2" frequency 14318180 Hz quality 450 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pcib0: _OSC returned error 0x10 > pci0: on pcib0 > amdsmn0: on hostb0 > amdtemp0: on hostb0 > pci0: at device 0.2 (no driver attached) > pcib1: at device 1.3 on pci0 > pci1: on pcib1 > xhci0: mem 0xf77a0000-0xf77a7fff irq 32 > at device 0.0 on pci1 > xhci0: 32 bytes context size, 64-bit DMA > usbus0 on xhci0 > ----------------- > > I don't remember if I had similar USB trouble on Linux, but I definitely > did during my brief excursion into NetBSD. If anyone knows whether this is > likely to be a CPU, mother board or software problem, or knows of something > I can try to get more information or try to debug the thing, please let me > know. > > Thanks, > Phil > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Bob Willcox | It's possible that the whole purpose of your life is to bob@immure.com | serve as a warning to others. Austin, TX | From owner-freebsd-stable@freebsd.org Mon Feb 10 13:22:44 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2237D23A229 for ; Mon, 10 Feb 2020 13:22:44 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48GRR716f6z4TLY for ; Mon, 10 Feb 2020 13:22:42 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 01ADMeMK008447 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Feb 2020 07:22:40 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 01ADMehi008446; Mon, 10 Feb 2020 07:22:40 -0600 (CST) (envelope-from bob) Date: Mon, 10 Feb 2020 07:22:40 -0600 From: Bob Willcox To: Phil Norman Cc: freebsd-stable@freebsd.org Subject: Re: USB trouble on Ryzen 3/AsRock mobo. Message-ID: <20200210132240.GF932@rancor.immure.com> Reply-To: Bob Willcox References: <20200209170544.GB932@rancor.immure.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 48GRR716f6z4TLY X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [2.70 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.39)[ip: (0.21), ipnet: 108.64.0.0/11(0.10), asn: 7018(1.72), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.11)[0.113,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.99)[0.994,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2020 13:22:44 -0000 Hi Phil, Thanks for the reply. I too have decided to replace the motherboard. Hopefully the next one will behave better. I'm sure that these manufactures don't test their products with FreeBSD. Bob On Mon, Feb 10, 2020 at 07:32:27AM +0100, Phil Norman wrote: > Hi. > > I'm afraid the best I could come up with is that the motherboard I was > using is not standards-compliant, and has a broken USB system. This might > explain why they insist you install their special drivers on Windows. > > My solution was to replace the motherboard with one that actually works > properly. > > Cheers, > Phil > > On Sun, 9 Feb 2020 at 18:05, Bob Willcox wrote: > > > Hi Phil, > > > > Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors > > you were getting? I just installed a recent 12.1 snapshot on a system with > > a > > Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT > > errors with this MB. > > > > The errors on this system appear to be continuing forever as they have been > > going on for over 30 minutes so far with no end in sight. On this system > > the > > initial dmesg messages for the usb errors looks strikingly similar to > > yours: > > > > Feb 9 18:46:57 han kernel: xhci0: Resetting controller > > Feb 9 18:46:57 han kernel: usb_alloc_device: set address 3 failed > > (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > > > Anyone have any advice on what I can do the get this to stop? The system is > > fundamentally unusable as it is. > > > > Thanks, > > Bob > > > > On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote: > > > Hi. > > > > > > I've recently converted to FreeBSD, fleeing the Windowsification of > > Ubuntu. > > > I've been having some trouble with the USB system, which seems strange as > > > FreeBSD's USB stack is, according to a friend, rock solid. I'd like to > > > narrow down if this is a hardware (CPU or mobo) or software issue. > > > > > > I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac" > > > motherboard (chosen because it supports ECC RAM and fits in an ITX case). > > > > > > On a cold boot (ie starting by flipping the physical PSU power switch), > > BSD > > > boots up nice and quickly, without errors, and then runs for days > > without a > > > single USB-related error on dmesg. However, any other kind of reboot > > which > > > doesn't interrupt the electricity supply yields a large number of USB > > > errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of > > > the xhci0 controller. > > > > > > On occasion, I also get problems with my keyboard randomly stopping > > working > > > (but then, if the USB subsystem is continuously resetting, that's only to > > > be expected). I also seem to get slow USB storage device read throughput > > > (2MB/s from a USB3 SSD), although I can't rule out that being caused by > > the > > > fuse ext4fs driver. > > > > > > Here's what I see in dmesg when the USB system's in spam mode: > > > > > > ---------------- > > > xhci0: Resetting controller > > > usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > igb0: link state changed to UP > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > uhid0 on uhub3 > > > uhid0: > > on > > > usbus1 > > > uhid1 on uhub3 > > > uhid1: > > 1.10/1.22, addr 4> on usbus1 > > > ums0 on uhub2 > > > ums0: on > > > usbus1 > > > ums0: 3 buttons and [XYZ] coordinates ID=0 > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > ugen0.2: at usbus0 (disconnected) > > > uhub_reattach_port: could not allocate new device > > > uhub1: at usbus0, port 1, addr 1 (disconnected) > > > uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > > > uhub1: 22 ports with 22 removable, self powered > > > xhci0: Resetting controller > > > ----------------- > > > > > > > > > Here's the start of dmesg: > > > > > > ----------------- > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > The Regents of the University of California. All rights reserved. > > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > > FreeBSD 11.2-PRERELEASE #0 r335198: Fri Jun 15 20:55:02 CEST 2018 > > > phil@bob:/usr/obj/usr/src/sys/BOB amd64 > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on > > LLVM > > > 6.0.0) > > > VT(efifb): resolution 1024x768 > > > CPU: AMD Ryzen 3 1200 Quad-Core Processor (3094.26-MHz > > K8-class > > > CPU) > > > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > > > > > > > Features=0x178bfbff > > > > > > > > Features2=0x7ed8320b > > > AMD Features=0x2e500800 > > > AMD > > > > > Features2=0x35c233ff > > > Structured Extended > > > > > Features=0x209c01a9 > > > XSAVE Features=0xf > > > AMD Extended Feature Extensions ID EBX=0x1007 > > > SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 > > > TSC: P-state invariant, performance statistics > > > real memory = 17179869184 (16384 MB) > > > avail memory = 16519221248 (15753 MB) > > > Event timer "LAPIC" quality 600 > > > ACPI APIC Table: > > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > > > FreeBSD/SMP: 1 package(s) x 4 core(s) > > > random: unblocking device. > > > Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid > > > Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) > > > ioapic0 irqs 0-23 on motherboard > > > ioapic1 irqs 24-55 on motherboard > > > SMP: AP CPU #3 Launched! > > > SMP: AP CPU #2 Launched! > > > SMP: AP CPU #1 Launched! > > > Timecounter "TSC-low" frequency 1547130097 Hz quality 1000 > > > random: entropy device external interface > > > kbd0 at kbdmux0 > > > netmap: loaded module > > > module_register_init: MOD_LOAD (vesa, 0xffffffff80a3bd40, 0) error 19 > > > random: registering fast source Intel Secure Key RNG > > > random: fast provider: "Intel Secure Key RNG" > > > nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX > > > platforms 390.59 Wed May 9 21:54:48 PDT 2018 > > > nexus0 > > > cryptosoft0: on motherboard > > > aesni0: on motherboard > > > acpi0: on motherboard > > > acpi0: Power Button (fixed) > > > cpu0: on acpi0 > > > cpu1: on acpi0 > > > cpu2: on acpi0 > > > cpu3: on acpi0 > > > attimer0: port 0x40-0x43 irq 0 on acpi0 > > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > > Event timer "i8254" frequency 1193182 Hz quality 100 > > > atrtc0: port 0x70-0x71 on acpi0 > > > atrtc0: registered as a time-of-day clock, resolution 1.000000s > > > Event timer "RTC" frequency 32768 Hz quality 0 > > > hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 > > on > > > acpi0 > > > Timecounter "HPET" frequency 14318180 Hz quality 950 > > > Event timer "HPET" frequency 14318180 Hz quality 450 > > > Event timer "HPET1" frequency 14318180 Hz quality 450 > > > Event timer "HPET2" frequency 14318180 Hz quality 450 > > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > > > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > > > pcib0: port 0xcf8-0xcff on acpi0 > > > pcib0: _OSC returned error 0x10 > > > pci0: on pcib0 > > > amdsmn0: on hostb0 > > > amdtemp0: on hostb0 > > > pci0: at device 0.2 (no driver attached) > > > pcib1: at device 1.3 on pci0 > > > pci1: on pcib1 > > > xhci0: mem 0xf77a0000-0xf77a7fff irq > > 32 > > > at device 0.0 on pci1 > > > xhci0: 32 bytes context size, 64-bit DMA > > > usbus0 on xhci0 > > > ----------------- > > > > > > I don't remember if I had similar USB trouble on Linux, but I definitely > > > did during my brief excursion into NetBSD. If anyone knows whether this > > is > > > likely to be a CPU, mother board or software problem, or knows of > > something > > > I can try to get more information or try to debug the thing, please let > > me > > > know. > > > > > > Thanks, > > > Phil > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > > " > > > > -- > > Bob Willcox | It's possible that the whole purpose of your life is to > > bob@immure.com | serve as a warning to others. > > Austin, TX | > > -- Bob Willcox | It's possible that the whole purpose of your life is to bob@immure.com | serve as a warning to others. Austin, TX | From owner-freebsd-stable@freebsd.org Tue Feb 11 03:49:02 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 973DA24CEA0 for ; Tue, 11 Feb 2020 03:49:02 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Gpfj3yYkz4R7M for ; Tue, 11 Feb 2020 03:49:01 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 01B3mrsb009825 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Feb 2020 21:48:53 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 01B3mrL8009824; Mon, 10 Feb 2020 21:48:53 -0600 (CST) (envelope-from bob) Date: Mon, 10 Feb 2020 21:48:53 -0600 From: Bob Willcox To: Phil Norman Cc: freebsd-stable@freebsd.org Subject: Re: USB trouble on Ryzen 3/AsRock mobo. Message-ID: <20200211034853.GI932@rancor.immure.com> Reply-To: Bob Willcox References: <20200209170544.GB932@rancor.immure.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 48Gpfj3yYkz4R7M X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [2.27 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.32)[-0.317,0]; IP_SCORE(0.39)[ip: (0.20), ipnet: 108.64.0.0/11(0.09), asn: 7018(1.72), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(1.00)[0.997,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 03:49:02 -0000 Well, I replaced the Gigabyte MB with an ASUS PRIME A3201-K and it is so far working fine. No USB_ERR_TIMEOUT spewing. The other MB never did stop spewing the errors (left it on for over 24 hours spewing). Bob On Mon, Feb 10, 2020 at 07:32:27AM +0100, Phil Norman wrote: > Hi. > > I'm afraid the best I could come up with is that the motherboard I was > using is not standards-compliant, and has a broken USB system. This might > explain why they insist you install their special drivers on Windows. > > My solution was to replace the motherboard with one that actually works > properly. > > Cheers, > Phil > > On Sun, 9 Feb 2020 at 18:05, Bob Willcox wrote: > > > Hi Phil, > > > > Did you ever determine the cause and solution to the USB_ERR_TIMEOUT errors > > you were getting? I just installed a recent 12.1 snapshot on a system with > > a > > Gigabyte GA-AB350N Ryzen motherboard and am seeing similar USB_ERR_TIMEOUT > > errors with this MB. > > > > The errors on this system appear to be continuing forever as they have been > > going on for over 30 minutes so far with no end in sight. On this system > > the > > initial dmesg messages for the usb errors looks strikingly similar to > > yours: > > > > Feb 9 18:46:57 han kernel: xhci0: Resetting controller > > Feb 9 18:46:57 han kernel: usb_alloc_device: set address 3 failed > > (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han kernel: usbd_setup_device_desc: getting device > > descriptor at addr 3 failed, USB_ERR_TIMEOUT > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > Feb 9 18:46:57 han syslogd: last message repeated 1 times > > Feb 9 18:46:57 han kernel: usbd_req_re_enumerate: addr=3, set address > > failed! (USB_ERR_TIMEOUT, ignored) > > Feb 9 18:46:57 han kernel: Root mount waiting for: usbus0 > > > > Anyone have any advice on what I can do the get this to stop? The system is > > fundamentally unusable as it is. > > > > Thanks, > > Bob > > > > On Tue, Jun 19, 2018 at 09:38:17PM +0200, Phil Norman wrote: > > > Hi. > > > > > > I've recently converted to FreeBSD, fleeing the Windowsification of > > Ubuntu. > > > I've been having some trouble with the USB system, which seems strange as > > > FreeBSD's USB stack is, according to a friend, rock solid. I'd like to > > > narrow down if this is a hardware (CPU or mobo) or software issue. > > > > > > I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac" > > > motherboard (chosen because it supports ECC RAM and fits in an ITX case). > > > > > > On a cold boot (ie starting by flipping the physical PSU power switch), > > BSD > > > boots up nice and quickly, without errors, and then runs for days > > without a > > > single USB-related error on dmesg. However, any other kind of reboot > > which > > > doesn't interrupt the electricity supply yields a large number of USB > > > errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of > > > the xhci0 controller. > > > > > > On occasion, I also get problems with my keyboard randomly stopping > > working > > > (but then, if the USB subsystem is continuously resetting, that's only to > > > be expected). I also seem to get slow USB storage device read throughput > > > (2MB/s from a USB3 SSD), although I can't rule out that being caused by > > the > > > fuse ext4fs driver. > > > > > > Here's what I see in dmesg when the USB system's in spam mode: > > > > > > ---------------- > > > xhci0: Resetting controller > > > usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > igb0: link state changed to UP > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > uhid0 on uhub3 > > > uhid0: > > on > > > usbus1 > > > uhid1 on uhub3 > > > uhid1: > > 1.10/1.22, addr 4> on usbus1 > > > ums0 on uhub2 > > > ums0: on > > > usbus1 > > > ums0: 3 buttons and [XYZ] coordinates ID=0 > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, > > > ignored) > > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > > USB_ERR_TIMEOUT > > > ugen0.2: at usbus0 (disconnected) > > > uhub_reattach_port: could not allocate new device > > > uhub1: at usbus0, port 1, addr 1 (disconnected) > > > uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > > > uhub1: 22 ports with 22 removable, self powered > > > xhci0: Resetting controller > > > ----------------- > > > > > > > > > Here's the start of dmesg: > > > > > > ----------------- > > > Copyright (c) 1992-2018 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > The Regents of the University of California. All rights reserved. > > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > > FreeBSD 11.2-PRERELEASE #0 r335198: Fri Jun 15 20:55:02 CEST 2018 > > > phil@bob:/usr/obj/usr/src/sys/BOB amd64 > > > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on > > LLVM > > > 6.0.0) > > > VT(efifb): resolution 1024x768 > > > CPU: AMD Ryzen 3 1200 Quad-Core Processor (3094.26-MHz > > K8-class > > > CPU) > > > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > > > > > > > Features=0x178bfbff > > > > > > > > Features2=0x7ed8320b > > > AMD Features=0x2e500800 > > > AMD > > > > > Features2=0x35c233ff > > > Structured Extended > > > > > Features=0x209c01a9 > > > XSAVE Features=0xf > > > AMD Extended Feature Extensions ID EBX=0x1007 > > > SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 > > > TSC: P-state invariant, performance statistics > > > real memory = 17179869184 (16384 MB) > > > avail memory = 16519221248 (15753 MB) > > > Event timer "LAPIC" quality 600 > > > ACPI APIC Table: > > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > > > FreeBSD/SMP: 1 package(s) x 4 core(s) > > > random: unblocking device. > > > Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid > > > Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) > > > ioapic0 irqs 0-23 on motherboard > > > ioapic1 irqs 24-55 on motherboard > > > SMP: AP CPU #3 Launched! > > > SMP: AP CPU #2 Launched! > > > SMP: AP CPU #1 Launched! > > > Timecounter "TSC-low" frequency 1547130097 Hz quality 1000 > > > random: entropy device external interface > > > kbd0 at kbdmux0 > > > netmap: loaded module > > > module_register_init: MOD_LOAD (vesa, 0xffffffff80a3bd40, 0) error 19 > > > random: registering fast source Intel Secure Key RNG > > > random: fast provider: "Intel Secure Key RNG" > > > nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX > > > platforms 390.59 Wed May 9 21:54:48 PDT 2018 > > > nexus0 > > > cryptosoft0: on motherboard > > > aesni0: on motherboard > > > acpi0: on motherboard > > > acpi0: Power Button (fixed) > > > cpu0: on acpi0 > > > cpu1: on acpi0 > > > cpu2: on acpi0 > > > cpu3: on acpi0 > > > attimer0: port 0x40-0x43 irq 0 on acpi0 > > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > > Event timer "i8254" frequency 1193182 Hz quality 100 > > > atrtc0: port 0x70-0x71 on acpi0 > > > atrtc0: registered as a time-of-day clock, resolution 1.000000s > > > Event timer "RTC" frequency 32768 Hz quality 0 > > > hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 > > on > > > acpi0 > > > Timecounter "HPET" frequency 14318180 Hz quality 950 > > > Event timer "HPET" frequency 14318180 Hz quality 450 > > > Event timer "HPET1" frequency 14318180 Hz quality 450 > > > Event timer "HPET2" frequency 14318180 Hz quality 450 > > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > > > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > > > pcib0: port 0xcf8-0xcff on acpi0 > > > pcib0: _OSC returned error 0x10 > > > pci0: on pcib0 > > > amdsmn0: on hostb0 > > > amdtemp0: on hostb0 > > > pci0: at device 0.2 (no driver attached) > > > pcib1: at device 1.3 on pci0 > > > pci1: on pcib1 > > > xhci0: mem 0xf77a0000-0xf77a7fff irq > > 32 > > > at device 0.0 on pci1 > > > xhci0: 32 bytes context size, 64-bit DMA > > > usbus0 on xhci0 > > > ----------------- > > > > > > I don't remember if I had similar USB trouble on Linux, but I definitely > > > did during my brief excursion into NetBSD. If anyone knows whether this > > is > > > likely to be a CPU, mother board or software problem, or knows of > > something > > > I can try to get more information or try to debug the thing, please let > > me > > > know. > > > > > > Thanks, > > > Phil > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > > " > > > > -- > > Bob Willcox | It's possible that the whole purpose of your life is to > > bob@immure.com | serve as a warning to others. > > Austin, TX | > > -- Bob Willcox | It's possible that the whole purpose of your life is to bob@immure.com | serve as a warning to others. Austin, TX | From owner-freebsd-stable@freebsd.org Tue Feb 11 14:07:15 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AA406235EFB for ; Tue, 11 Feb 2020 14:07:15 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48H4N260mYz43MY for ; Tue, 11 Feb 2020 14:07:14 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 01BE7Cgi011146 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 11 Feb 2020 08:07:12 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 01BE7Cpf011145 for freebsd-stable@freebsd.org; Tue, 11 Feb 2020 08:07:12 -0600 (CST) (envelope-from bob) Date: Tue, 11 Feb 2020 08:07:12 -0600 From: Bob Willcox To: stable list Subject: Certificate verification failures on 'make fetchindex' in /usr/ports Message-ID: <20200211140712.GJ932@rancor.immure.com> Reply-To: Bob Willcox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 48H4N260mYz43MY X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [2.25 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.39)[ip: (0.19), ipnet: 108.64.0.0/11(0.09), asn: 7018(1.72), country: US(-0.05)]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.99)[0.992,0]; NEURAL_HAM_MEDIUM(-0.33)[-0.334,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 14:07:15 -0000 Hi All, I just installed a recent snapshot of 12.1 on a new system and when I run 'make fetchindex' in the /usr/ports directory I get this: bob@han:0 /usr/ports> make fetchindex /usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2 https://www.FreeBSD.org/ports/INDEX-12.bz2 Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: Can anyone tell me how to fix this? Why would I be getting certificate verification failures? What am I missing? This is a brand new install and I have installed very little else (pdksh, ksh93, & bsdrcmds is all). Thanks, Bob -- Bob Willcox | It's possible that the whole purpose of your life is to bob@immure.com | serve as a warning to others. Austin, TX | From owner-freebsd-stable@freebsd.org Tue Feb 11 14:17:15 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1FBD5236898 for ; Tue, 11 Feb 2020 14:17:15 +0000 (UTC) (envelope-from michal.jakubik@zoho.com) Received: from sender4-pp-o93.zoho.com (sender4-pp-o93.zoho.com [136.143.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48H4bZ0zGsz44Rj for ; Tue, 11 Feb 2020 14:17:13 +0000 (UTC) (envelope-from michal.jakubik@zoho.com) ARC-Seal: i=1; a=rsa-sha256; t=1581430626; cv=none; d=zohomail.com; s=zohoarc; b=YKgfFHopc5D6fq5edfGyUsgcuFYjKrkirYeQaMOAPxtTbBrNsE5DT8ie6bzGHEndvPmk46al+Yo87pMRksxcK8f9zYupreT5hz0eqybb6JfSldr5pOqh3DncJJNwHk6qUAXfPr3gwn89UCjoCBo4V6DpBXBDDdRot4+Qx0wnbxw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1581430626; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:Reply-To:References:Subject:To; bh=PK+R5YlCq4pOBwzAmeskH0t/5ZEoqh7WmP4kE+rMwDA=; b=LUuhRTg/hz7FqqFa3kOEk3B1+JV2kRZ2sRRMc1/xuORQg2P/FdnNcKQA9rHTnN61XmQmxwVQCBFGmRufgG+5G6Z8qursQN3s3GvXA2ouQlk7PX3HHtuW0OVrrAQxDSf7kftstxbEiGXRW2QuPAwLarcHwg6zQAugmK6PL2usORE= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=swiftsmsgateway.com; spf=pass smtp.mailfrom=michal.jakubik@zoho.com; dmarc=pass header.from= header.from= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:reply-to:to:cc:message-id:in-reply-to:references:subject:mime-version:content-type:user-agent; b=aohPjrS8B5b4AY1WPAzZAef8vaYJk49Rd1o8F3oFraaTorB6mOoFvi6LsbgDQymOz4NcGb+IjaZ6 uYOHQ6N5SqN/tT782snxRojSblwgWLYOx/NtFO5tRGZYmQ0GM7Uq Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1581430621807409.2217152992854; Tue, 11 Feb 2020 06:17:01 -0800 (PST) Date: Tue, 11 Feb 2020 09:17:01 -0500 From: Mike Jakubik Reply-To: mike.jakubik@swiftsmsgateway.com To: "Bob Willcox" Cc: "stable list" Message-Id: <170349c466d.11a568c3a200262.329674455921888667@swiftsmsgateway.com> In-Reply-To: <20200211140712.GJ932@rancor.immure.com> References: <20200211140712.GJ932@rancor.immure.com> Subject: Re: Certificate verification failures on 'make fetchindex' in /usr/ports MIME-Version: 1.0 Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Rspamd-Queue-Id: 48H4bZ0zGsz44Rj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of michal.jakubik@zoho.com designates 136.143.188.93 as permitted sender) smtp.mailfrom=michal.jakubik@zoho.com X-Spamd-Result: default: False [-3.57 / 15.00]; MIME_TRACE(0.00)[0:+,1:+,2:~]; HAS_REPLYTO(0.00)[mike.jakubik@swiftsmsgateway.com]; ARC_ALLOW(-1.00)[i=1]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:136.143.188.0/23]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[swiftsmsgateway.com]; URI_COUNT_ODD(1.00)[21]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[93.188.143.136.list.dnswl.org : 127.0.15.0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-1.58)[ipnet: 136.143.188.0/24(-4.67), asn: 2639(-3.18), country: US(-0.05)]; FORGED_SENDER(0.30)[mike.jakubik@swiftsmsgateway.com,michal.jakubik@zoho.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[zoho.com]; ASN(0.00)[asn:2639, ipnet:136.143.188.0/24, country:US]; FROM_NEQ_ENVFROM(0.00)[mike.jakubik@swiftsmsgateway.com,michal.jakubik@zoho.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 14:17:15 -0000 Hi Bob, You need to install the root certificate bundle. cd /usr/ports/security/ca_root_nss/ && make install clean Cheers. ---- On Tue, 11 Feb 2020 09:07:12 -0500 Bob Willcox wrote ---- Hi All, I just installed a recent snapshot of 12.1 on a new system and when I run 'make fetchindex' in the /usr/ports directory I get this: bob@han:0 /usr/ports> make fetchindex /usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2 https://www.FreeBSD.org/ports/INDEX-12.bz2 Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: Can anyone tell me how to fix this? Why would I be getting certificate verification failures? What am I missing? This is a brand new install and I have installed very little else (pdksh, ksh93, & bsdrcmds is all). Thanks, Bob -- Bob Willcox | It's possible that the whole purpose of your life is to mailto:bob@immure.com | serve as a warning to others. Austin, TX | _______________________________________________ mailto:freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "mailto:freebsd-stable-unsubscribe@freebsd.org" Mike Jakubik https://www.swiftsmsgateway.com/ Disclaimer: This e-mail and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged or confidential. If you are not the intended recipient, or responsible for delivering the information to the intended recipient, you are hereby notified that any dissemination, distribution, printing or copying of this e-mail and any attachments is strictly prohibited. If this e-mail and any attachments were received in error, please notify the sender by reply e-mail and delete the original message. From owner-freebsd-stable@freebsd.org Tue Feb 11 17:19:04 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8500C23BB64 for ; Tue, 11 Feb 2020 17:19:04 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48H8dM4WVWz4HZ0 for ; Tue, 11 Feb 2020 17:19:03 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 01BHJ1j7011480 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Feb 2020 11:19:01 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 01BHJ1J2011477; Tue, 11 Feb 2020 11:19:01 -0600 (CST) (envelope-from bob) Date: Tue, 11 Feb 2020 11:19:01 -0600 From: Bob Willcox To: Mike Jakubik Cc: stable list Subject: Re: Certificate verification failures on 'make fetchindex' in /usr/ports Message-ID: <20200211171901.GA11453@rancor.immure.com> Reply-To: Bob Willcox References: <20200211140712.GJ932@rancor.immure.com> <170349c466d.11a568c3a200262.329674455921888667@swiftsmsgateway.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <170349c466d.11a568c3a200262.329674455921888667@swiftsmsgateway.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 48H8dM4WVWz4HZ0 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [2.04 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-0.55)[-0.546,0]; IP_SCORE(0.39)[ip: (0.19), ipnet: 108.64.0.0/11(0.09), asn: 7018(1.71), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(1.00)[0.996,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 17:19:04 -0000 Thanks alot Mike. That worked for me. Out of curriosity, is this a fairly recent change? For some reason I've never experienced this issue before, though it's been a number of months that I last installed a new system. Bob On Tue, Feb 11, 2020 at 09:17:01AM -0500, Mike Jakubik wrote: > Hi Bob, > > > > You need to install the root certificate bundle. > > > > cd /usr/ports/security/ca_root_nss/ && make install clean > > > > Cheers. > > > ---- On Tue, 11 Feb 2020 09:07:12 -0500 Bob Willcox wrote ---- > > > Hi All, > > I just installed a recent snapshot of 12.1 on a new system and when I run 'make fetchindex' > in the /usr/ports directory I get this: > > bob@han:0 /usr/ports> make fetchindex > /usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2 https://www.FreeBSD.org/ports/INDEX-12.bz2 > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > > Can anyone tell me how to fix this? Why would I be getting certificate verification > failures? What am I missing? This is a brand new install and I have installed very > little else (pdksh, ksh93, & bsdrcmds is all). > > Thanks, > Bob > > -- > Bob Willcox | It's possible that the whole purpose of your life is to > mailto:bob@immure.com | serve as a warning to others. > Austin, TX | > _______________________________________________ > mailto:freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "mailto:freebsd-stable-unsubscribe@freebsd.org" > > > > > > Mike Jakubik > > https://www.swiftsmsgateway.com/ > > > > Disclaimer: This e-mail and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged or confidential. If you are not the intended recipient, or responsible for delivering the information to the intended recipient, you are hereby notified that any dissemination, distribution, printing or copying of this e-mail and any attachments is strictly prohibited. If this e-mail and any attachments were received in error, please notify the sender by reply e-mail and delete the original message. -- Bob Willcox | It's possible that the whole purpose of your life is to bob@immure.com | serve as a warning to others. Austin, TX | From owner-freebsd-stable@freebsd.org Tue Feb 11 19:15:26 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EBB62240270; Tue, 11 Feb 2020 19:15:26 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48HCCf5nlVz4WP5; Tue, 11 Feb 2020 19:15:26 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1129) id A64072A20; Tue, 11 Feb 2020 19:15:26 +0000 (UTC) Date: Tue, 11 Feb 2020 19:15:26 +0000 From: Li-Wen Hsu To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD CI Weekly Report 2020-02-09 Message-ID: <20200211191526.GA99051@freefall.freebsd.org> Reply-To: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 19:15:27 -0000 (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2020-02-09 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2020-02-03 to 2020-02-09. During this period, we have: * 2010 builds (87.3% (+) passed, 12.7% () failed) of buildworld and buildkernel (GENERIC and LINT) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 324 test runs (61.7% (+) passed, 28.1% (-) unstable, 10.2% () exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 50 doc and www builds (96% (0) passed, 4.0% () failed) Test case status (on 2020-02-09 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | ------------------- | ---------- | ---------- | ------ | ------- | | head/amd64 | 7673 (0) | 7597 (-7) | 5 (+4) | 71 (+3) | | head/i386 | 7671 (0) | 7595 (-4) | 4 (+4) | 72 (0) | | 12-STABLE/amd64 | 7520 (0) | 7469 (-3) | 0 (0) | 51 (+3) | | 12-STABLE/i386 | 7518 (0) | 7462 (+3) | 0 (0) | 56 (-3) | | 11-STABLE/amd64 | 6861 (0) | 6811 (0) | 0 (0) | 50 (0) | | 11-STABLE/i386 | 6859 (0) | 6810 (0) | 0 (0) | 49 (0) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20200209 and archive is available at https://hackmd.io/@FreeBSD-CI/ , any help is welcome. ## News * https://ci.freebsd.org/job/FreeBSD-doc-head/ now includes building htdoc, the source of https://www.FreeBSD.org ## Failing builds and tests * https://ci.freebsd.org/job/FreeBSD-head-mips64-build/ * sys.geom.class.multipath.failloop.failloop ## Failed and fixed tests * https://ci.freebsd.org/job/FreeBSD-head-mips-build/ Workaround: disable GOOGLETEST: https://svnweb.freebsd.org/changeset/base/357703 More information is available at https://reviews.freebsd.org/D23128 * i386 boot panics after r357314 https://bugs.freebsd.org/243837 Fixed in r357463 * sys.capsicum.capsicum-test.main fails after r357412 https://bugs.freebsd.org/243839 Fixed in r357461 * lib.libc.gen.setdomainname_test.setdomainname_basic * sys.mac.portacl.nobody_test.main * sys.mac.portacl.root_test.main Fixed in https://svnweb.freebsd.org/changeset/base/357745 ## Failing and Flaky tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~13 failing and ~109 skipped cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details * Work for cleaning these failing cass are in progress * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/ * Total 3670 tests (+0), 2290 success (+13), 574 failures (-13), 806 skipped (0) ## Disabled Tests * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 * lib.libc.sys.stat_test.stat_socket https://bugs.freebsd.org/240621 * lib.libarchive.functional_test.test_write_filter_zstd https://bugs.freebsd.org/240683 * lib.libcasper.services.cap_dns.dns_test.main https://bugs.freebsd.org/241435 * local.kyua.* (31 cases) & local.lutok.* (3 cases) on 11-i386 https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/2278/testReport/ * sys.geom.class.multipath.failloop.failloop https://bugs.freebsd.org/242689 * sys.kern.ptrace_test.ptrace__procdesc_reparent_wait_child https://bugs.freebsd.org/243605 ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded * https://bugs.freebsd.org/239292 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger * https://bugs.freebsd.org/239397 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger * https://bugs.freebsd.org/239399 Flakey test case: sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger * https://bugs.freebsd.org/239425 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger * https://bugs.freebsd.org/241662 Flakey test case: lib.libarchive.functional_test.test_fuzz_iso9660 ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-stable@freebsd.org Wed Feb 12 00:20:08 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AAD4A2479D5 for ; Wed, 12 Feb 2020 00:20:08 +0000 (UTC) (envelope-from michal.jakubik@zoho.com) Received: from sender4-pp-o93.zoho.com (sender4-pp-o93.zoho.com [136.143.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48HKzC28FFz4rW8 for ; Wed, 12 Feb 2020 00:20:06 +0000 (UTC) (envelope-from michal.jakubik@zoho.com) ARC-Seal: i=1; a=rsa-sha256; t=1581466803; cv=none; d=zohomail.com; s=zohoarc; b=SYEgjznxZzJV0/CzjIlBF2n8pgYb3OPC+EfDHGkGA1iAMyo0oigMOQR8/c1Utxon4qamlWvby07NZcglQizkg1j3nSnZ+nvhGjCRkX82g02iDTZ0L2cJ+tsKyfUqu89AXwnq1F50YmnWmbXE+K96vawQkXi7hK29lU8Wnkd1ZAY= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1581466803; h=Content-Type:Date:From:In-Reply-To:MIME-Version:Message-ID:Reply-To:References:Subject:To; bh=1ZXjxwJFwxvjCJMNDEKAArjlXicLodXswf4TyH4hTCc=; b=GUl86cPIsFRzbBMkNWGseDKyrs/nbpGKrgM7cVf2hkZGwBZqnnOR++lFzIbeE8AIIPoWUlLJjBLbBViJAnY45mYUHXzxJ/LkOg/0stMy4Dgvwk7B8wsun2L8WQHzY5wYjM81SC1EqhpS/BX7ruO9if2r+oPKPc/6YJBCYigSFIw= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=swiftsmsgateway.com; spf=pass smtp.mailfrom=michal.jakubik@zoho.com; dmarc=pass header.from= header.from= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:reply-to:to:message-id:in-reply-to:references:subject:mime-version:content-type:user-agent; b=ugMyvWOjce1+Oi0UvKfQtUjUftVcehaoJFc+ygbukV3GVPJIZo0UZYszFJUH+rZqtbXlu7pK5SkV yIucHahGf6NjK6lRr8DPlwgLu4slir7BmJMiDmKQImFWE0UqUcgl Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1581466801469609.8254676242863; Tue, 11 Feb 2020 16:20:01 -0800 (PST) Date: Tue, 11 Feb 2020 19:20:01 -0500 From: Mike Jakubik Reply-To: mike.jakubik@swiftsmsgateway.com To: "stable list" Message-Id: <17036c4553a.11d35604d285670.2336320991524857666@swiftsmsgateway.com> In-Reply-To: <20200211171901.GA11453@rancor.immure.com> References: <20200211140712.GJ932@rancor.immure.com> <170349c466d.11a568c3a200262.329674455921888667@swiftsmsgateway.com> <20200211171901.GA11453@rancor.immure.com> Subject: Re: Certificate verification failures on 'make fetchindex' in /usr/ports MIME-Version: 1.0 Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Rspamd-Queue-Id: 48HKzC28FFz4rW8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of michal.jakubik@zoho.com designates 136.143.188.93 as permitted sender) smtp.mailfrom=michal.jakubik@zoho.com X-Spamd-Result: default: False [-4.57 / 15.00]; MIME_TRACE(0.00)[0:+,1:+,2:~]; HAS_REPLYTO(0.00)[mike.jakubik@swiftsmsgateway.com]; ARC_ALLOW(-1.00)[i=1]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:136.143.188.0/23]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[swiftsmsgateway.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[93.188.143.136.list.dnswl.org : 127.0.15.0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-1.58)[ipnet: 136.143.188.0/24(-4.68), asn: 2639(-3.19), country: US(-0.05)]; FORGED_SENDER(0.30)[mike.jakubik@swiftsmsgateway.com,michal.jakubik@zoho.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[zoho.com]; ASN(0.00)[asn:2639, ipnet:136.143.188.0/24, country:US]; FROM_NEQ_ENVFROM(0.00)[mike.jakubik@swiftsmsgateway.com,michal.jakubik@zoho.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2020 00:20:08 -0000 Not sure, i havent had a need to manually fetch a ports index in years, portsnap auto does it all. ---- On Tue, 11 Feb 2020 12:19:01 -0500 Bob Willcox wrote ---- Thanks alot Mike. That worked for me. Out of curriosity, is this a fairly recent change? For some reason I've never experienced this issue before, though it's been a number of months that I last installed a new system. Bob On Tue, Feb 11, 2020 at 09:17:01AM -0500, Mike Jakubik wrote: > Hi Bob, > > > > You need to install the root certificate bundle. > > > > cd /usr/ports/security/ca_root_nss/ && make install clean > > > > Cheers. > > > ---- On Tue, 11 Feb 2020 09:07:12 -0500 Bob Willcox wrote ---- > > > Hi All, > > I just installed a recent snapshot of 12.1 on a new system and when I run 'make fetchindex' > in the /usr/ports directory I get this: > > bob@han:0 /usr/ports> make fetchindex > /usr/bin/env fetch -am -o /usr/ports/INDEX-12.bz2 https://www.FreeBSD.org/ports/INDEX-12.bz2 > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > fetch: https://www.FreeBSD.org/ports/INDEX-12.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 > 34370596864:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > > Can anyone tell me how to fix this? Why would I be getting certificate verification > failures? What am I missing? This is a brand new install and I have installed very > little else (pdksh, ksh93, & bsdrcmds is all). > > Thanks, > Bob > > -- > Bob Willcox | It's possible that the whole purpose of your life is to > mailto:mailto:bob@immure.com | serve as a warning to others. > Austin, TX | > _______________________________________________ > mailto:mailto:freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "mailto:mailto:freebsd-stable-unsubscribe@freebsd.org" > > > > > > Mike Jakubik > > https://www.swiftsmsgateway.com/ > > > > Disclaimer: This e-mail and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged or confidential. If you are not the intended recipient, or responsible for delivering the information to the intended recipient, you are hereby notified that any dissemination, distribution, printing or copying of this e-mail and any attachments is strictly prohibited. If this e-mail and any attachments were received in error, please notify the sender by reply e-mail and delete the original message. -- Bob Willcox | It's possible that the whole purpose of your life is to mailto:bob@immure.com | serve as a warning to others. Austin, TX | Mike Jakubik https://www.swiftsmsgateway.com/ Disclaimer: This e-mail and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged or confidential. If you are not the intended recipient, or responsible for delivering the information to the intended recipient, you are hereby notified that any dissemination, distribution, printing or copying of this e-mail and any attachments is strictly prohibited. If this e-mail and any attachments were received in error, please notify the sender by reply e-mail and delete the original message.