Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #264482 > unrolled thread

IMPORTANT: do NOT upgrade to new stable point release

Back to article view | Back to linux.debian.user

Contents

  IMPORTANT: do NOT upgrade to new stable point release Dan Ritter <dsr@randomstring.org> - 2023-12-09 19:30 +0100
    Re: IMPORTANT: do NOT upgrade to new stable point release Nate Bargmann <n0nb@n0nb.us> - 2023-12-09 19:50 +0100
    Re: IMPORTANT: do NOT upgrade to new stable point release Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2023-12-09 20:00 +0100
    Re: IMPORTANT: do NOT upgrade to new stable point release Alexis Grigoriou <alexis@nanoid.net> - 2023-12-09 20:10 +0100
      Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-09 20:20 +0100
        Re: IMPORTANT: do NOT upgrade to new stable point release Greg Wooledge <greg@wooledge.org> - 2023-12-09 20:30 +0100
          Re: IMPORTANT: do NOT upgrade to new stable point release Richmond <dnomhcir@gmx.com> - 2023-12-09 21:00 +0100
          Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-09 21:00 +0100
        Re: IMPORTANT: do NOT upgrade to new stable point release Joe <joe@jretrading.com> - 2023-12-09 22:20 +0100
        Re: IMPORTANT: do NOT upgrade to new stable point release "Niall O'Reilly" <niall+lists@no8.be> - 2023-12-10 17:00 +0100
        Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 18:00 +0100
          Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 18:00 +0100
            Re: IMPORTANT: do NOT upgrade to new stable point release Curt <curty@free.fr> - 2023-12-10 18:10 +0100
              Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 18:30 +0100
                Re: IMPORTANT: do NOT upgrade to new stable point release <tomas@tuxteam.de> - 2023-12-10 18:30 +0100
                Re: IMPORTANT: do NOT upgrade to new stable point release John Hasler <john@sugarbit.com> - 2023-12-10 18:40 +0100
              Re: IMPORTANT: do NOT upgrade to new stable point release Greg Wooledge <greg@wooledge.org> - 2023-12-10 18:30 +0100
                Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 19:00 +0100
                  Re: IMPORTANT: do NOT upgrade to new stable point release Curt <curty@free.fr> - 2023-12-10 19:50 +0100
                    Re: IMPORTANT: do NOT upgrade to new stable point release Nicholas Geovanis <nickgeovanis@gmail.com> - 2023-12-10 20:40 +0100
                      Re: IMPORTANT: do NOT upgrade to new stable point release <tomas@tuxteam.de> - 2023-12-10 20:50 +0100
            Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-10 19:30 +0100
    6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-10 20:20 +0100
      Re: 6.1.0-15/6.1.66-1 broken too? "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 20:30 +0100
        Re: 6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-11 00:00 +0100
          Re: 6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-11 12:20 +0100
    Re: IMPORTANT: do NOT upgrade to new stable point release Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 22:30 +0100
      Re: IMPORTANT: do NOT upgrade to new stable point release "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 22:50 +0100
    Re: IMPORTANT: do NOT upgrade to new stable point release Gary Dale <gary@extremeground.com> - 2023-12-11 17:40 +0100
      Re: IMPORTANT: do NOT upgrade to new stable point release Махно <mindaugasceliesius@gmail.com> - 2023-12-11 17:50 +0100
      Re: IMPORTANT: do NOT upgrade to new stable point release Махно <mindaugasceliesius@gmail.com> - 2023-12-11 17:50 +0100
      Re: IMPORTANT: do NOT upgrade to new stable point release Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-11 17:50 +0100

Page 2 of 2 — ← Prev page 1 [2]

#264554

[Multipart message — attachments visible in raw view] — view raw

On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote:
> On Sun, Dec 10, 2023, 12:47 PM Curt <curty@free.fr> wrote:
[...]

> > It is the notion of simultaneity itself (the now of now) that is
> > relative rather than universal.
> >
> 
> I thought metaphysics was off-topic for this group. Moderators!! :-)

