UEFI+Nvidia segfault on boot, strange NVRM messages-corruption and stability problems

interzoneuk · #1 2nd July 2012, 09:12 AM

HI

(only) in UEFI mode with the Nvidia binary driver (i.e not nouveau) I get the following message on boot

Code:

----------------------------------------------------
[   24.237183] ADDRCONF(NETDEV_CHANGE): p1p1: link becomes ready
[   25.320325] ------------[ cut here ]------------
[   25.320331] WARNING: at arch/x86/mm/ioremap.c:104 __ioremap_caller+0x31d/0x370()
[   25.320332] Hardware name: MS-7758
[   25.320333] Modules linked in: bnep lockd sunrpc bluetooth rfkill tpm_bios ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter ip6_tables xt_state nf_conntrack vfat fat nvidia(PO) i2c_i801 r8169 snd_hda_codec_hdmi ppdev mii parport_pc shpchp coretemp microcode parport snd_hda_codec_realtek iTCO_wdt i2c_core serio_raw snd_hda_intel snd_hda_codec snd_hwdep iTCO_vendor_support uinput snd_pcm_oss snd_pcm snd_page_alloc snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore usb_storage crc32c_intel ghash_clmulni_intel video [last unloaded: scsi_wait_scan]
[   25.320358] Pid: 754, comm: X Tainted: P           O 3.4.4-3.fc17.x86_64 #1
[   25.320359] Call Trace:
[   25.320363]  [<ffffffff81056ebf>] warn_slowpath_common+0x7f/0xc0
[   25.320365]  [<ffffffff81056f1a>] warn_slowpath_null+0x1a/0x20
[   25.320367]  [<ffffffff8104130d>] __ioremap_caller+0x31d/0x370
[   25.320418]  [<ffffffffa08d0045>] ? os_map_kernel_space+0x85/0xf0 [nvidia]
[   25.320420]  [<ffffffff814cc239>] ? pci_conf1_read+0xc9/0x120
[   25.320422]  [<ffffffff81041394>] ioremap_cache+0x14/0x20
[   25.320459]  [<ffffffffa08d0045>] os_map_kernel_space+0x85/0xf0 [nvidia]
[   25.320500]  [<ffffffffa0896f31>] _nv014600rm+0xeb/0x10b [nvidia]
[   25.320534]  [<ffffffffa01e1eaa>] ? _nv009533rm+0x89/0x140 [nvidia]
[   25.320567]  [<ffffffffa01e2019>] ? _nv014166rm+0xb8/0x102 [nvidia]
[   25.320600]  [<ffffffffa01e24c7>] ? _nv014206rm+0x58/0x9e [nvidia]
[   25.320633]  [<ffffffffa01dd438>] ? _nv014176rm+0xbe/0x2f0 [nvidia]
[   25.320679]  [<ffffffffa01dd715>] ? _nv014211rm+0xab/0x174 [nvidia]
[   25.320714]  [<ffffffffa01dd82e>] ? _nv014175rm+0x50/0x5d [nvidia]
[   25.320749]  [<ffffffffa01e4896>] ? _nv014151rm+0x9ef/0xb29 [nvidia]
[   25.320792]  [<ffffffffa08aaf9f>] ? _nv012422rm+0x174/0x662 [nvidia]
[   25.320833]  [<ffffffffa08aaf1d>] ? _nv012422rm+0xf2/0x662 [nvidia]
[   25.320877]  [<ffffffffa022bdf1>] ? _nv003975rm+0x1e5/0x1deb [nvidia]
[   25.320964]  [<ffffffffa060d3bf>] ? _nv004000rm+0xabd2/0xd2d8 [nvidia]
[   25.321048]  [<ffffffffa060b9d7>] ? _nv004000rm+0x91ea/0xd2d8 [nvidia]
[   25.321080]  [<ffffffffa01a75de>] ? _nv009829rm+0x25/0x40 [nvidia]
[   25.321122]  [<ffffffffa08aacb1>] ? _nv014657rm+0x7c8/0x942 [nvidia]
[   25.321164]  [<ffffffffa08abe01>] ? _nv001088rm+0x522/0x7a1 [nvidia]
[   25.321205]  [<ffffffffa08a27cc>] ? rm_init_adapter+0xae/0x1bb [nvidia]
[   25.321209]  [<ffffffff810e1c29>] ? __setup_irq+0x3b9/0x510
[   25.321212]  [<ffffffff8116c9ea>] ? kmem_cache_alloc_trace+0x11a/0x130
[   25.321252]  [<ffffffffa08c5854>] ? nv_kern_open+0x4b4/0x800 [nvidia]
[   25.321256]  [<ffffffff811856db>] ? chrdev_open+0x9b/0x180
[   25.321259]  [<ffffffff8117f350>] ? __dentry_open+0x210/0x2f0
[   25.321263]  [<ffffffff81272085>] ? selinux_inode_permission+0xc5/0x110
[   25.321266]  [<ffffffff81185640>] ? cdev_put+0x30/0x30
[   25.321269]  [<ffffffff81180471>] ? nameidata_to_filp+0x71/0x80
[   25.321272]  [<ffffffff8118ffd8>] ? do_last+0x468/0x8f0
[   25.321275]  [<ffffffff8119056f>] ? path_openat+0xcf/0x3d0
[   25.321278]  [<ffffffff81190991>] ? do_filp_open+0x41/0xa0
[   25.321282]  [<ffffffff8119c6bd>] ? alloc_fd+0x4d/0x120
[   25.321285]  [<ffffffff8118056d>] ? do_sys_open+0xed/0x1c0
[   25.321290]  [<ffffffff810cfc3c>] ? __audit_syscall_entry+0xcc/0x300
[   25.321293]  [<ffffffff81180661>] ? sys_open+0x21/0x30
[   25.321297]  [<ffffffff815fc8a9>] ? system_call_fastpath+0x16/0x1b
[   25.321299] ---[ end trace b2d81e08c0f1ffb9 ]---
[   25.791735] NVRM: Your system is not currently configured to drive a VGA console
[   25.791738] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   25.791739] NVRM: requires the use of a text-mode VGA console. Use of other console
[   25.791740] NVRM: drivers including, but not limited to, vesafb, may result in
[   25.791741] NVRM: corruption and stability problems, and is not supported.

