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)
(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.
Created attachment 293361 [details] output.txt Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, November 1st, 2020 at 3:51 PM, <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=209993 > > --- Comment #1 from Andrew Morton (akpm@linux-foundation.org) --- > > (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. > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > You are receiving this mail because: > > You are on the CC list for the bug. > > You reported the bug.
Created attachment 293363 [details] publickey - D4v1d_4n0@protonmail.ch - 0x9FD99234.asc
Created attachment 293365 [details] signature.asc
Created attachment 293367 [details] publickey - D4v1d_4n0@protonmail.ch - 0x9FD99234.asc 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.
Created attachment 293369 [details] signature.asc
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.
Created attachment 293371 [details] publickey - D4v1d_4n0@protonmail.ch - 0x9FD99234.asc Sorry, it was my typo. It was tpm_crb Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, November 1st, 2020 at 4:41 PM, <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=209993 > > --- Comment #7 from 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. > > You are receiving this mail because: > > You are on the CC list for the bug. > > You reported the bug.
Created attachment 293373 [details] signature.asc
On Sun, Nov 01, 2020 at 04:41:15PM -0800, Randy Dunlap wrote: > 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. The latest commit for tpm_crb was done over a year ago. The corrateral damage is that tpm_crb is not initialized. I'll have to check the dmesg log but nothing at ATM points out TPM subsystem is causing this hang (neither is it disclosed). I'll do a more formal investigation this week. /Jarkko
Nothing alarming concerning TPM is in the log but there is a flood of "PCIe Bus Error" messages.