All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.org>
To: Norbert Preining <norbert@preining.info>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Lenovo X1 - kernel 6.0.N - complete freeze btrfs or i915 related
Date: Wed, 26 Oct 2022 22:33:19 +0200	[thread overview]
Message-ID: <5d59652451decb86786ff2dff9e4ffe3843f143b.camel@scientia.org> (raw)
In-Reply-To: <Y1krzbq3zdYOSQYG@bulldog>

Hey Norbert.


On Wed, 2022-10-26 at 21:45 +0900, Norbert Preining wrote:
> The laptop is freezing like hell. At the moment it hangs reproducible
> on every boot after a few seconds (around 20?).

Could it be the issue that has been reported independently by several
users?

E.g.:
https://lore.kernel.org/linux-btrfs/2291416ef48d98059f9fdc5d865b0ff040148237.camel@scientia.org/T/#u
https://lore.kernel.org/linux-btrfs/1c531dd5de7477c8b6ec15d4aebb8e42ae460925.camel@scientia.org/T/#t
https://lore.kernel.org/linux-btrfs/Y1krzbq3zdYOSQYG@bulldog/T/#u
https://lore.kernel.org/all/10522366-5c17-c18f-523c-b97c1496927b@net4u.de/
https://bugs.archlinux.org/task/76266
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848



Unfortunately, except for Josef Bacik's reply
(https://lore.kernel.org/all/Y1aeWdHd4%2FluzhAu@localhost.localdomain/)
there hasn't been any further word on this from any btrfs developer, so
it's hard to tell for people whether that issue could have caused any
further corruptions on the affected filesystems.

Also, in my case... I noticed the issue on some mv operation, as well
as on send|receive.... but otherwise I could mount my space cache v1
filesystems just normal without and lockups.
So it's also unclear, why it doesn't always show up.



Cheers,
Chris.

  reply	other threads:[~2022-10-26 20:33 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 [this message]
2022-10-27  5:15   ` Norbert Preining
2022-10-27  7:35     ` Filipe Manana
2022-10-27  8:05       ` Norbert Preining

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=5d59652451decb86786ff2dff9e4ffe3843f143b.camel@scientia.org \
    --to=calestyo@scientia.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=norbert@preining.info \
    /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.