http://bugzilla.opensuse.org/show_bug.cgi?id=1193652
Bug ID: 1193652
Summary: Logitech mouse and keyboard stop working on the latest
kernel.
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: benthomasgeorge7899(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 854509
--> http://bugzilla.opensuse.org/attachment.cgi?id=854509&action=edit
Logs of the said issue
The mouse and keyboard stopped working randomly first while working. Later on
reboot it works fine with bios and grub encryption password but within minutes
the kernel is loaded it disconnects the keyboard and mouse.
Possible reasons have been checked for-
1. Issue is not cause due to tlp
2. Issue not caused due to autosuspend of usb.
Both the mouse and keyboard and mouse are working fine on the previous kernel
5.15.5-1. Rollback to the previous kernel has solved the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190190
Bug ID: 1190190
Summary: kmod: manpage of modprobe.d not correctly rendered
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: sebix+novell.com(a)sebix.at
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The manpage of modprobe.d looks broken:
man modprobe.d | head
MODPROBE.D(5)
modprobe.d
MODPROBE.D(5)
.SH "NAME" modprobe.d - Configuration directory for modprobe
.SH "SYNOPSIS"
.PP /lib/modprobe.d/*.conf
.PP /usr/lib/modprobe.d/*.conf
The corresponding package `kmod` does not have a bugowner assigned in OBS, so I
chose none. Using TW 20210831.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191322
Bug ID: 1191322
Summary: Optimize building initrd when updating system
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: All
OS: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: Ulrich.Windl(a)rz.uni-regensburg.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When installing updates, dracut is called multiple times to update the initrds
of all kernels, for example when lvm2 is updated or when the kernel is updated.
It would be better if the initrds were updated once at the end of the
transaction (as Fedora does it, for example).
Despite of that when keeping older kernels, there may be reasons _not_ to
update the initrds of the older kernels:
First, some may be removed on next boot anyway, and second, more important:
If the idea of older kernels (and initrds) is to have a failback in case the
new kernel, initrd or and binaries inside are broken (and thus fail to boot),
it seems preferable to have the proven old kernel and initrd.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184804
Bug ID: 1184804
Summary: move kernel out of /boot
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: lnussel(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
One of the motivations for UsrMerge is to have all read-only parts of
the operating system in /usr. The kernel packages install files in /boot
though which isn't in line with that idea.
Having the kernel installed via rpm in /boot also causes issues with eg
snapshots if /boot is on a separate partition.
So it make sense to store the rpm provided parts of the kernel packages where
the rest of the OS is and manage /boot separately.
Looking at Fedora they install files like vmlinuz that used to be named
/boot/$name-$kver as (/usr)/lib/modules/$kver/$name instead. They
include /boot/$name-$kver as %ghost.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193599
Bug ID: 1193599
Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on
port D
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: x86-64
OS: openSUSE Leap 15.4
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: opendreas(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The following errors appear at boot
broken atomic modeset userspace detected, disabling atomic
[drm spcon_init [i915]] *ERROR* Failed to probe lspcon
[drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
[drm spcon_init [i915]] *ERROR* Failed to probe lspcon
[drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
[drm spcon_init [i915]] *ERROR* Failed to probe lspcon
[drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
[drm spcon_init [i915]] *ERROR* Failed to probe lspcon
[drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
Full log
https://paste.opensuse.org/83436185
Hardware
Dell Precision 7530
CPU: Intel Xeon E-2186M
GPU: Intel P630 / Nvidia Quadro P3200
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1196782
Bug ID: 1196782
Summary: Kernel 5.16 and 5.17 32bit tumbleweed hang after
freeing kernel memory
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86
OS: openSUSE Tumbleweed
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: linux(a)ljapunow.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Kernel 5.16 32bit hangs after freeing kernel memory on Dell X300 and Precision
M60. acpi=off solves the problem, but then undervolting (needs acpi) does not
work anymore. With kernel 5.15 there is no problem.
I also tested Dell E6420 (32bit kernel) and Samsung X20. Both work with kernel
5.16.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1193139
Bug ID: 1193139
Summary: [x86_64, 32-bit] mpx support broken
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: x86
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: tdevries(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Consider test-case mpx-out-of-bounds.c (
https://01.org/blogs/2016/intel-mpx-linux ):
...
$ cat mpx-out-of-bounds.c
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#define noinline __attribute__((noinline))
char dog[] = "dog";
char password[] = "secr3t";
noinline
char dog_letter(int nr)
{
return dog[nr];
}
int main(int argc, char **argv)
{
int max = sizeof(dog);
int i;
if (argc >= 2)
max = atoi(argv[1]);
for (i = 0; i < max; i++)
printf("dog[%d]: '%c'\n", i, dog_letter(i));
return 0;
}
...
With -m64:
...
$ gcc -Wall -o mpx-out-of-bounds mpx-out-of-bounds.c -mmpx
-fcheck-pointer-bounds
$ ./mpx-out-of-bounds 10
dog[0]: 'd'
dog[1]: 'o'
dog[2]: 'g'
dog[3]: ''
Saw a #BR! status 1 at 0x400634
dog[4]: 's'
Saw a #BR! status 1 at 0x400634
dog[5]: 'e'
Saw a #BR! status 1 at 0x400634
dog[6]: 'c'
Saw a #BR! status 1 at 0x400634
dog[7]: 'r'
Saw a #BR! status 1 at 0x400634
dog[8]: '3'
Saw a #BR! status 1 at 0x400634
dog[9]: 't'
...
With -m32:
...
$ gcc -m32 -Wall -o mpx-out-of-bounds mpx-out-of-bounds.c -mmpx
-fcheck-pointer-bounds
$ ./mpx-out-of-bounds 10 2>&1 | more
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
Saw a #BR! status 4157798670 at 0x8048492
Unexpected status with bound exception: 4157798670
<etc>
...
From what I understand, the problem starts the moment a first mpx instruction
is executed, which should trigger an exception that is caught by the kernel to
allocate some related tables.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189283
Bug ID: 1189283
Summary: kernel-obs-build needs af_alg
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
Found By: ---
Blocker: ---
libkcapi got updated to 1.3.1 (https://build.opensuse.org/request/show/910806)
and apparently gnutls picks that up now and enables support for it.
It seems like that depends on AF_ALG sockets though, which are currently not
enabled in kernel-obs-build (missing af_alg module), so various builds (libzip,
libvirt) fail with
libkcapi - Error: AF_ALG: socket syscall failed (errno: -97)
I'm not sure whether just af_alg is enough, it might need some other modules as
well.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193648
Bug ID: 1193648
Summary: mt7921e network card not initializing correctly
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: 64bit
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: otni.ledelay(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: Community User
Blocker: ---
Created attachment 854506
--> http://bugzilla.opensuse.org/attachment.cgi?id=854506&action=edit
output of 'journalctl --system --dmesg --boot 0'
I am dual booting win10 and TW on a new laptop, trying to slowly migrate to
Linux. I haven't however been able to get my WiFi working on Linux.
## I have tried:
- Disabling fast boot and Windows hibernation
- Several boot parameters:
* pcie_aspm=force
This did result in my wifi card almost working the first time I ran
with it. See journal2.txt for the results of that, what happened seems similar
to what's described here:
https://www.spinics.net/lists/linux-wireless/msg218339.html
It didn't work the second time I tried it.
* pcie_aspm=off
Didn't solve the problem, again identical results to journal.txt (but
without the "can't disable ASPM" warning)
* acpi_osi='Windows 2021'
Didn't solve the problem.
* acpi=off
Broke a bunch of other things but didn't solve the problem.
There was one time after a long time of not using my laptop that my wifi did
seem to work, journal attached as journal3.txt
## System information:
212:~ # tumbleweed installed
20211206
212:~ # uname -svrio
Linux 5.15.6-1-default #1 SMP Wed Dec 1 08:32:12 UTC 2021 (c2ce213) x86_64
GNU/Linux
212:~ # lspci -s 0000:02:00.0 -v
02:00.0 Network controller: MEDIATEK Corp. Device 7961
Subsystem: AzureWave Device 4680
Physical Slot: 0-1
Flags: fast devsel, IRQ 89, IOMMU group 9
Memory at ff20300000 (64-bit, prefetchable) [size=1M]
Memory at ff20400000 (64-bit, prefetchable) [size=16K]
Memory at ff20404000 (64-bit, prefetchable) [size=4K]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008
<?>
Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [200] Advanced Error Reporting
Kernel modules: mt7921e
212:~ # lshw -C network
*-network UNCLAIMED
description: Network controller
product: MEDIATEK Corp.
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@0000:02:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm cap_list
configuration: latency=0
resources: iomemory:ff0-fef iomemory:ff0-fef iomemory:ff0-fef
memory:ff20300000-ff203fffff memory:ff20400000-ff20403fff
memory:ff20404000-ff20404fff
*-network
description: Ethernet interface
physical id: 9
bus info: usb@1:1
logical name: enp4s0f3u1
serial: 3e:06:0b:1a:15:ec
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=rndis_host
driverversion=5.15.6-1-default duplex=half firmware=RNDIS device
ip=192.168.248.106 link=yes multicast=yes port=twisted pair
(The second one is my phone using USB tethering to provide my laptop with
internet, the problem is also present when my phone is not connected.)
212:~ # rfkill list all
0: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
212:~ # dmesg -l err
[ 2.446661] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010
[ 18.152314] Bluetooth: hci0: Failed to read MSFT supported features (-110)
212:~ # dmesg | grep mt7921e
[ 4.926736] mt7921e 0000:02:00.0: enabling device (0000 -> 0002)
[ 4.927096] mt7921e 0000:02:00.0: disabling ASPM L1
[ 4.927099] mt7921e 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM
control
[ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010
[ 6.020425] mt7921e: probe of 0000:02:00.0 failed with error -110
212:~ # journalctl --system --dmesg --boot 0 > journal.txt
212:~ # journalctl --system --dmesg --boot -8 > journal2.txt
212:~ # journalctl --system --dmesg --boot -18 > journal3.txt
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193374
Bug ID: 1193374
Summary: [kernel 5.15.3][zpci] not initialized/supported: =>
lspci -v / lspci -k lists no PCI devices
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: S/390-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: holger.rauch(a)posteo.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4743.0 Safari/537.36
Build Identifier:
a bug search for "zpci" yielded no results, so I decided to file this as a new
bug.
Regarding the actual details: please see "steps to reproduce" below (to me it
*seems* the missing PCI devices are a secondary error due to the missing zpci
initialization, which in turn is due to the missing CPU facilities).
Please also note that I haven't tried any other kernel releases besides the
default kernel shipped with OpenSUSE Tumbleweed (which, at the time of this
writing is 5.15.3)
Interesting questions in this regard:
1. Are other CPU facilities missing, too (besides the two mentioned ones "69"
and "71")?
2. Is there something like a reference list of all CPU facilities that
"normally" are/should be supported?
TIA for any additional help/info.
Reproducible: Always
Steps to Reproduce:
1. lspci -v / lspci -k
=> no devices listed (but interestingly, the exit status of both commands is
zero)
2. sudo dmesg | grep zpci
=> zpci: PCI is not supported because CPU facilities 69 or 71 are not available
3. grep facilities /proc/cpuinfo
=> facilities : 0 1 2 3 4 6 7 8 9 10 12 14 15 16 17 18 19 20 21 22 23 24
25 26 27 28 30 31 32 33 34 35 36 37 38 40 41 42 43 44 45 46 47 48 49 50 51 52
53 54 55 57 58 59 60 61 73 74 75 76 77 80 81 82 128 129 130 131 133 134 135 146
147 148 150 151 152 155 156 168
=> both CPU facilities indeed seem to be missing (note that the next facility
number after "61" is "73")
Actual Results:
no PCI devices
Expected Results:
The "lspci" command should list some PCI devices
uname -v
=> #1 SMP Fri Nov 19 08:35:39 UTC 2021 (404f576)
The machine I tested this on is part of the LinuxONE Community Cloud.
--
You are receiving this mail because:
You are the assignee for the bug.