Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1077725 > unrolled thread

Bug#997663: general: bullseye, system freezes completely when firefox freezes

Started byJacob Kochems <jacobkochems+bugtracking@gmail.com>
First post2021-10-24 01:00 +0200
Last post2021-10-24 17:30 +0200
Articles 9 — 7 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#997663: general: bullseye, system freezes completely when firefox freezes Jacob Kochems <jacobkochems+bugtracking@gmail.com> - 2021-10-24 01:00 +0200
    Bug#997663: general: bullseye, system freezes completely when firefox freezes Stephan Verbücheln <verbuecheln@posteo.de> - 2021-10-24 08:40 +0200
      Bug#997663: general: bullseye, system freezes completely when firefox freezes jacobkochems@gmail.com - 2021-10-24 12:30 +0200
        Bug#997663: general: bullseye, system freezes completely when firefox freezes Antonio Terceiro <terceiro@debian.org> - 2021-10-24 14:20 +0200
          Bug#997663: general: bullseye, system freezes completely when firefox freezes jacobkochems@gmail.com - 2021-10-24 14:40 +0200
        Bug#997663: general: bullseye, system freezes completely when firefox freezes erlenmayr@gmail.com - 2021-10-24 16:40 +0200
        Bug#997663: general: bullseye, system freezes completely when firefox freezes Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-25 07:10 +0200
    Bug#997663: general: bullseye, system freezes completely when firefox freezes Abou Al Montacir <abou.almontacir@sfr.fr> - 2021-10-24 13:10 +0200
    Bug#997663: general: bullseye, system freezes completely when firefox freezes jacobkochems@gmail.com - 2021-10-24 17:30 +0200

#1077725 — Bug#997663: general: bullseye, system freezes completely when firefox freezes

FromJacob Kochems <jacobkochems+bugtracking@gmail.com>
Date2021-10-24 01:00 +0200
SubjectBug#997663: general: bullseye, system freezes completely when firefox freezes
Message-ID<Dby9z-1Rm-1@gated-at.bofh.it>
Package: general
Severity: important
X-Debbugs-Cc: jacobkochems+bugtracking@gmail.com

Dear Maintainer,

* What led up to the situation?
When using Firefox (FF) with many open tabs it sometimes freezes and takes the
whole system with it. At this point all mouse and keyboard input is ignored. In
every case so far there was at least one tab with a YouTube video open. I
suspect using a lot of memory is the trigger here.

* What exactly did you do (or not do) that was effective (or ineffective)?
I tried to switch to a different tty via Ctrl+Alt+F<N>: no effect.
I tried the magic SysRq key sequence: REISUB: no effect.
I tried SysRq + f to call oom_kill: no effect.
Only a hard reset (power cycle) was effective so far.

* What was the outcome of this action?
The system freezes ignoring all user input.
If a video was playing at that time a short audio sequence of that video keeps
repeating in an infinite loop.

* What outcome did you expect instead?
I expect to be able to kill the offending applications.
I expect the system (be it gnome-shell, the kernel itself or other critical
components) to be able to handle failing user space programs without freezing
themselves. That is why I consider this *not* to be a bug of FF, although a bug
in FF seems to trigger it. No user space program should be able to tank the
system by hogging up resources.


Since I was unable to recover the system from this state I cannot provide any
error messages.
Is there a log file I can inspect after the fact?
If so, what should I look for?
Do I have to activate additional logging for this?

Some system information:
$ uname -v -r -m
5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64

CPU: Intel Core i7, 4 Cores
RAM: 8GB

Please let me know if you need additional system information.
I would appreciate any insight into how to diagnose this.

Thank you for your time.

Best regards,
Jacob

[toc] | [next] | [standalone]


#1077751

FromStephan Verbücheln <verbuecheln@posteo.de>
Date2021-10-24 08:40 +0200
Message-ID<DbFkJ-6nn-5@gated-at.bofh.it>
In reply to#1077725
Possibly relevant:
- Are you using X11 or Wayland?
- Do you have proprietary graphics drivers installed?
- Does the freeze occur without those?
- Can you SSH into the machine after the screen/input freezes?
- Do you have other indications that the machine is still working?

Regards

[toc] | [prev] | [next] | [standalone]


#1077785

