Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79554 > unrolled thread

Bug#1040738: linux: Please review firmware related Debian patches

Started byDiederik de Haas <didi.debian@cknow.org>
First post2023-07-09 23:40 +0200
Last post2024-06-19 17:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1040738: linux: Please review firmware related Debian patches Diederik de Haas <didi.debian@cknow.org> - 2023-07-09 23:40 +0200
    Bug#1040738: marked as done (linux: Please review firmware  related Debian patches) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-19 17:10 +0200

#79554 — Bug#1040738: linux: Please review firmware related Debian patches

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-07-09 23:40 +0200
SubjectBug#1040738: linux: Please review firmware related Debian patches
Message-ID<GPKil-47t9-1@gated-at.bofh.it>
Source: linux
Version: 6.4.1-1~exp1
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

While working on building/testing a Debian kernel for the PineTab2 I
noticed that I got a firmware (related) *error* in `dmesg`, while that
was not the case on a kernel with a Debian (based) config and the
upstream kernel source. Neither was it reported as an error in the OOTB
provided image/kernel (ALARM).
In both other cases it was reported as a *warning*.

When I build a new Debian kernel with the "firmware_class: Log every
success and failure against given device" patch removed (and adjusted
`d/patches/debian/firmware_class-refer-to-debian-wiki-firmware-page.patch`
to fix the resulting issue), then that same firmware related message was
reported as a warning too.

Before:  
```
root@pinetab2:~# dmesg --level emerg,alert,crit,err
[    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22
[    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22
[   23.391432] spi-nor spi4.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00
[   23.466581] ov5648 2-0036: failed to find 168000000 clk rate in endpoint link-frequencies
[   23.513593] Goodix-TS 1-005d: firmware: failed to load goodix_911_cfg.bin (-2)
[   23.513603] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[   23.513640] Goodix-TS 1-005d: firmware: failed to load goodix_911_cfg.bin (-2)
```

After:  
```
root@pinetab2:~# dmesg --level emerg,alert,crit,err
[    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22
[    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22
[   32.571259] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[   32.589465] ov5648 2-0036: failed to find 168000000 clk rate in endpoint link-frequencies
```
Note: The `spi-nor` msg already disappeared on a reboot, but is
irrelevant anyway. And looks like my patch (removal) wasn't complete,
but that also seems irrelevant.

I really don't like ignoring errors I see in `dmesg`. But this isn't the
first instance where I was inclined to do exactly that as the
Debian patch(es) 'upgrade' an upstream warning to an error.
And IIUC/IIRC I've also seen that several times when triaging Debian
kernel bugs, f.e. with an issue which 'rhymes' with yolo-debug.

So hereby a request to review the firmware related Debian patches to see
whether they still are the best way to solve the (initial) problem and
if not, improve on them so they will.

Cheers,
  Diederik

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZKsmVQAKCRDXblvOeH7b
bg0LAP43Zo91VX1KK8d7/Icsl3JerHPBmNAOskhTvGv3NkT5yAD+Obg69navr+Rw
sNgU43OHquxKFhGhlBOo1UWN+M9XNAg=
=9ctN
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]


#82761 — Bug#1040738: marked as done (linux: Please review firmware related Debian patches)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-06-19 17:10 +0200
SubjectBug#1040738: marked as done (linux: Please review firmware related Debian patches)
Message-ID<IR56F-44GJ-5@gated-at.bofh.it>
In reply to#79554

[Multipart message — attachments visible in raw view] — view raw

Your message dated Wed, 19 Jun 2024 15:00:12 +0000
with message-id <E1sJwnE-0063cs-Eg@fasolo.debian.org>
and subject line Bug#1040738: fixed in linux 6.9.2-1~exp1
has caused the Debian Bug report #1040738,
regarding linux: Please review firmware related Debian patches
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1040738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040738
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web