daily CVS update output
Updating src tree: P src/include/rpcsvc/yp_prot.h P src/lib/libc/arch/riscv/genassym.cf P src/lib/libc/arch/riscv/sys/__sigtramp2.S P src/sys/dev/pci/ixgbe/ixgbe.c P src/sys/net/nd.c P src/usr.bin/make/var.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 40259855 May 31 03:03 ls-lRA.gz
Re: Curious new panic
On Fri, May 31, 2024 at 12:36:13AM +, m...@netbsd.org wrote: > On Thu, May 30, 2024 at 09:17:10AM +0100, Chavdar Ivanov wrote: > > (btw, as I have reported earlier, this machine is not usable with our > > sysuitils/podman, as it comes with podman 5 apis, whereas ours is at > > 4.4). > > > > Hi, > > I happen to have a wip update to podman 5.0.3. I put it on wip/podman. > Feel free to try it out! > > ...also note, this versionof podman has trouble reading its old config files that live in ~/.config/containers/podman. I personally deleted this directory, but I don't remember what the exact error message was.
Re: Curious new panic
On Thu, May 30, 2024 at 09:17:10AM +0100, Chavdar Ivanov wrote: > (btw, as I have reported earlier, this machine is not usable with our > sysuitils/podman, as it comes with podman 5 apis, whereas ours is at > 4.4). > Hi, I happen to have a wip update to podman 5.0.3. I put it on wip/podman. Feel free to try it out!
Re: Curious new panic
On Thu, 30 May 2024 at 14:06, Markus Kilbinger wrote: > > See kern/58301 > Thanks, noted. > Am Do., 30. Mai 2024 um 14:59 Uhr schrieb Jason Thorpe : > > > > > > > > > On May 30, 2024, at 1:17 AM, Chavdar Ivanov wrote: > > > > > > Hi, > > > > > > On my amd64-current system from yesterday: > > > > > > NetBSD ymir.lorien.lan 10.99.10 NetBSD 10.99.10 (GENERIC) #6: Wed May > > > 29 17:55:25 BST 2024 > > > sysbu...@ymir.lorien.lan:/dumps/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC > > > amd64 > > > > > > I got an overnight panic, as follows: > > > ... > > > nvmm0: attached, using backend x86-vmx > > > panic: kernel diagnostic assertion "lle->la_numheld == 0" failed: > > > file "/home/sysbuild/src/sys/net/if_llatbl.c", > > > line 333 la_numheld 1 > 0, pkts_dropped 0 > > > cpu4: Begin traceback... > > > > Riastradh recently made a change in this area. Can you please file a bug > > report? > > > > -- thorpej > > --
Re: Curious new panic
See kern/58301 Am Do., 30. Mai 2024 um 14:59 Uhr schrieb Jason Thorpe : > > > > > On May 30, 2024, at 1:17 AM, Chavdar Ivanov wrote: > > > > Hi, > > > > On my amd64-current system from yesterday: > > > > NetBSD ymir.lorien.lan 10.99.10 NetBSD 10.99.10 (GENERIC) #6: Wed May > > 29 17:55:25 BST 2024 > > sysbu...@ymir.lorien.lan:/dumps/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC > > amd64 > > > > I got an overnight panic, as follows: > > ... > > nvmm0: attached, using backend x86-vmx > > panic: kernel diagnostic assertion "lle->la_numheld == 0" failed: > > file "/home/sysbuild/src/sys/net/if_llatbl.c", > > line 333 la_numheld 1 > 0, pkts_dropped 0 > > cpu4: Begin traceback... > > Riastradh recently made a change in this area. Can you please file a bug > report? > > -- thorpej >
Re: Curious new panic
> On May 30, 2024, at 5:58 AM, Jason Thorpe wrote: > Riastradh recently made a change in this area. Can you please file a bug > report? Nevermind. Someone else encountered the same problem and filed kern/58301. -- thorpej
Re: Curious new panic
> On May 30, 2024, at 1:17 AM, Chavdar Ivanov wrote: > > Hi, > > On my amd64-current system from yesterday: > > NetBSD ymir.lorien.lan 10.99.10 NetBSD 10.99.10 (GENERIC) #6: Wed May > 29 17:55:25 BST 2024 > sysbu...@ymir.lorien.lan:/dumps/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC > amd64 > > I got an overnight panic, as follows: > ... > nvmm0: attached, using backend x86-vmx > panic: kernel diagnostic assertion "lle->la_numheld == 0" failed: > file "/home/sysbuild/src/sys/net/if_llatbl.c", > line 333 la_numheld 1 > 0, pkts_dropped 0 > cpu4: Begin traceback... Riastradh recently made a change in this area. Can you please file a bug report? -- thorpej
Curious new panic
Hi, On my amd64-current system from yesterday: NetBSD ymir.lorien.lan 10.99.10 NetBSD 10.99.10 (GENERIC) #6: Wed May 29 17:55:25 BST 2024 sysbu...@ymir.lorien.lan:/dumps/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC amd64 I got an overnight panic, as follows: ... nvmm0: attached, using backend x86-vmx panic: kernel diagnostic assertion "lle->la_numheld == 0" failed: file "/home/sysbuild/src/sys/net/if_llatbl.c", line 333 la_numheld 1 > 0, pkts_dropped 0 cpu4: Begin traceback... vpanic() at netbsd:vpanic+0x173 kern_assert() at netbsd:kern_assert+0x4b lltable_drop_entry_queue() at netbsd:lltable_drop_entry_queue+0x8c llentry_free() at netbsd:llentry_free+0x67 in_lltable_free_entry() at netbsd:in_lltable_free_entry+0x2a arp_free() at netbsd:arp_free+0xc4 nd_timer() at netbsd:nd_timer+0x238 callout_softclock() at netbsd:callout_softclock+0xd2 softint_dispatch() at netbsd:softint_dispatch+0x112 DDB lost frame for netbsd:Xsoftintr+0x4c, trying 0xdd043e4790f0 Xsoftintr() at netbsd:Xsoftintr+0x4c --- interrupt --- 2ca7cb613d55b2a: cpu4: End traceback... dumping to dev 168,5 (offset=8, size=4189743): dump failed: insufficient space (7221248 < 8754551) ... I wasn't doing anything at the time, having to spend some time in bed... Before that, I was trying to figure out sysutils/podman and there was a running machine, the default fedora-coreos-40.20240416.2.0-qemu.x86_64 (btw, as I have reported earlier, this machine is not usable with our sysuitils/podman, as it comes with podman 5 apis, whereas ours is at 4.4). Chavdar --
