Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1021444] New: Display freeze with opensuse 42.2
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 23 Jan 2017 15:42:34 +0000
  • Message-id: <bug-1021444-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1021444


Bug ID: 1021444
Summary: Display freeze with opensuse 42.2
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: X11 Applications
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: parvathi.rajasekhar@xxxxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

I have installed brand new opensuse leap 42.2 on my new laptop . Post
installation I can see display freezes randomly but very frequently . Because
of this I need to a hard reboot everytime to get things working . I use mate
desktop environment and I can see freeze occurs 5-6 times a day .

If there is any workaround please let me know .


Hwinfo output is pasted here .


rajasekhar@blr-l-prajasekhar:~> sudo hwinfo --gfxcard
08: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: _Znp.LcWIU0SNBM0
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Device Name: "Onboard IGD"
Model: "Intel HD Graphics 520"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x1916 "HD Graphics 520"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x06dc
Revision: 0x07
Driver: "i915"
Driver Modules: "drm"
Memory Range: 0xe0000000-0xe0ffffff (rw,non-prefetchable)
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
I/O Ports: 0xf000-0xf03f (rw)
IRQ: 126 (30466 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00008086d00001916sv00001028sd000006DCbc03sc00i00"
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #8

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >