Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA
On Sun, 7 Mar 2021 00:09:33 +0200 Andriy Gapon wrote: > On 06/03/2021 20:09, Yoshihiro Ota wrote: > > Hi all, > > > > I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one. > > > > After upgrading one in VMWare, 'zfs mount -a' hangs the system. > > I don't have boottime zfs mount on nor don't have zfsroot. > > I just simply ran install world/kernel and mergemaster. > > Please use procstat -kk to capture a kernel stack trace of the hung process. Actually, spining was 'kldload zfs'. Console doesn't response but ping and sshd sessions still work. procstat output is below. In addition, this doesn't happen to systems that I've been following 13-CURRENT but rather happen only wiht a system upgraded from 12.2-RELEASE to 13-RC. # procstat -kk 1049 PIDTID COMMTDNAME KSTACK 1049 100215 kldload - spa_init+0xc6 zfs_kmod_init+0x1a zfs_modevent+0x34 module_register_init+0x8c linker_load_module+0xaab kern_kldload+0xc1 sys_kldload+0x50 syscall+0x17d g_ctx+0xe280bf29 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-13.0-RC1-amd64-disc1.iso unbootable on memstick
On Sun, Mar 7, 2021, 9:49 AM Rodney W. Grimes wrote: > > Hi. > > > > Are you shure you're using *.memstick.img? > > I am shure I am NOT using memstick, as the subject says > I am using: > FreeBSD-13.0-RC1-amd64-disc1.iso > > > > *.iso are for optical drives. > > Ah, not since 12.0, these are now "hybrid" type images that > are designed to be written to either a dvd or memstick. > > > If your memstick can perfectly (or at least enough for CD loader and > > kernel) mimic optical drive, maybe with help by firmware, it would be > > able to boot. > > > > Otherwise, you should write FreeBSD-13.0-RC1-*-memstick.img with > > dd. If you are using enough-sized memstick and amd64 arch PC, > > FreeBSD-13.0-RC1-amd64-mrmstick.img should be preferred. > > > > Note that if you downloaded smaller xz compressed image, you shoule > > decompress it before writing. > > > > If you are using *-memstick.img, something should need fixed. > > I have tested the memstick image it works fine. > > I have also done further investigation and this appears to be > a Legacy/bios vs EFI mode issue. All legacy only machines > fail to boot with the above error, all dual mode machines > must be forced into either EFI only, or dual mode/EFI first > inorder to boot these images. EFI only machines boot fine. > > Is what it looks like is we have lost the ability to boot > the .iso images in bios mode from a memory stick. I have > NOT done any testing on dvd media. > > Further note all of this works fine upto and including BETA4 > on all my legacy bios machines, though I do see another > environment that fails at BETA4 and continues to, but that > is rather special, called ventoy: > https://www.ventoy.net/ > that environment is probably looking very much like a > legacy BIOS system as to the way I have my ventoy setup. > By chance, have you tried this with qemu or bhyve? If it is reproducible there, it's a lot easier to investigate. Bisecting changes on the releng/13.0 branch becomes possible quickly then Warner > > On Sun, 7 Mar 2021 01:06:14 -0800 (PST) > > "Rodney W. Grimes" wrote: > > > > > Glen, > > > Things get worse... I could at least boot the BETA4 .iso when > > > I wrote it to a memstick. I can NOT boot the RC1. I have checked > > > the sha512 of my image, wrote it twice, same results, I get: > > I have now had Michael Dexter duplicate my findings, if he > sets his machines to either legacy first, or legacy only > he gets the same boot failures that I do when using the > FreeBSD-13.0-RC1-amd64-disc1.iso > image. > > > > > > > CD Loader 1.2 > > > > > > Bulding the boot loader arguments > > > Looking up /BOOT/LOADER... File not found > > > Looking up /boot/loader... File not found > > > Boot failed > > > > > > I have tried 2 different systems, all known to have booted and > > > installed many many many FreeBSD's from prior .iso written to > > > memstick. > > Now expanded to 4 systems, 2 of which can do dual mode Legacy/EFI. > > > > > > > Regards, > > > -- > > > Rod Grimes > rgri...@freebsd.org > > > ___ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to " > freebsd-stable-unsubscr...@freebsd.org" > > > > > > -- > > Tomoaki AOKI > > > > -- > Rod Grimes > rgri...@freebsd.org > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-13.0-RC1-amd64-disc1.iso unbootable on memstick
> Hi. > > Are you shure you're using *.memstick.img? I am shure I am NOT using memstick, as the subject says I am using: FreeBSD-13.0-RC1-amd64-disc1.iso > *.iso are for optical drives. Ah, not since 12.0, these are now "hybrid" type images that are designed to be written to either a dvd or memstick. > If your memstick can perfectly (or at least enough for CD loader and > kernel) mimic optical drive, maybe with help by firmware, it would be > able to boot. > > Otherwise, you should write FreeBSD-13.0-RC1-*-memstick.img with > dd. If you are using enough-sized memstick and amd64 arch PC, > FreeBSD-13.0-RC1-amd64-mrmstick.img should be preferred. > > Note that if you downloaded smaller xz compressed image, you shoule > decompress it before writing. > > If you are using *-memstick.img, something should need fixed. I have tested the memstick image it works fine. I have also done further investigation and this appears to be a Legacy/bios vs EFI mode issue. All legacy only machines fail to boot with the above error, all dual mode machines must be forced into either EFI only, or dual mode/EFI first inorder to boot these images. EFI only machines boot fine. Is what it looks like is we have lost the ability to boot the .iso images in bios mode from a memory stick. I have NOT done any testing on dvd media. Further note all of this works fine upto and including BETA4 on all my legacy bios machines, though I do see another environment that fails at BETA4 and continues to, but that is rather special, called ventoy: https://www.ventoy.net/ that environment is probably looking very much like a legacy BIOS system as to the way I have my ventoy setup. > On Sun, 7 Mar 2021 01:06:14 -0800 (PST) > "Rodney W. Grimes" wrote: > > > Glen, > > Things get worse... I could at least boot the BETA4 .iso when > > I wrote it to a memstick. I can NOT boot the RC1. I have checked > > the sha512 of my image, wrote it twice, same results, I get: I have now had Michael Dexter duplicate my findings, if he sets his machines to either legacy first, or legacy only he gets the same boot failures that I do when using the FreeBSD-13.0-RC1-amd64-disc1.iso image. > > > > CD Loader 1.2 > > > > Bulding the boot loader arguments > > Looking up /BOOT/LOADER... File not found > > Looking up /boot/loader... File not found > > Boot failed > > > > I have tried 2 different systems, all known to have booted and > > installed many many many FreeBSD's from prior .iso written to > > memstick. Now expanded to 4 systems, 2 of which can do dual mode Legacy/EFI. > > > > Regards, > > -- > > Rod Grimes > > rgri...@freebsd.org > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > -- > Tomoaki AOKI > -- Rod Grimes rgri...@freebsd.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-13.0-RC1-amd64-disc1.iso unbootable on memstick
Hi. Are you shure you're using *.memstick.img? *.iso are for optical drives. If your memstick can perfectly (or at least enough for CD loader and kernel) mimic optical drive, maybe with help by firmware, it would be able to boot. Otherwise, you should write FreeBSD-13.0-RC1-*-memstick.img with dd. If you are using enough-sized memstick and amd64 arch PC, FreeBSD-13.0-RC1-amd64-mrmstick.img should be preferred. Note that if you downloaded smaller xz compressed image, you shoule decompress it before writing. If you are using *-memstick.img, something should need fixed. On Sun, 7 Mar 2021 01:06:14 -0800 (PST) "Rodney W. Grimes" wrote: > Glen, > Things get worse... I could at least boot the BETA4 .iso when > I wrote it to a memstick. I can NOT boot the RC1. I have checked > the sha512 of my image, wrote it twice, same results, I get: > > CD Loader 1.2 > > Bulding the boot loader arguments > Looking up /BOOT/LOADER... File not found > Looking up /boot/loader... File not found > Boot failed > > I have tried 2 different systems, all known to have booted and > installed many many many FreeBSD's from prior .iso written to > memstick. > > Regards, > -- > Rod Grimes rgri...@freebsd.org > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Tomoaki AOKI ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD-13.0-RC1-amd64-disc1.iso unbootable on memstick
Glen, Things get worse... I could at least boot the BETA4 .iso when I wrote it to a memstick. I can NOT boot the RC1. I have checked the sha512 of my image, wrote it twice, same results, I get: CD Loader 1.2 Bulding the boot loader arguments Looking up /BOOT/LOADER... File not found Looking up /boot/loader... File not found Boot failed I have tried 2 different systems, all known to have booted and installed many many many FreeBSD's from prior .iso written to memstick. Regards, -- Rod Grimes rgri...@freebsd.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: geli broken in 13.0-BETA4 and later on armv8
Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote: > [Adding arm@ and making it clearer that this is armv8-only] > > On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote: > >On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable > > wrote: > >>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4 > >>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 - > >>RK3399, arm64) has changed so that a geli-encrypted partition (using > >>AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on > >>13.0-BETA4. > > > >I've confirmed that the problem is f76393a6305b - reverting that > >commit fixes the problem in releng/13.0. > > > >I've further verified that the bug is still present in main (14.x) > >at 028616d0dd69. Could you test this patch and let me know if it fixes the issue? https://people.freebsd.org/~gonzo/patches/armv8crypto-xts-fix.diff Thanks -- gonzo ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
