On Wed, Nov 04, 2020 at 10:55:12AM +0100, Reinoud Zandijk wrote:
> qemu-system-x86_64 -accel nvmm \
> -device virtio-net-pci \
> -device virtio-rng \
> -drive id=mydrive,file=./dummy.fs,format=raw,if=nonea\
> -device virtio-blk-pci,drive=mydrive
> -cdrom boot-com.iso -nographic
>
> But
Hello again.
So after backporting the -current pmap fixes to -8 in order to be able to
be able boot -d in order be able to examine I2C panics and after fixing them
I have an operational -8 machine again only to find that the USB problems
that made me update are still there.
The simplest
> So there seems to be something seriously amiss with I2C on -8 (and -9).
After fixing that, it boots again (with the adopted pmap changes).
Nevertheless, someone should review them, of course.
> Why not take spdmem out of your kernel config for now and test the
> pmap patches ?
It then panics in dbcool_chip_ident(). So there seems to be something seriously
amiss with I2C on -8 (and -9).