From: David Hu <D4v1d_4n0@protonmail.ch>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bug 209993] New: System won’t boot and hangs on boot because of unable to allocate memory address
Date: Mon, 02 Nov 2020 00:27:24 +0000 [thread overview]
Message-ID: <9pIOgSS1xvIBiywfzTwNpdGrF-e7I-YiHE3NOc3cIKXqvyPc178ro9Zjcj_k7ZhSx93QYYlp531NmTFK29JJL04a6KydZuvksgWATMugd7Q=@protonmail.ch> (raw)
In-Reply-To: <20201101155108.539629d017f624c64b377b91@linux-foundation.org>
[-- Attachment #1.1: Type: text/plain, Size: 2179 bytes --]
Sorry, I am afraid I do not have time to perform the bisect because my PC is a production PC.
Also, the output is too long (>65535 characters) that it cannot be sent through comments.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, November 1st, 2020 at 3:51 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
>
> bugzilla web interface).
>
> On Sun, 01 Nov 2020 21:56:26 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=209993
> >
> > Bug ID: 209993
> > Summary: System won’t boot and hangs on boot because of unable
> > to allocate memory address
> > Product: Memory Management
> > Version: 2.5
> > Kernel Version: 5.10-rc1
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: high
> > Priority: P1
> > Component: Other
> > Assignee: akpm@linux-foundation.org
> > Reporter: d4v1d_4n0@protonmail.ch
> > Regression: No
> >
>
> "Yes" :)
>
> > I compiled the kernel version 5.10.0-rc1 without problems but my Arch Linux
> >
> > system won’t boot with the new kernel. The journalctl -xe states the error
> >
> > kernel: tmp_crb MSFT0101:00: can’t request region for resource [mem
> >
> > 0xbf770000-0xbf773fff] what shall I do? I googled around and came up with no
> >
> > solutions. Maybe it is a new bug with the mainline kernel? (I use luks on lvm
> >
> > and the boot hangs after entering the correct passphrase)
>
> hm, that isn't a lot to go on. Could you please boot the most recent
>
> kernel which works OK, run `dmesg -s 1000000' and email us the output?
>
> That might at least let us figure out what's at 0xbf770000.
>
> Better, are you able to perform a bisection search between 5.9 and
>
> 5.10-rc1? https://wiki.gentoo.org/wiki/Kernel_git-bisect has
>
> instructions.
>
> Thanks.
[-- Attachment #1.2: publickey - D4v1d_4n0@protonmail.ch - 0x9FD99234.asc --]
[-- Type: application/pgp-keys, Size: 736 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2020-11-02 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209993-27@https.bugzilla.kernel.org/>
2020-11-01 23:51 ` Andrew Morton
2020-11-02 0:07 ` David Hu
2020-11-02 0:27 ` David Hu [this message]
2020-11-02 0:41 ` Randy Dunlap
2020-11-03 4:50 ` Jarkko Sakkinen
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='9pIOgSS1xvIBiywfzTwNpdGrF-e7I-YiHE3NOc3cIKXqvyPc178ro9Zjcj_k7ZhSx93QYYlp531NmTFK29JJL04a6KydZuvksgWATMugd7Q=@protonmail.ch' \
--to=d4v1d_4n0@protonmail.ch \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.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