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

Groups > linux.debian.user > #264567

Re: 6.1.0-15/6.1.66-1 broken too?

Cross-posted to 3 groups.

Show all headers | View raw

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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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

csiph-web