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

Groups > linux.debian.kernel > #81153 > unrolled thread

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

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: 6.1.0-15/6.1.66-1 broken too? Kevin Price <kp@osnanet.de> - 2023-12-11 00:00 +0100
    Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Salvatore Bonaccorso <carnil@debian.org> - 2023-12-11 12:40 +0100
      Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Salvatore Bonaccorso <carnil@debian.org> - 2023-12-11 19:20 +0100
        Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Jason Zarin <jason@zarin.org> - 2023-12-12 14:00 +0100
    Bug#1057967: linux/6.1.67-1 uploaded addressing #1057967 and #1057969 Salvatore Bonaccorso <carnil@debian.org> - 2023-12-12 15:10 +0100

#81153 — 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] | [next] | [standalone]

#81156 — Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

Control: tags -1 + moreinfo

Hi Kevin,

On Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price wrote:
> Package: linux-image-6.1.0-15-amd64
> Version: 6.1.66-1
> Severity: critical
> Control: -1 notfound 6.1.64-1
> 
> When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
> misbehaves in many ways, rendering it largely unusable. With kernels up
> to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
> this seemed fine.
> 
> Misbehavior includes, not limited to:
> 
> 1. Most actions take considerably longer than usual.
> 
> 2. The GDM greeter has an English keyboard layout, which otherwise is
> German. (Login works.)
> 
> 3. There seems to be no network connectivity. No WiFi icon. "ping
> 8.8.8.8" returns IIRC network unreachable.
> 
> 4. Launching Firefox does apparently nothing.
> 
> 5. Launching gnome-terminal does work, but some basic commands just
> freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
> the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".
> 
> 6. Shutting down takes ages, with systemd waiting for a bunch of
> processes (sudo) and services to terminate, most of the latter seem to
> be somehow network-related, but you tell me which aren't.
> 
> After more that 10 min I used hard power-off, leaving my ext4 dirty, but
> being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
> -13 working properly, and -15 showing the exact same misbehavior
> reproducibly.
> 
> I'll attach all I could get out of reportbug running under 6.1.0-15, and
> please let me know what further testing I may perform IOT help you.
> Please also specify whether you'd like me to do that testing under
> 6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
> will do anything fine.

It still would be helpfull if you can get to the logs of the previous
boot. After booting back in the working kernel, do you have anything
sensible logged in the previous boot log? If so can you share that
please? I'm right now curious to find out if we see the same as
#1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
issue.

Regards,
Salvatore

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

#81165 — Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

Hi,

On Mon, Dec 11, 2023 at 01:27:07PM +0100, Kevin Price wrote:
> Thank you Salvatore!
> 
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> > It still would be helpfull if you can get to the logs of the previous
> > boot. After booting back in the working kernel, do you have anything
> > sensible logged in the previous boot log? If so can you share that
> > please?
> 
> Sure. Here's my boot.log.

I was more interested to get some nformation from the kernel. If you
get dmesg output that would be good, maybe the journalctl from the bug
otherwise, which will help to get more context.

> 
> The first one at "Mon Dec 11 00:54:03 CET 2023" is the faulty 6.1.0-15.
> 
> The 2nd one at "Mon Dec 11 01:13:38 CET 2023" is the working 6.1.0-13.
> 
> Need any more logfiles or testing? I intend to test
> debian-live-12.4.0-amd64-gnome.iso on my computer, IOT rule out any
> local config peculiarities, FWIW.
> 
> > I'm right now curious to find out if we see the same as
> > #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> > cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> > issue.
> 
> Please let me know what kernel version you want me to test, if they're
> provides as debian binaries. I'd be glad to help, probably not only for
> my own sake. Bear with me I'm unwilling to build kernel packages myself,
> due to lack of computing resources. HTH

I have put binary packages for amd64 built in
https://people.debian.org/~carnil/tmp/linux/1057967/

*but* they are completely unofficial builds. To give assurance of
provenance I have generated a sha256sum file as well for the uploaded
files and signed it with my key in the Debian keyring.

If you personal policy allows you to install such packages please test
with those, otherwise we need you to have built your own packages.

Regards,
Salvatore

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

#81184 — Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

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

The test build also works on my system without issues [2010 macbook with
broadcom-sta-dkms driver]

On Mon, Dec 11, 2023 at 4:12 PM Kevin Price <kp@osnanet.de> wrote:

> Breaking news:
>
> Am 11.12.23 um 19:14 schrieb Salvatore Bonaccorso:
> > I have put binary packages for amd64 built in
> > https://people.debian.org/~carnil/tmp/linux/1057967/
>
> I confirm this test kernel is working fine for me, even with non-free
> broadcom-sta.
>
> (sent from
> "
> cat /proc/version
>
> Linux version 6.1.0-0.a.test-amd64 (debian-kernel@lists.debian.org)
> (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian)
> 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1a~test (2023-12-11)
> "
>
> through
>
> "
> modinfo wl
>
> filename:       /lib/modules/6.1.0-0.a.test-amd64/updates/dkms/wl.ko
> license:        MIXED/Proprietary
> alias:          pci:v*d*sv*sd*bc02sc80i*
> depends:        cfg80211
> …"
> )
>
> Thank you Salvatore. Let's get this into stable soon.
> --
> Kevin Price
>

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

#81186 — Bug#1057967: linux/6.1.67-1 uploaded addressing #1057967 and #1057969

Hi

Thanks to all for testing the test build with the one commit revert.

6.1.67-1 is now underway. I will check with stable release managers if
a SUA (update through stable-updates) can be released.

Regards,
Salvatore

[toc] | [prev] | [standalone]

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

csiph-web