Fromjacobkochems@gmail.com
Date2021-10-24 12:30 +0200
Message-ID<DbIVk-7E-7@gated-at.bofh.it>
In reply to#1077751
Hello Stephan,

> Possibly relevant:
> - Are you using X11 or Wayland?
Wayland

> - Do you have proprietary graphics drivers installed?
$ lspci -v | grep -A 10 VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620
(rev 02) (prog-if 00 [VGA controller])
	Subsystem: CLEVO/KAPOK Computer HD Graphics 620
	[...]
	Kernel driver in use: i915
	Kernel modules: i915
It seems to be the open source driver 'i915' in the package:
'xserver-xorg-video-intel'.

> - Does the freeze occur without those?
Does not apply. No proprietary graphics drivers installed.

> - Can you SSH into the machine after the screen/input freezes
Interesting idea. I will install 'openssh-server' and try this the next
time.

> - Do you have other indications that the machine is still working?
I'm not sure. Maybe I can try the keyboard backlight function?
Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ?

Thank you very much for your time.

Regards,
Jacob

[toc] | [prev] | [next] | [standalone]


#1077794

FromAntonio Terceiro <terceiro@debian.org>
Date2021-10-24 14:20 +0200
Message-ID<DbKDL-1cE-1@gated-at.bofh.it>
In reply to#1077785

[Multipart message — attachments visible in raw view] — view raw

On Sun, Oct 24, 2021 at 12:25:23PM +0200, jacobkochems@gmail.com wrote:
> Hello Stephan,
> 
> > Possibly relevant:
> > - Are you using X11 or Wayland?
> Wayland
> 
> > - Do you have proprietary graphics drivers installed?
> $ lspci -v | grep -A 10 VGA
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620
> (rev 02) (prog-if 00 [VGA controller])
> 	Subsystem: CLEVO/KAPOK Computer HD Graphics 620
> 	[...]
> 	Kernel driver in use: i915
> 	Kernel modules: i915
> It seems to be the open source driver 'i915' in the package:
> 'xserver-xorg-video-intel'.
> 
> > - Does the freeze occur without those?
> Does not apply. No proprietary graphics drivers installed.
> 
> > - Can you SSH into the machine after the screen/input freezes
> Interesting idea. I will install 'openssh-server' and try this the next
> time.
> 
> > - Do you have other indications that the machine is still working?
> I'm not sure. Maybe I can try the keyboard backlight function?
> Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ?

Does this only happen when on battery power?

There is https://gitlab.freedesktop.org/drm/intel/-/issues/3510 which
looks similar, and happens to me.

[toc] | [prev] | [next] | [standalone]


#1077824

Fromjacobkochems@gmail.com
Date2021-10-24 14:40 +0200
Message-ID<DbKXe-1mk-113@gated-at.bofh.it>
In reply to#1077794
Now that you mention it, often times it happened on battery power but I
couldn't swear that it didn't on AC.

Am Sonntag, dem 24.10.2021 um 09:13 -0300 schrieb Antonio Terceiro:
> On Sun, Oct 24, 2021 at 12:25:23PM +0200,
> jacobkochems@gmail.com wrote:
> > Hello Stephan,
> > 
> > > Possibly relevant:
> > > - Are you using X11 or Wayland?
> > Wayland
> > 
> > > - Do you have proprietary graphics drivers installed?
> > $ lspci -v | grep -A 10 VGA
> > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
> > 620
> > (rev 02) (prog-if 00 [VGA controller])
> >         Subsystem: CLEVO/KAPOK Computer HD Graphics 620
> >         [...]
> >         Kernel driver in use: i915
> >         Kernel modules: i915
> > It seems to be the open source driver 'i915' in the package:
> > 'xserver-xorg-video-intel'.
> > 
> > > - Does the freeze occur without those?
> > Does not apply. No proprietary graphics drivers installed.
> > 
> > > - Can you SSH into the machine after the screen/input freezes
> > Interesting idea. I will install 'openssh-server' and try this the
> > next
> > time.
> > 
> > > - Do you have other indications that the machine is still
> > > working?
> > I'm not sure. Maybe I can try the keyboard backlight function?
> > Or the Fn+Special-Function-Keys like: Volume or Display-Brightness
> > ?
> 
> Does this only happen when on battery power?
> 
> There is https://gitlab.freedesktop.org/drm/intel/-/issues/3510 which
> looks similar, and happens to me.

