https://bugzilla.suse.com/show_bug.cgi?id=1183265https://bugzilla.suse.com/show_bug.cgi?id=1183265#c2
--- Comment #2 from Oliver Kurz <okurz(a)suse.com> ---
This is an autogenerated message for openQA integration by the openqa_review
script:
This bug is still referenced in a failing openQA test: boot_linuxrc
https://openqa.opensuse.org/tests/1693232
To prevent further reminder comments one of the following options should be
followed:
1. The test scenario is fixed by applying the bug fix to the tested product or
the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183716https://bugzilla.suse.com/show_bug.cgi?id=1183716#c9
Dirk Mueller <dmueller(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Dirk Mueller <dmueller(a)suse.com> ---
config has been added to master.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184444
Bug ID: 1184444
Summary: problems with wireless mouse and keyboard (was not the
issue with previous kernel)
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: lubos.kocman(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Hello team,
since I've updated yesterday to kernel-default-5.3.18-135.1.g64d6137.x86_64
from the devel project I've started to notice "short lags" while using wireless
devices.
Namely both keyboard and mouse they're both connected to the computer via these
small usb dongles to the dell docking station.
I was initially thinking it's having something to do with my some performance
regression in OBS studio which seem to be more CPU extensive than ever, but
even with OBS off I'm still having these lags on these devices, while not
having lags e.g. on internal mouse.
I did notice following in dmesg:
[ 24.783730] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 24.799632] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 24.809635] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 365.415674] wlan0: Connection to AP ee:c3:2a:6a:2e:b7 lost
[ 365.536183] wlan0: Connection to AP 00:00:00:00:00:00 lost
[ 366.485975] wlan0: authenticate with e4:c3:2a:6a:2e:b6
[ 366.519342] wlan0: send auth to e4:c3:2a:6a:2e:b6 (try 1/3)
[ 366.570475] wlan0: authenticated
[ 366.571938] wlan0: associate with e4:c3:2a:6a:2e:b6 (try 1/3)
[ 366.580195] wlan0: RX AssocResp from e4:c3:2a:6a:2e:b6 (capab=0x1431
status=0 aid=1)
[ 366.585511] wlan0: associated
[ 366.682198] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by
e4:c3:2a:6a:2e:b6
[ 570.376659] logitech-hidpp-device 0003:046D:408A.0008: HID++ 4.5 device
connected.
[ 582.554558] logitech-hidpp-device 0003:046D:407B.0009: HID++ 4.5 device
connected.
[ 631.999763] mce: CPU2: Core temperature above threshold, cpu clock throttled
(total events = 79)
[ 631.999789] mce: CPU6: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999791] mce: CPU4: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999791] mce: CPU10: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999792] mce: CPU8: Core temperature above threshold, cpu clock throttled
(total events = 79)
[ 631.999793] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999794] mce: CPU9: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999795] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999796] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999796] mce: CPU7: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999797] mce: CPU8: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999798] mce: CPU5: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999799] mce: CPU11: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 631.999800] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 335)
[ 632.000734] mce: CPU2: Core temperature/speed normal
[ 632.000734] mce: CPU10: Package temperature/speed normal
I have teams permanently on. It's true that this typically starts to happen
during sessions involving teams or meet.opensuse.org. Again I had a feeling
that this did not happen on kernel-default-5.3.18-52.3.x86_64
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184415
Bug ID: 1184415
Summary: Remove /etc/modprobe.d/60-blacklist_fs-f2fs.conf from
suse-module-tools package in support of VM on shared
flash use case
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: peter.clark(a)ngic.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Please remove /etc/modprobe.d/60-blacklist_fs-f2fs.conf after f2fs driver
improvements in the kernel.
This would be in support of the use case of VMs running on shared flash-backed
storage. For this use case, journaled filesystems such as xfs/ext4 generate
journalling-related load for each VM in a cluster.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184419
Bug ID: 1184419
Summary: Leap 15.3 cannot handle encrypted swap with random key
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: x86-64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: nwr10cst-oslnx(a)yahoo.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Firefox/78.0
Build Identifier:
I heard about this problem in a forum post:
https://forums.opensuse.org/showthread.php/552398-encrypted-swap-on-raid1-n…
I then reproduced the problem in a KVM virtual machine (I did not use RAID).
I used the expert partitioner, and allocated a 2G partition for swap. I then
attempted to encrypt that partition with a random key. The installer seemed to
handle this well, except I ended up with an error message.
I was able to continue and ignore the error message. I had to click "Continue"
several to proceed to the install.
The installed system looked fine. But, on boot, in prompted me for an
encryption key for "cr_swap". I hit CTRL-D to skip that. The system booted,
but without swap.
I then configured the Leap 15.2 update repo as an additional repo. And I
installed kernel-default-5.3.18-lp152.66.2 from there.
Rebooting, I used the grub menu to boot with that Leap 15.2 kernel. And it
booted just fine with the swap working as it should.
It looks as if this kind of encryption is supported by the 15.2 kernel, but is
not supported by the 15.3 kernel.
Reproducible: Always
In my opinion, this is a serious security issue and should be a show stopper
for Leap 15.3 (until fixed).
I'll note that bug 1183063 is another (different) crypto-related issue with
Leap 15.3
--
You are receiving this mail because:
You are the assignee for the bug.