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 Team
Changed-By: Salvatore Bonaccorso
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 Team
Changed-By: Salvatore Bonaccorso
Your message dated Thu, 27 Oct 2022 06:17:10 +
with message-id
and subject line Bug#1022025: fixed in linux 5.10.149-2
has caused the Debian Bug report #1022025,
regarding regression on amdgpu: drm_kms_helper "flip_done timed out" messages
during boot and console freeze
to be marked as done.
Your message dated Thu, 27 Oct 2022 06:17:10 +
with message-id
and subject line Bug#1022025: fixed in linux 5.10.149-2
has caused the Debian Bug report #1022025,
regarding linux-image-5.10.0-19-amd64: no boot possible
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 27 Oct 2022 06:17:10 +
with message-id
and subject line Bug#1022025: fixed in linux 5.10.149-2
has caused the Debian Bug report #1022025,
regarding Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors
and alike
to be marked as done.
This means that
Your message dated Thu, 27 Oct 2022 06:17:10 +
with message-id
and subject line Bug#1022025: fixed in linux 5.10.149-2
has caused the Debian Bug report #1022025,
regarding linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on
machines with AMD integrated graphics
to be marked as
Your message dated Thu, 27 Oct 2022 06:17:10 +
with message-id
and subject line Bug#1022025: fixed in linux 5.10.149-2
has caused the Debian Bug report #1022025,
regarding Can't enable amdgpu driver in linux-image-5.10.0-19-amd64
to be marked as done.
This means that you claim that the
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Oct 2022 22:24:21 +0200
Source: linux
Architecture: source
Version: 5.10.149-2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 1022025
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 Team
Changed-By: Salvatore Bonaccorso
Package: src:linux
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: je8bn1...@mozmail.com
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
On Thursday, 27 October 2022 15:56:28 CEST Stephan Verbücheln wrote:
> Version: 6.0.3-1
>
> When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep
> failing. With kernel 5.19.x it works on the same machine with the same
> userland.
Can you try whether applying the following patch
Seems I'm not the only one who's quite concerned about the ongoing
security impact of user namspaces, as the recent/current discussion
about some LSM patches for 6.1 shows:
99% of all code does NOT WANT the user namespace thing, and it's been
a big new attack surface for the kernel getting
Your message dated Thu, 27 Oct 2022 14:38:11 +0200
with message-id <2663521.mvXUDI8C0e@bagend>
and subject line Seems to be fixed
has caused the Debian Bug report #1020534,
regarding sgx: EPC section 0x5020-0x55f7 (crash)
to be marked as done.
This means that you claim that the problem
Package: src:linux
Version: 6.0.3-1
When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep
failing. With kernel 5.19.x it works on the same machine with the same
userland.
Hardware: MacBookPro11,1, Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
I am not sure if this app is Apple
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
On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters
wrote:
> Source: linux
> Source-Version: 5.10.149-2
> Done: Salvatore Bonaccorso
>
> We believe that the bug you reported is fixed in the latest
version of
> linux, which is due to be installed in the Debian FTP archive.
I'm sorry, but your
Hi
On Thu, Oct 27, 2022 at 05:21:32PM +, inasprecali wrote:
> On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters
> wrote:
> > Source: linux
> > Source-Version: 5.10.149-2
> > Done: Salvatore Bonaccorso
> >
> > We believe that the bug you reported is fixed in the latest
> version of
> >
On Sun, 23 Oct 2022 10:12:17 +0200 Michael Becker wrote:
> 5.10.149-2 solved the problem
5.10.149-2 was no help with A10-7850K Radeon R7.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y
Package: src:linux
Version: 6.0.3-1
Severity: important
X-Debbugs-Cc: d...@shallowsky.com
Dear Maintainer,
As of a sid full-upgrade two days ago (Tue Oct 25), I'm seeing two
regressions on my Lenovo Carbon X1 gen7:
- systemctl suspend no longer works: instead of suspending, it freezes,
and I
Hi,
On Thu, Oct 27, 2022 at 07:12:43PM +, inasprecali wrote:
> On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso
> wrote:
> > Can you please fill a new bug for your issue, which would still
> > be
> > present in the 5.10.149-2 release? There are two users which
> > report
> > that they
On woensdag 26 oktober 2022 12:43:02 CEST Alexis Huxley wrote:
> Following other reports of post-grub kernel hangs on systems with
> amdgpu, I waited for new release of linux-image-5.10.0-19-amd64,
> which came quickly, but it did not solve the problem for me.
>
> Symptoms are: grub loads kernel
Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso
:
>According to your references there is the workaround of mounting with
>clear_cache,space_cache=v2 and convert the filesystem.
>
>What would one prevent doing so?
v2 space cache is still rather new and had only recently some
Control: severity -1 important
Hi,
On Wed, Oct 26, 2022 at 10:23:35PM +0200, Christoph Anton Mitterer wrote:
> Source: linux
> Version: 5.19.6-1
> Severity: critical
> Justification: breaks the whole system
>
>
> Hi.
>
> 6.0.3 introduced a commit that causes (permanent) CPU soft lockups
> for
Processing control commands:
> severity -1 important
Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting
space cache v1 filesystems
Severity set to 'important' from 'critical'
--
1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> tags 1022848 + fixed-upstream
Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting
space cache v1 filesystems
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso
wrote:
> Can you please fill a new bug for your issue, which would still
> be
> present in the 5.10.149-2 release? There are two users which
> report
> that they still have problems with the amdgpu driver still in
> 5.10.149-2.
I think bug
Processing commands for cont...@bugs.debian.org:
> tags 1022848 + upstream
Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting
space cache v1 filesystems
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1022848:
Hi Alexis,
[Cc'ing Alex Deucher who addressed the previous regressions as well]
On Wed, Oct 26, 2022 at 12:43:02PM +0200, Alexis Huxley wrote:
> Package: src:linux
> Version: 5.10.149-2
> Severity: serious
> Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked
> serious so
Hi All,
> Would you be able to start own kenel builds, confirming it does not
> happen with 5.10.140 upstream but with 5.10.149, and isolate the
> breaking change?
>
> (Are you able to boot the kernel from bullseye-backports?)
I will try to do this, but owing to my schedule, it will
be only
Control: severity -1 serious
Hi Christoph,
Thanks for the quick feedback!
On Thu, Oct 27, 2022 at 09:10:53PM +0200, Christoph Anton Mitterer wrote:
> Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso
> :
> >According to your references there is the workaround of mounting with
>
Processing control commands:
> severity -1 serious
Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting
space cache v1 filesystems
Severity set to 'serious' from 'important'
--
1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> tags 1022848 + pending
Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting
space cache
Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM]
vendor: Dell driver: radeon v: kernel arch: GCN-1 pcie: speed: 2.5 GT/s
lanes: 8 ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0
chip-ID: 1002:6611
Same failure as in my previous comment #45 about GCN2. In Bullseye
Hi,
This is my first bug report, so It seems that I've messed up the message body.
So here it is:
I've been experiencing several issues after upgrading my kernel to
linux-image-6.0.0-2-amd64:
* Suspend to ram no longer works. The screen just turns off, but the PC is
still running.
* The CPU
Processing commands for cont...@bugs.debian.org:
> # unconfuse the BTS
> notfound 924233 2.9.4-4
Bug #924233 {Done: Andrej Shadura } [obs-server]
obs-server: fails to purge: delgroup: `obsservicerun' still has `obsrun' as
their primary group!
No longer marked as found in versions
35 matches
Mail list logo
