Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Geert Stappers
On Wed, Dec 13, 2023 at 06:35:08AM +0100, to...@tuxteam.de wrote:
> On Tue, Dec 12, 2023 at 10:39:55PM -0600, David Wright wrote:
> > On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote:
> > > > Well, the machine in question has a wi-fi but I don't plan on using it.
> > > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > > > enough to trigger the bug.  Please correct me if I'm wrong.
> > > 
> > > "the bug"?
> > > 
> > > What's this bug you're referring to?
> > 
> > Perhaps:
> > 
> >   https://lists.debian.org/debian-user/2023/12/msg00680.html
> > 
> >   https://lists.debian.org/debian-user/2023/12/msg00682.html
> 
> Might be this:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
> 

An attempt to get beyond FUD

|Debian Bug report logs - #1057967
|linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely 
unusable version graph
|Package: src:linux; Maintainer for src:linux is Debian Kernel Team 
;
|Affects: src:broadcom-sta, src:linux, linux-image-6.1.0-15-amd64
|Reported by: Kevin Price
|Date: Mon, 11 Dec 2023 02:03:01 UTC
|Severity: serious
|Tags: confirmed
|Found in version linux/6.1.66-1
|Fixed in version linux/6.1.67-1
|Done: Salvatore Bonaccorso 

> Cheers
> t

Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread tomas
On Tue, Dec 12, 2023 at 10:39:55PM -0600, David Wright wrote:
> On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote:
> > > Well, the machine in question has a wi-fi but I don't plan on using it.
> > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > > enough to trigger the bug.  Please correct me if I'm wrong.
> > 
> > "the bug"?
> > 
> > What's this bug you're referring to?
> 
> Perhaps:
> 
>   https://lists.debian.org/debian-user/2023/12/msg00680.html
> 
>   https://lists.debian.org/debian-user/2023/12/msg00682.html

Might be this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967

Cheers
-- 
t


signature.asc
Description: PGP signature


Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Gareth Evans
Can anyone please explain:

1. Why upgrades of stable into a potentially seriously compromised state were 
allowed to continue, twice, rather than pulling the upgrades? or...

2. Why the best temporary solution isn't to revert the kernel to the last known 
good version so upgrades-other-than-kernel can continue?  There may be some 
versioning jiggery-pokery needed, but doesn't the +deb12xxx (or other) naming 
convention take care of that?  I'm sure I've seen packages previously with 
names like foo-1.3-really-1.2

This really doesn't seem to have been handled well from an official 
mitigation/communication pov.  There only seems to have been a debian-announce 
announcement re 12.3 issues.

I'm inclined to think there must be reasons why things that seem obvious have 
not been done, and keen to understand why, if so.  

Do 1 or 2 above involve disproportionate effort?  Were there 
backwards-incompatible changes to other things (such as filesystems) in the 
latest kernel(s), so reversion = breakage for some upgraded systems unaffected 
by recent issues?

Thanks,
Gareth



Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread David Wright
On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote:
> > Well, the machine in question has a wi-fi but I don't plan on using it.
> > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > enough to trigger the bug.  Please correct me if I'm wrong.
> 
> "the bug"?
> 
> What's this bug you're referring to?

Perhaps:

  https://lists.debian.org/debian-user/2023/12/msg00680.html

  https://lists.debian.org/debian-user/2023/12/msg00682.html

Cheers,
David.



The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Stefan Monnier
> Well, the machine in question has a wi-fi but I don't plan on using it.
> Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> enough to trigger the bug.  Please correct me if I'm wrong.

"the bug"?

What's this bug you're referring to?


Stefan