Re: tracking down i386 mount issue between Aug 2023 and now-- RELENG_13
- In reply to: mike tancsa : "tracking down i386 mount issue between Aug 2023 and now-- RELENG_13"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 17 Jan 2024 14:02:34 UTC
On 1/16/2024 9:48 AM, mike tancsa wrote: > > I dont have truss on the box to attach to the process and ktrace > doesnt seem to show anything either. Does this sort of hang ring a > bell for anyone ? Looking back at the git logs, a coarse search for > anything to do with mount, doesnt come up with much (2 below). Also > since then a new version of clang so not quite where to start. > > Any guidance appreciated. Testing is difficult as the hang doesnt > always happen -- sometimes within a day, sometimes 5 days. ssh is > usually borked as well as some processes. I have a scaled down > telegraf agent collecting some basic stats, and the cpu is pegged at > 100%. These are single core devices so not sure what is pegging the > CPU. RAM still shows some available so it doesnt seem to be memory > pressures. > > Another data point, in one of the test boxes I have running in the lab, on the serial console before it became unresponsive, I am seeing kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) kern.ipc.maxpipekva exceeded; see tuning(7) Beyond that printing out to the console, I cant do anything with the box as its not responsive.