Package: src:linux
Version: 6.7.12-1~bpo12+1
X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org
Severity: normal
X-Debbugs-Cc: elb...@debian.org
Hi linux maintainers,
Today I restarted the s390x host of ci.d.n because I lost access. I
inspected the journal and noticed there
Processing commands for cont...@bugs.debian.org:
> tags 1075770 + moreinfo
Bug #1075770 [src:linux] linux-image-6.9.7-amd64: adlp_tc_phy_connect [i915]
fills logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me
Hi,
On 09-07-2024 12:23 p.m., Paul Gevers wrote:
I'll see what I can do.
For the record: I have installed the unstable kernel on one of the
workers (ci-worker-arm64-11 [1]). Let's see how it behaves.
Paul
[1]
https://ci.debian.net/munin/ci-worker-arm64-11/ci-worker-arm64-11/index.html
O
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 13 Jul 2024 17:45:02 +0200
Source: linux-signed-amd64
Architecture: source
Version: 6.9.9+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By:
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 13 Jul 2024 17:45:02 +0200
Source: linux-signed-arm64
Architecture: source
Version: 6.9.9+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By:
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1072004
X-Debbugs-Cc: tj.iam...@proton.me
I've completed 10 successful passes of the autopkgtest reproducer with the
proposed
patch in the kernel bugzilla from Dominique Martinet on current
mainline, so with luck that might squeeze in to 6.1
Processing commands for cont...@bugs.debian.org:
> tags 1075713 + upstream
Bug #1075713 [src:linux] linux: D-I's X fails to start under kvm -vga qxl
Added tag(s) upstream.
> retitle 1075713 linux: Change to firmware fb device parent broke X fbdev
Bug #1075713 [src:linux] linux: D-I's X fails to st
Marek, could this also be the cause of your reported bug?
Am 13.07.24 um 19:20 schrieb Tj:
The recent commits to add the parent device path broke Debian's kvm based QA
workers for testing installer ISOs after a kernel upgrade from v6.8.12 to
v6.9.7. For the details:
https://bugs.debian.org/cg
Package: src:linux
Version: 6.9.9-1
Severity: important
X-Debbugs-Cc: ksyes19...@gmail.com
-- Package-specific info:
** Version:
Linux version 6.9.9-amd64 (debian-kernel@lists.debian.org)
(x86_64-linux-gnu-gcc-13 (Debian 13.3.0-3) 13.3.0, GNU ld (GNU Binutils for
Debian) 2.42.50.20240710) #1
Tj (2024-07-13):
> After reverting the recent sysfb commits:
>
> linux$ git l -n 15
> e932a4281dfd4 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Set
> firmware-framebuffer parent device"
> c16bbb2e6863d 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Create
> firmware device on
Hey Ben.
Nice to see a package for that :-)
On Tue, 2024-06-25 at 00:46 +0200, Ben Hutchings wrote:
> > net.ipv4.conf.all.rp_filter=1
>
> This is (effectively) set to 2 by the new configuration.
Just wondered why not using 1?
AFAIU, the RFC would recommend strict mode (1). Does that break
anyth
Hi
Am 13.07.24 um 19:20 schrieb Tj:
The recent commits to add the parent device path broke Debian's kvm based QA
workers for testing installer ISOs after a kernel upgrade from v6.8.12 to
v6.9.7. For the details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075713
It took some time to
12 matches
Mail list logo
