http://bugzilla.opensuse.org/show_bug.cgi?id=1180316
Bug ID: 1180316
Summary: [Build 20201222] openQA test fails in kdump_and_crash
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
URL: https://openqa.opensuse.org/tests/1523048/modules/kdum
p_and_crash/steps/58
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: dimstar(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: openQA
Blocker: Yes
## Observation
openQA test in scenario
opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G
fails in
[kdump_and_crash](https://openqa.opensuse.org/tests/1523048/modules/kdump_an…
After the update to kernel 5.10, kdump_and_crash fails
crash: cannot determine length of symbol: log_end
## Test suite description
Same as jeos, plus some more tests.
## Reproducible
Fails since (at least) Build
[20190311](https://openqa.opensuse.org/tests/877894)
## Expected result
Last good: (unknown) (or more recent)
## Further details
Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus…
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177624
Bug ID: 1177624
Summary: watchdog: BUG: soft lockup - CPU#16 stuck for 23s!
[qemu-system-aar:4554]
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: aarch64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: guillaume.gardet(a)arm.com
QA Contact: qa-bugs(a)suse.de
CC: afaerber(a)suse.com, dmueller(a)suse.com
Found By: ---
Blocker: ---
Created attachment 842562
--> http://bugzilla.opensuse.org/attachment.cgi?id=842562&action=edit
dmesg.log
The D05 machine used as a worker for openqa.opensuse.org have been upgraded
from Leap 15.1 to Leap 15.2 and shows lots of performance problems.
Lots of mistyping in qemu, few screen corruptions.
Checking the kernel log (in attachment), we can see some traces related to the
watchdog.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180380
Bug ID: 1180380
Summary: Blank external monitor after resume from suspend
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: jack(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 844706
--> https://bugzilla.suse.com/attachment.cgi?id=844706&action=edit
dmesg from the system
After resuming from suspend to RAM the external display connected through DVI
port on the docking station remains blank. Internal display is fine. I can use
xrandr to make the monitor work like:
xrandr --output DP1-1 --mode some-other-mode
xrandr --output DP1-1 --mode original-mode
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1179894
Bug ID: 1179894
Summary: warnings in OBS builds from kernel+initrd about
"Warning: running kernel does not support fscaps"
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: okurz(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com,
okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com
Depends on: 1178401
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1178401 +++
## Observation
https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o…
shows repeated warnings about:
```
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
```
## Steps to reproduce
Seemingly reproducible in any build of packages, e.g.
https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00…
shows the same
## Expected result
Only errors and warnings in the log that I as package/project maintainer can
fix
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622
Bug ID: 1174622
Summary: System not reconnecting to WLAN after suspend/resume
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: holgi(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: tiwai(a)suse.com
Found By: Development
Blocker: ---
Created attachment 840122
--> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit
Output of hwinfo --netcard
System with NetworkManger is connected to a wifi network. After suspend and
resume later, it is not able to reconnect to the same wifi network. After a
reboot, system is connecting to the same wifi network without any problems.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178463
Bug ID: 1178463
Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages
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: lmb(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 843325
--> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit
lsusb -vv
With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of:
...
[ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
...
The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell,
except for these messages, all USB connected peripherals (keyboard, mouse,
webcam) are working.
Attaching lsusb -vv and dmesg output.
--
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.