Dear Paul, On Sat, Jan 30, 2021 at 10:32:13PM +1100, Paul Ripke wrote: > On Sat, Jan 30, 2021 at 12:37:31AM +0100, Reinoud Zandijk wrote: > > On Thu, Jan 28, 2021 at 11:56:30PM +1100, Paul Ripke wrote: > > > Just tried running a newly built kernel on a GCE instance, and ran into > > > this panic. The previously running kernel is 9.99.73 from back around > > > October last year. > Confirmed that a kernel built immediately prior to the following commit > works, > and fails after this commit: > https://github.com/NetBSD/src/commit/7bca0bcf21c9b3465a6ee4eef6c01be32c9de1eb Thats good to know; I found a bug in memory allocation that might explain your panic and committed a fix for it. Could you please try out -current and see if the problem still persists? > > Could you A) test with virtio v1 PCI devices? ie without legacy and if > > that > > fails too could you B) test with src/sys/dev/pci/if_vioif.c:832 commented > > out > > and see if that makes a difference? That's a new virtio 1.0 feature that > > was > > apparently negotiated and should work in transitional devices and should > > not > > be accepted in older. It could be that CGE is making a mistake there but > > negotiating EVENT_IDX shifts registers so has a big impact if it goes > > wrong. > > A) Erm, how? Read thru some of the source and saw mentions of v1.0 vs v0.9, > but didn't see a way of just disabling legacy support Legacy support has to be disabled in the hypervisor (like GCE) as it needs to pass a different PCI product number. In Qemu its a property of each virtio PCI device but in GCE it might be global. With regards, Reinoud
Attachment:
signature.asc
Description: PGP signature