Am 02.06.2022 23:26, schrieb Markus Kolb:
Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb :
[...]
https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
Control: clone -1 -2
Control: notfound -2 linux/5.17.3-1
Control: retitle -2 linux-image-5.10.0-14-amd64: boot failure in VM after
upgrading from -13
Control: tag -2 moreinfo
On Friday, 3 June 2022 05:35:15 CEST Vicente Olivert Riera wrote:
> Package: src:linux
> Followup-For: Bug #1012210
This
Package: src:linux
Followup-For: Bug #1012210
X-Debbugs-Cc: vincent.olivert.ri...@gmail.com
I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021.
The software I'm using is UTM, which uses QEMU under the hood.
Yesterday I did a system upgrade:
aptitude -y update && aptitude
Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb :
>Because the kernel.org 5.10.113 with my stripped down config is running
>successful,
>I've rebuilt this kernel.org 5.10.113 with the Debian config
>/boot/config-5.10.0-14-amd64 via make oldconfig.
>There are some differences between kernel.org
Am 02.06.2022 17:27, schrieb Ben Hutchings:
On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
there is introduced the kernel config option
INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
but it is not handled anywhere in the code.
It is handled implicitly. When that config symbol is
On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
> In the patches
>
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
>
>
Because the kernel.org 5.10.113 with my stripped down config is running
successful,
I've rebuilt this kernel.org 5.10.113 with the Debian config
/boot/config-5.10.0-14-amd64 via make oldconfig.
There are some differences between kernel.org and Debian in the config,
I've put the config diff
Hi Markus,
On Wednesday, 1 June 2022 17:22:35 CEST Markus Kolb wrote:
> Am 01.06.2022 13:34, schrieb Diederik de Haas:
> > On Wednesday, 1 June 2022 13:23:26 CEST Diederik de Haas wrote:
> >> The current version in Sid/Unstable is 5.17.11-1 and it would be
> >> useful if you could test that as
Am 01.06.2022 13:34, schrieb Diederik de Haas:
On Wednesday, 1 June 2022 13:23:26 CEST Diederik de Haas wrote:
The current version in Sid/Unstable is 5.17.11-1 and it would be
useful if
you could test that as well.
In the screenshot you sent to the bug report, I saw mentions of an USB
hub.
On Wednesday, 1 June 2022 13:23:26 CEST Diederik de Haas wrote:
> The current version in Sid/Unstable is 5.17.11-1 and it would be useful if
> you could test that as well.
In the screenshot you sent to the bug report, I saw mentions of an USB hub.
Could you try to unplug any peripherals that are
Control: found -1 linux/5.17.3-1
On Wednesday, 1 June 2022 12:17:56 CEST Markus Kolb wrote:
> The kernel linux-image-4.19.0-20-amd64 from Buster works.
> This one is used at the moment for reportbug!
>
> But anything from the newer versions hangs during boot.
> I've tried the release kernel of
Package: src:linux
Version: 5.10.113-1
Severity: important
Dear Maintainer,
I've updated an older typewriter computer from Stretch to Buster and
from there to Bullseye.
The kernel linux-image-4.19.0-20-amd64 from Buster works.
This one is used at the moment for reportbug!
But anything from the
12 matches
Mail list logo
