From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Elmar Stellnberger <estellnb@elstel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Stable <stable@vger.kernel.org>
Subject: Re: Fwd: kernel fault on hibernation: get_zeroed_page/swsusp_write
Date: Sat, 24 Jun 2023 08:25:39 +0700 [thread overview]
Message-ID: <ZJZGE4ZxJzrhRznA@debian.me> (raw)
In-Reply-To: <ZJXFgfldS6W_LCiI@mail.dotplex.com>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On Fri, Jun 23, 2023 at 06:17:05PM +0200, Elmar Stellnberger wrote:
> Hi all, Hi Bagas S.
>
> As the issue didn't reproduce the way I would have liked (did not
> reproduce at all here, not even with the same kernel version; no
> further comment) I have now uploaded the /proc/kcore and the kernel
> binaries and symbol files I still had on disk at
> https://upload.elstel.info (This may move to something like
> upload.elstel.info/bugs/kernpagealloc in the future)
>
First, tl;dr:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
Can you attach [1] to your Bugzilla report? Also, any report on bisection?
Also, you don't need to upload full kernel images instead; people can
grab /proc/config.gz you uploaded on Bugzilla and then `make olddefconfig`
from it.
Anyway, telling regzbot:
#regzbot link: https://upload.elstel.info/kcore.xz
Thanks.
[1]: https://upload.elstel.info/kcore.xz
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-24 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:36 Bagas Sanjaya
2023-06-23 16:17 ` Elmar Stellnberger
2023-06-24 1:25 ` Bagas Sanjaya [this message]
2023-06-24 10:21 ` Elmar Stellnberger
2023-06-24 12:15 ` Bagas Sanjaya
2023-06-24 13:44 ` Thorsten Leemhuis
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=ZJZGE4ZxJzrhRznA@debian.me \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=estellnb@elstel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox