Thanks for the report Michael, and sorry about the breakage. I
believe this patch should fix the build, and I am testing it now:
--- sys/kern/kern_sysctl.c (revision 350714)
+++ sys/kern/kern_sysctl.c (working copy)
@@ -55,6 +55,7 @@
#include
#include
#include
+#include
As follows ..
--- kern_sysctl.o ---
/usr/src/sys/kern/kern_sysctl.c:1623:19: error: use of undeclared
identifier 'kdb_active'
if (arg2 == 0 || kdb_active) {
^
1 error generated.
*** [kern_sysctl.o] Error code 1
imb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 07 Aug 2019 13:02:23 +
"Poul-Henning Kamp" schrieb:
>
> In message <39fb31e6-a8ec-484c-b297-39c19a787...@gmail.com>, Enji Cooper
> writes
> :
>
> There is an "interesting" failure-mechanism when you move a disk
> between
In message <39fb31e6-a8ec-484c-b297-39c19a787...@gmail.com>, Enji Cooper writes
:
There is an "interesting" failure-mechanism when you move a disk
between 13/current and older systems which do not support ufs-hashes.
It will be prudent to make 11 and 12 clear the "use hashes" flags
in
(CCing Kirk)
> On Aug 7, 2019, at 01:37, O. Hartmann wrote:
>
> Hello,
>
> today I ran into a ctastrophy with r350671. After installing a fresh compiled
> system and rebooted the box, UEFI loader dropped a bunch of errors, like some
> hex numbers stating, that a hash/superblock has is wrong
Does mmcsd support kernel crash dumping?
>From my experience it does not. Any attempt to dump to an SD card leads
to a hang with no diagnostic. Maybe that depends on a controller?
>From reading the code, it seems that mmcsd_dump calls into the regular
write path and I could not find any
Hello,
today I ran into a ctastrophy with r350671. After installing a fresh compiled
system and rebooted the box, UEFI loader dropped a bunch of errors, like some
hex numbers stating, that a hash/superblock has is wrong and then the booting
stopped at the OK loader prompt.
Rebooting the machine
