Re: [Bug 209993] New: System won’t boot and hangs on boot because of unable to allocate memory address

[Randy Dunlap <rdunlap@infradead.org>]

Hi Jarkko,

Do you have any ideas about this?

>> kernel: tmp_crb MSFT0101:00: can’t request region for resource [mem
>> 0xbf770000-0xbf773fff]


David- did you type those lines in?
The "tmp_crb" should be "tpm_crb", as in drivers/char/tpm/tpm_crb.c.

A driver which handles the MSFT0101 TPM device apparently.



On 11/1/20 4:27 PM, David Hu wrote:
> 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.


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>