----------------------------------------------------

The system 'seems' fine however I worry about the 'Use of other console NVRM: drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported.' part....

Anyone know what I should do to stop the messages?

Cheers

george_toolan · #2 2nd July 2012, 11:13 AM

Did you install the latest UEFI BIOS 2.4?

interzoneuk · #3 2nd July 2012, 12:45 PM

Sorry - as far as UEFI is concerned i'm a confused noob...

I believe that my PC comes with UEFI 2.3.1 (or 2.3)

How can I check ?

srs5694 · #4 3rd July 2012, 07:16 PM

Quote:

Originally Posted by george_toolan

Did you install the latest UEFI BIOS 2.4?

The latest UEFI specification is version 2.3.1; there is, as yet, no UEFI 2.4 specification. That said, it's conceivable that some manufacturers have their own product-specific numbering schemes that go as high as 2.4. In any event, you're more-or-less hostage to your hardware manufacturer when it comes to firmware upgrades. EFI version numbers for some products are likely to remain stuck at 2.0, 2.1, or some other version number indefinitely. Firmware updates may be available for some models, but this isn't something you can count on.

Quote:

Originally Posted by interzoneuk

The system 'seems' fine however I worry about the 'Use of other console NVRM: drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported.' part....

My hunch is that when you boot in BIOS mode, no framebuffer driver gets loaded, or at least the nVidia driver gets loaded before the framebuffer driver does; but when you boot in EFI mode, the EFI framebuffer driver gets loaded and is interfering with the nVidia driver. The EFI framebuffer driver can only be compiled into the kernel or not at all, so if this hypothesis is correct, you'll need to recompile the kernel without the EFI framebuffer driver to use the proprietary nVidia driver. OTOH, this is the first I've heard of this problem, and I've been following Linux/EFI issues for long enough that I'd expect to have heard of it before now, so it could be that the message about console drivers is a red herring.

george_toolan · #5 4th July 2012, 09:46 AM

During POST hit Del to enter BIOS setup where you should find an information page somewhere.

Or try

Code:

dmesg | grep -i MS-7758

If this is a MS-7758 motherboard aka MSI Z77A-G43 then the latest BIOS version is 2.4 or better.

See

#6 4th July 2012, 11:27 AM

Quote:

Originally Posted by interzoneuk

HI

(only) in UEFI mode with the Nvidia binary driver (i.e not nouveau) I get the following message on boot

Code:

