Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress
On 12/09, Mark Johnston wrote: > On Thu, Dec 09, 2021 at 07:37:18PM +0100, Kirill Ponomarev wrote: > > On 12/08, Mark Johnston wrote: > > > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > > > 14.0-CURRENT > > > > #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails > > > > with the > > > > linker error shown below. > > > > > > > > Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build. > > > > > > > > > > > > [...] > > > > cc -O2 -pipe -O3 -fno-common > > > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/libelftc > > > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/common > > > > -DNDEBUG > > > > -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wall > > > > -Wno-format-y2k -W > > > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > > > -Wpointer-arith > > > > -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > > > > -Wunused-parameter > > > > -Wcast-align -Wchar-subscripts -Wnested-externs -Wredundant-decls > > > > -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations > > > > -Wthread-safety -Wno-empty-body -Wno-string-plus-int > > > > -Wno-unused-const-variable > > > > -Wno-error=unused-but-set-variable -Qunused-arguments > > > > -I/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/include > > > > -static > > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/lib > > > > -o nm nm.o > > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libdwarf > > > > -ldwarf > > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > > > -lelf > > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelftc > > > > -lelftc_pie > > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > > > -lelf -legacy ld: error: undefined symbol: uncompress > > > > >>> referenced by libdwarf_elf_init.c > > > > >>> libdwarf_elf_init.o:(_dwarf_elf_init) in archive > > > > >>> /usr/lib/libdwarf.a > > > > cc: error: linker command failed with exit code 1 (use -v to see > > > > invocation) > > > > *** [nm] Error code 1 > > > > > > Is this build using WITHOUT_CLEAN? If so I think you'll need to try a > > > clean build if you had previous built world between dbf05458e3bd and > > > 8d5d329553b3. > > > > I ran 'make clean' before buildworld and got the same issue. > > make clean, or make cleanworld? I think the latter is needed. And is > your buildworld done with WITHOUT_CLEAN set? I'm running it in /usr/src not in poudriere, so I ran with and without NO_CLEAN and ran "make cleanworld" as well, it's still failing. signature.asc Description: PGP signature
Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress
On Thu, Dec 09, 2021 at 07:37:18PM +0100, Kirill Ponomarev wrote: > On 12/08, Mark Johnston wrote: > > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > > 14.0-CURRENT > > > #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails > > > with the > > > linker error shown below. > > > > > > Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build. > > > > > > > > > [...] > > > cc -O2 -pipe -O3 -fno-common > > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/libelftc > > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/common > > > -DNDEBUG > > > -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wall -Wno-format-y2k > > > -W > > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > > -Wpointer-arith > > > -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > > > -Wunused-parameter > > > -Wcast-align -Wchar-subscripts -Wnested-externs -Wredundant-decls > > > -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations > > > -Wthread-safety -Wno-empty-body -Wno-string-plus-int > > > -Wno-unused-const-variable > > > -Wno-error=unused-but-set-variable -Qunused-arguments > > > -I/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/include > > > -static > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/lib > > > -o nm nm.o > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libdwarf > > > -ldwarf > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > > -lelf > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelftc > > > -lelftc_pie > > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > > -lelf -legacy ld: error: undefined symbol: uncompress > > > >>> referenced by libdwarf_elf_init.c > > > >>> libdwarf_elf_init.o:(_dwarf_elf_init) in archive > > > >>> /usr/lib/libdwarf.a > > > cc: error: linker command failed with exit code 1 (use -v to see > > > invocation) > > > *** [nm] Error code 1 > > > > Is this build using WITHOUT_CLEAN? If so I think you'll need to try a > > clean build if you had previous built world between dbf05458e3bd and > > 8d5d329553b3. > > I ran 'make clean' before buildworld and got the same issue. make clean, or make cleanworld? I think the latter is needed. And is your buildworld done with WITHOUT_CLEAN set?
Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress
Am Wed, 8 Dec 2021 10:43:41 -0500 schrieb Mark Johnston : > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > 14.0-CURRENT #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET > > 2021 amd64) fails with the linker error shown below. > > > > Due to this error, no FreeBSD pkg base nor NanoBSD Image can be > > build. > > > > > > [...] > > cc -O2 -pipe -O3 -fno-common > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/libelftc > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/common > > -DNDEBUG -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wall > > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > > -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align > > -Wchar-subscripts -Wnested-externs -Wredundant-decls > > -Wold-style-definition -Wno-pointer-sign > > -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body > > -Wno-string-plus-int -Wno-unused-const-variable > > -Wno-error=unused-but-set-variable -Qunused-arguments > > -I/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/include > > -static > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/lib > > -o nm nm.o > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libdwarf > > -ldwarf > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > -lelf > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelftc > > -lelftc_pie > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > -lelf -legacy ld: error: undefined symbol: uncompress > > >>> referenced by libdwarf_elf_init.c > > >>> libdwarf_elf_init.o:(_dwarf_elf_init) in archive > > >>> /usr/lib/libdwarf.a > > cc: error: linker command failed with exit code 1 (use -v to see > > invocation) *** [nm] Error code 1 > > Is this build using WITHOUT_CLEAN? If so I think you'll need to try a > clean build if you had previous built world between dbf05458e3bd and > 8d5d329553b3. > Hello. Thanks for responding. The issue occured in poudriere and indeed, I set WITHOUT_CLEAN. After deleting the obj folder poudriere and the 14-CURRENT environment compiled the 13-STABLE source as expected. Thanks. oh
Re: 14-current: unable to boot after upgrade (installworld)
tiger@dl:~ % gpart show
|
=>40 3907029088 da4 GPT (1.8T)
4010241 freebsd-boot (512K)
1064 984 - free - (492K)
2048 39070269442 freebsd-zfs (1.8T)
3907028992 136 - free - (68K)
=>40 3907029088 da5 GPT (1.8T)
4010241 freebsd-boot (512K)
1064 984 - free - (492K)
2048 39070269442 freebsd-zfs (1.8T)
3907028992 136 - free - (68K)
=>40 3907029088 da6 GPT (1.8T)
4010241 freebsd-boot (512K)
1064 984 - free - (492K)
2048 39070269442 freebsd-zfs (1.8T)
3907028992 136 - free - (68K)
=>40 3907029088 da7 GPT (1.8T)
4010241 freebsd-boot (512K)
1064 984 - free - (492K)
2048 39070269442 freebsd-zfs (1.8T)
3907028992 136 - free - (68K)
i'm not sure about video, everything happens faster than I can see :-) but
sometimes the system does not freeze and I can enter commands. Can this
help in some way?
чт, 9 дек. 2021 г. в 18:19, Toomas Soome :
>
>
> > On 9. Dec 2021, at 20:06, Sergey Dyatko wrote:
> >
> > I was sure the installer did it when I reinstalled the system from
> scratch. I
> > can load 14-current successfully after boot via PXE and installworld with
> > 13-current
> > now I did the following:
> > 1) boot from HDDs FreeBSD 14.0-CURRENT #0 main-n251494-f953785b3df (with
> > 'old' world)
> > 2)run installworld (f953785b3df)
> > 3) run `gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da${D}`
> > command , where D=4..7
> > root@dl:/usr/src # zpool status
> > pool: zroot
> > state: ONLINE
> > config:
> >
> >NAMESTATE READ WRITE CKSUM
> >zroot ONLINE 0 0 0
> > mirror-0 ONLINE 0 0 0
> >da4p2 ONLINE 0 0 0
> >da5p2 ONLINE 0 0 0
> > mirror-1 ONLINE 0 0 0
> >da6p2 ONLINE 0 0 0
> >da7p2 ONLINE 0 0 0
> > errors: No known data errors
> >
> > after `shutdown -r now` system still doesn't boot with the same error.
> As
> > far I can see, there is /boot/lua/config.lua present, but when I try to
> run
> > command more /boot/lua/config.lua system hangs with following error:
> > https://imgur.com/5p0xu6W.png
> >
>
> You seem to get 2x BTX panic, could you try to create video from console,
> so we could get register dumps?
>
> can this system do UEFI boot and if so, can you test it? Could you post
> partition tables?
>
> rgds,
> toomas
>
>
> >
> > чт, 9 дек. 2021 г. в 15:56, Warner Losh :
> >
> >> On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI
> >> wrote:
> >>
> >>> On Thu, 9 Dec 2021 13:36:10 +
> >>> "Sergey V. Dyatko" wrote:
> >>>
> Hi,
>
> Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh
> 14-current from git,it looked like this:
> 1) git pull https://git.freebsd.org/src.git /usr/src
> 2) cd /usr/src ; make buildworld; make kernel
> 3) shutdown -r now
> after that I _successfully_ booted into 14-current and continued with
> etcupdate -p
> make installworld
> etcupdate -B
> shutdown -r now
>
> but after that server doesn't come back. After I conneted to this
> >> server
> >>> via
> IPMI ip-kvm I saw following (sorry for external link):
> https://i.imgur.com/jH6MHd2.png
>
> Well. There was a migration to zol between r368473 and current 'main'
> >>> branch so
> I decided to install fresh 14-current from snapshot
> FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to
> >> avoid
> possible problems
>
> and again, after make kernel and reboot OS runs, but after
> installworld
> >>> I ended up in the same situation
>
> thoughts ?
>
> --
> wbr, Sergey
>
>
> >>>
> >>> Bootcode should be updated.
> >>> The procedure you wrote doesn't seem to update it.
> >>>
> >>
> >> The posted error is one you get when you can't read the filesystem,
> which
> >> is why you need to update
> >> boot blocks across the OpenZFS change.
> >>
> >> Warner
> >>
>
>
Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress
On 12/08, Mark Johnston wrote: > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > 14.0-CURRENT > > #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with > > the > > linker error shown below. > > > > Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build. > > > > > > [...] > > cc -O2 -pipe -O3 -fno-common > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/libelftc > > -I/pool/poudriere/jails/13amd64/usr/src/contrib/elftoolchain/common -DNDEBUG > > -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wall -Wno-format-y2k -W > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > > -Wunused-parameter > > -Wcast-align -Wchar-subscripts -Wnested-externs -Wredundant-decls > > -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations > > -Wthread-safety -Wno-empty-body -Wno-string-plus-int > > -Wno-unused-const-variable > > -Wno-error=unused-but-set-variable -Qunused-arguments > > -I/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/include > > -static > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/legacy/usr/lib > > -o nm nm.o > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libdwarf > > -ldwarf > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > -lelf > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelftc > > -lelftc_pie > > -L/pool/sources/13-STABLE/obj//pool/poudriere/jails/13amd64/usr/src/amd64.amd64/tmp/obj-tools/lib/libelf > > -lelf -legacy ld: error: undefined symbol: uncompress > > >>> referenced by libdwarf_elf_init.c > > >>> libdwarf_elf_init.o:(_dwarf_elf_init) in archive > > >>> /usr/lib/libdwarf.a > > cc: error: linker command failed with exit code 1 (use -v to see invocation) > > *** [nm] Error code 1 > > Is this build using WITHOUT_CLEAN? If so I think you'll need to try a > clean build if you had previous built world between dbf05458e3bd and > 8d5d329553b3. I ran 'make clean' before buildworld and got the same issue. signature.asc Description: PGP signature
Re: Kernel panic in networking code
On Thu, Dec 09, 2021 at 12:05:30PM -0500, Mark Johnston wrote: > On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > > Hey all, > > > > It looks like there's a potential deadlock in some networking code, > > specifically with ipv4 jails. I can reproduce by running Poudriere on > > 14-CURRENT. > > > > I am using HardenedBSD 14-CURRENT, but we don't have any changes to > > any point in the code paths that would trigger/cause this kind of > > kernel panic. > > > > I've uploaded the crash.txt file here: > > https://hardenedbsd.org/~shawn/2021-12-09_crash-01.txt > > There is some WIP to address this in https://reviews.freebsd.org/D9 > and its followup revision. Awesome. Thanks for the response! I'll follow along. I'm happy to test out the patch before it lands if needed/wanted. Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: 14-current: unable to boot after upgrade (installworld)
> On 9. Dec 2021, at 20:06, Sergey Dyatko wrote:
>
> I was sure the installer did it when I reinstalled the system from scratch. I
> can load 14-current successfully after boot via PXE and installworld with
> 13-current
> now I did the following:
> 1) boot from HDDs FreeBSD 14.0-CURRENT #0 main-n251494-f953785b3df (with
> 'old' world)
> 2)run installworld (f953785b3df)
> 3) run `gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da${D}`
> command , where D=4..7
> root@dl:/usr/src # zpool status
> pool: zroot
> state: ONLINE
> config:
>
>NAMESTATE READ WRITE CKSUM
>zroot ONLINE 0 0 0
> mirror-0 ONLINE 0 0 0
>da4p2 ONLINE 0 0 0
>da5p2 ONLINE 0 0 0
> mirror-1 ONLINE 0 0 0
>da6p2 ONLINE 0 0 0
>da7p2 ONLINE 0 0 0
> errors: No known data errors
>
> after `shutdown -r now` system still doesn't boot with the same error. As
> far I can see, there is /boot/lua/config.lua present, but when I try to run
> command more /boot/lua/config.lua system hangs with following error:
> https://imgur.com/5p0xu6W.png
>
You seem to get 2x BTX panic, could you try to create video from console, so we
could get register dumps?
can this system do UEFI boot and if so, can you test it? Could you post
partition tables?
rgds,
toomas
>
> чт, 9 дек. 2021 г. в 15:56, Warner Losh :
>
>> On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI
>> wrote:
>>
>>> On Thu, 9 Dec 2021 13:36:10 +
>>> "Sergey V. Dyatko" wrote:
>>>
Hi,
Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh
14-current from git,it looked like this:
1) git pull https://git.freebsd.org/src.git /usr/src
2) cd /usr/src ; make buildworld; make kernel
3) shutdown -r now
after that I _successfully_ booted into 14-current and continued with
etcupdate -p
make installworld
etcupdate -B
shutdown -r now
but after that server doesn't come back. After I conneted to this
>> server
>>> via
IPMI ip-kvm I saw following (sorry for external link):
https://i.imgur.com/jH6MHd2.png
Well. There was a migration to zol between r368473 and current 'main'
>>> branch so
I decided to install fresh 14-current from snapshot
FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to
>> avoid
possible problems
and again, after make kernel and reboot OS runs, but after installworld
>>> I ended up in the same situation
thoughts ?
--
wbr, Sergey
>>>
>>> Bootcode should be updated.
>>> The procedure you wrote doesn't seem to update it.
>>>
>>
>> The posted error is one you get when you can't read the filesystem, which
>> is why you need to update
>> boot blocks across the OpenZFS change.
>>
>> Warner
>>
Re: 14-current: unable to boot after upgrade (installworld)
I was sure the installer did it when I reinstalled the system from scratch. I
can load 14-current successfully after boot via PXE and installworld with
13-current
now I did the following:
1) boot from HDDs FreeBSD 14.0-CURRENT #0 main-n251494-f953785b3df (with
'old' world)
2)run installworld (f953785b3df)
3) run `gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da${D}`
command , where D=4..7
root@dl:/usr/src # zpool status
pool: zroot
state: ONLINE
config:
NAMESTATE READ WRITE CKSUM
zroot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
da4p2 ONLINE 0 0 0
da5p2 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
da6p2 ONLINE 0 0 0
da7p2 ONLINE 0 0 0
errors: No known data errors
after `shutdown -r now` system still doesn't boot with the same error. As
far I can see, there is /boot/lua/config.lua present, but when I try to run
command more /boot/lua/config.lua system hangs with following error:
https://imgur.com/5p0xu6W.png
чт, 9 дек. 2021 г. в 15:56, Warner Losh :
> On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI
> wrote:
>
> > On Thu, 9 Dec 2021 13:36:10 +
> > "Sergey V. Dyatko" wrote:
> >
> > > Hi,
> > >
> > > Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh
> > > 14-current from git,it looked like this:
> > > 1) git pull https://git.freebsd.org/src.git /usr/src
> > > 2) cd /usr/src ; make buildworld; make kernel
> > > 3) shutdown -r now
> > > after that I _successfully_ booted into 14-current and continued with
> > > etcupdate -p
> > > make installworld
> > > etcupdate -B
> > > shutdown -r now
> > >
> > > but after that server doesn't come back. After I conneted to this
> server
> > via
> > > IPMI ip-kvm I saw following (sorry for external link):
> > > https://i.imgur.com/jH6MHd2.png
> > >
> > > Well. There was a migration to zol between r368473 and current 'main'
> > branch so
> > > I decided to install fresh 14-current from snapshot
> > > FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to
> avoid
> > > possible problems
> > >
> > > and again, after make kernel and reboot OS runs, but after installworld
> > I ended up in the same situation
> > >
> > > thoughts ?
> > >
> > > --
> > > wbr, Sergey
> > >
> > >
> >
> > Bootcode should be updated.
> > The procedure you wrote doesn't seem to update it.
> >
>
> The posted error is one you get when you can't read the filesystem, which
> is why you need to update
> boot blocks across the OpenZFS change.
>
> Warner
>
Re: pkg sqlite database borked ( again ). How to restore?
Dennis Clarke via freebsd-current wrote: > Ah well ... that seems to toss a ton of errors and yet works ? Ooops. Sorry for the delay, I originally missed your post. I forgot to mention, this is for rebuilding the db from scratch, as such, you needed to delete the old db file first - hence the warnings about tables already existing, and presumably the other "UNIQUE" errors. I'd personally be uncomfortable keeping it like this, but I don't know enought about pkg, but if as you said it works, it seems the merge went ok! Cheers, Jamie
Re: Kernel panic in networking code
On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > Hey all, > > It looks like there's a potential deadlock in some networking code, > specifically with ipv4 jails. I can reproduce by running Poudriere on > 14-CURRENT. > > I am using HardenedBSD 14-CURRENT, but we don't have any changes to > any point in the code paths that would trigger/cause this kind of > kernel panic. > > I've uploaded the crash.txt file here: > https://hardenedbsd.org/~shawn/2021-12-09_crash-01.txt There is some WIP to address this in https://reviews.freebsd.org/D9 and its followup revision.
Re: 14-current: unable to boot after upgrade (installworld)
On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI wrote: > On Thu, 9 Dec 2021 13:36:10 + > "Sergey V. Dyatko" wrote: > > > Hi, > > > > Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh > > 14-current from git,it looked like this: > > 1) git pull https://git.freebsd.org/src.git /usr/src > > 2) cd /usr/src ; make buildworld; make kernel > > 3) shutdown -r now > > after that I _successfully_ booted into 14-current and continued with > > etcupdate -p > > make installworld > > etcupdate -B > > shutdown -r now > > > > but after that server doesn't come back. After I conneted to this server > via > > IPMI ip-kvm I saw following (sorry for external link): > > https://i.imgur.com/jH6MHd2.png > > > > Well. There was a migration to zol between r368473 and current 'main' > branch so > > I decided to install fresh 14-current from snapshot > > FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to avoid > > possible problems > > > > and again, after make kernel and reboot OS runs, but after installworld > I ended up in the same situation > > > > thoughts ? > > > > -- > > wbr, Sergey > > > > > > Bootcode should be updated. > The procedure you wrote doesn't seem to update it. > The posted error is one you get when you can't read the filesystem, which is why you need to update boot blocks across the OpenZFS change. Warner
Kernel panic in networking code
Hey all, It looks like there's a potential deadlock in some networking code, specifically with ipv4 jails. I can reproduce by running Poudriere on 14-CURRENT. I am using HardenedBSD 14-CURRENT, but we don't have any changes to any point in the code paths that would trigger/cause this kind of kernel panic. I've uploaded the crash.txt file here: https://hardenedbsd.org/~shawn/2021-12-09_crash-01.txt `uname -a`: FreeBSD ci-08 14.0-CURRENT-HBSD FreeBSD 14.0-CURRENT-HBSD #0 hardened/current/master-n191216-7474f245a83: Wed Dec 8 22:44:04 EST 2021 shawn@ci-08:/usr/obj/usr/src/amd64.amd64/sys/HARDENEDBSD amd64 Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: 14-current: unable to boot after upgrade (installworld)
On Thu, 9 Dec 2021 13:36:10 + "Sergey V. Dyatko" wrote: > Hi, > > Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh > 14-current from git,it looked like this: > 1) git pull https://git.freebsd.org/src.git /usr/src > 2) cd /usr/src ; make buildworld; make kernel > 3) shutdown -r now > after that I _successfully_ booted into 14-current and continued with > etcupdate -p > make installworld > etcupdate -B > shutdown -r now > > but after that server doesn't come back. After I conneted to this server via > IPMI ip-kvm I saw following (sorry for external link): > https://i.imgur.com/jH6MHd2.png > > Well. There was a migration to zol between r368473 and current 'main' branch > so > I decided to install fresh 14-current from snapshot > FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to avoid > possible problems > > and again, after make kernel and reboot OS runs, but after installworld I > ended up in the same situation > > thoughts ? > > -- > wbr, Sergey > > Bootcode should be updated. The procedure you wrote doesn't seem to update it. -- Tomoaki AOKI
Re: 14-current: unable to boot after upgrade (installworld)
On 09/12/2021 15:36, Sergey V. Dyatko wrote: Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr/src 2) cd /usr/src ; make buildworld; make kernel 3) shutdown -r now after that I _successfully_ booted into 14-current and continued with etcupdate -p make installworld etcupdate -B shutdown -r now but after that server doesn't come back. After I conneted to this server via IPMI ip-kvm I saw following (sorry for external link): https://i.imgur.com/jH6MHd2.png Well. There was a migration to zol between r368473 and current 'main' branch so I decided to install fresh 14-current from snapshot FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to avoid possible problems and again, after make kernel and reboot OS runs, but after installworld I ended up in the same situation thoughts ? Try to update boot blocks. Not sure what you use, like gptzfsboot, etc. -- Andriy Gapon
14-current: unable to boot after upgrade (installworld)
Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr/src 2) cd /usr/src ; make buildworld; make kernel 3) shutdown -r now after that I _successfully_ booted into 14-current and continued with etcupdate -p make installworld etcupdate -B shutdown -r now but after that server doesn't come back. After I conneted to this server via IPMI ip-kvm I saw following (sorry for external link): https://i.imgur.com/jH6MHd2.png Well. There was a migration to zol between r368473 and current 'main' branch so I decided to install fresh 14-current from snapshot FreeBSD-14.0-CURRENT-amd64-20211202-610d908f8a6-251253 in order to avoid possible problems and again, after make kernel and reboot OS runs, but after installworld I ended up in the same situation thoughts ? -- wbr, Sergey
