https://bugzilla.suse.com/show_bug.cgi?id=1182535
Bug ID: 1182535
Summary: Start-up hangs with iommu message
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: openSUSE Leap 15.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: pchadwick(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Leap startup stops with:
"Error getting iommu info. ist the iommu enabled?"
"Error initializing iommuv2"
Hardware is AMD Ryzen 5 3400G on an ASRock B450M based motherboard
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182349
Bug ID: 1182349
Summary: WARNING: CPU: 7 PID: 90 at
../drivers/gpu/drm/i915/display/intel_dp.c:1895
intel_dp_max_link_rate+0x7e/0xa0
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: hare(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Trying to feed an external EDID for i915 to facilitate headless operation on an
Intel NUC resulted in repeated warnings
Feb 17 08:47:38 localhost kernel: ------------[ cut here ]------------
Feb 17 08:47:38 localhost kernel: i915 0000:00:02.0: drm_WARN_ON(len <= 0)
Feb 17 08:47:38 localhost kernel: WARNING: CPU: 7 PID: 90 at
../drivers/gpu/drm/i915/display/in>
and a non-working display.
(Arguably the display doesn't work as it's headless, but the vncviewer for
Intel AMT stays blank, too. It doesn't when a monitor is connected.)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180260
Bug ID: 1180260
Summary: [RPi4] Switch to vc4 for display/sound (was rooted
through efifb)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: nsaenzjulienne(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
With v5.10 vc4, the driver enabling RPi's display controller, now supports
RPi4. Let's switch the board's kernel configuration and firmware config to use
this instead of efifb, which is extremely limited (no sound, no resolution
changes).
Among other things, some clocks have to be set-up as builtin, a fix is needed
in u-boot so as to cater to DT changes involved in enabling vc4 and some
overlays have to be selected in config.txt
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1179226
Bug ID: 1179226
Summary: System hang related to power saving
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: jc(a)phocean.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
# Issue :
Screen and input devices would stop responding (black screen, no TTY), as soon
as the computer goes into some low power mode.
It can be triggered by locking the screen in Gnome (through gdm), and can also
be reproduced in XFCE / LightDM by just leaving the computer for a while.
# Impact :
- black screen, no TTY access
- unresponsive system (impossible to launch new processes, reboot, no way to
switch init3 & init 5, etc.)
- SSH/network access still available, existing process seem to run
Moreover, no related log entry, no error (journalctl, dmesg...).
# Notes :
Hardware is very likely to be fine :
- no issue with a Fedora LiveUSB ;
- memtest tests passed.
# Hardware :
Asus PN40
Intel(R) Celeron(R) J4005 CPU @ 2.00GHz
Intel Corporation UHD Graphics 605 (rev 03)
# System
Tumbleweed 20201123
I have no idea on how to debug it further. My huntch is that it is power saving
related with Intel chipset.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177499
Bug ID: 1177499
Summary: prctl test fails on Tumbleweed
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: msuchanek(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
https://build.opensuse.org/package/live_build_log/home:michals/python-pytho…
@require('get_no_new_privs')
def test_no_new_privs(self):
"""Test the no_new_privs function"""
self.assertEqual(prctl.get_no_new_privs(), 0)
pid = os.fork()
if pid:
self.assertEqual(os.waitpid(pid, 0)[1], 0)
else:
prctl.set_no_new_privs(1)
self.assertEqual(prctl.get_no_new_privs(), 1)
if os.geteuid() != 0:
sp = subprocess.Popen(['ping', '-c1', 'localhost'],
stderr=subprocess.PIPE)
sp.communicate()
self.assertNotEqual(sp.returncode, 0)
os._exit(0)
It assumes that by default you cannot ping, and PR_SET_NO_NEW_PRIVS is
inherited across fork.
Has there been some change in the capabilities recently?
--
You are receiving this mail because:
You are the assignee for the bug.