Hold on. Since Einstein this is plain old boring physics ;-P

Cheers
-- 
t

[toc] | [prev] | [next] | [standalone]

#264546

On 2023-12-10 11:56, Andrew M.A. Cater wrote:
> On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
>> On 2023-12-09 14:18, Michael Kjörling wrote:
>>> On 9 Dec 2023 20:54 +0200, from alexis@nanoid.net (Alexis Grigoriou):
>>>> I just upgraded to Bookworm this morning. I did reboot a couple of
>>>> times but there seems to be no problem (yet). Is there anything I
>>>> should look for or do other than rebooting?
>>> If you upgraded this morning, then I would expect that you are okay
>>> for now.
>>>
>>> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>>> the bug is present in kernel Debian package version 6.1.64-1. If you
>>> are on 6.1.55-1 (current Bookworm stable per last night) you _likely_
>>> aren't affected. If you are on 6.1.55-1 (or earlier), just hold off on
>>> upgrades for now; and if you need to upgrade something else, take
>>> great care for now to ensure that no Linux kernel packages get
>>> upgraded to any version < 6.1.66, and preferably not < 6.1.66-1.
>>>
>>> For versions, check:
>>>
>>> * uname -v
>>> * dpkg -l linux-image-\*
>>>
>>> In that bug report thread, #21 lists 6.1.66 as fixed upstream, and #28
>>> indicates that 6.1.66-1 includes the fix from upstream, and that it is
>>> being published.
>>>
>> Any idea when the fixed version will hit stable? With headless servers, it's
>> a pain to downgrade to a previous kernel version.
>>
> Give them a little while: release team are working on it right now as I type
>
> I'm fairly sure they're pushing it out more or less immediately once they're
> sure that it's built correctly and synced to all the appropriate places to
> be further synced to mirrors
>
> "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>
> Andy
> (amacater@debian.org)
>
Thanks. I logged into each of my headless servers and removed the 
problematic kernel then rebooted them so they are all at 6.1.0-13 now.

[toc] | [prev] | [next] | [standalone]

#264550 — 6.1.0-15/6.1.66-1 broken too?

Am 09.12.23 um 19:09 schrieb Dan Ritter:
> The new kernel release is reported to contain an ext4 data
> corruption bug. It's prudent not to upgrade, or if you have
> started to upgrade, not to reboot, until a new kernel release
> is prepared.

Thanks for your announcement. I'm running out of time to properly report
a bug against 6.1.66-1.

#1057843 states that it's fixed with 6.1.0-15/6.1.66-1. This I highly
doubt. I handpicked that version from
https://deb.debian.org/debian/pool/main/l/ , and installed the 6.1.66-1
packages[1]. That was totally messed up and made my amd64 system highly
unresponsive and erratic to the point it would hang shutting down. So I
booted back into 6.1.0-13, which still works fine, and purged 6.1.0-14
and 6.1.0-15, and IOT have two working options, I reinstalled 6.0.1-12,
which had been autoremoved with the update.

[1] Packages I used:

[src:linux]
linux-compiler-gcc-12-x86_6.1.55-1_amd64.deb
linux-headers-6.1.0-13-amd64_6.1.55-1_amd64.deb
linux-headers-6.1.0-13-common_6.1.55-1_all.deb
linux-kbuild-6.1_6.1.55-1_amd64.deb
linux-libc-dev_6.1.55-1_amd64.deb

[src:linux-signed-amd64]
linux-headers-amd64_6.1.55-1_amd64.deb (optional meta-pkg)
linux-image-6.1.0-13-amd64_6.1.55-1_amd64.deb
linux-image-amd64_6.1.55-1_amd64.deb (optional meta-pkg)

Other versions I tried:
6.1.0-12/6.1.52-1 works
6.1.0-13/6.1.55-1 works
6.1.0-14/6.1.64-1 broken, according to #1057843
6.1.0-15/6.1.66-1 broken as experienced

