From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216368] do_IRQ: stack overflow at boot during btrfs handling on a PowerMac G5 11,2
Date: Thu, 25 Aug 2022 11:06:43 +0000 [thread overview]
Message-ID: <bug-216368-206035-BTko10ogyh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216368-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216368
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #4 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Christophe Leroy from comment #3)
> It should be investigated with BTRFS team why the callstack is so deep.
Did anyone forward this to the Btrfs team? if so: where? If not I guess I can
do that.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-25 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 0:09 [Bug 216368] New: do_IRQ: stack overflow at boot on a PowerMac G5 11,2 bugzilla-daemon
2022-08-16 0:10 ` [Bug 216368] " bugzilla-daemon
2022-08-16 0:10 ` bugzilla-daemon
2022-08-16 7:30 ` bugzilla-daemon
2022-08-25 11:06 ` bugzilla-daemon [this message]
2022-08-25 11:57 ` [Bug 216368] do_IRQ: stack overflow at boot during btrfs handling " bugzilla-daemon
2022-09-05 17:16 ` bugzilla-daemon
2022-12-18 23:19 ` bugzilla-daemon
2022-12-18 23:21 ` bugzilla-daemon
2023-12-31 18:48 ` bugzilla-daemon
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=bug-216368-206035-BTko10ogyh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.