All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Preining <norbert@preining.info>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Christoph Anton Mitterer <calestyo@scientia.org>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Lenovo X1 - kernel 6.0.N - complete freeze btrfs or i915 related
Date: Thu, 27 Oct 2022 17:05:35 +0900	[thread overview]
Message-ID: <Y1o7z/yKVEfbw05M@bulldog> (raw)
In-Reply-To: <CAL3q7H6yYSGRBtWa69-qM+6UjzpTXQspWtXDc=FTKtv2kSivMg@mail.gmail.com>

Hi,

> Your log showed only i915 problems:

Yes, because the btrfs error forced a complete hang without a way to
capturing the errors, but I have a photo, and put in the first two
lines of the backtrace.

But the issue seems to be resolved with 6.0.5 and some rescue booting.

Concerning the i915 error, that is reproducible. I will contact
the  maintainers.

> If that persists, just contact the i915 developers and maintainers:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n10214

Thanks and all the best

Norbert

--
PREINING Norbert                              https://www.preining.info
Mercari Inc.     +     IFMGA Guide     +     TU Wien     +     TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

      reply	other threads:[~2022-10-27  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 12:45 Lenovo X1 - kernel 6.0.N - complete freeze btrfs or i915 related Norbert Preining
2022-10-26 20:33 ` Christoph Anton Mitterer
2022-10-27  5:15   ` Norbert Preining
2022-10-27  7:35     ` Filipe Manana
2022-10-27  8:05       ` Norbert Preining [this message]

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=Y1o7z/yKVEfbw05M@bulldog \
    --to=norbert@preining.info \
    --cc=calestyo@scientia.org \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.