On Wednesday, 1 February 2023 02:52:13 CET Dr. David Alan Gilbert wrote:
> bisected:
> GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should
> depend on ARCH_LAYERSCAPE BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f]
> dma-mapping: remove CONFIG_DMA_REMAP GOOD
> [e62c17f0455a7
Hi Salvatore and Gunnar,
On Tuesday, 31 January 2023 19:17:43 CET Salvatore Bonaccorso wrote:
> > Gunnar indicated that he's willing to remove the files from
> > raspi-firmware,
> > but they still need to be added to firmware-brcm80211, so pretty please?
>
> So I looked at this, and don't think t
Control: tag -1 upstream fixed-upstream
On Saturday, 28 January 2023 07:22:11 CET Stuart Read wrote:
> I found this upstream bug report:
> http://lists.infradead.org/pipermail/linux-mediatek/2022-December/054010.ht
> ml
>
> However it is unclear to me if or when the fix will be applied to the
> k
On Friday, 27 January 2023 21:05:47 CET Computer Enthusiastic wrote:
> This patch [2] applies to kernel version 5.10.y, too. I used it with a
> custom built kernel since it was published .
>
> The author of the patch acknowledged that the patch applies to kernel
> version 5.10.y asking me to send
Control: tag -1 moreinfo
On 26 Nov 2022 20:31:25 +0100 Klaus Singvogel wrote:
> This issue only happens only with linux-image-6.0.0-0.deb11.2-amd64
> After I booted the old linux-image-5.19.0-0.deb11.2-amd64, the issue does
> not occur.
Does this issue still occur with version 6.0.12-1~bpo11+1 w
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/libinput/libinput/-/issues/852
On 25 January 2023 17:52:10 CET, Tobias Klausmann
wrote:
>Also reported to libinput upstream:
>
>https://gitlab.freedesktop.org/libinput/libinput/-/issues/852
Thanks! Updated bug metada
Control: found -1 5.10.162-1
On Wednesday, 25 January 2023 11:18:35 CET Keyu Tao wrote:
> [ 214.783069] CPU: 0 PID: 372 Comm: kworker/0:4 Kdump: loaded Not tainted
> 5.10.0-21-amd64 #1 Debian 5.10.162-1
signature.asc
Description: This is a digitally signed message part.
On Monday, 23 January 2023 19:05:43 CET Florian Rehnisch wrote:
> I researched a bit and found a discussion in the Arch forum, and also an
> issue in the upstream bugzilla, mentioning a patch.
>
> I applied that patch against linux-source/6.1.7-1, built it, and it
> fixed the freeze. That patch is
Control: reassign -1 dkms
Control: forcemerge 1029063 -1
On Monday, 23 January 2023 14:53:18 CET Stefano Simonucci wrote:
> Building module:
> Cleaning build area...
> make -j8 KERNELRELEASE=6.1.0-1-amd64 all
> KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2)
> Error! Bad return
ely?), it would replace your existing 5.10.0-20-amd64
kernel and there is no (easy) way to see that you would be booting into
your new patched kernel from GRUB.
HTH,
Diederik>From 3ed496982f556d17a87f830acaf5023d4f5d9a9b Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Thu, 19 Jan 2023
Control: tag -1 fixed-upstream
On Wednesday, 18 January 2023 11:35:30 CET only4com wrote:
> Package: linux-image-6.1.0-1-amd64
> Version: 6.1.4-1
>
> After updating the linux image from linux-image-6.0.0-6-amd64 to
> linux-image-6.1.0-1-amd64 Version 6.1.4-1 I cannot mount a samba share from
> an
> > Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> > > On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> > > > This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> > > > ligh
Control: tag -1 moreinfo
On Tuesday, 17 January 2023 14:20:19 CET Claire Osborne wrote:
> Booting in recovery mode on 5.10.0.20 also failed
>
> I have fallen back to the previously installed kernel 5.10.19 - with the
> same effect.
>
> Booting in recovery mode on 5.10.0.19 also fails.
What was
Hi OdyX,
On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> light up", so feel free to close the bug; I'll test if I get the same
> symptoms on an unpatched kernel anyway :-)
If this issue doesn't occur wi
On Saturday, 14 January 2023 16:30:05 CET Salvatore Bonaccorso wrote:
> On Thu, Jan 12, 2023 at 02:51:05PM +0100, Diederik de Haas wrote:
> > On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> > > Fwiw there is a general regression with AMDGPU MST on
Source: linux
Version: 6.1.4-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The DeviceTree files (*.dtb) as shipped with the Debian kernel have the
executable bit set, but there is absolutely no need for that.
Lintian rightfully complains about it (executable-not-elf-or-script
Hi Julian,
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
The following paragraph may not be ideally formulated:
"Currently, I am using git
On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
> upstream here:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Thanks! About an hour ago the suggested fix was to revert commit
4d07b0bc403403438d9cf
Control: forwarded -1
http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.htm
On Wednesday, 11 January 2023 19:28:25 CET Julian Groß wrote:
> On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas
> wrote:
> > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure
> > to find the exact commit which introduced the issue you reported, but it&#
Control: found -1 6.0~rc7-1~exp1
On Wednesday, 11 January 2023 15:04:30 CET Julian wrote:
> 6.0~rc7-1~exp1 is also broken.
>
> I will go through https://wiki.debian.org/DebianKernel/GitBisect and see
> what I can find. Thankfully the documentation is quite comprehensive.
That would be great, tha
On Wednesday, 11 January 2023 08:33:29 CET Didier 'OdyX' Raboud wrote:
> Package: src:linux
> Version: 6.1.4-1
> Severity: serious
>
> Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking
> Station doesn't get any output.
Can you try the previous versions of the 6.1.x series w
On Tue, 23 Nov 2021 07:58:32 +0100 Ard Biesheuvel wrote:
> I don't see a reason to revert the default upstream. The feature
> remains deprecated (and in the longer term, the EFI handover protocol
> may be deprecated and removed as well), so the earlier the bootloaders
> adapt, the better it is.
>
Control: forwarded -1
https://lore.kernel.org/all/877f41ovlu@free-electrons.com/
Hi Ben,
On 07 Mar 2017 18:16:45 +0100 Gregory CLEMENT
wrote:
> On lun., févr. 20 2017, Ben Hutchings wrote:
> > On Mon, 2017-02-20 at 17:50 +0100, Thomas Petazzoni wrote:
> >> On Mon, 20 Feb 2017 16:40:25 +0
Control: found -1 6.0.10-1
On Monday, 9 January 2023 13:20:08 CET Julian Groß wrote:
> when running Linux Kernel version 6.0.12 or 6.0.10, my system seemingly
> randomly freezes due to the filesystem being set to read-only due to an
> issue with my nvme controller.
> The issue does *not* appear o
Control: tag -1 upstream
Control: severity -1 normal
On Wed, 04 Jan 2023 12:04:52 +0100 xevilstar wrote:
> Package: linux-image-6.2.0-rc2
> Version: 6.2.0-rc2-1
>
> I am testing linux kernel 6.2-rc2
That is great, but you should report any issues you find to the relevant
upstream maintainers.
On Wednesday, 4 January 2023 15:38:32 CET Tim Düsterhus wrote:
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's
On Wednesday, 4 January 2023 16:39:33 CET Renato Gallo wrote:
> 5.10 should be EOL by now
Please refrain from comments like that.
It doesn't help at all and is also plain false.
signature.asc
Description: This is a digitally signed message part.
On Friday, 30 December 2022 12:42:53 CET Thorsten Glaser wrote:
> I think I reported the same thing against experimental some time ago,
> but it now is a regression in stable. Building kernel modules shows:
>
> tglase@tglase-edge:~/lnx/master/janz $ make
> make -C '/lib/modules/5.10.0-20-amd64/bui
On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote:
> >> Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and
> >> linux-image-5.6.0-2-amd64 (5.6.14-1).>
> > This also affects 5.5.0-rc5-amd64.
> >
> > (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/l
>
Control: reassign -1 src:linux 6.0.3-1~bpo11+1
On Tuesday, 27 December 2022 15:42:31 CET Wolf-Dieter Groll wrote:
> Package: linux-image-amd64
> Version: 6.0.3-1~bpo11+1
Stable backports now has 6.0.12-1~bpo11+1, could you try that too?
signature.asc
Description: This is a digitally signed messa
On Tuesday, 9 November 2021 01:30:03 CET nerdopolis wrote:
> +++ b/debian/config/kernelarch-x86/config
> @@ -75,6 +75,7 @@ CONFIG_IA32_EMULATION=y
> ## file: arch/x86/Kconfig.cpu
> ##
> # CONFIG_PROCESSOR_SELECT is not set
> +CONFIG_X86_SYSFB=y
It is now in a different location and quoting the
On Thursday, 22 December 2022 22:20:44 CET Kamila Szewczyk wrote:
> [ 297.413358] vboxdrv: loading out-of-tree module taints kernel.
If you're indeed testing this inside VirtualBox, do look whether there's an
update for that (too).
> [ 3025.190695] ACPI Error: No handler for Region [ECSI] (0
Control: reassign src:linux 5.10.158-2
On Wednesday, 21 December 2022 22:45:12 CET sapcie wrote:
> Package: linux-image-5.10.0-20-amd64
> Version: latest
> Severity: normal
Bug https://bugs.debian.org/1010733 also mentions that same audio device,
although that seems to have failed with 5.10.0-13
On Wednesday, 21 December 2022 17:11:55 CET Diederik de Haas wrote:
> Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is
> a self-built kernel from current master, it seems more likely to be an
> upstream issue/regression.
I just noticed the following part from t
On Wednesday, 21 December 2022 12:47:45 CET Zhang Ning wrote:
> Package: linux-image-arm64
> Version: 6.1-1~exp1
>
> WIFI works well for my Arm64 SBCs (Khadas VIM1 & VIM3), both are Amlogic
> SBC, S905x and A311D, with kernel 6.0 and early versions.
>
> these two boards are well supported by debi
found 1026174 linux/6.0.10-2
signature.asc
Description: This is a digitally signed message part.
On Saturday, 22 May 2021 00:46:55 CET Vagrant Cascadian wrote:
> Package: src:linux
> Version: 5.10.28-1
> File: /boot/vmlinuz-5.10.0-6-armmp-lpae
> Control: block 986767 by -1
>
> The ethernet bridge fails to work on 5.10.x (also tried 5.10.38-1),
> but works fine on 4.19.x from buster. (This was
On Thursday, 15 December 2022 11:47:11 CET Diederik de Haas wrote:
> On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> > after the discussion about the root cause of this issue on the linux-scsi
> > mailing list[1] there was one simple patch submitted to this list[2
On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> after the discussion about the root cause of this issue on the linux-scsi
> mailing list[1] there was one simple patch submitted to this list[2] that
> just changes the logic of the selection of the dma mask: in case of a 64bit
> hos
Control: found -1 6.0.12-1
On Thursday, 15 December 2022 10:09:27 CET Bernhard wrote:
> This bug still exist in Daily image from today (2022-12-15).
That's using the 6.0.0-6-armmp kernel.
signature.asc
Description: This is a digitally signed message part.
On Tuesday, 13 December 2022 15:40:04 CET Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
>
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upg
Control: tag -1 -moreinfo
On Wednesday, 1 June 2022 01:27:32 CET Diederik de Haas wrote:
> What's the current status wrt this bug?
Just saw upstream commit 630dc25e43dacfb5af94cd41532e77c47ec1caff which should
become part of 6.1-rc9 and/or 6.1 and it would be interesting to know if tha
Control: tag -1 moreinfo
On Sunday, 3 July 2022 14:40:36 CET Jean-Marc LACROIX wrote:
> Package: linux-image-5.18.0-2-arm64
> Version: 5.18.5-1
>
> Please find in attached file success story (!) on recent boot for
> target rock64 (pine64) with 64 Go class10 MMC card with Debian 11.3
> Bu
Control: tag -1 =upstream
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Thursday, 8 December 2022 15:27:49 CET Dröszler Gábor wrote:
> Package: src:linux
> Version: 5.10.149-2
> Severity: important
>
> Debian Bullseye not boot with XEN, linux-image-5.1
Control: severity -1 important
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Monday, 31 October 2022 13:44:05 CET Taavi Ansper wrote:
> Yes we are using xen virtualization
Merging it with 1022126 then
signature.asc
Descriptio
Control: tag -1 upstream
On Thursday, 8 December 2022 12:48:08 CET Marco Moock wrote:
> > Has it worked properly before with an older kernel? If so, which?
>
> No, it is a general problem.
Tagging the bug accordingly
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
>My Logitech
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
> Package: src:linux
> Version: 6.0.10-2
>
>My Logitech Inc. QuickCam Communicate STX USB Webcam 046d:08d7 can't
>use USB 2.0, although the manufacturer says it supports it.
Has it worked properly before with an older kernel? If
On Wednesday, 7 December 2022 05:57:55 CET Christoph Anton Mitterer wrote:
> A patch has now been posted for dash at:
> https://lore.kernel.org/dash/y47zlpwkqy+ji...@gondor.apana.org.au/
> which is apparently scheduled to be merged into their git.
FTR: a v2 of that patch has been posted:
https://l
Control: tag -1 moreinfo
On Mon, 03 Sep 2012 14:24:47 -0700 Russ Allbery wrote:
> Ben Hutchings writes:
> > On Mon, Sep 03, 2012 at 12:21:06PM -0700, Russ Allbery wrote:
> > [...]
> >> linux-libc-dev maintainers, when upgrading to squeeze, there is
> >> currently nothing preventing linux-libc-de
Control: tag -1 moreinfo
Hi Hank,
On Tuesday, 13 September 2022 17:48:22 CET Hank Barta wrote:
> Package: src:linux
> Version: 5.19.6-1
>
>* What led up to the situation?
>
> Apparent inability to initialize/connect to the SD card H/W. This leads to
> the message below that is repeated abou
On Friday, 10 June 2022 14:16:00 CET Diederik de Haas wrote:
> If I understand the forwarded thread correctly, the reported symptoms went
> completely away by updating firmware files from
> https://github.com/RPi-Distro/ firmware-nonfree/tree/master/brcm on
> 2021-03-29.
> Those
On Tuesday, 6 December 2022 23:10:32 CET Olivier Mehani wrote:
> >What's the version of NFS you're using?
>
> The clients are recent Linux hosts, and one Kodi 19.x. I don't specify a
> version in either their fstab or the server's exports.
Sorry, I meant the package version of the NFS server
sig
On Tue, 11 Apr 2017 23:28:41 +0100 Ben Hutchings wrote:
> Control: severity -1 important
> Control: severity 824442 important
>
> On Tue, 2017-04-11 at 23:20 +0200, Aurelien Jarno wrote:
> > On 2017-04-11 03:35, Ben Hutchings wrote:
> > > Control: tag -1 moreinfo
> > >
> > > On Mon, 10 Apr 2017
Control: tag -1 moreinfo
On Monday, 1 August 2022 02:07:02 CET Linas Vepstas wrote:
> I just attempted a hand-build of kernel 5.18.15 and it exhibits exactly the
> same failure, the same stack traces.
Does the problem still occur with a recent 6.0 kernel?
There have recently also been uploads of
Control: found -1 5.10.149-2
On Tuesday, 6 December 2022 15:27:11 CET bob wrote:
> It still occurs with
> Linux AsusTUFgX570 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21)
Thanks, updated bug accordingly.
It may be useful to keep testing new updates, also from backports, but I
suspect thi
On Tuesday, 6 December 2022 12:54:31 CET Olivier Mehani wrote:
> NFS would still be accessible as before (:
What's the version of NFS you're using?
signature.asc
Description: This is a digitally signed message part.
On Sunday, 30 October 2022 09:34:25 CET Salvatore Bonaccorso wrote:
> > I can no longer reproduce this. Currently running Ubuntu 22.10 with
> > kernel 5.19.0-23-generic. C-states enabled in the BIOS.
>
> But what about Debian's kernels? Are you able to reproduce your issue
> still with most recent
Control: found -1 5.15.5-2~bpo11+1
On Thursday, 30 June 2022 01:10:05 CET Douglas Silva wrote:
> I've tested 5.15.5-2~bpo11+1 and it's reproducible.
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 moreinfo
On Saturday, 25 June 2022 05:33:01 CET Ian Turner wrote:
> On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience
> occasional kworker kernel hangs with numerous other associated
> uninterruptable processes.
>
> * The issue is resolved in linux-image-5.16.
On maandag 5 december 2022 19:29:46 CET Alexandr Podgorniy wrote:
> I don't know, but current 6.0.10-1 kernel works fine. Issue disappeared
> after few updates, 5.19 kernel worked fine as far as i remember.
Can you find out the lowest kernel version in which it was fixed?
Or would you rather just
Control: retitle -1 Please add brcmfmac43456-sdio.* files as it's not just used
in RPi devices
On 10 Nov 2022 11:40:06 +0100 Diederik de Haas wrote:
> On Sat, 9 Apr 2022 17:52:00 -0500 Gunnar Wolf wrote:
> > Please note I'm currenlty shipping the required files in
>
Control: tag -1 moreinfo
On woensdag 22 juni 2022 00:20:22 CET you wrote:
> Kernel 5.18.3 contains (at least) 2 patches related to dpaa2-eth.
> Kernel 5.18.5-1 (currently in Sid) does contain quite a few fixes vs 5.18.2,
> so it would be useful to verify if that fixes your issue. I don't know when
Control: tag -1 moreinfo
On 5 Jul 2022 18:21:27 +0500 Alexandr Podgorniy wrote:
> I tried 5.18.0-2-amd64 kernel recently and noticed that it doesn't go to
> sleep when Bluetooth mouse connected. Otherwise it's fine. Not tried
> 5.18.5 yet.
FTR: 5.18.5 is 5.18.0-2 and if that didn't fix it, the
On Tuesday, 31 May 2022 18:52:44 CET Diederik de Haas wrote:
> Now that 989153 and 989181 have been merged into this one and the bug is
> reopened, then the next question becomes: how to proceed.
Ping?
signature.asc
Description: This is a digitally signed message part.
On Monday, 5 December 2022 18:03:57 CET Laurent Bonnaud wrote:
> On 12/5/22 17:34, Diederik de Haas wrote:
> > btw: What's the reason for not using a 5.10 kernel on a Stable system?
> > (Not that I mind, just curious)
>
> I had a NFS problem with the 5.10 kernel and test
Control: found -1 5.16.12-1~bpo11+1
Control: tag -1 moreinfo
On Tuesday, 17 May 2022 15:25:29 CET Bob wrote:
> This behavior is still exibited by ... 5.16.0-0.bpo.4-amd64 from backports
Updated bug with that info.
Does this problem still occur with the latest 5.10 version and/or the latest
bac
Control: tag -1 moreinfo
On Wednesday, 30 March 2022 19:49:03 CET Laurent Bonnaud wrote:
> For now it seems to run fine even with this warning (no user complained).
>
> Additionally, I am not sure if the problem will occur again and how often.
> I will reboot the system, monitor it and update th
Control: retitle -1 mdadm --examine in chroot without /dev mounted corrupts
host's filesystem
Control: found -1 5.10.127-2
Control: fixed -1 5.18.2-1~bpo11+1
On Tuesday, 2 August 2022 11:03:09 CET Chris Hofstaedtler wrote:
> Control: reassign -1 src:linux
On 10 Feb 2021 14:29:52 +0100 Patrick Ce
On dinsdag 29 november 2022 02:35:44 CET Moessbauer, Felix wrote:
> The reason is well documented in this link and this has already been
> fixed upstream in the 6.0.x branch.
In the upstream 6.0.4 release to be exact and part of Debian's 6.0.5-1 upload.
signature.asc
Description: This is a digita
Control: found -1 4.9.88-1+deb9u1
Control: notfound -1 4.9.88-1
Hi Salvatore,
On zondag 20 november 2022 16:38:25 CET Salvatore Bonaccorso wrote:
> On Sun, Nov 20, 2022 at 04:26:45PM +0100, Diederik de Haas wrote:
> > Control: notfound -1 4.9.88-1+deb9u1
> > Control: found -1 4.
Control: notfound -1 4.9.88-1+deb9u1
Control: found -1 4.9.88-1
On zondag 20 november 2022 13:55:09 CET Salvatore Bonaccorso wrote:
> Seems the BSP was productive :).
Yeah, once I set up the VM and created the script, it was actually quite easy.
> If you have spare cycles, might you
> check if d
Control: found -1 5.14.9-2
Control: found -1 5.15.5-2
Control: fixed -1 5.15.15-2
Control: fixed -1 5.16.11-1
Control: fixed -1 5.18.16-1
Control: fixed -1 6.0.3-1
On zondag 20 november 2022 12:18:50 CET you wrote:
> Control: found -1 5.14.9-2 5.15.5-2
> Control: fixed -1 5.15.15-2 5.16.11-1 5.18
Control: found -1 5.14.9-2 5.15.5-2
Control: fixed -1 5.15.15-2 5.16.11-1 5.18.16-1 6.0.3-1
On zaterdag 19 november 2022 21:22:46 CET Diederik de Haas wrote:
> found 900821 5.10.70-1
> fixed 900821 5.10.84-1
I continued testing with kernels from backports and updated metadata
accor
user debian-rele...@lists.debian.org
usertag 900821 + bsp-2022-11-nl-tilburg
found 900821 5.10.70-1
fixed 900821 5.10.84-1
thanks
We have/had a BSP in Tilburg today and I went to work on this bug.
With success :-)
I first created a new Bullseye VM with virt-manager using the
debian-11.5.0-amd64-
Control: tag -1 -moreinfo upstream
Control: found -1 20221012-1
On Friday, 11 November 2022 20:41:56 CET Rui Dinis wrote:
> After further testing with firmware-misc-nonfree 20220913-1 and
> firmware-misc-nonfree 20221012-1, the problem still persists the machine
> crashes after several minutes or
Package: firmware-brcm80211
Version: 20221012-1
Severity: normal
X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
With a freshly made RPi 3 Bookworm image (with [1]) I booted up my
RPi 3B+ and noticed the following error in `dmesg`:
[ 19.801109] brcmfmac mmc1:0001:1: firmware: failed
On donderdag 10 november 2022 11:54:59 CET Diederik de Haas wrote:
> > Perhaps I didn't understand what you meant... Does the linux image
> > 6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this
> > case, is it sufficient to download the linux image and t
Just a quick response to this question, but I'll leave it up to Salvatore for
the rest of the bug handling/assistance :-)
On donderdag 10 november 2022 11:35:33 CET Guy Durrieu wrote:
> > I am not sure I am able to do that :)
>
> Perhaps I didn't understand what you meant... Does the linux image
On Sat, 9 Apr 2022 17:52:00 -0500 Gunnar Wolf wrote:
> Please note I'm currenlty shipping the required files in
> raspi-firmware -- I believe their right place is in
> firmware-brcm80211, so please just ping me (or better, raise a bug on
> raspi-firmware) whent they are added to this package.
I o
On donderdag 10 november 2022 03:42:36 CET Christoph Anton Mitterer wrote:
> On Thu, 2022-11-10 at 03:37 +0100, Christoph Anton Mitterer wrote:
> > $ ls -al 6.0.0-3-amd64/build 6.0.0-3-amd64/source
> > lrwxrwxrwx 1 calestyo calestyo 36 Nov 5 14:41 6.0.0-3-amd64/build ->
> > /usr/src/linux-headers-
Control: tag -1 pending
On Wednesday, 9 November 2022 00:27:11 CET Diederik de Haas wrote:
> The /usr/lib/linux-image-6.1.0-0-arm64 does indeed not exist.
Since merging https://salsa.debian.org/kernel-team/linux/-/merge_requests/581
the directory does exist and is populated, thus tagging
Source: linux
Version: 6.1~rc3-1~exp1
Severity: important
I just used d-i from 20221108 to install a fresh Debian Bookworm system
on my Rock64. After reboot I added (Sid and) Experimental sources as my
goal is/was to install/run kernel version 6.1~rc3-1~exp1.
That did not succeed:
==
On dinsdag 8 november 2022 08:40:46 CET xiao sheng wen wrote:
> Package: src:linux
> Version: 5.10.149-2
>
> My PC has [AMD/ATI] Kaveri [Radeon R7 Graphics] card.
>
> When I add radeon.cik_support=0 amdgpu.cik_support=1 in grub.cfg boot line,
> the PC can't boot, it's screen will dark, the keybo
On Thursday, 3 November 2022 22:18:53 CET Salvatore Bonaccorso wrote:
> >From the cover letter in the series:
> > The first patch will fix this, and the second will make sure we avoid that
> > situation entirely in the future. This has been tested with 5.19.12.
> > Earlier versions might need a bac
On Tuesday, 1 November 2022 22:36:56 CET Salvatore Bonaccorso wrote:
> Source: linux
> Version: 6.0.6-2
> Severity: serious
> Justification: FTBFS
>
> Documenting the build failures on arm64 and armhf due to ABI changes:
>
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=6.0.
On donderdag 3 november 2022 12:37:19 CET you wrote:
> I was able to reproduce this on a RPi 1, found that is was reported upstream
> here:
> https://lore.kernel.org/dri-devel/20220922145448.w3xfywkn5ecak...@pengutronix.de/
>
> and found the patches that were applied upstream in 6.1-rc2 where ther
://lore.kernel.org/all/20220929-rpi-pi3-unplugged-fixes-v1-0-cd22e9622...@cerno.tech/
On Monday, 31 October 2022 00:37:54 CET Diederik de Haas wrote:
> Control: found -1 5.19.6-1
> Control: severity -1 important
> Control: tag -1 moreinfo
>
> On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans
>
Control: severity -1 normal
On Wednesday, 2 November 2022 18:16:12 CET nmr wrote:
> Package: src:linux
> Version: 5.10.4-1
This is one of the very first 5.10.x versions! ...
> -- System Information:
> Debian Release: 11.5
> APT prefers stable-security
> APT policy: (500, 'stable-security'),
On Thursday, 27 October 2022 15:56:33 CET Gabriel Rolland [Res Novae] wrote:
> Same problem with the Dell PowerEdge T140 with LSI MegaRAID SAS-3 3008
> [Fury] (rev 02) and linux-image-5.10.0-19-amd64 (NO UEFI)
>
> No problem booting with the old 4.19.0-22-amd64 kernel
The best way to make progres
Control: reassign -1 src:linux 5.10.149-2
Control: tag -1 moreinfo
On maandag 31 oktober 2022 11:30:29 CET Taavi Ansper wrote:
> Package: Linux Kernel
> Version: 5.10.19
>
> After the new security patch to upgrade kernel to 5.10.19 we noticed that
> our external NetApp disk bay drives did not sho
Control: found -1 5.19.6-1
Control: severity -1 important
Control: tag -1 moreinfo
On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans wrote:
> Package: linux-image-5.19.0-1-arm64
> Severity: critical
> Justification: breaks the whole system
Only affecting RPi3 in certain conditions, thus lowering sever
On Saturday, 29 October 2022 23:17:20 CET Vincent Bernat wrote:
> > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi
> > t/log/?qt=grep&q=WCN6855 does show various results which come very close
> > ...SILICONZ_LITE-3.6510.7 vs the referenced ...SILICONZ_LITE-3.6510.16.
> >
Control: reassign -1 src:linux 4.19.260-1
signature.asc
Description: This is a digitally signed message part.
Control: reassign -1 src:linux 6.0.3-1
Control: severity -1 important
On Sunday, 30 October 2022 00:50:25 CEST Gabriel Francisco wrote:
> Package: linux-headers-6.0.0-2-amd64
> Version: 6.0.3-1
> Severity: normal
>
> With this kernel seems to crash bluetooth when returning from
> suspend. Few day
Control: tag -1 -a11y
On zaterdag 29 oktober 2022 12:33:59 CEST femenia wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: grave
> Tags: a11y
I don't see how a11y is relevant here, so removing the tag
signature.asc
Description: This is a digitally signed message part.
On zaterdag 29 oktober 2022 07:15:19 CEST Vincent Bernat wrote:
> On 2022-10-29 00:50, Diederik de Haas wrote:
> >> The card works just fine with a 5.19 kernel after installing these files
> >> in /usr/lib/firmware/ath11k/WCN6855/hw2.0/:
> >> https://github.com/kv
On Saturday, 29 October 2022 11:08:01 CEST karol wrote:
> Package: src:linux
> Version: 6.0.3-1
>
> I noticed several internal crashed in linux kernel ...
> This happened today during resume.
>
> They are follow as below:
>
> paź 29 10:55:35 karol kernel: [ cut here ]
> p
On Saturday, 29 October 2022 10:59:21 CEST Salvatore Bonaccorso wrote:
> > It was based on that log that I did most/all my recent bug closing.
>
> The files are present in the source and copied to debian/build/install
> . But they are then not installed in any of the produced binary
> packages in
301 - 400 of 740 matches
Mail list logo