[toc] | [prev] | [next] | [standalone]


#1077859

Fromerlenmayr@gmail.com
Date2021-10-24 16:40 +0200
Message-ID<DbMPg-2tY-21@gated-at.bofh.it>
In reply to#1077785
On Sun, 24 Oct 2021 12:25:23 +0200 jacobkochems@gmail.com wrote:
> Wayland
> It seems to be the open source driver 'i915' in the package:
> 'xserver-xorg-video-intel'.
> Does not apply. No proprietary graphics drivers installed.
Also try to use Firefox without hardware acceleration. If a process
brings down the kernel, I would expect the bug there.

> I'm not sure. Maybe I can try the keyboard backlight function?
> Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ?
I mean networking in the first place, like the SSH. Or when you are
connected to IRC, does it time out or stay online?

This is just to narrow down where the bug is. I had the experience
before some time ago that the input and screen were frozen but the
programs were still running.

Regards

[toc] | [prev] | [next] | [standalone]


#1077905

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2021-10-25 07:10 +0200
Message-ID<Dc0pc-2zk-3@gated-at.bofh.it>
In reply to#1077785

[Multipart message — attachments visible in raw view] — view raw

On Du, 24 oct 21, 12:25:23, jacobkochems@gmail.com wrote:
> Hello Stephan,
> 
> > Possibly relevant:
> > - Are you using X11 or Wayland?
> Wayland
> 
> > - Do you have proprietary graphics drivers installed?
> $ lspci -v | grep -A 10 VGA
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620
> (rev 02) (prog-if 00 [VGA controller])
> 	Subsystem: CLEVO/KAPOK Computer HD Graphics 620
> 	[...]
> 	Kernel driver in use: i915
> 	Kernel modules: i915
> It seems to be the open source driver 'i915' in the package:
> 'xserver-xorg-video-intel'.

You can try forcing use of the 'modesetting' built-in Xorg driver, e.g. 
by removing xserver-xorg-video-intel.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#1077788

FromAbou Al Montacir <abou.almontacir@sfr.fr>
Date2021-10-24 13:10 +0200
Message-ID<DbJy1-Bu-13@gated-at.bofh.it>
In reply to#1077725

[Multipart message — attachments visible in raw view] — view raw

On Sun, 2021-10-24 at 00:50 +0200, Jacob Kochems wrote:
> That is why I consider this *not* to be a bug of FF, although a bug
> in FF seems to trigger it. No user space program should be able to tank the
> system by hogging up resources.
I fully share this idea that Linux should be robust to any kind of these
freezes.
In past most of these bugs were closed without any real fix. I hope this will
not be the case here.
-- 
Cheers,
Abou Al Montacir

[toc] | [prev] | [next] | [standalone]


#1077867

Fromjacobkochems@gmail.com
Date2021-10-24 17:30 +0200
Message-ID<DbNBD-36E-1@gated-at.bofh.it>
In reply to#1077725
I just wrote an Email to the manufacturer of my "TUXEDO InfinityBook
Pro 13" and referenced this bug report. They sell specifically Linux
suited Hardware. Since they offer a Distro of their own I hope they can
shed some light on the hardware issues raised here. If there are some
special kernel parameters to be set they should know about it.

Also, I tried to provoke the system freeze with a memory bomb:
> #include <stdio.h>
> #include <stdlib.h>
> 
> #define KIB 1024
> #define MIB (KIB * KIB)
> #define ALLOC_MIB 10
> #define ALLOC_SIZE (ALLOC_MIB * MIB)
> 
> int main (void)
> {
>   int totalMiB = 0;
> 
>   printf("membomb: started\n");
>   while (1)
>   {
>     if ( malloc(ALLOC_SIZE) == NULL )
>     {
>       printf("membomb: malloc() failed, exiting\n");
>       return 1;
>     }
>       totalMiB += ALLOC_MIB;
>       printf("membomb: total memory allocated: %d MiB\n", totalMiB);
>   }
>   return 0;
> }
I tried this on AC and on Battery to no avail I'm afraid. After some
sluggish input behaviour the system kills the process, as it should.
Maybe I need to consume the memory of the graphic chip? For Intel HD
Graphics, is that even a separate thing?

Regards,
Jacob

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web