October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1203539] Boot hangs with update to kernel 5.14.21-15040.24.21-default
by bugzilla_noreply＠suse.com 29 Oct '22

29 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203539 http://bugzilla.opensuse.org/show_bug.cgi?id=1203539#c22 --- Comment #22 from John Carrick Smith <jcarricksmith(a)gmail.com> --- Created attachment 862542 --> http://bugzilla.opensuse.org/attachment.cgi?id=862542&action=edit Output to console on hang The attached picture is the screen of my computer. I had added sysrq_always_enabled to the boot command line, and then before the CAPSLOCK and NUMLOCK lights started flashing I pressed <Alt> <SysRq> <k> . The result was this dump to screen .I hope that it is of some help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202386] New: after upgrade, pc randomly freezes with kernel panic and segfault in power management
by bugzilla_noreply＠suse.com 28 Oct '22

28 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1202386 Bug ID: 1202386 Summary: after upgrade, pc randomly freezes with kernel panic and segfault in power management Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860780 --> https://bugzilla.suse.com/attachment.cgi?id=860780&action=edit extract from journalctl --system output after upgrade my laptop to OpenSuse TumbleWeed 20220813, with kernel 5.19.0-1-default , I experience random kernel panics (PC freezes with caps lock blinking) and in system logs I find some error message about power management (see attachment). Hardware name: LENOVO 20YRS2D84A/20YRS2D84A, BIOS N37ET39W (1.20 ) 04/15/2022 -- You are receiving this mail because: You are the assignee for the bug.

1 38

[Bug 1204786] New: Boot is hanging when intel ethernet card is enabled
by bugzilla_noreply＠suse.com 27 Oct '22

