NVIDIA related warning on booting linux 4.14
I am seeing a warning while booting linux 4.14.2 [code][ 43.438583] resource sanity check: requesting [mem 0x000a0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000bffff window] [ 43.438698] caller _nv001193rm+0x166/0x1c0 [nvidia] mapping multiple BARs [ 43.802318] nvidia-modeset: Allocated GPU:0 (GPU-a432c7bb-af50-7966-be96-385d4d9c5c97) @ PCI:0000:01:00.0[/code] This warning wasn't there under the previous kernel I was using (4.9 series)
I am seeing a warning while booting linux 4.14.2
[   43.438583] resource sanity check: requesting [mem 0x000a0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000bffff window]
[ 43.438698] caller _nv001193rm+0x166/0x1c0 [nvidia] mapping multiple BARs
[ 43.802318] nvidia-modeset: Allocated GPU:0 (GPU-a432c7bb-af50-7966-be96-385d4d9c5c97) @ PCI:0000:01:00.0


This warning wasn't there under the previous kernel I was using (4.9 series)

#1
Posted 11/29/2017 07:30 AM   
They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was Info: mapping multiple BARs. Your kernel is fine.
They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was
Info: mapping multiple BARs. Your kernel is fine.

#2
Posted 11/29/2017 09:56 AM   
[quote=""]They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was Info: mapping multiple BARs. Your kernel is fine.[/quote] GPU bios?
said:They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was
Info: mapping multiple BARs. Your kernel is fine.

GPU bios?

#3
Posted 11/29/2017 10:25 AM   
Motherboard BIOS. You may disregard these messages - they are harmless.
Motherboard BIOS.

You may disregard these messages - they are harmless.

Artem S. Tashkinov
Linux and Open Source advocate

#4
Posted 11/29/2017 10:57 AM   
[quote=""]They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was Info: mapping multiple BARs. Your kernel is fine.[/quote] I did journalctl | grep BARs. The journal goes back to june. There was no mention of the term 'BARs' in the journal till now.
said:They just changed the message in newer kernels. It has probably always been there due to a buggy bios. The previous message was
Info: mapping multiple BARs. Your kernel is fine.

I did journalctl | grep BARs. The journal goes back to june. There was no mention of the term 'BARs' in the journal till now.

#5
Posted 11/29/2017 09:29 PM   
I can confirm this message just occured with kernel 4.14.x, never had this with older versions. According to this: [url]https://lwn.net/Articles/300667/[/url] [code](patch) ioremap sanity check to catch mapping requests exceeding the BAR sizes Go through the iomem resource tree to check if any of the ioremap() requests span more than any slot in the iomem resource tree and do a WARN_ON() if we hit this check. This will raise a red-flag, if some driver is mapping more than what is needed. And hopefully identify possible corruptions much earlier.[/code] Can someone confirm, this won't lead to "possible corruptions"? Thanks in advance Marcus
I can confirm this message just occured with kernel 4.14.x, never had this with older versions.

According to this: https://lwn.net/Articles/300667/

(patch) ioremap sanity check to catch mapping requests exceeding the BAR sizes

Go through the iomem resource tree to check if any of the ioremap() requests
span more than any slot in the iomem resource tree and do a WARN_ON() if we hit
this check.

This will raise a red-flag, if some driver is mapping more than what
is needed. And hopefully identify possible corruptions much earlier.


Can someone confirm, this won't lead to "possible corruptions"?

Thanks in advance
Marcus

#6
Posted 12/05/2017 03:41 PM   
I'm a bit puzzled why this message is displayed just now for some people. The change of the message was already in kernel 4.8. Since then not much has changed in regard to ioremap. Just some changes in the e820 code. Can this cause corruption? Possibly but unlikely and if so, you can't do anything about it anyway other than wait for a fixed bios from your manufacturer. Why is this displayed now? Mystery, better asked that on the kernel mailing list.
I'm a bit puzzled why this message is displayed just now for some people. The change of the message was already in kernel 4.8. Since then not much has changed in regard to ioremap. Just some changes in the e820 code.
Can this cause corruption? Possibly but unlikely and if so, you can't do anything about it anyway other than wait for a fixed bios from your manufacturer.
Why is this displayed now? Mystery, better asked that on the kernel mailing list.

#7
Posted 12/05/2017 04:33 PM   
I filed bug 2017354 about this. From the investigation, I'm pretty sure this message is harmless but we're fixing it for a future driver release nonetheless.
Answer Accepted by Original Poster
I filed bug 2017354 about this. From the investigation, I'm pretty sure this message is harmless but we're fixing it for a future driver release nonetheless.

Aaron Plattner
NVIDIA Linux Graphics

#8
Posted 12/05/2017 05:55 PM   
Scroll To Top

Add Reply