From: Elmar Stellnberger <estellnb@elstel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
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 12:21:29 +0200 [thread overview]
Message-ID: <ZJbDqStCNfdpwObE@mail.dotplex.com> (raw)
In-Reply-To: <ZJZGE4ZxJzrhRznA@debian.me>
Hi Bagas S., Hi all
concerns: Bug 217544 - kernel fault on hibernation: get_zeroed_page/swsusp_write
https://bugzilla.kernel.org/show_bug.cgi?id=217544
Bisection does not make sense here, since I can not reproduce the
issue. Packing the kernel binaries and symbol files was meant to invoke
gdb directly on the kcore:
> /usr/src/kernel-6.3.7-desktop586-1.mga9/scripts/extract-vmlinux vmlinuz-6.3.7-desktop-1.mga9 >vmlinux
> file vmlinuz-6.3.7-desktop-1.mga9
vmlinuz-6.3.7-desktop-1.mga9: Linux kernel x86 boot executable bzImage, version 6.3.7-desktop-1.mga9 (iurt@ecosse.mageia.org) #1 SMP PREEMPT_DYNAMIC Fri Jun 9 17:47:53 UTC 2023, RO-rootFS, swap_dev 0X6, Normal VGA
> file vmlinux
vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, BuildID[sha1]=942674511321671b33c739cceddb1e3a48a17895, stripped
> grep __alloc_pages /boot/System.map...
0xc03758... T __alloc_pages
> gdb vmlinux kcore
# x/5i 0xc03758..
Am Sat, Jun 24, 2023 at 08:25:39AM +0700 schrieb Bagas Sanjaya:
> 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.
>
I would heavily doubt that the same symbols would get to be located at
the same address if you started to compile from source, even if you
applied all Mageia specific patches. We would need reproducible builds
for that. Nonetheless you are free to check whether the symbols will
reside at the same place in your System.map afterwards.
I wonder whether there is a way to convert the System.map text file
(which looks to me like the output of 'nm -S') back into an elf section
to be added to the stripped vmlinux with objcopy. Shouldn´t there be a
script/ for this?
:: Sometimes you have only one chance to catch a bug.
Cheers,
Elmar
Am Sat, Jun 24, 2023 at 08:25:39AM +0700 schrieb Bagas Sanjaya:
> On Fri, Jun 23, 2023 at 06:17:05PM +0200, Elmar Stellnberger wrote:
> Can you attach [1] to your Bugzilla report? Also, any report on bisection?
Pardon, what is [1]?
next prev parent reply other threads:[~2023-06-24 10:21 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
2023-06-24 10:21 ` Elmar Stellnberger [this message]
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=ZJbDqStCNfdpwObE@mail.dotplex.com \
--to=estellnb@elstel.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--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