Mailinglist Archive: opensuse-bugs (4775 mails)

< Previous Next >
[Bug 1049268] New: leap42.3/42.2 System becomes unresponsive (system freezes completely)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 18 Jul 2017 22:48:27 +0000
  • Message-id: <>

Bug ID: 1049268
Summary: leap42.3/42.2 System becomes unresponsive (system
freezes completely)
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.3
Hardware: x86-64
OS: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Firefox
Assignee: bnc-team-mozilla@xxxxxxxxxxxxxxxxxxxxxx
Reporter: spirosla@xxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

I do not know whether the problem that I describe in the following is a problem
related to the kernel or graphics subsystem or OpenSUSE or something else
(Firefox or LibreOffice per se).

The problem is similar to the Bug 1014999 [Display freezes randomly on Leap
42.2 running KDE Plasma (plasmashell 5.8.x)], but it is not identical.
Leap 42.3 has the same problem, maybe in more intensive way.

Description: The computer/display locks up at random intervals running openSUSE
Leap 42.2/Leap42.3 with the standard KDE Plasma. When this happens, the mouse
pointer may or may not still works, but the user is unable to do anything with
it. The keyboard is locked completely and the only remedy is to do a hard
shut-down (forced power down) and fresh boot. In journal there is no records
related to the locking up (if the logs of journal did not corrupted by the
locking up).

The problem

Locking up/freezing was mostly happening, when Firefox or LibreOffice or vlc
were open, but also it was happening some times, when the KDE Settings Manager
(systemsettings5), or QGIS, or Spyder3, or Chrome, or Opera was open.
When I was using Leap 42.1 I did not have any problem.
When I upgraded from Leap42.1 to 42.2, the system started locking up/freezing
randomly (over six times a day).

My Workarounds
I experimented with different processors (AMD FX-6300 and FX-6350), memory
modules, and different graphic cards: 2 Radeon (Radeon ASUS R7 240 R7240 and
Radeon SAPPHIRE RADEON HD6450) and one Nvidia (Nvidia Gigabyte GT710) on an
ASUS SABERTOOTH 990FX R2.0 motherboard. In vain: the locking up were happening
many times per day.

I managed to minimize system locking up with the following workarounds:
1) I changed boot settings. I disabled: C6-state, C1E-state, AMD Turbo Core,
and all available power savings features of AMD and Sabertooth 990FX R2.0
2) I used the RADEON HD6450 graphic card.
3) I disabled hardware accelerator in Firefox, LibreOffice and I installed the
LibreOffice 5.3.
4) I stopped using vlc in favour of Smplayer with mplayer back-end (not mpv,
because smplayer with mpv produces also locking up),
5) I created new user and new profiles for Firefox, LibreOffice.

With this workarounds I am confronting, approximately, only 1 to 3 locking ups
of the system per week - mostly when Firefox is open (none by LibreOffice).

Leap 42.3
Leap 42.3 has the same problem, maybe in more intensive way.
I installed Leap 42.3 in a new disk (standard Installation, only Main and
Update standard repos).
The system froze three times within 6 hours:
One, when I was trying to change settings in KDE System Settings
Second, with Firefox open.
Third, when I was updating the system via Yast (graphical front-end) while the
kernel 4.4.74 was being installed, with result the entire system was corrupted
and needing re-installation.
The third is most serious because locking up with only Yast running has never
been occurred in Leap 42.2.
In addition: 2017-07-18: System became unresponsive three consecutive times
when Firefox was open. Only remedy was to forced power-down.

I think that is a problem related with changes between leap 42.1 and leap 42.2
in base system, or kernel or kernel-firmware specific but I am not sure. In
addition, because in windows 7 there is no any problem, I think the locking
up/freezing of the system is not a problem being generated by my hardware.

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages