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
Changes
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
Change
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
Change
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
Cha
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 yo
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 d
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 don
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 proble
Here we go, another one, it seems:
CVE-2022-2588 (https://seclists.org/oss-sec/2022/q3/115)
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:
https://lwn.net/ml/linux-kernel
Processing control commands:
> forwarded -1
> https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/T/#u
Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as
dom0
Bug #1022126 [src:linux] mpt3sas broken with xen dom0
Changed Bug forwarded-to-address to
'http
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/T/#u
On donderdag 27 oktober 2022 00:21:32 CEST you wrote:
> Control: forwarded -1 1022...@bugs.debian.org
Pfft *facepalm*
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> forwarded -1 1022...@bugs.debian.org
Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as
dom0
Bug #1022126 [src:linux] mpt3sas broken with xen dom0
Set Bug forwarded-to-address to '1022...@bugs.debian.org'.
Set Bug forwarded-to-address to
Control: forwarded -1 1022...@bugs.debian.org
Control: tag -1 -moreinfo
On woensdag 26 oktober 2022 23:57:05 CEST Debian Bug Tracking System wrote:
> Unset Bug forwarded-to-address
Oeps
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> forcemerge -1 1022126
Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as
dom0
Bug #1022126 [src:linux] mpt3sas broken with xen dom0
Unset Bug forwarded-to-address
Added tag(s) moreinfo.
Merged 1022126 1022268
--
1022126: https://bugs.d
Control: forcemerge -1 1022126
On woensdag 26 oktober 2022 18:18:28 CEST Daniel Smolik wrote:
> Hi, I have normal boot with 5.10-18 see attached dmesg. And 2
> screenshots with boot failure under 5.10.-19.
I was pretty certain I had heard of such an issue before, but couldn't find it.
Until just
We had have Problems with 5.10.0.19 (149-1) and all AMD-Computers with
onboard graphics.
Update 149-2 had solved on most computers, but this computer has shows
blankscreen a boot...
I have remove boot-option amdgpu.dc=1, since this change 149-2 works.
What has changed between 5.10.0.18 and 5
Processing control commands:
> retitle -1 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1
> filesystems
Bug #1022848 [src:linux] linux: 6.0.5 fixes critical btrfs bug
Changed Bug title to '6.0.5 fixes critical btrfs bug in 6.0.3, affecting space
cache v1 filesystems' from 'linu
Control: retitle -1 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space
cache v1 filesystems
Control: notfound -1 5.19.6-1
Control: found -1 6.0.3-1
No idea why reportbug picked 5.19.6, which I have not even installed
anymore... o.O
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 some people with btrfs filesystems, effectively breaking the
system, e.g. when booting.
See e.g.
https://lore.kernel.org/linux-btr
Processing control commands:
> reassign -1 src:linux
Bug #1022170 [preempt_rt] Excessive network latency with PREEMPT_RT
Warning: Unknown package 'preempt_rt'
Bug reassigned from package 'preempt_rt' to 'src:linux'.
Ignoring request to alter found versions of bug #1022170 to the same values
previ
Package: src:linux
Version: 5.10.149-2
Severity: important
Tags: upstream
-- Package-specific info:
** Kernel log: boot messages should be attached
[ 166.804963] md0: detected capacity change from 0 to 12001828929536
[ 272.116656] sd 3:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_OK
driv
Package: firmware-iwlwifi
Version: 20210818-1
Severity: important
X-Debbugs-Cc: zhengyi...@outlook.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 (o
https://salsa.debian.org/kernel-team/linux/-/merge_requests/563
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos?
⠈⠳⣄
Package: nfs-kernel-server
Version: 1:1.3.4-6
Severity: wishlist
Dear Maintainer,
I needed a way to have rpc.nfsd bind to a specific IP address.
The man page for rpc.nfsd documents a parameter exactly for this, plus some
others.
At first signt, it seems that there is no Debian way to pass para
the kernel command line is:
sugo$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.10.0-18-amd64 root=/dev/mapper/vg0-root ro ipv6.disable=1
amdgpu.dc=0 swapaccount=1
sugo$
where obviously 18 is 19 when booting the bad kernel.
Package: src:linux
Version: 5.10.149-2
Severity: serious
Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked
serious so this marked serious too
Dear Maintainer,
Following other reports of post-grub kernel hangs on systems with
amdgpu, I waited for new release of linux-imag
27 matches
Mail list logo
