On Tue, Dec 05, 2023 at 04:22:47PM +0100, Jo Geraerts wrote: > *92547 388831 1 0 7 0 mrouted
Cool, you are running a multicast router. Unfortunately this code path is not well tested. > *cpu0: receive 1: so 0xfffffd80259ea760, so_type 3, sb_cc 40 When the multicast routing daemon reads from raw socket, the kernel crashes. Kernel has no data in the queue, but counter says there should be 40 bytes. So it panics. What kind of multicast traffic are you using mrouted for? Is the machine stable if you don't start mrouted? Does it help if you emulate only one virtual CPU? It could be race or a single packet that crashes the machine. Can you use tcpdump e.g. on the vm host to see what packets are delivered to mrouted when the crash happens? It may be an IGMP packet. netstat -na and netstat -g output would be useful. fstat -p <pid of mrouted> helps to see for which sockets recvfrom(2) may be called. > wait until the kids come complaining internet is not working anymore. Sorry, no kids around to reproduce. I need your help to debug. bluhm
