On 2024/10/18 12:48, joshua stein wrote:
> On Fri, 18 Oct 2024 at 13:28:05 +0100, Stuart Henderson wrote:
> > I've not got a test machine running yet, but from observations (I
> > haven't gone through all the logs to verify, those "seconds after start"
> > logs are a pain to correlate with time of
On Fri, 18 Oct 2024 at 13:28:05 +0100, Stuart Henderson wrote:
> I've not got a test machine running yet, but from observations (I
> haven't gone through all the logs to verify, those "seconds after start"
> logs are a pain to correlate with time of day!) it seems to only happen
> when the monitor
On 2024/10/14 14:30, Stuart Henderson wrote:
> On 2024/10/08 11:08, Mark Kettenis wrote:
> > > > $ ls -lh /var/log/Xorg.0.log*
> > > > -rw-r--r-- 1 root wheel 45.6K Oct 7 13:37 /var/log/Xorg.0.log
> > > > -rw-r--r-- 1 root wheel 433M Oct 3 11:48 /var/log/Xorg.0.log.old
> > > >
> > > > hmm
On 2024/10/08 11:08, Mark Kettenis wrote:
> > > $ ls -lh /var/log/Xorg.0.log*
> > > -rw-r--r-- 1 root wheel 45.6K Oct 7 13:37 /var/log/Xorg.0.log
> > > -rw-r--r-- 1 root wheel 433M Oct 3 11:48 /var/log/Xorg.0.log.old
> > >
> > > hmm, there are loads of modeline dumps:
>
> Probably means
On Tue, Oct 8, 2024 at 8:07 AM joshua stein wrote:
> On Tue, 08 Oct 2024 at 11:08:57 +0200, Mark Kettenis wrote:
> > > Date: Tue, 8 Oct 2024 00:59:19 +0100
> > > From: Stuart Henderson
> > >
> > > On 2024/10/07 14:17, Stuart Henderson wrote:
> > > > On 2024/10/07 14:04, Matthieu Herrb wrote:
> >
On 2024/10/08 09:05, joshua stein wrote:
> On Tue, 08 Oct 2024 at 11:08:57 +0200, Mark Kettenis wrote:
> > > Date: Tue, 8 Oct 2024 00:59:19 +0100
> > > From: Stuart Henderson
> > >
> > > On 2024/10/07 14:17, Stuart Henderson wrote:
> > > > On 2024/10/07 14:04, Matthieu Herrb wrote:
> > > > > The
On Tue, 08 Oct 2024 at 11:08:57 +0200, Mark Kettenis wrote:
> > Date: Tue, 8 Oct 2024 00:59:19 +0100
> > From: 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. Sometime
> Date: Tue, 8 Oct 2024 00:59:19 +0100
> From: 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.
> > >
> > >
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
=
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
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
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
12 matches
Mail list logo
