Bug#823983: kfreebsd-10.3: hangs at boot mounting root ZFS pool
Package: src:kfreebsd-10 Version: 10.3~svn297264-1~debug1 Severity: important Tags: experimental I have a few systems running this kernel, amd64 arch, having a ZFS root filesystem. Most are working fine, but one in particular hangs at boot, right after kernel message "Mounting root/root..." or similar. The boot partition is plain UFS. GRUB doesn't need to access the ZFS pool during boot, although it is able to. d-i can mount the pool and that way I was able to revert back to 10.1 kernel, which is fine. The pool is comprised of only one device, which is an msdos primary partition. System has only 1GiB RAM which may be relevant, though with 10.1 it had been stable for months. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.3-0-amd64 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
libarchive 3.2.0 testsuite failure causes FTBFS on kfreebsd
Hello kfreebsd porters! I've recently uploaded a new upstream release of libarchive (3.2.0) to experimental. Apparently there's a regression on kfreebsd where one of the tests now fails and we thus get FTBFS on kfreebsd-*. Unfortunately the details of the failing test is not available in the build log (only which files to look at), so a local build is needed to be able to investigate it. eg: | FAIL: bsdtar_test | = | | | If tests fail or crash, details will be in: |/tmp/bsdtar_test.2016-05-06T11.18.44-000 (above snippet from: https://buildd.debian.org/status/fetch.php?pkg=libarchive=kfreebsd-amd64=3.2.0-1=1462533614 ) To make the matter worse we also have Bug#823893 (CVE-2016-1541) which is fixed in 3.2.0 and I'd thus like to upload it to unstable ASAP. Do you think there's any chance you will find time to help out with looking into the cause of the regression any time soon? Do you think uploading libarchive 3.2.0 to unstable would cause you much problems? Do you think we should delay (and for how long) the upload given the above mentioned circumstances? Regards, Andreas Henriksson
