From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Yosry Ahmed <yosryahmed@google.com>,
Nhat Pham <nphamcs@gmail.com>, Linux-MM <linux-mm@kvack.org>
Subject: Re: [regression] oops on heavy compilations ("kernel BUG at mm/zswap.c:1005!" and "Oops: invalid opcode: 0000")
Date: Fri, 23 Aug 2024 14:12:00 +0200 [thread overview]
Message-ID: <126650CA-CA83-4FE4-8AD1-F51A94FA117A@gmail.com> (raw)
In-Reply-To: <6f65e3a6-5f1a-4fda-b406-17598f4a72d5@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
> Wiadomość napisana przez Linux regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> w dniu 23.08.2024, o godz. 13:51:
>
> If that is the case nobody might
> look into this unless you are able to provide more details, like the
> result of a bisction
> (https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
> ) -- that's just how it is…
oh well - bisecting might be painful as to provoke oops - usually i need - literally - multiple days of constant 12c/24t compilation…
[-- Attachment #2: Type: text/html, Size: 4436 bytes --]
next prev parent reply other threads:[~2024-08-23 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BD22A15A-9216-4FA0-82DF-C7BBF8EE642E@gmail.com>
2024-08-23 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-08-23 12:12 ` Piotr Oniszczuk [this message]
2024-08-23 13:13 ` Matthew Wilcox
2024-08-23 14:35 ` Nhat Pham
2024-08-23 14:47 ` Matthew Wilcox
2024-08-23 16:07 ` Yosry Ahmed
2024-08-23 15:06 ` Piotr Oniszczuk
2024-08-23 16:16 ` Nhat Pham
2024-08-23 17:24 ` Piotr Oniszczuk
2024-08-23 18:06 ` Nhat Pham
2024-08-24 10:50 ` Piotr Oniszczuk
2024-08-25 5:55 ` Piotr Oniszczuk
2024-08-25 15:05 ` Pedro Falcato
2024-08-25 16:24 ` Piotr Oniszczuk
2024-08-27 18:48 ` Yosry Ahmed
2024-08-29 15:50 ` Piotr Oniszczuk
2024-08-29 21:54 ` Yosry Ahmed
2024-08-29 22:29 ` Matthew Wilcox
2024-08-29 22:53 ` Yosry Ahmed
2024-08-31 9:41 ` Piotr Oniszczuk
2024-08-31 17:23 ` Yosry Ahmed
2024-09-02 8:57 ` Piotr Oniszczuk
2024-09-03 17:49 ` Yosry Ahmed
2024-09-03 22:43 ` Nhat Pham
2024-09-04 23:36 ` Yosry Ahmed
2024-09-13 9:03 ` Tomáš Trnka
2024-09-13 17:39 ` Yosry Ahmed
[not found] ` <27594ee6-41dd-4951-b4cc-31577c9466db@amd.com>
2024-09-03 17:52 ` Yosry Ahmed
2024-08-23 18:42 ` Takero Funaki
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=126650CA-CA83-4FE4-8AD1-F51A94FA117A@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=yosryahmed@google.com \
/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