On 2026-04-08 at 03:49, alain williams wrote: > On Wed, Apr 01, 2026 at 01:47:50PM -0700, Van Snyder wrote: > >> On Wed, 2026-04-01 at 21:51 +0200, M G Berberich wrote:
>>> In the firefox settings (Hamburger-menu→Settings or >>> about:preferences): General → Performance >> >> Thanks. I found and disabled them. > > It is now a week since I also disabled these in Firefox. Before so > doing I had had a problem every day or few. I think that it is > reasonable to assume a cause. > > A user program should not be able to do this. Who should I report > this to, a Debian maintainer or direct to the kernel mail list ? Based on how I understand matters, the user program (Firefox) is not, in fact, doing this; it's just the triggering factor. The thing producing the freeze/crash in cases like this is, from what I understand, invariably in one of three places: the graphics driver, the GPU *firmware*, or the userspace graphics stack (between the driver and the user-facing application). So the bug report should go to wherever the code for the component in question is maintained. For the graphics driver, if you're using one of the open graphics drivers, that will likely be either the kernel or a separate tree where the driver is developed. If you're using a proprietary graphics driver, however, it will almost certainly be the company who provides that opaque binary driver (and, as of the last time I was paying close attention to such things, sometimes an opaque binary graphics stack along with it) - in which case, good luck. For the userspace graphics stack, it will *probably* be the Mesa project. For proprietary drivers, however, see the parenthetical above. And if the problematic component is the firmware, you're almost *certainly* going to be dealing with the company who provides the GPU, since if there are any successful open-GPU-firmware projects out there - especially ones for anything vaguely like current/modern GPUs - I'm not aware of them. I don't think I have enough information about the issue to be able to advise as to which of these is the most likely appropriate place. If I were in such a situation myself, I'd either ask for advice on how to figure that out (whether by asking here, or asking in a bug report against the Debian package of the graphics driver, or asking on the LKML or in Mesa support forums, or wherever else seemed like the best fit for such a question), or give up and just file the report against the graphics driver and hope (politely) that they'd be able to figure out where it should be redirected to. > I have the journal logs which, hopefully, will be useful at finding > the problem. One may hope, but unless (and possibly even if) there's a stack trace in those logs, I suspect it more likely that it will be necessary to enable debug logging in some way - which might involve installing a custom debug build of the graphics driver, or of the stack component in question - and then reproduce the failure. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
