Re: IMPORTANT: do NOT upgrade to new stable point release
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 Махно 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 <2695bd53d...@ewoof.net> rašė: > > > > On 11 Dec 2023 11:34 -0500, from g...@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?” > >
Re: IMPORTANT: do NOT upgrade to new stable point release
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 <2695bd53d...@ewoof.net> rašė: > > On 11 Dec 2023 11:34 -0500, from g...@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?” >
Re: IMPORTANT: do NOT upgrade to new stable point release
On 11 Dec 2023 11:34 -0500, from g...@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?”
Re: IMPORTANT: do NOT upgrade to new stable point release
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.
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote: > On Sat, 9 Dec 2023 13:09:23 -0500 > 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- > > > > 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
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sat, 9 Dec 2023 13:09:23 -0500 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- > 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/
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote: > On Sun, Dec 10, 2023, 12:47 PM Curt 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 signature.asc Description: PGP signature
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023, 12:47 PM Curt wrote: > On 2023-12-10, Gary Dale wrote: > > > > On 2023-12-10 12:24, Greg Wooledge wrote: > >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > >>> On 2023-12-10, Andrew M.A. Cater wrote: > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > >>> You mean in the Zulu Time Zone (as I am all at sea)? > >> Use "date -u" to see current UTC time. That should be sufficient to > >> let you know how long it has been since Andrew's "now". > >> > > You're getting too complicated. The date stamp on his e-mail will > > display the correct local time (as you have set it) so I can see that he > > wrote it 30 minutes ago. That relative time is universal across time > zones. > > > > > > 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!! :-) >
Re: IMPORTANT: do NOT upgrade to new stable point release
On 2023-12-10, Gary Dale wrote: > > On 2023-12-10 12:24, Greg Wooledge wrote: >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: >>> On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 >>> You mean in the Zulu Time Zone (as I am all at sea)? >> Use "date -u" to see current UTC time. That should be sufficient to >> let you know how long it has been since Andrew's "now". >> > You're getting too complicated. The date stamp on his e-mail will > display the correct local time (as you have set it) so I can see that he > wrote it 30 minutes ago. That relative time is universal across time zones. > > It is the notion of simultaneity itself (the now of now) that is relative rather than universal.
Re: IMPORTANT: do NOT upgrade to new stable point release
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 ale...@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 (amaca...@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.
Re: IMPORTANT: do NOT upgrade to new stable point release
On 2023-12-10 12:24, Greg Wooledge wrote: On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That should be sufficient to let you know how long it has been since Andrew's "now". You're getting too complicated. The date stamp on his e-mail will display the correct local time (as you have set it) so I can see that he wrote it 30 minutes ago. That relative time is universal across time zones.
Re: IMPORTANT: do NOT upgrade to new stable point release
Andy writes: > This fails with leap seconds, potentially, and also TAI astronomical > time seems to be its own animal. TAI isn't good enough for the astronomers. https://en.wikipedia.org/wiki/Terrestrial_Time -- John Hasler j...@sugarbit.com Elmwood, WI USA
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023 at 05:20:40PM +, Andrew M.A. Cater wrote:
> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> > On 2023-12-10, Andrew M.A. Cater wrote:
> > >
> > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
> >
> > You mean in the Zulu Time Zone (as I am all at sea)?
> >
> > > Andy
> > > (amaca...@debian.org)
> > >
> > >
> >
>
> Not this again :) GMT (was) the world standard reference point from 1884
> and the Washington Conference (or thereabouts).
>
> For most purposes GMT + == UTC (or UCT if you're Francophone) ==
Actually this would be TUC ("Temps universel coordonné), while English
would be CUT, but for once, they compromised on UTC [1] :-)
Cheers
[1] https://fr.wikipedia.org/wiki/UTC
--
t
signature.asc
Description: PGP signature
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That should be sufficient to let you know how long it has been since Andrew's "now".
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? > > > Andy > > (amaca...@debian.org) > > > > > Not this again :) GMT (was) the world standard reference point from 1884 and the Washington Conference (or thereabouts). For most purposes GMT + == UTC (or UCT if you're Francophone) == Zulu time (26 time zones to cope with half hour offsets - ?? go from A-Z??) == "military time" (if you're US military) and quite possibly NATO time. This fails with leap seconds, potentially, and also TAI astronomical time seems to be its own animal. Does this help? Andy (amaca...@debian.org) > >
Re: IMPORTANT: do NOT upgrade to new stable point release
On 2023-12-10, Andrew M.A. Cater wrote: > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? > Andy > (amaca...@debian.org) > >
Re: IMPORTANT: do NOT upgrade to new stable point release
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 ale...@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 (amaca...@debian.org)
Re: IMPORTANT: do NOT upgrade to new stable point release
On 2023-12-09 14:18, Michael Kjörling wrote: On 9 Dec 2023 20:54 +0200, from ale...@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.
Re: IMPORTANT: do NOT upgrade to new stable point release
On 9 Dec 2023, at 19:18, Michael Kjörling wrote: > 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. TSM for this advice. As I'm not used to having to "take great care" like this, I would appreciate confirmation that what I've done is likely to be useful. I've dropped a file into /etc/apt/preferences.d/ containing the following text. Package: linux-image-amd64 Pin: version 6.1.55-1 Pin-Priority: 1100 As I noticed that an upgrade to 6.1.64-1 was also in line for linux-libc-dev, I did the same for this package too. As a result, apt-cache policy is telling me linux-image-amd64: Installed: 6.1.55-1 Candidate: 6.1.55-1 Version table: 6.1.64-1 500 500 https://ftp.debian.org/debian bookworm/main amd64 Packages *** 6.1.55-1 1100 100 /var/lib/dpkg/status 6.1.52-1 500 500 https://security.debian.org/debian-security bookworm-security/main amd64 Packages linux-libc-dev: Installed: 6.1.55-1 Candidate: 6.1.55-1 Version table: 6.1.64-1 500 500 https://ftp.debian.org/debian bookworm/main amd64 Packages *** 6.1.55-1 1100 100 /var/lib/dpkg/status 6.1.52-1 500 500 https://security.debian.org/debian-security bookworm-security/main amd64 Packages Thanks in anticipation of a simple yes or no. Niall O'Reilly
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sat, 9 Dec 2023 19:18:20 + Michael Kjörling <2695bd53d...@ewoof.net> wrote: > On 9 Dec 2023 20:54 +0200, from ale...@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. > It appears from the link in the bug report that 6.5.x kernels (sid/trixie) are not affected. Does anyone know otherwise? https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/ Is the bug likely to affect all architectures? I have a Pi bookworm (armhf) on 6.1.63-1, with 6.1.58-1 also installed. I can probably roll back to 6.1.54-1 if necessary. -- Joe
Re: IMPORTANT: do NOT upgrade to new stable point release
On 9 Dec 2023 14:26 -0500, from g...@wooledge.org (Greg Wooledge): >> If you upgraded this morning, then I would expect that you are okay >> for now. > > That doesn't appear to be true. > >> 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. > > This is the kernel I got this morning: > > ii linux-image-6.1.0-14-amd64 6.1.64-1 amd64Linux 6.1 for 64-bit > PCs (signed) Alexis Grigoriou is in UTC+0200 per the email headers; you are in UTC-0500. Thus "this morning" is 7 hour later for you than for Alexis, only because of that. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: IMPORTANT: do NOT upgrade to new stable point release
Greg Wooledge writes: > On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: >> If you upgraded this morning, then I would expect that you are okay >> for now. > > That doesn't appear to be true. > >> 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. > > This is the kernel I got this morning: > > ii linux-image-6.1.0-14-amd64 6.1.64-1 amd64 Linux 6.1 for 64-bit PCs > (signed) > > This is the current result of looking for a newer one: > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Based on the warnings given here, I rebooted to the prior kernel: > > unicorn:~$ uname -a Linux unicorn 6.1.0-13-amd64 #1 SMP > PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux > > I guess I'll wait and see what happens next. I upgraded some time today to a December kernel. I have now gone back to September 29 kernel. But is there a way to tell what if anything got corrupted? I am using a 32 bit system and ext4. I booted this: 6.1.0-13-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) i686 GNU/Linux then: aptitude remove linux-image-6.1.0-14-686-pae
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: > If you upgraded this morning, then I would expect that you are okay > for now. That doesn't appear to be true. > 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. This is the kernel I got this morning: ii linux-image-6.1.0-14-amd64 6.1.64-1 amd64Linux 6.1 for 64-bit PCs (signed) This is the current result of looking for a newer one: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Based on the warnings given here, I rebooted to the prior kernel: unicorn:~$ uname -a Linux unicorn 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux I guess I'll wait and see what happens next.
Re: IMPORTANT: do NOT upgrade to new stable point release
On 9 Dec 2023 20:54 +0200, from ale...@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. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sat, 2023-12-09 at 13:09 -0500, Dan Ritter wrote: > > > 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. > 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?
Re: IMPORTANT: do NOT upgrade to new stable point release
09.12.23, 19:09 +0100, Dan Ritter: > 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. Thank you very much for the hint, Dan! -- Regards mks
Re: IMPORTANT: do NOT upgrade to new stable point release
Thanks for the tip. I updated this morning well before any announcements and having seen this I rebooted into the 6.1.0-12 (6.1.52) package. Good thing old kernels are kept around. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
