Re: panic: /e: bad dir ino 584288256 at offset 0: null entry

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

On 13/10/2020 03:45, Richard Todd wrote:
[snip]

> Dunno what in particular in there is the problem, but obviously anything
> going astray in the dma code has the potential to wreak havoc on the FS
> when there's a lot of disk I/O going on...

Can you try this patch please?

Thanks,
Nick

Index: sys/dev/acpi/virtio_acpi.c
===================================================================
RCS file: /cvsroot/src/sys/dev/acpi/virtio_acpi.c,v
retrieving revision 1.2
diff -u -p -r1.2 virtio_acpi.c
--- sys/dev/acpi/virtio_acpi.c	16 Nov 2018 23:18:17 -0000	1.2
+++ sys/dev/acpi/virtio_acpi.c	19 Oct 2020 10:13:25 -0000
@@ -95,7 +95,14 @@ virtio_acpi_attach(device_t parent, devi
 	sc->sc_handle = aa->aa_node->ad_handle;
 	msc->sc_iot = aa->aa_memt;
 	vsc->sc_dev = self;
-	vsc->sc_dmat = aa->aa_dmat;
+
+	if (BUS_DMA_TAG_VALID(aa->aa_dmat64)) {
+		aprint_verbose_dev(self, "using 64-bit DMA\n");
+		vsc->sc_dmat = aa->aa_dmat64;
+	} else {
+		aprint_verbose_dev(self, "using 32-bit DMA\n");
+		vsc->sc_dmat = aa->aa_dmat;
+	}

 	rv = acpi_resource_parse(self, aa->aa_node->ad_handle, "_CRS",
 	    &res, &acpi_resource_parse_ops_default);