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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173819
Bug ID: 1173819
Summary: 'BUG: workqueue lockup' on ThunderX2 machines with
kernel 4.12.14 in OBS
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: aarch64
OS: Other
Status: NEW
Severity: Normal
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: adrian.schroeter(a)suse.com, afaerber(a)suse.com,
dmueller(a)suse.com
Found By: ---
Blocker: ---
obs-arm-7, -8 and -9 are often down in OBS these days due to kernel issues.
One issue is a workqueue lockup:
BUG: workqueue lockup - pool cpus=59 node=0 flags=0x0 nice=0 stuck for 92265s!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1173776
Bug ID: 1173776
Summary: media: add support for eyeTV Geniatech T2 lite
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: Other
OS: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: thomas(a)abiwatch.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Would you consider to pick following patch into your kernel for Leap 15.2?
commit 14494583336880640654300c76d0f5df3360d85f
media: dvbsky: add support for eyeTV Geniatech T2 lite
It went in to v5.5 and later it got automatically added to stable v5.4.y.
It should apply cleanly and just work.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172541
Bug ID: 1172541
Summary: Mysterious crashes with kernel 5.6.14
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Factory
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: jimc(a)jfcarter.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Version: kernel-default-5.6.14-1.1.x86_64 and aarch64 for Tumbleweed
I did a dist-upgrade on 2020-06-02. After I waited for
download.opensuse.org to recover from its illness, the upgrade went
smoothly. But after I rebooted all the machines, 5 to 10 minutes
later two of them went catatonic, and a third (my laptop) froze up
a few minutes after being booted up two days later. After I power cycled
the gateway machine, it again froze about five minutes after booting.
On those hosts I reverted (by the grub menu) to
kernel-default-5.6.12-1.3.x86_64 and aarch64. There were no further
catatonic incidents. The other hosts continued (on 5.6.14) for up to
36 hours and did not go catatonic (but I eventually reverted them also).
Here are the symptoms: On two machines I was working on the console
(XFCE) when it happened. It seemed perfectly normal, but suddenly
keystrokes had no effect and continuously updating apps (load meter
etc.) ceased updating. On the gateway, network thru traffic was no
longer forwarded. After I rebooted it I checked syslog (debug level).
After the last normal message (e.g. DHCP lease renewed) there was a
burst of \0's, and the dmesg dump appeared immediately after, starting
with "microcode updated early to revision..." and "Jun 4 08:47:03
jacinth kernel: [ 0.000000] Linux version 5.6.12-1-default
(geeko@buildhost) (gcc version 9.3.1 20200406 [revision
6db837a5288ee3ca5ec504fbd5a765817e556ac2] (SUSE Linux)) #1 SMP Tue May
12 17:44:12 UTC 2020 (9bff61b)", i.e. the very first expected messages
from dmesg. (I carefully booted it into 5.6.12 not 5.6.14.) I have not
been able to find any useful symptoms that might shed light on what is
killing the machines.
Machines running 5.6.12 did not crash, both before the dist-upgrade and
after I reverted.
For what it's worth, here is some data about the various machines.
These went catatonic:
jacinth Gateway, directory server, never sleeps. Intel NUC6CAYH,
Celeron(R) CPU J3455 @ 1.50GHz, Intel HD Graphics 500
(i915). It runs hostapd as a wireless access point, driver
8812au from
rtl8812au-kmp-default-5.6.4.2+git20200318.49e98ff_k5.6.12_1-1.7.x86_64
xena Laptop, wireless, powered off when the human is sleeping.
Acer Aspire A515-54-51D1, Intel(R) Core(TM) i5-8265U
CPU @ 1.60GHz, Intel UHD Graphics 620 (Whiskey Lake) (i915)
diamond Normal desktop. When it crashed nobody was using it. At
night it hibernates. Intel NUC7i5BNH, Core(TM) i5-7260U CPU
@ 2.20GHz, Intel Iris Plus Graphics 640 (i915)
These survived up to 36 hours on 5.6.14 (called "non-catatonic" below):
claude Webserver (1.5 hits/min). VM (KVM) on Jacinth, x86_64,
video=cirrus
holly Desktop replacement. Raspberry Pi-3B, Broadcom BCM2837
@1.2GHz and VideoCore IV (vc4). aarch64. RPi's can't sleep.
iris Audio-video player (17kbyte/sec), hibernates when unused.
Intel NUC6CAYH, Celeron(R) CPU J3455 @ 1.50GHz (like Jacinth),
Intel HD Graphics 500 (i915)
oso Development VM (KVM) on Diamond, x86_64, video=cirrus
petra Development VM (KVM) on Xena, x86_64, video=cirrus
surya Cloud server, VM (KVM) at Linode, never sleeps :-), Intel(R)
Xeon(R) CPU E5-2680 v3 @ 2.50GHz, no GPU at all.
Thinking that X-Windows activity might be correlated with catatonia,
for about 6 hours I set the non-catatonic machines (except Surya, has no
console) to show screensaver eye candy continuously. I was wrong; none
of them crashed.
Iris hardware is identical to Jacinth, yet it did not go catatonic while
Jacinth failed more times than any other host.
I don't really know what effective action could be taken, beyond trying
to guess which kernel patch may have been the culprit. Anyway, thank
you for whatever you can do with this info.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174278
Bug ID: 1174278
Summary: kernel-firmware-amdgpu 20200702 breaks video on Raven
Ridge
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: adam.reichold(a)t-online.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 839828
--> http://bugzilla.opensuse.org/attachment.cgi?id=839828&action=edit
GZippped output of YaST's hardware information module
Update kernel-firmware-amdgpu from 20200610-1.1 to 20200702-1.1 breaks video on
a HP ProBook 455R G6 containing an AMD Ryzen 5 3500U with Radeon Vega Mobile
Gfx, i.e. AMD Raven Ridge.
The problem manifests itself as a blank screen when the boot splash would be
displayed and continuously spinning system fan. The machine is unresponsive
when reaching this state, i.e. escape and sysrq keys are not working.
Downgrading just the kernel-firwmare-amdgpu packages works around the issue.
There is one kernel log message only visible with the new firmware:
kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB
test failed on gfx (-110).
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173402
Bug ID: 1173402
Summary: Kernel delays boot by 12s if ip= option given
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: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: dracut-maintainers(a)suse.de, iforster(a)suse.com
Found By: ---
Blocker: ---
For networking in the initrd, the "ip=dhcp" (or similiar) option can be set in
the kernel cmdline. This is parsed by dracut and used to configure wicked.
However, this option is also parsed by the kernel in its ip autoconfig code,
which then ends up trying to bring up the network itself. This bringup includes
a 12s delay to wait for interfaces to appear:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net…
At this point the initrd isn't even mounted, so there are no kernel modules
available and no interfaces appear.
@kernel maintainers: Is it maybe possible to not do autoconfig in this
circumstance? It might be possible to check whether there are any network
drivers at all (the default kernel seems to have those as modules only) or
whether it's booting an initrd. Though in the latter case I guess it's possible
that some initrd out there relies on the kernel's successful autoconfig?
@dracut maintainers: It seems like "rd.neednet=1" is enough to get dracut to
acquire an address over DHCP, so a workaround is to just drop "ip=dhcp". I'd
like to have confirmation that this is intended behaviour and won't break
without notice in the future. This doesn't help for cases without DHCP though.
If it's not possible to avoid the "ip=foo" induced kernel delay, it might be a
good idea to provide "rd.ip=foo" or similar as alias, which is ignored by the
kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173158
Bug ID: 1173158
Summary: CONFIG_MODULE_SIG=y
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: lnussel(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: opensuse-releaseteam(a)suse.de
Found By: ---
Blocker: ---
The 15.2 kernel has CONFIG_MODULE_SIG=y enabled. Correct me if I'm wrong but
that means the NVidia driver won't work with secure boot enabled, right? Users
would have to go to the BIOS and disable secure boot. A step that was not
required in any openSUSE before, right?
Do we really want that? If so, requires explicit documentation IMO.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174737
Bug ID: 1174737
Summary: kernel-default-5.3.18-lp152.33.1.x86_64 hard lockup
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: novell(a)tower-net.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 840209
--> http://bugzilla.opensuse.org/attachment.cgi?id=840209&action=edit
boot-no-kdump.log
The latest kernel update
kernel-default-5.3.18-lp152.33.1.x86_64 (33.1)
produces hard lockup crashes after some minutes up to an hour of working.
Can't see any error messages in the logs.
Also when booting the kernel with enabled kdump, the kernel doesn't crash any
longer.
The older kernel package "kernel-default-5.3.18-lp152.26.2.x86_64" (26.2) works
without problems (also without kdump enabled).
I'm attaching 2 boot journal logs. One with enabled kdump, the other with
disabled kdump which locked up.
If I can provide some more information please ask.
Thanks
Markus
--
You are receiving this mail because:
You are the assignee for the bug.