re: panic: kernel diagnostic assertion "offset < map->dm_maps" failed
i'm pretty sure i've solved this properly this attempt, but review on this change would be appreciated. https://www.netbsd.org/~mrg/if_rge.c.v3.diff it includes a potential way to avoid wm(4) calling panic() if bus_dmamap_load*() fails.. .mrg.
daily CVS update output
Updating src tree: P src/share/man/man4/drm.4 P src/share/man/man4/lagg.4 P src/sys/dev/pci/ixgbe/ixgbe.c P src/sys/dev/pci/ixgbe/ixv.c P src/sys/net/lagg/if_lagg.c P src/tests/net/if_lagg/t_lagg.sh P src/tests/sbin/ifconfig/t_capabilities.sh P src/usr.sbin/postinstall/postinstall.in Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 42872424 Oct 19 03:03 ls-lRA.gz
Re: random lockups
On 19/10/23 02:12, Greg Troxel wrote: I realize this could be a vast number of things, flaky power, bad power supply, bad RAM, but it feels correlated with updating. I think this updated included a zfs actually-return-memory fix (which is very welcome but epsilon scary). Is anyone else seeing problems, especially new problems with netbsd-10? Yes. A week or so ago I had a similar-ish sounding lockup on 10.99.10 compiled on Oct 7. I was building NetBSD releases with two -j8 builds jobs running concurrently on a Xeon E3 with four cores, hyperthreading and 32 GB of ECC memory. In my case my two extant ssh sessions were still working, but I couldn't make new ssh sessions, "sync" hung one ssh session and the hung while running "shutdown". I'm a little bit suspicious that I pushed ZFS a bit too hard. All of my source and object files are on ZFS on that system. That system is one of a number of Xeon E3 systems I built years ago that have been thoroughly reliable. Cheers, Lloyd
random lockups
I have a 2019 Dell SFF computer, which I think has 9th gen i7, with 32G ram and a samsung ssd total memory = 32577 MB cpu0: "Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz" wd0: i915drmkms0 at pci0 dev 2 function 0: Intel UHD Graphics 630 (rev. 0x02) It's running netbsd-10 with modesetting, with most data on ZFS . Except for video artifacts, it is basically running very well. It seemed to have no issues for a while, and then I upgraded it from an august build: -rw-r--r-- 1 root wheel 24840504 Aug 6 05:51 /netbsd.ok -rw-r--r-- 1 root wheel 29577080 Oct 8 09:04 /netbsd since then, perhaps under load (building packages, rsyncing about 0.5T to an external UFS2 disk), it has locked up twice. Monitor in power save mode (which it would have gone to), no ping, need to press/hold to power off. I realize this could be a vast number of things, flaky power, bad power supply, bad RAM, but it feels correlated with updating. I think this updated included a zfs actually-return-memory fix (which is very welcome but epsilon scary). Is anyone else seeing problems, especially new problems with netbsd-10?
