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

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

Bug#1111095: A question.

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

  Bug#1111095: A question. topaze666 <topaze666@gmail.com> - 2025-08-17 11:30 +0200
    Bug#1111095: A question. Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-08-20 10:20 +0200
    Bug#1111095: A question. Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-08-20 10:20 +0200

#88873 — Bug#1111095: A question.

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

Just a little feedback after a few days' "use". Unfortunately, at this
stage, my system is unusable because there are far too many crashes. It's
switching between windows that at some point will inevitably crash the
system.

Question: could using a previous kernel (while keeping the latest official
kernel, with the option of switching from grub), provide a temporary
solution (1), to regain a stable configuration available? I'm talking about
an older kernel officially provided by Trixie.

(1) I'm aware that this kind of bug is often tricky or time-consuming to
fix.

Thank you.

[toc] | [next] | [standalone]

#88935

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

On Wed, Aug 20, 2025 at 10:14:11AM +0200, Uwe Kleine-König wrote:
> Control: tag -1 + moreinfo
> 
> Hello,
> 
> On Sun, Aug 17, 2025 at 11:19:19AM +0200, topaze666 wrote:
> > Just a little feedback after a few days' "use". Unfortunately, at this
> > stage, my system is unusable because there are far too many crashes. It's
> > switching between windows that at some point will inevitably crash the
> > system.
> > 
> > Question: could using a previous kernel (while keeping the latest official
> > kernel, with the option of switching from grub), provide a temporary
> > solution (1), to regain a stable configuration available? I'm talking about
> > an older kernel officially provided by Trixie.
> > 
> > (1) I'm aware that this kind of bug is often tricky or time-consuming to
> > fix.
> 
> The most time-consuming task is on determining the culprit and you're in
> the best position to debug that.
> 
> There are many kernel packages available at
> https://snapshot.debian.org/package/linux/, can you do a package
> bisection and pinpoint the oldest kernel that has this issue? (That is,
> pick a kernel somewhat in the middle between 6.1 (from bookworm, good)
> and 6.12 (from trixie, bad), say 6.7-1 and test that. Depending on
> the result, continue to search between 6.1 and 6.7-1 (if 6.7-1 is
> bad) or 6.7-1 and 6.12 (if 6.7-1 still works). Tell us if you need more
> guidance here.
> 
> Make sure to uninstall the old kernels at the end to not be exposed to
> security issues that are already fixed in later kernels.

Another thing you can test is installing a 6.16 kernel from
experimental.

Best regards
Uwe

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

#88936

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

Control: tag -1 + moreinfo

Hello,

On Sun, Aug 17, 2025 at 11:19:19AM +0200, topaze666 wrote:
> Just a little feedback after a few days' "use". Unfortunately, at this
> stage, my system is unusable because there are far too many crashes. It's
> switching between windows that at some point will inevitably crash the
> system.
> 
> Question: could using a previous kernel (while keeping the latest official
> kernel, with the option of switching from grub), provide a temporary
> solution (1), to regain a stable configuration available? I'm talking about
> an older kernel officially provided by Trixie.
> 
> (1) I'm aware that this kind of bug is often tricky or time-consuming to
> fix.

The most time-consuming task is on determining the culprit and you're in
the best position to debug that.

There are many kernel packages available at
https://snapshot.debian.org/package/linux/, can you do a package
bisection and pinpoint the oldest kernel that has this issue? (That is,
pick a kernel somewhat in the middle between 6.1 (from bookworm, good)
and 6.12 (from trixie, bad), say 6.7-1 and test that. Depending on
the result, continue to search between 6.1 and 6.7-1 (if 6.7-1 is
bad) or 6.7-1 and 6.12 (if 6.7-1 still works). Tell us if you need more
guidance here.

Make sure to uninstall the old kernels at the end to not be exposed to
security issues that are already fixed in later kernels.

Best regards
Uwe

[toc] | [prev] | [standalone]

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

csiph-web