On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote:
> Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit:
> > On Tuesday, 14 February 2023 18:10:11 CET Samuel Thibault wrote:
> > > Some people on debian-accessibility wanted to install debian in arm64
&
Control: tag -1 -moreinfo
On Monday, 20 February 2023 00:38:28 CET Diederik de Haas wrote:
> On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote:
> > Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit:
> > > On Tuesday, 14 February 2023 18:10:11 CET Sam
On Monday, 20 February 2023 01:07:29 CET Samuel Thibault wrote:
> Diederik de Haas, le lun. 20 févr. 2023 00:38:28 +0100, a ecrit:
> > On Monday, 20 February 2023 00:27:57 CET Samuel Thibault wrote:
> > > Diederik de Haas, le lun. 20 févr. 2023 00:14:19 +0100, a ecrit:
>
On Thursday, 23 February 2023 12:14:57 CET segfault wrote:
> Package: linux-image-6.0.0-0.deb11.6-amd64
> Version: 6.0.12-1~bpo11+1
>
> This version of the kernel is vulnerable to security issues from
> DSA-5324-1. Is an upload of a version which fixes those issues planned
> for bullseye-backports
On Friday, 24 February 2023 00:28:33 CET Thorsten Alteholz wrote:
> upgrading from kernel 5.18.5-1 to 6.1.8-1 (and 6.1.12-1) network devices
> using driver module ixgbe stop working. The devices are recognized and can
> be configured but "ip a" shows "no-carrier" for them.
> With kernel 5.18.5-1 ev
On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> Source: linux
> Version: 5.10.0-21-powerpc64le
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: dan...@mariadb.org
>
> >From https://jira.mariadb.org/browse/MDEV-30728
>
> MariaDB's mtr tests on a numbe
On Sunday, 5 March 2023 03:08:23 CET Steve McIntyre wrote:
> On Sun, Mar 05, 2023 at 12:09:24AM +, Steve McIntyre wrote:
> >Source: linux
> >Version: 6.1.12-1
> >
> >I've just upgraded my Seattle-based system to bookworm and it no
> >longer finds the onboard AHCI SATA storage so it stops at an
Control: tag -1 moreinfo
On Sunday, 5 March 2023 09:26:20 CET Marc wrote:
> Package: firmware-brcm80211
> Version: 20210315-3
>
> The firmware for the wifi hardware found on the GPD Pocket 1 is missing in
> latest firmware package. Installing an old package from bullseyes fixes the
> issue.
You
On Wednesday, 8 March 2023 15:49:03 CET Cyril Brulebois wrote:
> This is definitely a blocking issue for booting on both Pi 4 (SD card)
> and CM4 (SD card or internal eMMC). That's also seen with v6.1.15
> (annotating accordingly) and v6.2 (not annotating as we have no such
> package in the archive
Control: tag -1 moreinfo
On Thursday, 9 March 2023 15:04:11 CET Bastian Germann wrote:
> The driver CAN_MCP251X is already enabled on all platforms.
> Please enable CAN_MCP251XFD as module as well. Thank you!
Can you describe *why* this would a useful addition?
For CAN_MCP251X the motivation wa
On Thursday, 9 March 2023 03:38:13 CET d...@kataplop.net wrote:
> Here's the result of using latest package:
>
> [38.546040] brcmfmac :01:00.0: firmware: failed to load
> brcm/brcmfmac4356-pcie.bin (-2) [ 38.546408] brcmfmac :01:00.0:
> firmware: failed to load brcm/brcmfmac4356-pcie.bin
On Friday, 10 March 2023 04:00:44 CET d...@kataplop.net wrote:
> March 9, 2023 5:25 PM, "Diederik de Haas" wrote:
> > The brcm/brcmfmac4356-pcie.bin file (f.e.) has been moved/renamed to
> > cypress/cyfmac4356-pcie.bin and *maybe* that causes the issue.
> >
> &g
Control: reassign -1 src:linux 6.1.15-1
Control: tag -1 -moreinfo +upstream
Control: forwarded -1
https://lore.kernel.org/linux-wireless/2716728.5R3jveeIG6@prancing-pony/
On Friday, 10 March 2023 13:07:22 CET d...@kataplop.net wrote:
> March 10, 2023 10:57 AM, "Diederik de Haas" w
On Thursday, 9 March 2023 19:17:10 CET Diederik de Haas wrote:
> In https://bugs.debian.org/1032367 we have a user who reported that the
> brcm/brcmfmac4356-pcie.bin firmware file failed to load with a new firmware-
> brcm80211 package, while it succeeded with an old one.
>
On Friday, 10 March 2023 17:16:48 CET Diederik de Haas wrote:
> On Friday, 10 March 2023 13:07:22 CET d...@kataplop.net wrote:
> > March 10, 2023 10:57 AM, "Diederik de Haas" wrote:
> > > I'm 99% sure this would be a *workaround*, but let's verify anyway
ing the fw, as expected
> (same error message)
I still think the upstream kernel should do something with the 'new' use of
the cypress directory as I described in my mail to the ML(s).
But the cause for the breakage is actually a (Debian) packaging change and I'm
about to revert t
On Monday, 13 March 2023 16:23:19 CET Bastian Germann wrote:
> Am 09.03.23 um 15:31 schrieb Diederik de Haas:
> > Can you describe*why* this would a useful addition?
>
> The chip is in several industrial PCs but the most popular device should be
> the Waveshare 2-Chann
Control: tag -1 moreinfo
Hi Julian,
On Thursday, 12 January 2023 19:31:37 CET Julian Groß wrote:
> My computer just froze on Kernel version 5.19.11-1. Though nothing got
> logged.
What's the current status on this bug?
Currently there is a version 6.1.15 in Testing/Unstable and it would be usefu
On Tuesday, 14 March 2023 14:55:04 CET Julien Cristau wrote:
> Package: src:linux
> Version: 6.1.12-1
>
> After upgrading to 6.1.12-1 my laptop started hanging regularly (3 times
> in a few hours). Downgraded to 6.1.8-1 and I've not seen this for a
> week, so this looks like a recent regression.
Previously I tried to be nice and gave you pointers which I hoped would give
you insight as to why your behavior is unhelpful, which in turn would result
in improved behavior. That did not have the intended effect.
So now I'm NOT going to be nice, so I added commun...@debian.org in the
address
On Thursday, 16 March 2023 18:11:27 CET Julien Cristau wrote:
> > I rebooted on 6.1.15-1 last night and things are still looking good so
> > I'll call this fixed. Thanks.
>
> Spoke too soon:
> > [84564.498495] BUG: kernel NULL pointer dereference, address:
> > 0398 [84564.498502] #PF:
On Saturday, 18 March 2023 21:17:52 CET Salvatore Bonaccorso wrote:
> > https://www.openwall.com/lists/oss-security/2023/03/14/2
> >
> > Filing a bug (for trixie (added in 6.2), can be applied early to notice
> > potentially affected applications early on)
>
> Just for reference in the bug, this
On Saturday, 18 March 2023 22:42:15 CET Salvatore Bonaccorso wrote:
> "early", i.e. it can be in one of the first uploads to experimental we
> will do. But I will prefer to have it separate from the rebase to new
> upstream version, i.e. as own dedicated change/mr.
>
> So please keep the default i
On Saturday, 18 March 2023 21:33:10 CET Salvatore Bonaccorso wrote:
> > The following looks similar, though it is reported to happen on dock
> > unplug. I assume your issue is independent on that?
I guess that is https://bugzilla.kernel.org/show_bug.cgi?id=217106 ?
> And if you do some bisection/
Source: linux
Version: Future Android/Waydroid support
Severity: wishlist
Forwarded: https://github.com/waydroid/waydroid/issues/811
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In https://salsa.debian.org/kernel-team/linux/-/merge_requests/651 I had
initially removed the 2 Android related pat
Control: reassign -1 src:linux 6.1.20-1
On Friday, 24 March 2023 12:44:33 CET Tim Rühsen wrote:
> Package: linux-image-amd64
> Version: 6.1.20-1
>
> We run a priviledged eBPF based tool with a communication between kernel and
> user space. It runs without issues on kernels 4.15 to 5.18.
> On kern
Control: tag -1 moreinfo
On Saturday, 25 March 2023 15:27:52 CET Vivek K J wrote:
> I've been using a automount script (in /etc/fstab) to mount my
> windows NTFS partition in Debian Testing. But after updating to
> 6.1.0-6-amd64 the kernel doesn't boot and stucks at recovery mode. On
> commenting
Control: found -1 5.19~rc4-1~exp1
Control: forwarded -1
https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoi...@gmail.com/
On Saturday, 25 March 2023 16:00:47 CET Florian Lehner wrote:
> > Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily
> > test various kern
On Sunday, 26 March 2023 17:55:17 CEST Vincent Blut wrote:
> Le 2023-03-26 15:12, Andy Smith a écrit :
> > I've got a laptop running testing with a Realtek 8852be card in it.
> >
> > This driver seems to be present in upstream kernel from 6.1:
> > https://elixir.bootlin.com/linux/v6.1/source/d
On Sunday, 26 March 2023 18:54:21 CEST Andy Smith wrote:
> Ah, okay. I did see some comments somewhere that it would be present
> in an upstream 6.2 release, so that makes sense.
>
> Okay, so perhaps I should wait for bookworm-backports to be a thing
> and then that may include a 6.2 or later kern
On Sunday, 26 March 2023 23:58:58 CEST Ken Milmore wrote:
> The upstream fix [1] to avoid the irksome error messages has been to replace
> a call to request_firmware() from the iwlwifi driver with
> firmware_request_nowarn() instead. This causes option flag FW_OPT_NO_WARN to
> be set inside the fir
On Monday, 27 March 2023 15:59:37 CEST Marcel Camijn wrote:
> We recently got new hardware with a new raid controller but noticed that the
> required module MPI3MR is not enabled. The latest uploaded kernel image has
> "#CONFIG_SCSI_MPI3MR is not set" in the config.
>
> The module seems to be incl
On Tuesday, 28 March 2023 00:21:59 CEST Ken Milmore wrote:
> > I don't know if it's also an upstream kernel issue or it's only caused by
> > Debian's patch, but AFAICT that patch needs to be revised to (at least)
> > account for the upstream change(s?) in firmware loading.
>
> AFAICT, it's just a
Control: reassign src:linux 6.1.15-1
On Wednesday, 29 March 2023 09:59:22 CEST Stefan K wrote:
> Package: linux-image-amd64
> Version: 6.1.15-1
Unstable has version 6.1.20-1, can you test whether the issue is present there
too?
signature.asc
Description: This is a digitally signed message part.
On Monday, 27 March 2023 17:35:25 CEST Diederik de Haas wrote:
> While looking into it, I did find some troubling aspects though.
> I noticed that in upstream's master branch there were quite some commits
> *after* 6.1 of which a reasonable amount has been backported to 6.1.
>
Control: reopen -1
On Tuesday, 21 March 2023 14:21:05 CEST Debian Bug Tracking System wrote:
> > In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
> > for recommendations on which/how/what kernel modules to enable.
>
> In https://git.kernel.org/linus/9e18d0c82f0c07f2a41898d4ad
On Wednesday, 29 March 2023 22:59:13 CEST Diederik de Haas wrote:
> Control: reopen -1
>
> On Tuesday, 21 March 2023 14:21:05 CEST Debian Bug Tracking System wrote:
> > > In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
> > > for rec
Control: found -1 6.1.20-1
> > Unstable has version 6.1.20-1, can you test whether the issue is present
> > there too?
> Yes, it still happens with 6.1.20-1..
Updating metadata accordingly
On Thursday, 30 March 2023 14:46:51 CEST Stefan K wrote:
> With Kernel 6.0.0-0.deb11.6-amd64 it works fine
On Friday, 31 March 2023 12:57:44 CEST Stefan K wrote:
> when I searching my error message I got a lot of hits..
> In arch it's solved:
> https://bugs.archlinux.org/task/76934
>
> the patch:
> https://gitlab.freedesktop.org/superm1/linux/-/commit/2145b4de3fea9908cda6be
> f0693a797cc7f4ddfc.patch
to the actual one which is para 4.2.2 and I have
attached a patch which reverts the referenced commit and that .patch file is
what you give as an argument to `bash debian/bin/test-patches`.
If you could try that to see if that indeed fixes the issue, that would be
very helpful.
HTH
>From 2e6223080905caf4c775680201700b2
Is it sufficient to apply the patch given by Diederik de Haas ?
I'm guessing you forgot to do the Preparation from 4.2.1
>Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit :
>> Hi,
>>
>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote:
>>> Hello
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
> I am in trouble... I first did "Obtaining the kernel source", and at the
> end I got a /root/linux-source-6.1/ directory.
>
> Then I did "Rebuilding official Debian kernel packages" and
> "Preparation", and then I got among others a
> /
Control: tag -1 upstream
On Saturday, 1 April 2023 22:47:35 CEST Guy Durrieu wrote:
> I just finished to build the patched kernel.
Well done!
> After installing it, the system 6.1.0-7 boots again and run fine.
> Thus the source was well identified by Bjørn Mork.
This is great :-)
> I just had
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:
> 2) The commit that Bjørn identified also contained a "Link:" tag:
> https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com
>
> The best thing to do is to respond to that thread and explain the issue y
On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> > Not sure why patchwork still shows v2 of the patch as v4 is available
> > here:
> > https://lore.kernel.org/all/20230308154244.722337-1-hdego...@redha
On Tuesday, 4 April 2023 13:11:16 CEST Julien Cristau wrote:
> On Mon, Apr 3, 2023 at 15:16:42 +0200, Diederik de Haas wrote:
> > On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
> >
> > On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> >
On Friday, 7 April 2023 23:15:03 CEST Debian Bug Tracking System wrote:
> > Comments:
> > 1. If the kernel installation requires the headers to function properly,
> > then they should probably be a package dependency.
>
> As said above, the kernel does need the headers installed.
Correction: the
Note: I do NOT speak on behalf of the kernel team.
On Tuesday, 18 April 2023 09:47:14 CEST Marco d'Itri wrote:
> On Apr 18, Jamie Bainbridge wrote:
> > I have a laptop with iwlwifi wireless card:
> > $ sudo lspci -nn | grep Net
> > Network controller [0280]: Intel Corporation Wireless 7265 [808
On On Apr 18, Jamie Bainbridge wrote:
> > > I can only assume from the massive Ubuntu install base that this file
> > > doesn't cause any problems for devices which don't need the modules
> > > loaded in this order, while also resolving whatever problem requires
> > > that modules are loaded in th
On Sunday, 23 April 2023 15:43:01 CEST Ben Hutchings wrote:
> Can you confirm exactly which upstream release you've tested
The initial bug report (which didn't end up on debian-kernel ML) had:
On Tue, 18 Apr 2023 12:12:58 +1000 Rod Webster wrote:
> We note that RT latency/jitter has significantl
Control: tag -1 moreinfo
On Friday, 28 April 2023 20:15:46 CEST Harold Grove wrote:
> Package: src:linux
> Version: 6.1.20-2
Unstable now has version 6.1.25-1, could you try that?
> I'm also seeing a possibly related kernel oops when unloading the psmouse
> module. The module is being unloaded v
Control: forwarded -1
https://salsa.debian.org/kernel-team/linux/-/merge_requests/675
On Monday, 1 May 2023 09:47:48 CEST Roger Shimizu wrote:
> Did you forget to enclose the patch?
It's here: https://salsa.debian.org/kernel-team/linux/-/merge_requests/675
signature.asc
Description: This is a d
On Monday, 1 May 2023 20:40:11 CEST Rusty Grove wrote:
> The script is something I did
Can you test without that script then?
IMO the proper way to deal with suspend/resume should be done by the system/
kernel and it *could* be that your script is actually interfering with that.
> I'm not quite s
Control: reassign -1 firmware-brcm80211
Control: affects -1 -raspi-firmware
Control: retitle -1 Missing symlinks for RPi 4 (to
brcmfmac43455-sdio.raspberrypi,4-model-b.txt)
On Thursday, 4 May 2023 00:21:25 CEST James Addison wrote:
> I added a note[1] on the rpi4-uefi.dev GitHub repository, and f
On Thursday, 4 May 2023 01:03:08 CEST Diederik de Haas wrote:
> Control: affects -1 -raspi-firmware
That it affects a RPi device does NOT mean it affects the raspi-firmware
package,
so I removed that field (hopefully)
signature.asc
Description: This is a digitally signed message part.
Source: firmware-nonfree
Version: 20230210-5
Severity: normal
X-Debbugs-Cc: 1029...@bugs.debian.org, k...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While trying to prepare a MR to fix bug #1029843, I encountered a
failure which seems to be `gencontrol.py`'s inability to deal with
Control: block -1 1035505
On Thursday, 4 May 2023 01:41:12 CEST Cyril Brulebois wrote:
> Diederik de Haas (2023-05-04):
> > And that makes it a firmware-brcm80211 issue and now it all does make
> > sense as it now all does tie together :-)
>
> Great, that's what it l
On Thursday, 4 May 2023 12:25:29 CEST Diederik de Haas wrote:
> While trying to prepare a MR to fix bug #1029843, I encountered a
> failure which seems to be `gencontrol.py`'s inability to deal with
> spaces and/or backslashes (used to escape the spaces).
Here's the branch th
On Monday, 8 May 2023 14:08:14 CEST James Addison wrote:
> On Mon, 1 May 2023 11:18:03 +0100, James Addison wrote:
> > > Diederik de Haas (2023-04-30):
> > > > And that's exactly what happens or will happen. Even though the RPi4
> > > > filename doesn&#
On Tuesday, 9 May 2023 18:04:35 CEST fab...@greffrath.com wrote:
> today I tried again with a TP-Link TL-WN725N Nano USB dongle which
> contains the Realtek RTL8188EU chip set. Same result, the adapter is not
> recognized and I am presented with a list of kernel modules of which
> none works. But i
On Tuesday, 9 May 2023 18:49:35 CEST Vincent Blut wrote:
> > today I tried again with a TP-Link TL-WN725N Nano USB dongle which
> > contains the Realtek RTL8188EU chip set. Same result, the adapter is not
> > recognized and I am presented with a list of kernel modules of which none
> > works. But i
On Tuesday, 9 May 2023 20:01:00 CEST Vincent Blut wrote:
> > Am I missing something (still)?
>
> Color me stupid. I was working from upstream's master branch which have the
> staging driver removed. Sorry for the confusion!
I'm not in the habit of calling people stupid ;-)
I'm actually glad you p
On Wednesday, 10 May 2023 04:29:10 CEST Aram Akhavan wrote:
> Package: nfs-common
> Version: 1:1.3.4-6
We're currently at version 2.6.2 (or .3 in experimental) and I doubt that
upstream cares about version 1.3.4.
Can you reproduce the issue with version 2.6.2 (or higher)?
signature.asc
Descripti
Control: reassign -1 src:linux 6.1.25-1
Control: tag -1 upstream
Control: forwarded -1
https://lore.kernel.org/all/20230127-rpi-cursor-corruption-v2-1-1f97bd00d...@cerno.tech/
On Wednesday, 10 May 2023 19:04:55 CEST James Addison wrote:
> Followup-For: Bug #1035878
> Control: reassign -1 linux-im
Control: reassign -1 debian-kernel-handbook 1.0.21
Control: severity -1 wishlist
Control: retitle -1 debian-kernel-handbook: Paragraph 4.5.1.1. Disk space
requirements needs an update (from 2018 numbers)?
On Thursday, 11 May 2023 14:33:40 CEST Claude Heiland-Allen wrote:
> I freed up more space,
On Friday, 12 May 2023 04:05:42 CEST Nathan Schulte wrote:
> amdgpu :03:00.0: andgpu: Fetched VBIOS from ATRM
> amdgpu: ATOM BIOS: 113-BRT112124.001
I don't know if (or how) that^ bios can be updated, but I did see:
BIOS FA617XT.303 03/23/2023
And I did see that a 307 BIOS is available, so my
Control: clone -1 -2
Control: forwarded -2 https://bugzilla.kernel.org/show_bug.cgi?id=217336
Control: retitle -2 Strange keyboard issues on ASUS TUF Gaming A16 Advantage
Edition, model FA617XT
On Friday, 12 May 2023 04:05:42 CEST Nathan Schulte wrote:
> I don't think it's related to the issue he
Control: tag -1 moreinfo
On Saturday, 13 May 2023 03:02:50 CEST xiao sheng wen wrote:
> Package: src:linux
> Version: 6.3.1-1~exp1
You reported the issue against version 6.3.1-1, but that version isn't
mentioned in your bug report. What's the status with that version?
> When I use Debian 11.6,
On Saturday, 13 May 2023 11:09:46 CEST Diederik de Haas wrote:
> On Saturday, 13 May 2023 03:02:50 CEST xiao sheng wen wrote:
> > Package: src:linux
> > Version: 6.3.1-1~exp1
>
> You reported the issue against version 6.3.1-1, but that version isn't
> mentioned i
On Thursday, 18 May 2023 12:52:24 CEST David Reviejo wrote:
> Seems to be an amdgpu bug introduced two or three kernel releases ago, as
> you can see googling around; for example here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2191739
>
> or here:
>
> https://gitlab.freedesktop.org/drm/amd
On Thursday, 18 May 2023 13:19:52 CEST Diederik de Haas wrote:
> I _think_ I got the right commit for the 6.3 branch attached.
It seems a '>' snuck in the attachment/patch as the very first char, so you may
want to remove that.
signature.asc
Description: This is a digitally signed message part.
Control: found -1 6.1.25-1
Control: retitle -1 Kernel panic - not syncing: Timeout: Not all CPUs entered
broadcast exception handler
On Tuesday, 23 May 2023 18:49:00 CEST Olivier Berger wrote:
> It used to work fine with 6.1.0-7 but has had problems with the 2 later
> updates of the testing kerne
On Tuesday, 2 May 2023 00:36:05 CEST Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > clone 1022061 -1
> > retitle -1 linux: test-patches script produces uninstallable packages
> > # First version with signed/unsigned Conflicts
> > reassign -1 src:linux 4.7~r
On maandag 21 juni 2021 03:14:47 CEST Davide Beatrici wrote:
> I reproduced the problem on 5.10.0-6 as well
> I believe the relay in the amplifier is going bad
It maybe useful to try a 5.9.x kernel as well, to properly rule out the kernel
as the source of the issues. Difference between -6 and -7
On maandag 21 juni 2021 13:20:46 CEST Drew Parsons wrote:
> I was surprised to see python2 pulled in on a new bullseye
> installation using nfs.
>
> It's a trivial patch of course to update the hashbangs for mountstats
> and nfsiostat in nfs-common 1:1.3.4-5 to python3.
https://salsa.debian.org/k
On zondag 27 juni 2021 22:37:10 CEST Salvatore Bonaccorso wrote:
> Let's ask the release team instead. Here my arguments why: nfs-utils
> needs a major rehaul, this was not possible to finish in time for
> bullseye, so this means nfs-utils is generally in not a very good
> shape for bullseye,detail
stem)
LSM: AppArmor: enabled
>From 3613d72806d37dcb7812c55513fcf232afb7746f Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Sun, 23 May 2021 23:53:22 +0200
Subject: [PATCH 4/4] Enable Power Management ICs for RK805 components.
https://www.cnx-software.com/pdf/Rockchip-Roadmap-2019-.11_
Control: found -1 5.10.46-1
signature.asc
Description: This is a digitally signed message part.
Control: found -1 5.10.46
Control: tag -1 upstream patch
commit 44dd5e2106dc2fd01697b539085818d1d1c58df0 from 5.13
commit bbac8bd65f5402281cb7b0452c1c5f367387b459 from linux-next from 20210701
Those 2 patches make USB3 work on the Rock64 :)
signature.asc
Description: This is a digitally signed m
I filed the following bug which may be related?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990867
Even though the (error) messages are/seem quite different, maybe
the 'Read-only file system' message is also kernel related?
I don't know the details anymore, but I've seen 'efivars' come by
o
Control: tags -1 confirmed
On zaterdag 24 juli 2021 01:29:55 CEST piorunz wrote:
> GPU core works at 100% usage at all times, even at idle.
>
> $ cat /sys/class/drm/card0/device/gpu_busy_percent
> 99
>
> $ sensors
> (...)
> amdgpu-pci-0900
> Adapter: PCI adapter
> vddgfx:1.14 V
> fan1:
:
deb [check-valid-until=no]
https://snapshot.debian.org/archive/debian/20210529T204006Z/ sid main
Installed linux-image-5.10.0-7-amd64 and rebooted into that ...
On zaterdag 24 juli 2021 14:22:38 CEST Diederik de Haas wrote:
> On zaterdag 24 juli 2021 01:29:55 CEST piorunz wrote:
> > GPU
On zaterdag 24 juli 2021 22:03:23 CEST Diederik de Haas wrote:
> > It's already backported to 5.10, just after 5.10.46 was released:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h
> > =l inux-5.10.y&id=fea853aca3210c21dfcf07bb82d501b7fd190
On zondag 25 juli 2021 00:48:41 CEST Davide Beatrici wrote:
> Package: linux-image-5.10.0-8-amd64
> Version: 5.10.46-2
>
> As soon as the screen resolution changes, all LEDs (GPUTach) on the side of
> my Vega 56 light up and never turn off again, indicating a constant 100%
> utilization.
>
> The
On vrijdag 30 juli 2021 17:22:06 CEST Jan Huijsmans wrote:
> ** Command line:
> ... root=/dev/sda1
I'm assuming you're the same person as in #984873, but iirc my mail to you wrt
that bug report bounced and hasn't received an answer.
Given that you're now booting from USB (again), it may be useful
On vrijdag 30 juli 2021 21:28:54 CEST Diederik de Haas wrote:
> On vrijdag 30 juli 2021 17:22:06 CEST Jan Huijsmans wrote:
> I'm assuming you're the same person as in #984873, but iirc my mail to you
> wrt that bug report bounced and hasn't received an answer.
And that
Source: linux
Version: 5.10.46-3
Severity: wishlist
Tags: patch
At
https://salsa.debian.org/raspi-team/image-specs/-/issues/7#note_206349
it was reported that CPU frequency scaling was enabled for armhf and
arm64, but not for armel. I (and others) have been able to confirm that.
So I build my own
Hi,
On vrijdag 6 augustus 2021 15:14:26 CEST Uwe Kleine-König wrote:
> On Thu, Aug 05, 2021 at 05:26:09PM +0000, Diederik de Haas wrote:
> > https://salsa.debian.org/raspi-team/image-specs/-/issues/7#note_206349
> >
> > So I build my own kernel wit
On vrijdag 6 augustus 2021 16:07:18 CEST Diederik de Haas wrote:
> > > -CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> > > +# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> > > -# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
> > > +CO
On donderdag 5 augustus 2021 19:26:09 CEST Diederik de Haas wrote:
> I 'heard' that the schedutil governor is good for big.little CPUs, but
On my amd64 machine (with Ryzen 1800X CPU) 'schedutil' is enabled and set as
default, so the above statement is a bit too simplisti
Source: linux
Version: 5.13.9-1~exp2
Severity: wishlist
Currently there are some LED triggers builtin and some as modules:
$ grep 'CONFIG_LEDS_TRIGGER' /boot/config-5.13.0-trunk-arm64
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_ONESHOT=m
CONFIG_LEDS_TRIGGER_DISK=y
CONF
On Friday, 28 October 2022 04:07:05 CEST Akkana Peck wrote:
> - systemctl suspend no longer works: instead of suspending, it freezes,
> and I have to hold the power button for 10 seconds to force a power down
> - the laptop's built-in sound card (intel, using the firmware-intel-sound
> package)
On Friday, 28 October 2022 14:57:12 CEST Bogdan Veringioiu wrote:
> this issue affecting the LVDS connector was reported here:
>
> https://gitlab.freedesktop.org/drm/intel/-/issues/7301
>
> and fixed.
>
> Any chance it will be backported in 5.10?
https://lore.kernel.org/all/20221026101134.20865
On Friday, 28 October 2022 18:58:12 CEST Akkana Peck wrote:
> That does sound like exactly the same sound issue. Sorry if this is a
> dumb question, but where would I find 6.0.5-1? I tried searching for
> linux-image-6.0.5, 6.0.5 and 6.0.5-1 in both unstable and experimental
It'll takes some time
Control: tag -1 upstream
Control: merge -1 1022544
On Friday, 28 October 2022 19:51:43 CEST karol wrote:
> Version: 6.0.3-1
> Severity: important
signature.asc
Description: This is a digitally signed message part.
On Friday, 28 October 2022 20:18:03 CEST Debian Bug Tracking System wrote:
> > merge -1 1022544
>
> Bug #1022981 [src:linux] linux-image-6.0.0-2-amd64: after boot kernel 6.0
> failed to instatiate audio card regression from 5.19 Unable to merge bugs
> because:
> done of #1022544 is 'Salvatore Bona
Control: found -1 6.0.5-1
On Friday, 28 October 2022 23:09:00 CEST Stephan Verbücheln wrote:
> I have now compiled and booted vanilla kernel 6.0.5. “efibootmgr -o” is
> not working.
>
> I double-checked that with kernel 5.19.11 (Debian), it is working fine.
Thanks for testing and reporting back.
Control: fixed -1 20220913-1
On Wednesday, 6 July 2022 12:46:16 CEST Enrique wrote:
> Package: firmware-brcm80211
> Version: 20210315-3
>
> I have installed pure Debian on a Raspberry Pi 4 and the kernel shows
> this error messages at boot:
>
> jul 06 11:57:25 alcatraz kernel: brcmfmac mmc0:0001
Control: tag -1 upstream
Control: forcemerge -1 1022544
On Saturday, 29 October 2022 00:09:10 CEST zezamoral wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: important
>
>* Updating to Linux Image amd64 6.0.3-1 caused the sound card to be
> undetected..
Same issue as 1022544, thus
Control: tag -1 moreinfo
On Monday, 11 April 2022 23:32:26 CEST Tobias Koeck wrote:
> Package: firmware-amd-graphics
> Version: 20210818-1
>
> I was affected by a freeze by this bug
>
> https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-FW-Avoid-VCN-Mult
> i-Hang
>
> Can you add the fir
501 - 600 of 750 matches
Mail list logo
