Package: src:linux
Version: 5.10.216-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading to linux-image-5.10.0-29 the system fails to boot with
grub 'Error 16: Inconsistent filesystem structure'. Booting into
linux-image-5.10.0-28-amd64
and the system is on
Hi Mark,
On Tuesday, 7 May 2024 19:30:59 CEST Mark Pearson wrote:
> > I already mentioned that MR 85 is a BIG one (but the only one which needs
> > to go through NEW), which in turn means that reviewing takes more then 10
> > minutes (to put it mildly).
> >
> > The updates after that are indicati
On Tue, 7 May 2024 21:01:06 +0200
Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
>
> Hi Tito,
>
> On Tue, May 07, 2024 at 10:19:44AM +0200, Tito Ragusa wrote:
> > Package: src:linux
> > Version: 6.1.90-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> >* What led up to the
Package: src:linux
Version: 6.7.12-1
Severity: normal
Dear Maintainer,
Since upgrading to Linux 6.7.12 from 6.6.15, connecting to WiFi after
waking up
from hibernation fails. The journal lists these kernel errors, I can't
see any
other relevant errors:
Mai 07 16:53:03 kernel: mt7921e :01:00.
Hi,
On Tue, May 07, 2024 at 06:35:06PM +, Kari Lempiäinen wrote:
> Hi,
>
> Looks like this fixed the problem. I ran a couple of backup jobs to
> cifs-mounted shares and no error messages so far. Thanks!
Thanks for the confirmation!
Regards,
Salvatore
Control: tags -1 + moreinfo
Hi Tito,
On Tue, May 07, 2024 at 10:19:44AM +0200, Tito Ragusa wrote:
> Package: src:linux
> Version: 6.1.90-1
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
>Rebooting the box after kernel package upgrade
>
>* What exactly
Processing control commands:
> tags -1 + moreinfo
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs
about br_netfilter and nf_conntrack
Added tag(s) moreinfo.
--
1070685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070685
Debian Bug Tracking System
Contact ow..
Hi,
Looks like this fixed the problem. I ran a couple of backup jobs to
cifs-mounted shares and no error messages so far. Thanks!
Regards,
Kari
From: Salvatore Bonaccorso on behalf of
Salvatore Bonaccorso
Date: Tuesday, 7. May 2024 at 19.01
To: Kari Lempiäinen
Cc: 1069...@bugs.debian.org <
Hi Diederik,
On Tue, May 7, 2024, at 11:17 AM, Diederik de Haas wrote:
> On Tuesday, 7 May 2024 15:49:45 CEST Mark Pearson wrote:
>> > As I see it, the primary problem is the lack of people actively
>> > contributing to the Debian kernel team's work. In general.
>>
>> Interesting read, and combin
Hi,
On Tue, May 07, 2024 at 03:30:58PM +, Kari Lempiäinen wrote:
> Hi,
>
> New kernel 6.1.0-21 seems to be out. Could you verify if this bus is fixed in
> it?
>
> I found from
> https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.90 that
> there is a commit b3686200adba26d
Hi,
New kernel 6.1.0-21 seems to be out. Could you verify if this bus is fixed in
it?
I found from
https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.90 that
there is a commit b3686200adba26dd1f8beee3d9c1b34563db1e65 is that a fix for
this?
Regards,
Kari
From: Salvatore Bon
On Tuesday, 7 May 2024 15:49:45 CEST Mark Pearson wrote:
> > As I see it, the primary problem is the lack of people actively
> > contributing to the Debian kernel team's work. In general.
>
> Interesting read, and combined with my notes to Didier - is this something
> where I and some in my team c
Hi Diederik,
On Tue, May 7, 2024, at 5:22 AM, Diederik de Haas wrote:
> On Tuesday, 7 May 2024 08:25:23 CEST Didier 'OdyX' Raboud wrote:
>> What I did back then to try to help getting the firmware package in better
>> shape was to dive in the (complex) packaging and try to produce "ready-to-
>> me
Hi Didier
On Tue, May 7, 2024, at 2:25 AM, Didier 'OdyX' Raboud wrote:
> Hello there Mark,
>
> thanks for your email, and for the followup ping; weeks are well-filled with
> $job, baby and other involvements.
Congrats! Exciting times (my eldest just passed her driving test last
week...the time
On Tuesday, 7 May 2024 08:25:23 CEST Didier 'OdyX' Raboud wrote:
> What I did back then to try to help getting the firmware package in better
> shape was to dive in the (complex) packaging and try to produce "ready-to-
> merge" merge-requests for new upstream releases, fixes, etc, then pinging
> Be
Package: src:linux
Version: 6.1.90-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Rebooting the box after kernel package upgrade
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing
* What was the outcome of this action
16 matches
Mail list logo
