Re: uvm_fault, Xorg active, [bread() ffs2_balloc() ffs_write ...]

2024-10-07 Thread Matthieu Herrb
On Mon, Oct 07, 2024 at 12:55:08PM +0100, Stuart Henderson wrote: > I have a bunch of machines running mostly X, mate desktop environment, > chromium. > > Occasionally there are panics while the machine is idle - I left > instructions and someone on-site managed to get some photos this time. > >

Re: uvm_fault, Xorg active, [bread() ffs2_balloc() ffs_write ...]

2024-10-07 Thread Jonathan Gray
On Mon, Oct 07, 2024 at 12:55:08PM +0100, Stuart Henderson wrote: > I have a bunch of machines running mostly X, mate desktop environment, > chromium. > > Occasionally there are panics while the machine is idle - I left > instructions and someone on-site managed to get some photos this time. > >

huge Xorg.0.logs [was Re: uvm_fault, Xorg active, ...]

2024-10-07 Thread Stuart Henderson
On 2024/10/07 14:17, Stuart Henderson wrote: > On 2024/10/07 14:04, Matthieu Herrb wrote: > > The only file that Xorg writes to is its log file. Sometimes, when > > input devices go bad, it can be very verbose. > > > > Can you check if any of the Xorg.0.log files are huge ? > > yes: > > $ ls -lh

Re: uvm_fault, Xorg active, [bread() ffs2_balloc() ffs_write ...]

2024-10-07 Thread Claudio Jeker
On Mon, Oct 07, 2024 at 02:04:04PM +0200, Matthieu Herrb wrote: > On Mon, Oct 07, 2024 at 12:55:08PM +0100, Stuart Henderson wrote: > > I have a bunch of machines running mostly X, mate desktop environment, > > chromium. > > > > Occasionally there are panics while the machine is idle - I left > >

Re: uvm_fault, Xorg active, [bread() ffs2_balloc() ffs_write ...]

2024-10-07 Thread Stuart Henderson
On 2024/10/07 14:04, Matthieu Herrb wrote: > The only file that Xorg writes to is its log file. Sometimes, when > input devices go bad, it can be very verbose. > > Can you check if any of the Xorg.0.log files are huge ? yes: $ ls -lh /var/log/Xorg.0.log* -rw-r--r-- 1 root wheel 45.6K Oct 7 1

Re: uvm_fault, Xorg active, [bread() ffs2_balloc() ffs_write ...]

2024-10-07 Thread Stuart Henderson
On 2024/10/07 23:19, Jonathan Gray wrote: > try ufs_ihash.c > 1.28? Thanks, will do. (Uptime on this machine was about 7 weeks before it hit it, so it's not exactly a frequent problem - slightly easier to run into it as there are 30 of these machines). > > revision 1.

Re: Fwd: openBSD bug template

2024-10-07 Thread Kalen Romansky
log file: 00:00:00.000 [INFO] [sway/main.c:338] Sway version 1.9 00:00:00.000 [INFO] [sway/main.c:339] wlroots version 0.17.4 00:00:00.005 [INFO] [sway/main.c:120] OpenBSD Dagobah.lan 7.6 GENERIC.MP#338 amd64 ... 00:00:00.195 [DEBUG] [wlr] [backend/libinput/events.c:70] Adding wskbd0 [0:0] 00:00:00

Re: huge Xorg.0.logs [was Re: uvm_fault, Xorg active, ...]

2024-10-07 Thread Matthieu Herrb
On Tue, Oct 08, 2024 at 08:12:09AM +0200, Matthieu Herrb wrote: > > I don't know if you're hitting a bug or flaky hardware to trigger this > event flow (if it happens on more than one machine flaky hardware is > unlikely) > Looking a bit deeper in the code, this may be triggered by some applica

Re: huge Xorg.0.logs [was Re: uvm_fault, Xorg active, ...]

2024-10-07 Thread Matthieu Herrb
On Tue, Oct 08, 2024 at 08:44:05AM +0200, Matthieu Herrb wrote: > this when I've a bit more time. in the mean time the patch below > should disable the offending logs. Oops, old version. The full one is: Index: hw/xfree86/modes/xf86EdidModes.c =

Re: huge Xorg.0.logs [was Re: uvm_fault, Xorg active, ...]

2024-10-07 Thread Matthieu Herrb
On Tue, Oct 08, 2024 at 12:59:19AM +0100, Stuart Henderson wrote: > On 2024/10/07 14:17, Stuart Henderson wrote: > > On 2024/10/07 14:04, Matthieu Herrb wrote: > > > The only file that Xorg writes to is its log file. Sometimes, when > > > input devices go bad, it can be very verbose. > > > > > > C