For now, I've purged the broken ones, and put the working ones on hold
with dpkg.

Any ideas?
-- 
Kevin Price

[toc] | [prev] | [next] | [standalone]

#264551 — Re: 6.1.0-15/6.1.66-1 broken too?

On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote:
> Am 09.12.23 um 19:09 schrieb Dan Ritter:
> > The new kernel release is reported to contain an ext4 data
> > corruption bug. It's prudent not to upgrade, or if you have
> > started to upgrade, not to reboot, until a new kernel release
> > is prepared.
> 
> Thanks for your announcement. I'm running out of time to properly report
> a bug against 6.1.66-1.
> 
> #1057843 states that it's fixed with 6.1.0-15/6.1.66-1. This I highly
> doubt. I handpicked that version from
> https://deb.debian.org/debian/pool/main/l/ , and installed the 6.1.66-1
> packages[1]. That was totally messed up and made my amd64 system highly
> unresponsive and erratic to the point it would hang shutting down. So I
> booted back into 6.1.0-13, which still works fine, and purged 6.1.0-14
> and 6.1.0-15, and IOT have two working options, I reinstalled 6.0.1-12,
> which had been autoremoved with the update.
> 
> [1] Packages I used:
> 
> [src:linux]
> linux-compiler-gcc-12-x86_6.1.55-1_amd64.deb
> linux-headers-6.1.0-13-amd64_6.1.55-1_amd64.deb
> linux-headers-6.1.0-13-common_6.1.55-1_all.deb
> linux-kbuild-6.1_6.1.55-1_amd64.deb
> linux-libc-dev_6.1.55-1_amd64.deb
> 
> [src:linux-signed-amd64]
> linux-headers-amd64_6.1.55-1_amd64.deb (optional meta-pkg)
> linux-image-6.1.0-13-amd64_6.1.55-1_amd64.deb
> linux-image-amd64_6.1.55-1_amd64.deb (optional meta-pkg)
> 
> Other versions I tried:
> 6.1.0-12/6.1.52-1 works
> 6.1.0-13/6.1.55-1 works
> 6.1.0-14/6.1.64-1 broken, according to #1057843
> 6.1.0-15/6.1.66-1 broken as experienced
> 
> For now, I've purged the broken ones, and put the working ones on hold
> with dpkg.
> 
> Any ideas?
> -- 
> Kevin Price
>

If you hand-picked packages: I would suggest using apt to upgrade the whole
system . 

For anybody who followed my initially erroneous advice to remove
linux-image-amd64 - installing that package should pull in 6.1.0-15
correctly as a dependency.

Kevin: Do you have any logs to show brokenness? For what it's worth,
there were other updates and fixes besides just #1057843 in the new
release.

With every good wish, as ever,

Andy
[amacater@debian.org]

[toc] | [prev] | [next] | [standalone]

#264567 — Re: 6.1.0-15/6.1.66-1 broken too?

I confirm that 6.1.66-1 (6.1.0-15) severely breaks my
amd64/bookworm/gnome physical machine, which runs fine with 6.1.52-1 and
6.1.55-1.

