January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1207259] BananaPi no HDMI output with kernel 6.0.3+, 6.1.1+ fails to boot
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c5 --- Comment #5 from peter haak <peter_haak_otd(a)web.de> --- Created attachment 864229 --> https://bugzilla.suse.com/attachment.cgi?id=864229&action=edit boot.log Kernel 5.6.14 und zum teil 6.1.1.1 from Kernel 6.0.3 no image avalibal and from 6.1.1 no log file on the install system sd-card -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] BananaPi no HDMI output with kernel 6.0.3+, 6.1.1+ fails to boot
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c4 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|after Kernel update from |BananaPi no HDMI output |6.0 to 6.1 |with kernel 6.0.3+, 6.1.1+ | |fails to boot Flags|needinfo?(peter_haak_otd@we | |b.de) | --- Comment #4 from Fabian Vogt <fvogt(a)suse.com> --- Can you attach the boot log with booting the 5.16, 6.0.3 and 6.1.1 kernels? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] after Kernel update from 6.0 to 6.1
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c3 --- Comment #3 from peter haak <peter_haak_otd(a)web.de> --- with the 5.16. Kernel the system runs after a zypper dup wihtout Kernel update the system runs but no HDMI output zypper dup with Kernel update the system is not reacheabel via ssh and has no usb -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] after Kernel update from 6.0 to 6.1
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c2 --- Comment #2 from peter haak <peter_haak_otd(a)web.de> --- The system runs normal without a Display i have had a running system with the Kernel 6.0.1 an the HDMI output was ok then i make a zypper dup to kernel 6.0.3 an the HDMI Screen change from black background to green background and after a shourt time no HDMI input Signal but the System was reachabel per ssh and works then i mad a zypper dup to the latest update Kernel 6.1.1 and the System has no HDMI ( the same as before ) and was not reachebel per ssh and the usb keyboard has no connection. then i take a old system image with Kernel 5.9.14 and HDMI works an the system runs. I locked the kernel update The following item is locked and will not be changed by any action: Installed: kernel-default 5.16.14-1.1 an made a zypper dup after reboot and the same result with the HDMI output after the update to 6.0.3 and the system runs with the 5.16 kernel if i unlock the Kernel update the system doesnt run -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207231] New: Btrfs errors on kernel 6.1.3 (write time tree block corruption detected)
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207231 Bug ID: 1207231 Summary: Btrfs errors on kernel 6.1.3 (write time tree block corruption detected) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wardlawhunter(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please see the following log: [ 59.345109] BTRFS error (device nvme0n1p2): block=1754410582016 write time tree block corruption detected [ 59.353413] BTRFS error (device nvme0n1p2): parent transid verify failed on logical 1754410582016 mirror 1 wanted 1036990 found 845765 [ 59.353476] BTRFS: error (device nvme0n1p2: state AL) in free_log_tree:3284: errno=-5 IO failure [ 59.353478] BTRFS info (device nvme0n1p2: state EAL): forced readonly [ 59.355231] BTRFS warning (device nvme0n1p2: state EAL): Skipping commit of aborted transaction. [ 59.355232] BTRFS: error (device nvme0n1p2: state EAL) in cleanup_transaction:1958: errno=-5 IO failure Started getting this error on kernel 6.1.3 after updating my system recently (20221211-0 -> 20230116-0). Did a memtest to make sure my RAM was okay (passed with no errors). Using snapper to rollback to before the update (kernel 6.0.12) has fixed the issue. Shortly after booting my system (less than 10 minutes post-boot) the root filesystem would become read-only (see log). This would happen following every boot. Didn't btrfs get updated in 6.1? Specifically, async buffered writes? -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1206681] WARNING: CPU: 1 PID: 4119 at fs/btrfs/qgroup.c:2756 btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs]
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206681 https://bugzilla.suse.com/show_bug.cgi?id=1206681#c13 Michal Koutn� <mkoutny(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoutny(a)suse.com --- Comment #13 from Michal Koutn� <mkoutny(a)suse.com> --- Joining the party with 6.1.4-1-default (the btrfs was almost on a freshly installed openSUSE TW, coincided with `git clone` of a large repo). Similarly to other, some 10 minutes after boot: > [ 627.800083] WARNING: CPU: 6 PID: 27806 at fs/btrfs/qgroup.c:2756 btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] The warning was raised 37 times in short succession (~10ms). Then (apparently) nothing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c11 --- Comment #11 from Chris Puttick <chris(a)twoten.is> --- zypper dup shows no updates available in current running OS. All I did to restore operation was use the boot menu to select the previous kernel so assuming everything else is running latest. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207228] New: rpi3 brcmfmac wifi firmware missing
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207228 Bug ID: 1207228 Summary: rpi3 brcmfmac wifi firmware missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [ 39.824407] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 39.836871] mc: Linux media interface: v0.10 [ 39.850223] usbcore: registered new interface driver brcmfmac [ 40.015257] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi-rpi.bin failed with error -2 [ 40.081486] videodev: Linux video capture interface: v2.00 [ 40.263182] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 40.341185] Bluetooth: HCI UART driver ver 2.3 [ 40.352894] Bluetooth: HCI UART protocol H4 registered [ 40.364785] Bluetooth: HCI UART protocol BCSP registered [ 40.415277] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2 [ 40.426573] Bluetooth: HCI UART protocol LL registered [ 40.444547] Bluetooth: HCI UART protocol ATH3K registered [ 40.469305] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 40.485583] Bluetooth: HCI UART protocol Intel registered [ 40.501084] Bluetooth: HCI UART protocol Broadcom registered [ 40.501649] Bluetooth: HCI UART protocol QCA registered [ 40.501671] Bluetooth: HCI UART protocol AG6XX registered [ 40.501954] Bluetooth: HCI UART protocol Marvell registered [ 40.533819] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator [ 40.534127] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator [ 40.610445] bcm2835_audio bcm2835_audio: card created with 8 channels [ 40.651481] uart-pl011 3f201000.serial: no DMA platform data [ 40.669358] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 40.800798] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. [ 40.919324] Bluetooth: hci0: BCM: chip id 94 [ 40.948546] Bluetooth: hci0: BCM: features 0x2e [ 40.972840] Bluetooth: hci0: BCM43430A1 [ 40.984591] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000 [ 41.035704] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch [ 41.505843] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 42.159532] Bluetooth: hci0: BCM: features 0x2e [ 42.177635] Bluetooth: hci0: BCM43438A1 37.4MHz Raspberry Pi 3-0141 [ 42.189575] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0508 [ 43.347986] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 43.358796] Bluetooth: BNEP filters: protocol multicast [ 43.370905] Bluetooth: BNEP socket layer initialized [ 43.404820] Bluetooth: MGMT ver 1.22 [ 43.495610] NET: Registered PF_ALG protocol family [ 44.799320] NET: Registered PF_QIPCRTR protocol family [ 47.701868] bpfilter: Loaded bpfilter_umh pid 932 [ 47.703555] Started bpfilter [ 49.732371] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 49.753071] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off [ 49.768474] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 54.149507] NET: Registered PF_PACKET protocol family [ 61.617821] systemd-journald[692]: Data hash table of /run/log/journal/ef3f848bf8074e9ea7dfe8342fc03956/system.journal has a fill level at 75.0 (3205 of 4273 items, 2461696 file size, 768 bytes per hash table item), suggesting rotation. [ 61.640490] systemd-journald[692]: /run/log/journal/ef3f848bf8074e9ea7dfe8342fc03956/system.journal: Journal header limits reached or header out-of-date, rotating. [ 2213.594521] usbcore: deregistering interface driver brcmfmac cd /lib/firmware/brcm ln -s brcmfmac43430-sdio.bin.xz brcmfmac43430-sdio.raspberrypi-rpi.bin.xz ln -s brcmfmac43430-sdio.raspberrypi,3-model-b.txt.xz brcmfmac43430-sdio.txt.xz [ 2220.779695] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 2220.796092] usbcore: registered new interface driver brcmfmac [ 2221.045048] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766 [ 2224.542332] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2406.455700] smsc95xx 1-1.1:1.0 eth0: Link is Down -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c10 --- Comment #10 from Daniel Wagner <daniel.wagner(a)suse.com> --- Or do you run already the new user space with the older kernel successfully? In this case we know it's the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c9 --- Comment #9 from Daniel Wagner <daniel.wagner(a)suse.com> --- Would it possible just to upgrade the kernel and see if the regression is caused by the kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0