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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175105
Bug ID: 1175105
Summary: mdadm doesn't except partition for --add because of
"dirt" in that partition of a fresh gpt table
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: ralf(a)czekalla.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I'm about to migrate an important central private nextcloud server to 15.2.
I'm use RAID1 for all my partitions and benefit from that with easy made clones
with the help of mdadm by growing the number of raid-devices and adding a
refreshed SSD with a new gpt partition table and cloned partitions
descriptions.
This worked for most of the six partitions but one. (It's not the first
installation I transform with this idea. Did these processes already several
times)
This faulty one showed weird error messages I couldn't find a real good reason
for, like ...
...on console:
# mdadm --verbose /dev/md2 --add /dev/sdc5
mdadm: add new device failed for /dev/sdc5 as 4: Invalid argument
# mdadm -E /dev/sdc5
/dev/sdc5:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x9
Array UUID : 94bbbcd3:ad4d1b0b:dcd4d548:1af16050
Name : any:2
Creation Time : Fri Feb 2 20:09:03 2018
Raid Level : raid1
Raid Devices : 3
Avail Dev Size : 83892192 sectors (40.00 GiB 42.95 GB)
Array Size : 41945984 KiB (40.00 GiB 42.95 GB)
Used Dev Size : 83891968 sectors (40.00 GiB 42.95 GB)
Super Offset : 83892208 sectors
Unused Space : before=0 sectors, after=224 sectors
State : active
Device UUID : c9e17312:0069d580:42782958:8817e0f7
Internal Bitmap : -16 sectors from superblock
Update Time : Mon Aug 10 18:09:21 2020
Bad Block Log : 512 entries available at offset -8 sectors - bad blocks
present.
Checksum : 7b5d72a - correct
Events : 0
Device Role : spare
Array State : AA. ('A' == active, '.' == missing, 'R' == replacing)
First I was blinded by the "bad blocks present", but all devices checked out
perfectly healthy in smart and also extended device scans didn't show any
problems. Took me several hours to get through all this.
dmesg:
md: sdc5 does not have a valid v1.0 superblock, not importing!
md: md_import_device returned -22
Also tried to --zero-superblock the partition of course. No change of behavior
and still the above error message in dmesg remained.
At the end I found a surprising hint on serverfault.com
(https://serverfault.com/questions/696392/how-to-add-disk-back-to-raid-and-r…)
from Oct. 2015 with a similar behavior that suggested to clean-up of the
partition first with dd writing zeros (dd if=/dev/zero of=/dev/sdc5
status=progress) and try again later to add the last seemingly faulty
partition.
And long story short, this really worked.
Somehow mdadm - and md behind - is choking on some dirt inside of partition
blocks from old content before the disk/ssd was wiped with a new gpt partition
table. (Of course with SSDs you try to prevent unnecessary writes and wiping
every block of a disk first)
I'm using md device type 1.0 here (in contrast to the serverfault.com case),
where the RAID/md setup data is stored at the end of the partition. I had to
wipe exactly this area at the end of the partition to add it afterwards
successfully. Of course, no effect when doing this at the beginning of the
partition (mentioned in the serverfault.com case) where md type 1.2 stores the
md setup data.
I think after 5 years this might need a clean up in mdadm or md device
management.
At least the error message should suggest to clean the partition first instead
of this error message in dmesg. Also the --zero-superblock should wipe out the
dirt beneath the superblock and not seemingly let some stuff leak here.
Thanks
Ralf
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175646
Bug ID: 1175646
Summary: After bios update, some keyboard function keys not
recognized.
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: openSUSE Leap 15.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: zhonb(a)yahoo.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I performed a bios update on a Dell precision 7530, which resolved my issue
with the bug reported here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1175626
However, the new bios version (1.13.1) does not map the keyboard function keys
correctly. Some work (e.g., volume control, keyboard backlight) and some don't
(wifi toggle, screen brightness). Is there a way to map the new keyboard
configuration in the bios so it works correctly in openSUSE? The keyboard
functions correctly in windows. It does not work correctly in LEAP, tumbleweed
or the latest fedora release.
--
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=1175300
Bug ID: 1175300
Summary: AMDGPU Driver Brightness Issue
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: jshand2013(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
hi, just checked the amdgpu brightness level and it seems to be on 20%
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174868
Bug ID: 1174868
Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes
completely freezes, 20°C warmer and journal is trimmed
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: markus.zimmermann(a)symflower.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel
5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to
15.2 and then the problems started to show. The CPU is constantly hotter while
working. by 20°C.
This machine now freezes sometimes completely.
The machine is then
- not pingable
- no keyboard interaction works
- lid close/open does nothng
- no mouse interaction works
- the notebook is really warm
- When a freeze happens also a trim of the journal happens... e.g. we loose the
whole journal for the day.
- We SSH'ed into the machine and watched via "htop", "journal -f" and
"sensors". WHen the machine freezes, there is no significant load via htop
seeable, there are no interesting logs in journal and sensors shows that it is
simply hotter.
Interestingly, we upgraded another machine before (also a Thinkpad T480s) and
this does not have any problems.
We are btw on the latest firmwares using fwupdmgr.
What should we try? How can we debug it?
--
You are receiving this mail because:
You are the assignee for the bug.