Am 10.12.23 um 20:24 schrieb Andrew M.A. Cater:
> On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote:
>> Am 09.12.23 um 19:09 schrieb Dan Ritter:
>>> The new kernel release is reported to contain an ext4 data
>>> corruption bug. It's prudent not to upgrade, or if you have
>>> started to upgrade, not to reboot, until a new kernel release
>>> is prepared.
>>
>> Thanks for your announcement. I'm running out of time to properly report
>> a bug against 6.1.66-1.
>>
>> #1057843 states that it's fixed with 6.1.0-15/6.1.66-1. This I highly
>> doubt. I handpicked that version from
>> https://deb.debian.org/debian/pool/main/l/ , and installed the 6.1.66-1
>> packages[1]. That was totally messed up and made my amd64 system highly
>> unresponsive and erratic to the point it would hang shutting down. So I
>> booted back into 6.1.0-13, which still works fine, and purged 6.1.0-14
>> and 6.1.0-15, and IOT have two working options, I reinstalled 6.0.1-12,
>> which had been autoremoved with the update.
>>
>> [1] Packages I used:
>>
>> [src:linux]
>> linux-compiler-gcc-12-x86_6.1.55-1_amd64.deb
>> linux-headers-6.1.0-13-amd64_6.1.55-1_amd64.deb
>> linux-headers-6.1.0-13-common_6.1.55-1_all.deb
>> linux-kbuild-6.1_6.1.55-1_amd64.deb
>> linux-libc-dev_6.1.55-1_amd64.deb
>>
>> [src:linux-signed-amd64]
>> linux-headers-amd64_6.1.55-1_amd64.deb (optional meta-pkg)
>> linux-image-6.1.0-13-amd64_6.1.55-1_amd64.deb
>> linux-image-amd64_6.1.55-1_amd64.deb (optional meta-pkg)
>>
>> Other versions I tried:
>> 6.1.0-12/6.1.52-1 works
>> 6.1.0-13/6.1.55-1 works
>> 6.1.0-14/6.1.64-1 broken, according to #1057843
>> 6.1.0-15/6.1.66-1 broken as experienced
>>
>> For now, I've purged the broken ones, and put the working ones on hold
>> with dpkg.
>>
>> Any ideas?
>> -- 
>> Kevin Price
>>
> 
> If you hand-picked packages: I would suggest using apt to upgrade the whole
> system .

Done that, now that 6.1.0-15/6.1.66-1 is available through apt.

> Kevin: Do you have any logs to show brokenness?

Which ones?

> For what it's worth,
> there were other updates and fixes besides just #1057843 in the new
> release.

Some of that must be the culprit, breaking my system.

What happens, at a first glance:

1. Bootup to the gdm greeter works, but there I get an unusal keyboard
layout. And everything takes longer.

2. There seems to be no network connectivity. (no WiFi icon)

3. Launching Firefox apparently does nothing.

4. Launching gnome-teminal works, but many commands just stall, such as
"sudo dmesg" or "ip a".

5. Shutting down takes ages, with systemd waiting for a bunch of
services to terminate, most of which seem to be network-related. After
much more that 10 min I used hard power-off.

I'm uncertain whether such an unstable system is even capable of going
through the reportbug script. Any ideas, which logfiles might be useful
to debug this issue, and whom to address this to, IOT to prevent similar
experiences from many more users?

Also what kind of testing could I usefully perform? Any kernel
parameters maybe?
-- 
Kevin Price

[toc] | [prev] | [next] | [standalone]

#264595 — Re: 6.1.0-15/6.1.66-1 broken too?

Please see https://bugs.debian.org/1057967 for follow-up.

Am 11.12.23 um 06:21 schrieb Stephan Verbücheln:
[...]
> My hardware is a 2014 Macbook Pro (Intel CPU and graphics).

Stephan and all, would you please post your information there? TIA
-- 
Kevin Price

[toc] | [prev] | [next] | [standalone]

#264564

On Sat, 9 Dec 2023 13:09:23 -0500
Dan Ritter <dsr@randomstring.org> wrote:

> https://fulda.social/@Ganneff/111551628003050712
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
> 
> The new kernel release is reported to contain an ext4 data
> corruption bug. It's prudent not to upgrade, or if you have
> started to upgrade, not to reboot, until a new kernel release
> is prepared.
> 
> 
> -dsr-
> 

It appears the new, repaired, kernel and minor version of Bookworm have
landed. Now, who wants to live dangerously? :-)

root@tiassa:~# apt update
Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 Packages [8,787 kB]
Get:4 http://deb.debian.org/debian bookworm/main Translation-en [6,109 kB]
Fetched 15.1 MB in 3s (4,432 kB/s)                                 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
38 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.3' to '12.4'
root@tiassa:~# apt list --upgradable
Listing... Done
…
libudev1/stable 252.19-1~deb12u1 amd64 [upgradable from: 252.17-1~deb12u1]
linux-image-amd64/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1]
linux-libc-dev/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1]
…
root@tiassa:~# 


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#264565

