From owner-freebsd-current@freebsd.org Sat Dec 7 04:57:16 2019 Return-Path: Delivered-To: freebsd-current@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 53C691C8211 for ; Sat, 7 Dec 2019 04:57:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47VHHv5H7gz4QDB; Sat, 7 Dec 2019 04:57:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id xB74vBCH073034 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 6 Dec 2019 20:57:12 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xB74vA5F073033; Fri, 6 Dec 2019 20:57:10 -0800 (PST) (envelope-from fbsd) Date: Fri, 6 Dec 2019 20:57:10 -0800 From: bob prohaska To: Alexander Motin Cc: sgk@troutmask.apl.washington.edu, Warner Losh , FreeBSD Current Subject: Re: CAM breaks USB [was Re: USB causing boot to hang] Message-ID: <20191207045709.GA72838@www.zefox.net> References: <20191206202316.GA1053@troutmask.apl.washington.edu> <20191206223144.GA3224@troutmask.apl.washington.edu> <20191206225231.GA949@troutmask.apl.washington.edu> <20191206234105.GA1027@troutmask.apl.washington.edu> <3df3ff25-9f62-6f0f-7823-e846a43725eb@FreeBSD.org> <20191207020809.GA1234@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47VHHv5H7gz4QDB X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Dec 2019 04:57:16 -0000 For what it's worth, there does seem to be something amiss with USB. An RPI2 at r355446 is having difficulty finding its USB devices on a hands-off reboot. The problem wasn't apparent until this most recent upgrade. Here's the console output: DRAM: 944MB Number of U-Boot devices: 1 U-Boot env: loaderdev='mmc 0' Found U-Boot device: disk Checking unit=0 slice= partition=... good. Booting from disk0s2a: Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x6b58cc data=0x93968+0x1edd98 syms=[0x4+0x7b420+0x4+0xcacef] /boot/entropy size=0x1000 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by U-Boot at address 0x100. Kernel entry at 0x2200180... Kernel args: (null) ---<>--- Copyright (c) 1992-2019 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 12.1-STABLE r355446 RPI2 arm FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) VT: init without driver. CPU: ARM Cortex-A7 r0p5 (ECO: 0x00000000) CPU Features: Multiprocessing, Thumb2, Security, Virtualization, Generic Timer, VMSAv7, PXN, LPAE, Coherent Walk Optional instructions: SDIV/UDIV, UMULL, SMULL, SIMD(ext) LoUU:2 LoC:3 LoUIS:2 Cache level 1: 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc 32KB/32B 2-way instruction cache Read-Alloc Cache level 2: 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc real memory = 989851648 (943 MB) avail memory = 955912192 (911 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: unblocking device. random: entropy device external interface kbd0 at kbdmux0 ofwbus0: simplebus0: mem 0x3f000000-0x3fffffff on ofwbus0 lintc0: mem 0x40000000-0x400000ff on simplebus0 intc0: mem 0xb200-0xb3ff irq 4 on simplebus0 gpio0: mem 0x200000-0x2000af irq 5,6,7,8 on simplebus0 gpio0: read-only pins: 46,48-53. gpio0: reserved pins: 48-53. gpiobus0: on gpio0 generic_timer0: irq 0,1,2,3 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 bcmwd0: mem 0x10001c-0x100027 on simplebus0 gpioc0: on gpio0 iichb0: mem 0x205000-0x20501f irq 9 on simplebus0 iichb1: mem 0x804000-0x80401f irq 10 on simplebus0 spi0: mem 0x204000-0x20401f irq 11 on simplebus0 spibus0: on spi0 bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff irq 12,13,14,15,16,17,18,19,20,21,22,23,24 on simplebus0 mbox0: mem 0xb880-0xb8bf irq 25 on simplebus0 sdhci_bcm0: mem 0x300000-0x3000ff irq 26 on simplebus0 mmc0: on sdhci_bcm0 uart0: mem 0x201000-0x201fff irq 27 on simplebus0 uart0: console (115200,n,8,1) vchiq0: mem 0xb800-0xb84f irq 28 on simplebus0 vchiq: local ver 8 (min 3), remote ver 8. pcm0: on vchiq0 bcm283x_dwcotg0: mem 0x980000-0x99ffff irq 29 on simplebus0 usbus0 on bcm283x_dwcotg0 cpulist0: on ofwbus0 cpu0: on cpulist0 bcm2835_cpufreq0: on cpu0 cpu1: on cpulist0 cpu2: on cpulist0 cpu3: on cpulist0 fb0: on ofwbus0 fbd0 on fb0 VT: initialize with new VT driver "fb". fb0: 656x416(656x416@0,0) 24bpp fb0: fbswap: 1, pitch 1968, base 0x3daac000, screen_size 818688 gpioled0: on ofwbus0 cryptosoft0: Timecounters tick every 1.000 msec iicbus0: on iichb0 iic0: on iicbus0 iicbus1: on iichb1 iic1: on iicbus1 usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 8GB at mmc0 41.6MHz/4bit/65535-block bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF Release APs Trying to mount root from ufs:/dev/ufs/rootfs [rw]... Warning: no time-of-day clock registered, system time will not be set accurately uhub0: 1 port with 1 removable, self powered Setting hostuuid: 95acec23-6e2c-11e7-8cb9-b827eb1a5a4b. Setting hostid: 0x6aebd8b6. swapon: /dev/da0b: No such file or directory Starting file system checks: /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ufs/rootfs: clugen0.2: at usbus0 euhub1 on uhub0 uhub1: on usbus0 uhub1: MTT enabled free (5579 frags, 12994 blocks, 2.3% fragmentation) Can't stat /dev/da0d: No such file or directory Can't stat /dev/da0e: No such file or directory Can't stat /dev/da0d: No such file or directory Can't stat /dev/da0e: No such file or directory Can't stat /dev/da0a: No such file or directory Can't stat /dev/da0a: No such file or directory THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/da0d (/tmp), ufs: /dev/da0e (/usr), ufs: /dev/da0a (/var) Warning! Some of the devices might not be available; retrying Waiting 30s for the root mount holders: usbus0 CAMuhub1: 5 ports with 4 removable, self powered .ugen0.3: at usbus0 smsc0 on uhub1 smsc0: on usbus0 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: 4e:61:0e:1c:ae:c0 .ugen0.4: at usbus0 umass0 on uhub1 umass0: on usbus0 .ugen0.5: at usbus0 ...............Restarting file system checks: /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ufs/rootfs: clean, 109531 free (5579 frags, 12994 blocks, 2.3% fragmentation) Can't stat /dev/da0d: No such file or directory Can't stat /dev/da0e: No such file or directory Can't stat /dev/da0d: No such file or directory Can't stat /dev/da0e: No such file or directory Can't stat /dev/da0a: No such file or directory Can't stat /dev/da0a: No such file or directory THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/da0d (/tmp), ufs: /dev/da0e (/usr), ufs: /dev/da0a (/var) Unknown error 3; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! 2019-12-06T20:07:21.926442-08:00 init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: The machine seems able to boot hands-off a kernel from r333740, so I don't think it's hardware. /boot/loader.conf contains bob@www:~ % more /boot/loader.conf kern.cam.boot_delay="20000" vm.pageout_oom_seq="2048" bob@www:~ % Booting direct to single-user, running fsck and exiting the shell brought multi-user operation. Still, It appears that recognition of an FTDI FT232 usb-serial adapter is impaired as well. It had to be unplugged and replugged after booting to be recognized. Also FWIW, an RPI3 running r355422 seems not to share the difficulty. Hope this is of some use, bob prohaska