From: Xi Ruoyao <xry111@xry111.site>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>,
David Wang <00107082@163.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
catalin.marinas@arm.com, lance.yang@linux.dev, b-padhi@ti.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Jan Polensky <japo@linux.ibm.com>
Subject: Re: Linux 6.18-rc6
Date: Tue, 18 Nov 2025 00:59:42 +0800 [thread overview]
Message-ID: <35aee4dea7e6823c5c8f7a4cd421f7a0baf20b08.camel@xry111.site> (raw)
In-Reply-To: <25e4c75c-097d-44bb-8739-136a0238d5bf@kernel.org>
On Mon, 2025-11-17 at 15:08 +0100, David Hildenbrand (Red Hat) wrote:
> (It dose not always happens, sometimes I don't get this crash and It
> dose not always err on same line.)
On my system what happened was very random. Some symptoms:
- ibus-libpinyin sometimes crashed after inputting one or two keys
- epiphany (GNOME browser) sometimes crashed on startup
- GCC sometimes hung building itself (on the insn-match-*.cc files)
- "make" sometimes segfaulted
- GDB sometimes segfaulted (detected when trying to analysis the core
dump from above)
Some "interesting" aspect of them:
- once a symptom showed up, it did kept reproducing until reboot
- when GDB happened to work, it showed that ibus-libpinyin, epiphany,
and make all crashed in their (different) hashtable implementations
I tried to bisect but failed because it was too random. After applying
the patch I rebooted 10 times and there's no longer such a symptom (at
least yet). This I'm 90% sure what hit is the same issue.
Tested-by: Xi Ruoyao <xry111@xry111.site>
--
Xi Ruoyao <xry111@xry111.site>
next prev parent reply other threads:[~2025-11-17 16:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 22:42 Linus Torvalds
2025-11-17 8:20 ` David Wang
2025-11-17 10:33 ` Linus Torvalds
2025-11-17 12:56 ` David Wang
2025-11-17 13:30 ` David Hildenbrand (Red Hat)
2025-11-17 13:45 ` David Wang
2025-11-17 14:08 ` David Hildenbrand (Red Hat)
2025-11-17 15:28 ` David Wang
2025-11-17 16:59 ` Xi Ruoyao [this message]
2025-11-17 21:19 ` Joan Bruguera Micó
2025-11-17 17:28 ` Linus Torvalds
2025-11-17 17:53 ` David Hildenbrand (Red Hat)
2025-11-17 17:59 ` Linus Torvalds
2025-11-17 18:24 ` David Hildenbrand (Red Hat)
2025-11-17 19:17 ` David Hildenbrand (Red Hat)
2025-11-18 1:10 ` Linus Torvalds
2025-11-18 4:13 ` David Wang
2025-11-18 13:55 ` David Wang
2025-11-18 14:12 ` David Hildenbrand (Red Hat)
2025-11-18 14:33 ` David Wang
2025-11-18 14:44 ` Carlos Llamas
2025-11-18 14:51 ` David Hildenbrand (Red Hat)
2025-11-18 14:53 ` Carlos Llamas
2025-11-18 15:09 ` David Wang
2025-11-18 7:28 ` David Hildenbrand (Red Hat)
2025-11-18 16:49 ` Linus Torvalds
2025-11-19 15:42 ` Catalin Marinas
2025-11-18 3:59 ` Carlos Llamas
2025-11-17 16:42 ` Linus Torvalds
2025-11-17 18:13 ` Guenter Roeck
2025-11-18 17:23 ` Stephanie Gawroriski
2025-11-18 18:01 ` Linus Torvalds
2025-11-18 20:18 ` Stephanie Gawroriski
2025-11-19 9:08 ` Heikki Krogerus
2025-11-19 14:18 ` Stephanie Gawroriski
2025-11-19 15:04 ` Stephanie Gawroriski
2025-11-24 9:50 ` Heikki Krogerus
2025-11-26 16:01 ` Stephanie Gawroriski
2025-11-27 9:53 ` Heikki Krogerus
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=35aee4dea7e6823c5c8f7a4cd421f7a0baf20b08.camel@xry111.site \
--to=xry111@xry111.site \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=b-padhi@ti.com \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=japo@linux.ibm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®