On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote:
> On Sat, 9 Dec 2023 13:09:23 -0500
> Dan Ritter <dsr@randomstring.org> wrote:
> 
> > https://fulda.social/@Ganneff/111551628003050712
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
> > 
> > The new kernel release is reported to contain an ext4 data
> > corruption bug. It's prudent not to upgrade, or if you have
> > started to upgrade, not to reboot, until a new kernel release
> > is prepared.
> > 
> > 
> > -dsr-
> > 
> 
> It appears the new, repaired, kernel and minor version of Bookworm have
> landed. Now, who wants to live dangerously? :-)
> 
> root@tiassa:~# apt update
> Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
> Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
> Get:3 http://deb.debian.org/debian bookworm/main amd64 Packages [8,787 kB]
> Get:4 http://deb.debian.org/debian bookworm/main Translation-en [6,109 kB]
> Fetched 15.1 MB in 3s (4,432 kB/s)                                 
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> 38 packages can be upgraded. Run 'apt list --upgradable' to see them.
> N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.3' to '12.4'
> root@tiassa:~# apt list --upgradable
> Listing... Done
> …
> libudev1/stable 252.19-1~deb12u1 amd64 [upgradable from: 252.17-1~deb12u1]
> linux-image-amd64/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1]
> linux-libc-dev/stable 6.1.66-1 amd64 [upgradable from: 6.1.55-1]
> …
> root@tiassa:~# 
> 
> 
> -- 
> Does anybody read signatures any more?
> 
> https://charlescurley.com
> https://charlescurley.com/blog/
>

I'd suggest apt-get update ; apt-get dist-upgrade or equivalent.

There were a few other bug fixes as well in this point release but I 
think you've got the three major packages that changed.

Base files also changed, obviously :) 

All the very best, as ever,

Andy

[toc] | [prev] | [next] | [standalone]

#264643

On 2023-12-09 13:09, Dan Ritter wrote:
>
> https://fulda.social/@Ganneff/111551628003050712
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>
> The new kernel release is reported to contain an ext4 data
> corruption bug. It's prudent not to upgrade, or if you have
> started to upgrade, not to reboot, until a new kernel release
> is prepared.
>
>
> -dsr-
>
Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I 
assume this is the fixed version.

[toc] | [prev] | [next] | [standalone]

#264644

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and
no problems!

2023-12-11, pr, 18:47 Махно <mindaugasceliesius@gmail.com> rašė:
>
> I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and
> no problems!
>
>
> 2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d63c@ewoof.net> rašė:
> >
> > On 11 Dec 2023 11:34 -0500, from gary@extremeground.com (Gary Dale):
> > > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume
> > > this is the fixed version.
> >
> > It certainly should be, but some people have reported other issues
> > with the new 12.4 upgrade. See other recent posts to this list.
> >
> > --
> > Michael Kjörling                     🔗 https://michael.kjorling.se
> > “Remember when, on the Internet, nobody cared that you were a dog?”
> >

[toc] | [prev] | [next] | [standalone]

#264645

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and
no problems!


2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d63c@ewoof.net> rašė:
>
> On 11 Dec 2023 11:34 -0500, from gary@extremeground.com (Gary Dale):
> > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume
> > this is the fixed version.
>
> It certainly should be, but some people have reported other issues
> with the new 12.4 upgrade. See other recent posts to this list.
>
> --
> Michael Kjörling                     🔗 https://michael.kjorling.se
> “Remember when, on the Internet, nobody cared that you were a dog?”
>

[toc] | [prev] | [next] | [standalone]

#264646

On 11 Dec 2023 11:34 -0500, from gary@extremeground.com (Gary Dale):
> Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume
> this is the fixed version.

It certainly should be, but some people have reported other issues
with the new 12.4 upgrade. See other recent posts to this list.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web