Date: Mon, 13 Jun 2022 08:33:25 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <20220613153325.GA12588@www.zefox.net> In-Reply-To: <1B845A0C-EDDC-407C-96A8-AAF4E92C2A4D@yahoo.com> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <20220601214401.GA42494@www.zefox.net> <20220602045202.GA44686@www.zefox.net> <1B845A0C-EDDC-407C-96A8-AAF4E92C2A4D@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 11, 2022 at 06:52:42PM -0700, Mark Millard wrote: > There was another UFS/FFS superblock integrity-check fix today. > Time to try again? > > The fix was . . . > > The branch main has been updated by mckusick: > > URL: https://cgit.FreeBSD.org/src/commit/?id=800a53b445e7eb113ba193b1ac98631299178529 > There still seems to be something wrong. It looked like git picked up the change, but after a build/install cycle I'm still seeing: ..... Root mount waiting for: CAM Root mount waiting for: CAM da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <ASMT ASM105x 0> Fixed Direct Access SPC-4 SCSI device da0: Serial Number 12345678D558 da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors) da0: quirks=0x2<NO_6_BYTE> Mounting from ufs:/dev/da0s2a failed with error 22; retrying for 3 more seconds Mounting from ufs:/dev/da0s2a failed with error 22: Invalid fstype. Loader variables: vfs.root.mountfrom=ufs:/dev/da0s2a vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>:<device> [options] Mount <device> using filesystem <fstype> and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line> Abort manual input mountroot> ufs:/dev/da0s2a Trying to mount root from ufs:/dev/da0s2a []... Mounting from ufs:/dev/da0s2a failed with error 22; retrying for 3 more seconds Mounting from ufs:/dev/da0s2a failed with error 22: Invalid fstype. As earlier, hitting [enter] at the mountroot> prompt starts the debugger. Booting a kernel from main-n255816-e26ef41f799 goes straight to single-user: OK boot kernel.0529 Loading kernel... /boot/kernel.0529/kernel text=0x2a8 text=0x82ccb0 text=0x24c4a4 data=0x1b9f38 data=0x0+0x34e000 syms=[0x8+0x132f18+0x8+0x15ac23] Loading configured modules... /boot/kernel.0529/filemon.ko text=0x1867 text=0x19b8 data=0x510+0x20 syms=[0x8+0xd38+0x8+0x7ea] /boot/kernel.0529/umodem.ko text=0x20e0 text=0x1360 data=0x6d8+0x4 syms=[0x8+0xee8+0x8+0xb46] /boot/entropy size=0x1000 /etc/hostid size=0x25 Using DTB provided by EFI at 0x7ef5000. EFI framebuffer information: addr, size 0x3eaf0000, 0x10a800 dimensions 656 x 416 stride 656 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 ---<<BOOT>>--- GDB: debug ports: uart GDB: current port: uart KDB: debugger backends: ddb gdb KDB: current backend: ddb WARNING: Cannot find freebsd,dts-version property, cannot check DTB compliance Copyright (c) 1992-2022 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 14.0-CURRENT #74 main-n255816-e26ef41f799: Wed May 25 15:05:14 PDT 2022 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 FreeBSD clang version 14.0.3 (https://github.com/llvm/llvm-project.git llvmorg-14.0.3-0-g1f9140064dfb) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 656x416 module firmware already present! KLD file umodem.ko is missing dependencies real memory = 993984512 (947 MB) avail memory = 944148480 (900 MB) Starting CPU 1 (1) Starting CPU 2 (2) Starting CPU 3 (3) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: unblocking device. random: entropy device external interface MAP 39f34000 mode 2 pages 1 MAP 39f38000 mode 2 pages 3 MAP 39f3c000 mode 2 pages 4 MAP 3b350000 mode 2 pages 16 MAP 3f100000 mode 0 pages 1 kbd0 at kbdmux0 ofwbus0: <Open Firmware Device Tree> simplebus0: <Flattened device tree simple bus> on ofwbus0 ofw_clkbus0: <OFW clocks bus> on ofwbus0 clk_fixed0: <Fixed clock> on ofw_clkbus0 clk_fixed1: <Fixed clock> on ofw_clkbus0 regfix0: <Fixed Regulator> on ofwbus0 regfix1: <Fixed Regulator> on ofwbus0 bcm2835_firmware0: <BCM2835 Firmware> on simplebus0 ofw_clkbus1: <OFW clocks bus> on bcm2835_firmware0 psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0 intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 39 on simplebus0 gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 7,8 on simplebus0 gpiobus0: <OFW GPIO bus> on gpio0 gpio1: <Raspberry Pi Firmware GPIO controller> on bcm2835_firmware0 gpiobus1: <GPIO bus> on gpio1 mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 6 on simplebus0 generic_timer0: <ARMv7 Generic Timer> irq 1,2,3,4 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 usb_nop_xceiv0: <USB NOP PHY> on ofwbus0 bcm2835_clkman0: <BCM283x Clock Manager> mem 0x7e101000-0x7e102fff on simplebus0 gpioc0: <GPIO controller> on gpio0 uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 9 on simplebus0 uart0: console (115200,n,8,1) spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e2041ff irq 11 on simplebus0 spibus0: <OFW SPI bus> on spi0 spibus0: <unknown card> at cs 0 mode 0 spibus0: <unknown card> at cs 1 mode 0 iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 19 on simplebus0 bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 21,22 on simplebus0 usbus1 on bcm283x_dwcotg0 bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38 on simplebus0 bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023 on simplebus0 bcmrng0: <Broadcom BCM2835/BCM2838 RNG> mem 0x7e104000-0x7e10400f irq 40 on simplebus0 sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 48 on simplebus0 mmc0: <MMC/SD bus> on sdhci_bcm0 gpioc1: <GPIO controller> on gpio1 fb0: <BCM2835 VT framebuffer driver> on simplebus0 fb0: keeping existing fb bpp of 32 fbd0 on fb0 WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 14.0. VT: Replacing driver "efifb" with new "fb". fb0: 656x416(656x416@0,0) 32bpp fb0: fbswap: 1, pitch 2624, base 0x3eaf0000, screen_size 1091584 pmu0: <Performance Monitoring Unit> irq 0 on ofwbus0 cpulist0: <Open Firmware CPU Group> on ofwbus0 cpu0: <Open Firmware CPU> on cpulist0 bcm2835_cpufreq0: <CPU Frequency Control> on cpu0 cpu1: <Open Firmware CPU> on cpulist0 cpu2: <Open Firmware CPU> on cpulist0 cpu3: <Open Firmware CPU> on cpulist0 gpioled0: <GPIO LEDs> on ofwbus0 gpioled0: <led0> failed to map pin lock order reversal: (sleepable after non-sleepable) 1st 0xffff000000c49aa0 LED mtx (LED mtx, sleep mutex) @ /usr/src/sys/dev/led/led.c:298 2nd 0xffffa00000dc1c10 Raspberry Pi firmware gpio (Raspberry Pi firmware gpio, sx) @ /usr/src/sys/arm/broadcom/bcm2835/raspberrypi_gpio.c:252 lock order LED mtx -> Raspberry Pi firmware gpio attempted at: #0 0xffff0000004c9024 at witness_checkorder+0xadc #1 0xffff000000464638 at _sx_xlock+0x7c #2 0xffff0000007e1e3c at rpi_fw_gpio_pin_set+0xe8 #3 0xffff0000001c9378 at led_create_state+0x158 #4 0xffff0000001950ec at gpioled_attach+0x290 #5 0xffff000000494328 at device_attach+0x3f8 #6 0xffff000000493e98 at device_probe_and_attach+0x7c #7 0xffff0000004961e4 at bus_generic_new_pass+0xfc #8 0xffff000000496194 at bus_generic_new_pass+0xac #9 0xffff000000496194 at bus_generic_new_pass+0xac #10 0xffff00000049110c at bus_set_pass+0x4c #11 0xffff0000003e2ab0 at mi_startup+0x1fc #12 0xffff0000000008b8 at virtdone+0x7c uma_zalloc_debug: zone "malloc-64" with the following non-sleepable locks held: exclusive sleep mutex LED mtx (LED mtx) r = 0 (0xffff000000c49aa0) locked @ /usr/src/sys/dev/led/led.c:298 stack backtrace: #0 0xffff0000004c9470 at witness_debugger+0x5c #1 0xffff0000004ca66c at witness_warn+0x400 #2 0xffff0000006f8224 at uma_zalloc_debug+0x30 #3 0xffff0000006f7d98 at uma_zalloc_arg+0x2c #4 0xffff00000042e230 at malloc+0x94 #5 0xffff0000007d70a8 at bcm2835_firmware_property+0x44 #6 0xffff0000007e1e54 at rpi_fw_gpio_pin_set+0x100 #7 0xffff0000001c9378 at led_create_state+0x158 #8 0xffff0000001950ec at gpioled_attach+0x290 #9 0xffff000000494328 at device_attach+0x3f8 #10 0xffff000000493e98 at device_probe_and_attach+0x7c #11 0xffff0000004961e4 at bus_generic_new_pass+0xfc #12 0xffff000000496194 at bus_generic_new_pass+0xac #13 0xffff000000496194 at bus_generic_new_pass+0xac #14 0xffff00000049110c at bus_set_pass+0x4c #15 0xffff0000003e2ab0 at mi_startup+0x1fc #16 0xffff0000000008b8 at virtdone+0x7c uma_zalloc_debug: zone "malloc-16" with the following non-sleepable locks held: exclusive sleep mutex LED mtx (LED mtx) r = 0 (0xffff000000c49aa0) locked @ /usr/src/sys/dev/led/led.c:298 stack backtrace: #0 0xffff0000004c9470 at witness_debugger+0x5c #1 0xffff0000004ca66c at witness_warn+0x400 #2 0xffff0000006f8224 at uma_zalloc_debug+0x30 #3 0xffff0000006f7d98 at uma_zalloc_arg+0x2c #4 0xffff00000042e230 at malloc+0x94 #5 0xffff000000742d88 at bounce_bus_dmamem_alloc+0x50 #6 0xffff0000007d9b24 at bcm2835_mbox_property+0xdc #7 0xffff0000007d70dc at bcm2835_firmware_property+0x78 #8 0xffff0000007e1e54 at rpi_fw_gpio_pin_set+0x100 #9 0xffff0000001c9378 at led_create_state+0x158 #10 0xffff0000001950ec at gpioled_attach+0x290 #11 0xffff000000494328 at device_attach+0x3f8 #12 0xffff000000493e98 at device_probe_and_attach+0x7c #13 0xffff0000004961e4 at bus_generic_new_pass+0xfc #14 0xffff000000496194 at bus_generic_new_pass+0xac #15 0xffff000000496194 at bus_generic_new_pass+0xac #16 0xffff00000049110c at bus_set_pass+0x4c #17 0xffff0000003e2ab0 at mi_startup+0x1fc uma_zalloc_debug: zone "malloc-128" with the following non-sleepable locks held: exclusive sleep mutex LED mtx (LED mtx) r = 0 (0xffff000000c49aa0) locked @ /usr/src/sys/dev/led/led.c:298 stack backtrace: #0 0xffff0000004c9470 at witness_debugger+0x5c #1 0xffff0000004ca66c at witness_warn+0x400 #2 0xffff0000006f8224 at uma_zalloc_debug+0x30 #3 0xffff0000006f7d98 at uma_zalloc_arg+0x2c #4 0xffff00000042e230 at malloc+0x94 #5 0xffff000000742dd8 at bounce_bus_dmamem_alloc+0xa0 #6 0xffff0000007d9b24 at bcm2835_mbox_property+0xdc #7 0xffff0000007d70dc at bcm2835_firmware_property+0x78 #8 0xffff0000007e1e54 at rpi_fw_gpio_pin_set+0x100 #9 0xffff0000001c9378 at led_create_state+0x158 #10 0xffff0000001950ec at gpioled_attach+0x290 #11 0xffff000000494328 at device_attach+0x3f8 #12 0xffff000000493e98 at device_probe_and_attach+0x7c #13 0xffff0000004961e4 at bus_generic_new_pass+0xfc #14 0xffff000000496194 at bus_generic_new_pass+0xac #15 0xffff000000496194 at bus_generic_new_pass+0xac #16 0xffff00000049110c at bus_set_pass+0x4c #17 0xffff0000003e2ab0 at mi_startup+0x1fc uma_zalloc_debug: zone "malloc-64" with the following non-sleepable locks held: exclusive sleep mutex LED mtx (LED mtx) r = 0 (0xffff000000c49aa0) locked @ /usr/src/sys/dev/led/led.c:298 stack backtrace: #0 0xffff0000004c9470 at witness_debugger+0x5c #1 0xffff0000004ca66c at witness_warn+0x400 #2 0xffff0000006f8224 at uma_zalloc_debug+0x30 #3 0xffff0000006f7d98 at uma_zalloc_arg+0x2c #4 0xffff00000042e230 at malloc+0x94 #5 0xffff000000742e60 at bounce_bus_dmamem_alloc+0x128 #6 0xffff0000007d9b24 at bcm2835_mbox_property+0xdc #7 0xffff0000007d70dc at bcm2835_firmware_property+0x78 #8 0xffff0000007e1e54 at rpi_fw_gpio_pin_set+0x100 #9 0xffff0000001c9378 at led_create_state+0x158 #10 0xffff0000001950ec at gpioled_attach+0x290 #11 0xffff000000494328 at device_attach+0x3f8 #12 0xffff000000493e98 at device_probe_and_attach+0x7c #13 0xffff0000004961e4 at bus_generic_new_pass+0xfc #14 0xffff000000496194 at bus_generic_new_pass+0xac #15 0xffff000000496194 at bus_generic_new_pass+0xac #16 0xffff00000049110c at bus_set_pass+0x4c #17 0xffff0000003e2ab0 at mi_startup+0x1fc armv8crypto0: CPU lacks AES instructions Timecounters tick every 1.000 msec usbus1: 480Mbps High Speed USB v2.0 iicbus0: <OFW I2C bus> on iichb0 iic0: <I2C generic I/O> on iicbus0 ugen1.1: <DWCOTG OTG Root HUB> at usbus1 uhub0 on usbus1 uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 mmcsd0: 64GB <SDHC EC2QT 3.0 SN 529453E5 MFG 08/2019 by 27 SM> at mmc0 50.0MHz/4bit/65535-block bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIPT ICache,64 byte ERG,64 byte CWG> Instruction Set Attributes 0 = <CRC32> Instruction Set Attributes 1 = <> Processor Features 0 = <AdvSIMD,FP,EL3 32,EL2 32,EL1 32,EL0 32> Processor Features 1 = <> Memory Model Features 0 = <TGran4,TGran64,SNSMem,BigEnd,16bit ASID,1TB PA> Trying to mount root from ufs:/dev/da0s2a [rw]... Memory Model Features 1 = <8bit VMID> Memory Model Features 2 = <32bit CCIDX,48bit VA> Debug Features 0 = <DoubleLock,2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3,Debugv8> Debug Features 1 = <> Auxiliary Features 0 = <> Auxiliary Features 1 = <> AArch32 Instruction Set Attributes 5 = <CRC32,SEVL> AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3+v4,AdvSIMD> AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP DP Conv,SIMDHP SP Conv,SIMDSP,SIMDInt,SIMDLS,FPDNaN,FPFtZ> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 CPU 2: ARM Cortex-A53 r0p4 affinity: 2 CPU 3: ARM Cortex-A53 r0p4 affinity: 3 Release APs...done WARNING: WITNESS option enabled, expect reduced performance. uhub0: 1 port with 1 removable, self powered ugen1.2: <vendor 0x0424 product 0x9514> at usbus1 uhub1 on uhub0 uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus1 uhub1: MTT enabled Root mount waiting for: usbus1 CAM uhub1: 5 ports with 4 removable, self powered ugen1.3: <vendor 0x0424 product 0xec00> at usbus1 smsc0 on uhub1 smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus1 smsc0: chip 0xec00, rev. 0002 miibus0: <MII bus> on smsc0 smscphy0: <SMC LAN8700 10/100 interface> PHY 1 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: <USB Ethernet> on smsc0 ue0: Ethernet address: b8:27:eb:71:46:4e Root mount waiting for: usbus1 CAM ugen1.4: <VIA Labs, Inc. USB2.0 Hub> at usbus1 uhub2 on uhub1 uhub2: <VIA Labs, Inc. USB2.0 Hub, class 9/0, rev 2.10/90.70, addr 4> on usbus1 uhub2: 4 ports with 4 removable, self powered Root mount waiting for: usbus1 CAM Root mount waiting for: usbus1 CAM usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASMT ASM105x (0x174c:0x55aa) ugen1.5: <ASMT ASM105x> at usbus1 umass0 on uhub2 umass0: <ASMT ASM105x, class 0/0, rev 2.10/1.00, addr 5> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:0:0: Attached to scbus0 ugen1.6: <FTDI FT232R USB UART> at usbus1 Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM ugen1.5: <ASMT ASM105x> at usbus1 (disconnected) umass0: at uhub2, port 4, addr 5 (disconnected) umass0: detached Root mount waiting for: CAM usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASMT ASM105x (0x174c:0x55aa) ugen1.5: <ASMT ASM105x> at usbus1 umass0 on uhub2 umass0: <ASMT ASM105x, class 0/0, rev 2.10/1.00, addr 5> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:0:0: Attached to scbus0 Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <ASMT ASM105x 0> Fixed Direct Access SPC-4 SCSI device da0: Serial Number 12345678D558 da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors) da0: quirks=0x2<NO_6_BYTE> Warning: no time-of-day clock registered, system time will not be set accurately Dual Console: Serial Primary, Video Secondary Setting hostuuid: 30303030-3030-3030-3064-626136386435. Setting hostid: 0x5cd40a6a. Starting file system checks: Cannot find file system superblock Cannot find file system superblock Warning! Some of the devices might not be available; retrying Restarting file system checks: Cannot find file system superblock Cannot find file system superblock Unknown error 3; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! 2022-06-13T08:05:20.701056-07: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: root@:/ # uname -a FreeBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #74 main-n255816-e26ef41f799: Wed May 25 15:05:14 PDT 2022 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 root@:/ # root@:/ # fsck Cannot find file system superblock Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? no root@:/ # root@:/ # fsck -y Cannot find file system superblock Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? no Indeed, it looks as if the -y option of fsck is now gone..... Yet, somewhat astonishingly: root@:/ # exit Setting hostuuid: 30303030-3030-3030-3064-626136386435. Setting hostid: 0x5cd40a6a. Fast boot: skipping disk checks. Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.32/mach/CORE /usr/local/llvm10/lib Setting hostname: www.zefox.org. Setting up harvesting: [CALLOUT],[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: . lo0: link state changed to UP smsc0: chip 0xec00, rev. 0002 ue0: link state changed to DOWN ue0: link state changed to UP Starting Network: lo0 ue0. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80009<RXCSUM,VLAN_MTU,LINKSTATE> ether b8:27:eb:71:46:4e inet 50.1.20.28 netmask 0xffffff00 broadcast 50.1.20.255 media: Ethernet autoselect (100baseTX <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> Starting devd. Autoloading module: uftdi.ko uftdi0 on uhub1 uftdi0: <FT232R USB UART> on usbus1 add host 127.0.0.1: gateway lo0 fib 0: route already in table add net default: gateway 50.1.20.1 add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Updating motd:. Creating and/or trimming log files. Updating /var/run/os-release done. Starting syslogd. Clearing /tmp (X related). No core dumps found. Setting date via ntp. 13 Jun 08:22:48 ntpdate[875]: step time server 86.3.245.8 offset -24453.100209 sec Mounting late filesystems:. Starting powerd. Starting sendmail. Starting sendmail_msp_queue. Starting cron. Performing sanity check on sshd configuration. Starting sshd. Configuring vt: blanktime. Starting background file system checks in 60 seconds. Mon Jun 13 08:23:00 PDT 2022 FreeBSD/arm64 (www.zefox.org) (ttyu0) login: at which point it's possible to run well enough to update and recompile. Seemingly this is a local problem unique to my systems. In the meantime I'll try another git pull and recompile.... Thanks for writing! bob prohaska > commit 800a53b445e7eb113ba193b1ac98631299178529 > Author: Kirk McKusick <mckusick@FreeBSD.org> > AuthorDate: 2022-06-11 18:04:19 +0000 > Commit: Kirk McKusick <mckusick@FreeBSD.org> > CommitDate: 2022-06-11 18:05:14 +0000 > > Bug fix to UFS/FFS superblock integrity checks when reading a superblock. > > One of the checks was that the cylinder group size (fs_cgsize) > matched that calculated by CGSIZE(). The value calculated by CGSIZE() > has changed over time as the filesystem has evolved. Thus comparing > the value of CGSIZE() of the current generation filesystem may not > match the size as computed by CGSIZE() that was in effect at the > time an older filesystem was created. Therefore the check for > fs_cgsize is changed to simply ensure that it is not larger than > the filesystem blocksize (fs_bsize). > > Reported by: Martin Birgmeier > Tested by: Martin Birgmeier > MFC after: 1 month (with 076002f24d35) > PR: 264450 > Differential Revision: https://reviews.freebsd.org/D35219 > --- > sys/ufs/ffs/ffs_subr.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/sys/ufs/ffs/ffs_subr.c b/sys/ufs/ffs/ffs_subr.c > index f25a6cba12f4..3e31746c2cfc 100644 > --- a/sys/ufs/ffs/ffs_subr.c > +++ b/sys/ufs/ffs/ffs_subr.c > @@ -385,7 +385,7 @@ validate_sblock(struct fs *fs, int isaltsblk) > roundup(howmany(SBLOCKSIZE, fs->fs_fsize), fs->fs_frag) || > fs->fs_iblkno != fs->fs_cblkno + fs->fs_frag || > fs->fs_dblkno != fs->fs_iblkno + fs->fs_ipg / INOPF(fs) || > - fs->fs_cgsize != fragroundup(fs, CGSIZE(fs))) > + fs->fs_cgsize > fs->fs_bsize) > return (ENOENT); > if (fs->fs_csaddr != cgdmin(fs, 0) || > fs->fs_cssize != > > > === > Mark Millard > marklmi at yahoo.com > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220613153325.GA12588>