On 18.11.2019. 0:31, Hrvoje Popovski wrote: > On 14.11.2019. 1:06, Stuart Henderson wrote: >> Apart from the obvious style(9) problems, can anyone give me guidance on >> how to approach this diff? I'm quite uneasy at the amount of changes but >> these >> nics are quite important, they're all over the place on Atom C3xxx boards >> which are pretty much the main "next step up" from APUs. >> >> I have an A2SDi-2C-HLN4F that I need to put in service soon (not so >> bothered about the ix on this box, I'm using 4xSFP+ ixl, but giving it >> a spin) - applying my merged diff (https://junkpile.org/ixgbe.diff2) > > with this diff box panic while booting at starting network > > ix0 at pci1 dev 0 function 0 "Intel 82599" rev 0x01: msi, address > ix1 at pci1 dev 0 function 1 "Intel 82599" rev 0x01: msi, address > em0 at pci7 dev 0 function 0 "Intel I350" rev 0x01: msi, address > em1 at pci7 dev 0 function 1 "Intel I350" rev 0x01: msi, address > > net.inet.ip.forwarding: 0 -> 1 > starting network > panic: attempt to execute user address 0x0 in supervisor mode > Stopped at db_enter+0x10: popq %rbp > TID PID UID PRFLAGS PFLAGS CPU COMMAND > *489100 47566 0 0x3 0 0K ifconfig > db_enter() at db_enter+0x10 > panic(ffffffff81cbe37d) at panic+0x128 > pageflttrap(ffff8000224ebeb0,0) at pageflttrap+0x2db > kerntrap(ffff8000224ebeb0) at kerntrap+0x91 > alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b > 0(ffff800000078000,ffff800000078000,aa0519036f37d371,ffff800000078000,ffff80000 > 0159300,7) at 0 > ixgbe_init(ffff800000078000) at ixgbe_init+0x36 > ixgbe_ioctl(ffff800000078048,8020690c,ffff800000159300) at ixgbe_ioctl+0x15a > in_ifinit(ffff800000078048,ffff800000159300,ffff8000224ec2d0,1) at > in_ifinit+0xf3 > in_ioctl_change_ifaddr(8040691a,ffff8000224ec2c0,ffff800000078048,1) at > in_ioctl_change_ifaddr+0x350 > in_ioctl(8040691a,ffff8000224ec2c0,ffff800000078048,1) at in_ioctl+0x12e > ifioctl(fffffd83b36cad80,8040691a,ffff8000224ec2c0,ffff8000ffff4ee0) at > ifioctl+0x99e > sys_ioctl(ffff8000ffff4ee0,ffff8000224ec3d0,ffff8000224ec430) at > sys_ioctl+0x3c2 > syscall(ffff8000224ec4a0) at syscall+0x389 > end trace frame: 0xffff8000224ec520, count: 0 > https://www.openbsd.org/ddb.html describes the minimum info required in bug > reports. Insufficient info makes it difficult to find and fix bugs. > ddb{0}>
it seems that 82599 is affected by this diff, x552 and x540 are fine
