On Tue, Jan 17, 2023 at 7:17 AM Andreas Gerstmayr wrote:
>
> On 12.01.23 23:00, Ian Rogers wrote:
> > Currently flame graph generation requires a d3-flame-graph template to
> > be installed. Unfortunately this is hard to come by for things like
> > Debian [1]. If the template isn't installed then
Currently flame graph generation requires a d3-flame-graph template to
be installed. Unfortunately this is hard to come by for things like
Debian [1]. If the template isn't installed then ask if it should be
downloaded from jsdelivr CDN. The downloaded HTML file is validated
against an md5sum. If
Processing control commands:
> found -1 6.1.6-1
Bug #1029046 [src:linux] Wayland session doesn't get back to life post-suspend
The source 'linux' and version '6.1.6-1' do not appear to match any binary
packages
Marked as found in versions linux/6.1.6-1.
> found -1 6.1.4-1
Bug #1029046
Control: found -1 6.1.6-1
Control: found -1 6.1.4-1
Control: severity -1 serious
Hello there,
Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> > This is on 6.1.4-1a~test, patched against the "2nd
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 1027483 + pending
Bug #1027483 [src:linux] linux-image-5.10.0-20-amd64: sound with
firmware-sof-intel on
On Tue, 17 Jan 2023 at 20:49, Cyril Brulebois wrote:
>
> Hi folks,
>
> First off: sorry I haven't been able to work on this sooner. For some
> context, you can check the notes for the meeting I had with Steve
> after the GR result was published:
>
Hi folks,
First off: sorry I haven't been able to work on this sooner. For some
context, you can check the notes for the meeting I had with Steve
after the GR result was published:
https://lists.debian.org/debian-boot/2022/10/msg00044.html
This mail is about moving packages from non-free to
Hi,
On 17-01-2023 07:14, Salvatore Bonaccorso wrote:
I will bite the bullet (taking full responsibility for it if
necessary, don't blame the other kernel team members) and ask here now
the release team: Can we let linux 6.1.4-1 despite the RC bug
reported, migrate to testing, so we can move on
Hi Randy,
Please let me know if you are available for the given position:-
Position:- Program/Project Manager with Sustainability
Location:- Seattle, WA – remote must be able to work PST
Duration:- 12+months
* Support the visualization and reporting of enterprise wide Sustainability
Hi,
Sorry - can this be closed please.
I am going to diplomatically say that a network engineer suffered a failure
between mouse and keyboard - who did not appreciate that /etc/fstab is an
integral part of the system boot process.
My apologies if this has wasted anyone's time.
Kind regards
On Tue, 17 Jan 2023 15:59:51 +0100 Diederik de Haas
wrote:
> What was the latest 5.10.x kernel which did boot correctly? Reboot-
This will (or should) have been the 5.10.0-20 kernel as a post installation
reboot due to either new kernel or package dependency trigger indicated in
On 12.01.23 23:00, Ian Rogers wrote:
Currently flame graph generation requires a d3-flame-graph template to
be installed. Unfortunately this is hard to come by for things like
Debian [1]. If the template isn't installed then ask if it should be
downloaded from jsdelivr CDN. The downloaded HTML
Processing control commands:
> tag -1 moreinfo
Bug #1029080 [src:linux] linux-image-5.10.0-20-amd64: Boot failure "PM: Image
not found (code -22)" where power management is NOT used
Added tag(s) moreinfo.
--
1029080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029080
Debian Bug Tracking
Control: tag -1 moreinfo
On Tuesday, 17 January 2023 14:20:19 CET Claire Osborne wrote:
> Booting in recovery mode on 5.10.0.20 also failed
>
> I have fallen back to the previously installed kernel 5.10.19 - with the
> same effect.
>
> Booting in recovery mode on 5.10.0.19 also fails.
What was
Hi OdyX,
On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> light up", so feel free to close the bug; I'll test if I get the same
> symptoms on an unpatched kernel anyway :-)
If this issue doesn't occur
Processing commands for cont...@bugs.debian.org:
> reassign 1029063 dkms
Bug #1029063 [src:linux] reportbug: linux-image-6.0.0-6-amd64 remains
unconfigured because of errors
Bug reassigned from package 'src:linux' to 'dkms'.
No longer marked as found in versions linux/6.0.12-1.
Ignoring request
Hello Salvatore,
17 janvier 2023 07:14 "Salvatore Bonaccorso" a écrit:
> I will bite the bullet (taking full responsibility for it if
> necessary, don't blame the other kernel team members) and ask here now
> the release team: Can we let linux 6.1.4-1 despite the RC bug
> reported, migrate to
Control: reassign -1 dkms - breaks kernel installation
Control: severity -1 grave
On Tue, Jan 17, 2023 at 09:36:26AM +0100, Stefano Simonucci wrote:
> Package: src:linux
> Version: 6.0.12-1
> Severity: critical
> Justification: breaks the whole system
No, it does not. The kernel is the system
Processing control commands:
> reassign -1 dkms - breaks kernel installation
Unknown command or malformed arguments to command.
> severity -1 grave
Bug #1029063 [src:linux] reportbug: linux-image-6.0.0-6-amd64 remains
unconfigured because of errors
Severity set to 'grave' from 'critical'
--
Hi all,
I'm trying to update the driver for our Intel C62x Chipset QuickAssist
Technology add-on card, but getting the mentioned errors when I try to load the
modules. I haven't done this in a while, but I thought the process was pretty
straightforward:
1. Stop the QAT services [ ok ]
2.
Package: src:linux
Version: 6.1.4-1
Followup-For: Bug #1028451
X-Debbugs-Cc: vent...@debian.org
Dear Maintainer,
I can confirm this bug on my Lenovo T14s with integrated AMD graphics. I have
two monitors connected via docking station. One Display Port the other one via
HDMI, since 6.1 only one
Package: src:linux
Version: 6.0.12-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
in the last upgrade I got this errors:
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.0.0-6-amd64 all
KERNEL_SRC=/lib/modules/6.0.0-6-amd64/build...(bad exit status:
22 matches
Mail list logo
