Mapping stable-security to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Oct 2022 22:24:21 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.10.149+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel
Mapping stable-security to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Oct 2022 22:24:21 +0200
Source: linux-signed-amd64
Architecture: source
Version: 5.10.149+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel
Mapping stable-security to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Oct 2022 22:24:21 +0200
Source: linux-signed-arm64
Architecture: source
Version: 5.10.149+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel
The new Debian 11/bullseye kernel 5.10.149-2 does not help on my setup.
Still a black screen and nothing is logged.
Also in rescue mode without "quiet".
My GPU is:
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81)
02:00.1
Hi,
I can confirm that, I have the same problem here. I can't boot into the
5.10.0.19-amd64 kernel, just a blackscreen.
Processor: AMD Ryzen 5 5600G with Radeon Graphics.
Awaiting a solution,
Maurício Forain.
After updating to the latest version (5.10.149-2), my system
running an AMD GPU and CPU still does not boot. I am unable to
retrieve any logs from the systemd journal.
CPU: AMD FX-8350
GPU: AMD R9 270X (Southern Islands Family)
Kernel command line parameters:
Control: severity -1 important
Control: tag -1 moreinfo
On zondag 23 oktober 2022 11:28:33 CEST Dan Smolik wrote:
> after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable.
> Problem is similar this bug
> https://bugzilla.kernel.org/show_bug.cgi?id=209177.
> I try recommended
Processing control commands:
> severity -1 important
Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as
dom0
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as
dom0
Added
Am 23.10.22 um 13:43 schrieb Diederik de Haas:
You both have kernel parameters like these. Can you explain why?
I have an AMD GPU on a machine and I have never set parameters like these.
These are parameters for Southern Islands (si) and Sea Islands (cik) AMD
GPUs:
Sorry this is production machine and I can't reboot it very often. But
tomorrow at night I try it and record boot. I have remote management on
this machine.
Regards Dan
Dne 23. 10. 22 v 13:52 Diederik de Haas napsal(a):
Control: severity -1 important
Control: tag -1 moreinfo
On zondag 23
On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:
> > You both have kernel parameters like these. Can you explain why?
> > I have an AMD GPU on a machine and I have never set parameters like these.
>
> These are parameters for Southern Islands (si) and Sea Islands (cik) AMD
> GPUs:
On Sun, 23 Oct 2022 13:43:30 +0200 Diederik de Haas
wrote:
> Andreas and inasprecali,
>
> On zondag 23 oktober 2022 09:17:44 CEST Andreas Wirooks wrote:
> > Kernel parameters are:
> > radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1
> > amdgpu.cik_support=1 amdgpu.gpu_recovery=1
>
>
On Sun, 23 Oct 2022 13:40:26 +0200 Diederik de Haas
wrote:
> Does it really not boot? Or does the screen not work properly?
>
> The cases in this bug report all boot AFAIK, it's just that the
screen does
> not work properly, but people were able to SSH into the machine.
> If your system
linux-signed-arm64_6.0.3+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-arm64_6.0.3+1.dsc
linux-signed-arm64_6.0.3+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On zondag 23 oktober 2022 12:02:52 CEST inasprecali wrote:
> After updating to the latest version (5.10.149-2), my system
> running an AMD GPU and CPU still does not boot. I am unable to
> retrieve any logs from the systemd journal.
Does it really not boot? Or does the screen not work properly?
Andreas and inasprecali,
On zondag 23 oktober 2022 09:17:44 CEST Andreas Wirooks wrote:
> Kernel parameters are:
> radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1
> amdgpu.cik_support=1 amdgpu.gpu_recovery=1
You both have kernel parameters like these. Can you explain why?
I have an
Hi again,
It seems the linux regression update [DSA 5257-2] has fixed this issue.
Thanks team!
Cheers,
Kees
On Sat, Oct 22, 2022 at 11:15:05AM +0200, Bastian Blank wrote:
> On Sat, Oct 22, 2022 at 10:59:30AM +0200, Bastian Blank wrote:
> > I would like to do some last minute changes to the linux package
> # Drop special case use of rcX as abi name
>
> While having the ability to distiguish between
5.10.149-2 solved the problem
many thanks for the quick fix
Weitergeleitete Nachricht
Betreff: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot
possible)
Datum: Wed, 19 Oct 2022 14:33:04 +
Von: Debian Bug Tracking System
Antwort an:
Package: src:linux
Version: 5.10.149-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: mar...@mydatex.cz
Dear Maintainer,
after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable.
Problem is similar this bug
https://bugzilla.kernel.org/show_bug.cgi?id=209177.
Mapping sid to unstable.
binary:ata-modules-6.0.0-2-arm64-di is NEW.
binary:btrfs-modules-6.0.0-2-arm64-di is NEW.
binary:cdrom-core-modules-6.0.0-2-arm64-di is NEW.
binary:crc-modules-6.0.0-2-arm64-di is NEW.
binary:crypto-dm-modules-6.0.0-2-arm64-di is NEW.
binary:crypto-modules-6.0.0-2-arm64-di
On Sunday, 23 October 2022 15:15:36 CEST inasprecali wrote:
> It does not boot at all, I'm unable to SSH into it. It's not
> merely that the display does not work.
Then I'm inclined to think this *is* a separate issue, which is due to the
upgrade to -19, but that you happen to have an AMD GPU
Hi Dan!
Thanks so much for your description, it already gives me some ideas how to
improve things wrt the documentation :-)
On Wednesday, 19 October 2022 23:56:23 CEST Dan Coleman wrote:
> use test-patches in debian/bin/test-patches.
>From bug 1022025:
On Thursday, 20 October 2022 21:48:20
Package: src:linux
Version: 6.0.3-1
Severity: normal
Dear Maintainer,
After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
I believe that the relevant dmesg message is this one, as it is not printed
with the 6.0.0-1 version:
snd_hda_codec_hdmi ehdaudio0D2: failed to create hda
Am 23.10.22 um 14:27 schrieb Diederik de Haas:
On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:
You both have kernel parameters like these. Can you explain why?
I have an AMD GPU on a machine and I have never set parameters like these.
These are parameters for Southern Islands
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Oct 2022 21:05:40 +0200
Source: linux-signed-arm64
Architecture: source
Version: 6.0.3+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
Source: linux
Version: 5.10.140-1
Severity: wishlist
X-Debbugs-Cc: dfo...@gmail.com
Dear maintainers,
please considser building the uleds module (CONFIG_LEDS_USER=m).
The kernel documentation says:
> The uleds driver supports userspace LEDs. This can be useful for testing
> triggers and can
Diederik de Haas writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.
>
> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch
On zondag 23 oktober 2022 19:01:06 CEST Andreas Wirooks wrote:
> Am 23.10.22 um 14:27 schrieb Diederik de Haas:
> > On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote:
> >>> You both have kernel parameters like these. Can you explain why?
> >>> I have an AMD GPU on a machine and I have
Diederik de Haas writes:
> Then I'm inclined to think this *is* a separate issue, which is
> due to the upgrade to -19, but that you happen to have an AMD
> GPU is 'not' relevant.
> I realize it's not what you want, but may result in an useful
> extra data point if you (for this test) switch
Package: src:linux
Version: 6.0.3-1
Severity: important
Hello,
starting with 5.18.0-3-amd64 I experience significant performance loss
(clock speed slows down to 400 MHz) on higher CPU usage.
After checking for differences I figured out that the long-term intel rapl mmio
power limit now defaults
Control: tag -1 upstream
On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote:
> After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
> I believe that the relevant dmesg message is this one, as it is not printed
> with the 6.0.0-1 version:
>
> snd_hda_codec_hdmi
Processing control commands:
> tag -1 upstream
Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade
to 6.0.0-2
Bug #1022558 [src:linux] linux-image-6.0.0-2-amd64: Audio fails to start, but
works with 5.19
Added tag(s) upstream.
Added tag(s) upstream.
--
1022544:
Hi!
On Sun, 23 Oct 2022 23:24:46 +0200 Diederik de Haas
wrote:
>
> On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote:
> > After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore.
> > I believe that the relevant dmesg message is this one, as it is not printed
> > with the
Package: src:linux
Version: 6.0.3-1
Severity: important
X-Debbugs-Cc: lisan...@debian.org
>From dmesg (see below) audio stack fails to be initialized. If I boot
with 5.19 everything works as expected.
[ 36.646398] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI
Hi Again.
This is in kernel bugzilla now:
https://bugzilla.kernel.org/show_bug.cgi?id=216613
Regards,
Daniel.
Package: firmware-misc-nonfree
Version: 20210818-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What
Processing commands for cont...@bugs.debian.org:
> severity 1022544 important
Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade
to 6.0.0-2
Severity set to 'important' from 'normal'
> merge 1022544 1022558
Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more
Revised kernel works for me as well! Thanks everyone for the rapid response.
Package: src:linux
Version: 6.0.2-1+b1
Severity: normal
Tags: patch
X-Debbugs-Cc: t...@seoss.co.uk
Firstly, thanks for the work on the Debian kernel packaging!
Upstream kernel v5.19 incorporated a patch which split out Solarflare
SFC9000 (NIC model SFN5000 and SFN6000 series) driver support from
40 matches
Mail list logo
