mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dave Hansen <dave.hansen@intel.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com
Subject: Re: 6.16-rcX: crashing way too often on thinkpad X220
Date: Wed, 23 Jul 2025 22:35:14 +0200	[thread overview]
Message-ID: <aIFHgit57Uc4BDiy@duo.ucw.cz> (raw)
In-Reply-To: <c99e3b89-0b46-4803-997c-e6634268bcd8@intel.com>

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

Hi!

> >> I have had 4th or so crash with 6.16. That's not usual.
> > Two more crashes today. Last one was with 6.16-rc7+.
> > 
> > Ideas welcome,
> 
> Still nothing in the logs?
> 
> The age old idea of getting console and trying to capture an oops always
> applies.
> 
> I've got an x230 sitting here that I have an ExpressCard serial port
> for. There's also netconsole and xhci debug cables.

I was kind of wornering if I'm only one seeing problems. I've now
built 6.15, and I plan to switch to it on next crash to see if it is
maybe hardware being flakey or what.

Oh, and I got _something_, see the thread. But that did not kill the
machine, so...

I'm currently traveling, and wifi reception is bad (and not really
chance to do heavy debugging).

Best regards,
								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2025-07-23 20:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 17:35 Pavel Machek
2025-07-23 15:06 ` Pavel Machek
2025-07-23 15:11   ` Dave Hansen
2025-07-23 20:35     ` Pavel Machek [this message]
2025-07-23 15:42   ` locking problems in iwlwifi? was " Pavel Machek
2025-07-23 17:13     ` Johannes Berg
2025-07-23 20:37       ` Pavel Machek
2025-07-24  8:50         ` John Ogness
2025-07-23 21:42       ` Pavel Machek
2025-09-15  9:32       ` Pavel Machek
2025-07-23 17:31     ` Thomas Gleixner
2025-07-23 17:32       ` Thomas Gleixner
2025-07-24 17:15         ` Pavel Machek
2025-07-24 17:51           ` Waiman Long
2025-07-24 17:55             ` Waiman Long
2025-07-24 21:24               ` Thomas Gleixner
2025-07-25  0:33                 ` Hillf Danton
2025-07-25 15:23                 ` Thomas Gleixner
2025-07-25 19:05                   ` Pavel Machek
2025-07-24 19:07             ` Pavel Machek
2025-07-24 19:22               ` Waiman Long
2025-07-24 22:21                 ` Thomas Gleixner
2025-07-25  1:56                   ` Waiman Long
2025-07-24 19:45             ` John Ogness
2025-07-25  0:16               ` Waiman Long
2025-07-25 13:44                 ` Thomas Gleixner
2025-07-25 19:38                   ` Waiman Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aIFHgit57Uc4BDiy@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®