re: panic: kernel diagnostic assertion "offset < map->dm_maps" failed

2023-10-16 Thread matthew green
> #3 0x80fe6e5f in kern_assert () > #4 0x8058be67 in bus_dmamap_sync () > #5 0x8044edc7 in rge_rxeof () > #6 0x804536fd in rge_intr () i'm pretty sure this is the 2nd bus_dmamap_sync() call, as that's the only dma map that has load/unload applied at run time, vs

daily CVS update output

2023-10-16 Thread NetBSD source update
Updating src tree: P src/sys/arch/amd64/amd64/locore.S P src/sys/arch/i386/i386/locore.S P src/sys/arch/vax/vax/pmap.c P src/sys/arch/x86/acpi/acpi_machdep.c P src/sys/arch/x86/acpi/acpi_wakeup.c P src/sys/arch/x86/include/genfb_machdep.h P src/sys/arch/x86/pci/pci_machdep.c P src/sys/arch/x86/x8

Re: panic: kernel diagnostic assertion "offset < map->dm_maps" failed

2023-10-16 Thread Thomas Klausner
On Tue, Oct 17, 2023 at 10:07:14AM +1100, Matthew Green wrote: > > panic: kernel diagnostic assertion "offset < map->dm_maps" failed: file > > "/usr/src/sys/arch/x86/x86/bus_dma.c", line 826 bad offset 0x0 >= 0x0 > > this is from: > > KASSERTMSG(offset < map->dm_mapsize, > "bad offset 0x%"PR

re: panic: kernel diagnostic assertion "offset < map->dm_maps" failed

2023-10-16 Thread matthew green
> panic: kernel diagnostic assertion "offset < map->dm_maps" failed: file > "/usr/src/sys/arch/x86/x86/bus_dma.c", line 826 bad offset 0x0 >= 0x0 this is from: KASSERTMSG(offset < map->dm_mapsize, "bad offset 0x%"PRIxBUSADDR" >= 0x%"PRIxBUSSIZE, offset, map->dm_mapsize); the mapsize bei

panic: kernel diagnostic assertion "offset < map->dm_maps" failed

2023-10-16 Thread Thomas Klausner
Hi! I just tried checking out pkgsrc on an nvme when the machine paniced: panic: kernel diagnostic assertion "offset < map->dm_maps" failed: file "/usr/src/sys/arch/x86/x86/bus_dma.c", line 826 bad offset 0×0 >= 0x0 That's a GENERIC 10.99.10/amd64 from releng, Oct 11. Has anyone seen this one

Automated report: NetBSD-current/i386 test failure

2023-10-16 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if_lagg/t_lagg:lagg_mtu The above test failed in each of the last 4 test runs, and passed in at least 26 consecutive runs before that. The following commits were made bet

Re: new rust

2023-10-16 Thread Havard Eidnes
>>for i in 0..u64::MAX { >>match libc::_cpuset_isset(i, set) { >> [...] >> but ... under which conditions would it seg-fault inside that >> function? > > What's does the Rust impl. of _cpuset_isset() look like? Does it > take ints by any c