27 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204786 Bug ID: 1204786 Summary: Boot is hanging when intel ethernet card is enabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bechir.kahla(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862487 --> http://bugzilla.opensuse.org/attachment.cgi?id=862487&action=edit boot_logs I have a Lenovo ThinkPad P15 Gen 2i. This laptop is running OpenSuse Leap 15.4 when installing the laptop I had no issue, but just after rebooting it the boot hangs and many services where failing to start, even the sudo commands hangs The issue is not reproduced systematically, sometimes the system boots correctly but it is very frequent. Disabling my IO devices from the bios one by one helped me to understand that the issue is coming from the my ethernet card which is an itel card. an lspci for the ethernet device I am using done in the initramfs as it was hanging if I run it after igc module insertion : >0b:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-LM (rev 03) > Subsystem: Lenovo Device 22d8 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 255 > Region 0: Memory at be300000 (32-bit, non-prefetchable) [disabled] [size=1M] > Region 3: Memory at be400000 (32-bit, non-prefetchable) [disabled] [size=16K] > Capabilities: [40] Power Management version 3 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ > Address: 0000000000000000 Data: 0000 > Masking: 00000000 Pending: 00000000 > Capabilities: [70] MSI-X: Enable- Count=5 Masked- > Vector table: BAR=3 offset=00000000 > PBA: BAR=3 offset=00002000 > Capabilities: [a0] Express (v2) Endpoint, MSI 00 > DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset- > MaxPayload 256 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- > LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <4us > ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ > LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- > DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Not Supported > AtomicOpsCap: 32bit- 64bit- 128bitCAS- > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled > AtomicOpsCtl: ReqEn- > LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- > Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- > Compliance De-emphasis: -6dB > LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, >EqualizationPhase1- > EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- > Capabilities: [100 v2] Advanced Error Reporting > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- > CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ > AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- > MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > HeaderLog: 00000000 00000000 00000000 00000000 > Capabilities: [140 v1] Device Serial Number 90-2e-16-ff-ff-f3-4f-ea > Capabilities: [1c0 v1] Latency Tolerance Reporting > Max snoop latency: 3145728ns > Max no snoop latency: 3145728ns > Capabilities: [1f0 v1] Precision Time Measurement > PTMCap: Requester:+ Responder:- Root:- > PTMClockGranularity: 4ns > PTMControl: Enabled:+ RootSelected:- > PTMEffectiveGranularity: 4ns > Capabilities: [1e0 v1] L1 PM Substates > L1SubCap: PCI-PM_L1.2- PCI-PM_L1.1+ ASPM_L1.2- ASPM_L1.1+ L1_PM_Substates+ > L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1+ ASPM_L1.2- ASPM_L1.1+ > > L1SubCtl2: > Kernel modules: igc I attached some logs but I don't see many entries from igc driver just : >oct. 27 09:47:01 localhost kernel: igc 0000:0b:00.0: enabling device (0000 -> 0002) >oct. 27 09:47:01 localhost kernel: igc 0000:0b:00.0: PTM enabled, 4ns granularity >oct. 27 09:47:01 localhost kernel: igc 0000:0b:00.0 (unnamed net_device (uninitialized): PHC added >oct. 27 09:47:01 localhost kernel: igc 0000:0b:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x1 link) >oct. 27 09:47:01 localhost kernel: igc 0000:0b:00.0 eth0: MAC:90:2e:16:f3:4f:ea >oct. 27 09:47:25 localhost NetworkManager[1554]: <info> [1666856845.4896] device (eth0): driver 'igc' does not support carrier detection. I will try to enable higher log level for igc module and attach the new logs -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1204275] New: yast2 shows wrong version available for kernel-devel and kernel default devel
by bugzilla_noreply＠suse.com 27 Oct '22

27 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204275 Bug ID: 1204275 Summary: yast2 shows wrong version available for kernel-devel and kernel default devel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: klaus.braun(a)geographie.uni-freiburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, in yast2 when I list packages with available updates (Packages / All Packages / Update if newer version available) the entries for kerne-devel and kernel-default-devel show up in red, meaning the installed packages are newer than the available ones. Additionally the version installed matches exactly the version of the kernel, which is 5.3.18-150300.59.93.1. The version for the availbale packages are given as 5.3.18.57.3 which I think is really older than the installed one but I don't know why those are showing up at all if the installed kernel devel packages matches the installed kernel. And I don't know what will happen when I do this "update" and the devel packages then possibly will be downgraded. This might be related to bug 1202116, but for me it doesn't make sense if I compile nvidia drivers with kernel-devel packages with an older version number than the installed kernel has. Best Klaus -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1204700] New: [RPi3] Kernel 6.0 "Failed to attach USB driver: -22"
by bugzilla_noreply＠suse.com 27 Oct '22

27 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204700 Bug ID: 1204700 Summary: [RPi3] Kernel 6.0 "Failed to attach USB driver: -22" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2803022/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ivan.ivanov(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, david.kubat(a)suse.com, dmueller(a)suse.com, guillaume.gardet(a)arm.com, ivan.ivanov(a)suse.com, mbrugger(a)suse.com, patrik.jakobsson(a)suse.com, tzimmermann(a)suse.com Depends on: 1204315 Found By: openQA Blocker: Yes +++ This bug was initially created as a clone of Bug #1204315 +++ Oct 04 00:00:07.567844 localhost kernel: Failed to attach USB driver: -22 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1204717] New: On 6.0.3-1-default Thinkpad T60 and maybe some others old laptops did not poweroff
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204717 Bug ID: 1204717 Summary: On 6.0.3-1-default Thinkpad T60 and maybe some others old laptops did not poweroff 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On 6.0.3-1-default Thinkpad T60 and maybe some others old laptops did not poweroff After poweroff command OS halted but power is still on. I tested on another old laptops, and on old fujitsu Fujitsu-Siemens all work fine, but on thinkpad T60 poweroff did not work -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Guillaume GARDET from comment #1) > Oct 04 00:00:01.306451 localhost kernel: simple-framebuffer > simple-framebuffer.0: [drm] *ERROR* could not acquire memory range [mem > 0x3eaa9000-0x3ebfafff flags 0x200]: error -16 Could you check what conflicts in those memory area by looking at /proc/iomem? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190764] New: [Build 20210920] btrfs: invalid qgroupid or subvolume path
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190764 Bug ID: 1190764 Summary: [Build 20210920] btrfs: invalid qgroupid or subvolume path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1929805/modules/btrf s_qgroups/steps/24 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-DVD-x86_64-extra_tests_filesystem@64bit fails in [btrfs_qgroups](https://openqa.opensuse.org/tests/1929805/modules/btrfs_qgro… The openQA test code is this: assert_script_run "btrfs quota enable ."; # Create subvolumes, qgroups, assigns and limits # 2/1 # / \ # 1/1 1/2 # / \ / | \ # a b c d(k) assert_script_run "for c in {a..d}; do btrfs subvolume create \$c; done"; assert_script_run "for c in 1/1 1/2 2/1; do btrfs qgroup create \$c .; done"; assert_script_run "for c in a b; do btrfs qgroup assign \$c 1/1 .; done"; assert_script_run "for c in b c d; do btrfs qgroup assign \$c 1/2 .; done"; assert_script_run "for c in 1/1 1/2; do btrfs qgroup assign \$c 2/1 .; done"; And the last command here returns: ERROR: invalid qgroupid or subvolume path: a ERROR: invalid qgroupid or subvolume path: b ## Test suite description Maintainer: QE Core Filesystem related tests, for example snapper and btrfs features. ## Reproducible Fails since (at least) Build [20210920](https://openqa.opensuse.org/tests/1928938) ## Expected result Last good: [20210918](https://openqa.opensuse.org/tests/1927312) (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.

1 4

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |postix(a)posteo.eu Flags| |needinfo?(postix(a)posteo.eu) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 https://bugzilla.suse.com/show_bug.cgi?id=1204705#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Also, I'm building a test kernel with a suspected patch reverted. It's being build in OBS home:tiwai:bsc1204705 repo. Once after the build finishes, could you give it a try, too? -- You are receiving this mail because: You are the assignee for the bug.

1 0