----------------------------------------------------
[   24.237183] ADDRCONF(NETDEV_CHANGE): p1p1: link becomes ready
[   25.320325] ------------[ cut here ]------------
[   25.320331] WARNING: at arch/x86/mm/ioremap.c:104 __ioremap_caller+0x31d/0x370()
[   25.320332] Hardware name: MS-7758
[   25.320333] Modules linked in: bnep lockd sunrpc bluetooth rfkill tpm_bios ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter ip6_tables xt_state nf_conntrack vfat fat nvidia(PO) i2c_i801 r8169 snd_hda_codec_hdmi ppdev mii parport_pc shpchp coretemp microcode parport snd_hda_codec_realtek iTCO_wdt i2c_core serio_raw snd_hda_intel snd_hda_codec snd_hwdep iTCO_vendor_support uinput snd_pcm_oss snd_pcm snd_page_alloc snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore usb_storage crc32c_intel ghash_clmulni_intel video [last unloaded: scsi_wait_scan]
[   25.320358] Pid: 754, comm: X Tainted: P           O 3.4.4-3.fc17.x86_64 #1
[   25.320359] Call Trace:
[   25.320363]  [<ffffffff81056ebf>] warn_slowpath_common+0x7f/0xc0
[   25.320365]  [<ffffffff81056f1a>] warn_slowpath_null+0x1a/0x20
[   25.320367]  [<ffffffff8104130d>] __ioremap_caller+0x31d/0x370
[   25.320418]  [<ffffffffa08d0045>] ? os_map_kernel_space+0x85/0xf0 [nvidia]
[   25.320420]  [<ffffffff814cc239>] ? pci_conf1_read+0xc9/0x120
[   25.320422]  [<ffffffff81041394>] ioremap_cache+0x14/0x20
[   25.320459]  [<ffffffffa08d0045>] os_map_kernel_space+0x85/0xf0 [nvidia]
[   25.320500]  [<ffffffffa0896f31>] _nv014600rm+0xeb/0x10b [nvidia]
[   25.320534]  [<ffffffffa01e1eaa>] ? _nv009533rm+0x89/0x140 [nvidia]
[   25.320567]  [<ffffffffa01e2019>] ? _nv014166rm+0xb8/0x102 [nvidia]
[   25.320600]  [<ffffffffa01e24c7>] ? _nv014206rm+0x58/0x9e [nvidia]
[   25.320633]  [<ffffffffa01dd438>] ? _nv014176rm+0xbe/0x2f0 [nvidia]
[   25.320679]  [<ffffffffa01dd715>] ? _nv014211rm+0xab/0x174 [nvidia]
[   25.320714]  [<ffffffffa01dd82e>] ? _nv014175rm+0x50/0x5d [nvidia]
[   25.320749]  [<ffffffffa01e4896>] ? _nv014151rm+0x9ef/0xb29 [nvidia]
[   25.320792]  [<ffffffffa08aaf9f>] ? _nv012422rm+0x174/0x662 [nvidia]
[   25.320833]  [<ffffffffa08aaf1d>] ? _nv012422rm+0xf2/0x662 [nvidia]
[   25.320877]  [<ffffffffa022bdf1>] ? _nv003975rm+0x1e5/0x1deb [nvidia]
[   25.320964]  [<ffffffffa060d3bf>] ? _nv004000rm+0xabd2/0xd2d8 [nvidia]
[   25.321048]  [<ffffffffa060b9d7>] ? _nv004000rm+0x91ea/0xd2d8 [nvidia]
[   25.321080]  [<ffffffffa01a75de>] ? _nv009829rm+0x25/0x40 [nvidia]
[   25.321122]  [<ffffffffa08aacb1>] ? _nv014657rm+0x7c8/0x942 [nvidia]
[   25.321164]  [<ffffffffa08abe01>] ? _nv001088rm+0x522/0x7a1 [nvidia]
[   25.321205]  [<ffffffffa08a27cc>] ? rm_init_adapter+0xae/0x1bb [nvidia]
[   25.321209]  [<ffffffff810e1c29>] ? __setup_irq+0x3b9/0x510
[   25.321212]  [<ffffffff8116c9ea>] ? kmem_cache_alloc_trace+0x11a/0x130
[   25.321252]  [<ffffffffa08c5854>] ? nv_kern_open+0x4b4/0x800 [nvidia]
[   25.321256]  [<ffffffff811856db>] ? chrdev_open+0x9b/0x180
[   25.321259]  [<ffffffff8117f350>] ? __dentry_open+0x210/0x2f0
[   25.321263]  [<ffffffff81272085>] ? selinux_inode_permission+0xc5/0x110
[   25.321266]  [<ffffffff81185640>] ? cdev_put+0x30/0x30
[   25.321269]  [<ffffffff81180471>] ? nameidata_to_filp+0x71/0x80
[   25.321272]  [<ffffffff8118ffd8>] ? do_last+0x468/0x8f0
[   25.321275]  [<ffffffff8119056f>] ? path_openat+0xcf/0x3d0
[   25.321278]  [<ffffffff81190991>] ? do_filp_open+0x41/0xa0
[   25.321282]  [<ffffffff8119c6bd>] ? alloc_fd+0x4d/0x120
[   25.321285]  [<ffffffff8118056d>] ? do_sys_open+0xed/0x1c0
[   25.321290]  [<ffffffff810cfc3c>] ? __audit_syscall_entry+0xcc/0x300
[   25.321293]  [<ffffffff81180661>] ? sys_open+0x21/0x30
[   25.321297]  [<ffffffff815fc8a9>] ? system_call_fastpath+0x16/0x1b
[   25.321299] ---[ end trace b2d81e08c0f1ffb9 ]---
[   25.791735] NVRM: Your system is not currently configured to drive a VGA console
[   25.791738] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   25.791739] NVRM: requires the use of a text-mode VGA console. Use of other console
[   25.791740] NVRM: drivers including, but not limited to, vesafb, may result in
[   25.791741] NVRM: corruption and stability problems, and is not supported.

----------------------------------------------------

The system 'seems' fine however I worry about the 'Use of other console NVRM: drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported.' part....

Anyone know what I should do to stop the messages?

Cheers

Stop messing around with uefi and blacklist vesafb instead.

interzoneuk · #7 4th July 2012, 07:19 PM

I updated the bios just the other day...

Code:

dmesg | grep -i MS-7758
[    0.000000] DMI: MSI MS-7758/Z77A-G43 (MS-7758), BIOS V2.4 06/19/2012
[   13.222709] Hardware name: MS-7758

isn't the 2.4 bit just the bios version (rather than uefi)

Quote:

Stop messing around with uefi and blacklist vesafb instead.

I'll try that however I don't think its loaded..... (can't see the module with lsmod)

I'll report back after black listing.....

Thanks for all the input - much appreciated.

#8 4th July 2012, 07:44 PM

Quote:

Originally Posted by interzoneuk

I updated the bios just the other day...

Code:

dmesg | grep -i MS-7758
[    0.000000] DMI: MSI MS-7758/Z77A-G43 (MS-7758), BIOS V2.4 06/19/2012
[   13.222709] Hardware name: MS-7758

isn't the 2.4 bit just the bios version (rather than uefi)

I'll try that however I don't think its loaded..... (can't see the module with lsmod)

I'll report back after black listing.....

Thanks for all the input - much appreciated.

vesafb is used by plymouth on bootup

Code:

[leigh@main-pc ~]$ dmesg |grep vesafb
[    1.422045] vesafb: mode is 1280x800x32, linelength=5120, pages=0
[    1.422046] vesafb: scrolling: redraw
[    1.422048] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    1.422333] vesafb: framebuffer at 0xdd000000, mapped to 0xffffc90011800000, using 4032k, total 4032k
[   10.948619] NVRM: drivers including, but not limited to, vesafb, may result in

The quickest way to disable it is to edit /etc/default/grub and remove rhgb from the boot options.
You will need to run "grub2-mkconfig -o /boot/grub2/grub.cfg" afterwards.

This post maybe of interest.

http://www.nvnews.net/vbulletin/showthread.php?t=179755

interzoneuk · #9 6th July 2012, 09:49 PM

thanks for the responses.

I am not loading plymouth as I boot from arch linux grub - they share the same /boot/efi folder, I do not have the rhgb option

i.e:-

--------------------------
[morgan@fc17 ~]$ dmesg |grep vesafb
[ 14.871789] NVRM: drivers including, but not limited to, vesafb, may result in
--------------------------

p.s the same msg occurs in arch and ubuntu 12.04 (all 64bit os)

I think I am just going to re-install and not use UEFI at all -as far as I can see its a nightmare.