Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-13-12, 11:11 AM   #1
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi,

Probably I catch some bug on linux 3.1.10 and last stable Nvidia driver. I attached all bug logs.
I have had errors since I switched 2 days ago from legacy boot to UEFI. I have had in kernel efifb since this time.

best regards,

packages:
nvidia 290.10-3
nvidia-cg-toolkit 3.0-3
nvidia-utils 290.10-1
opencl-nvidia 290.10-1


error:
WARNING: at arch/x86/mm/ioremap.c:102 __ioremap_caller+0x302/0x380()
Hardware name: Latitude E6410
Modules linked in: xts gf128mul dm_crypt binfmt_misc zfs(P) zunicode(P) zavl(P) zcommon(P) znvpair(P) spl ipmi_watchdog ipmi_msghandler ums_cypress usb_storage mmc_block lis3lv02d_i2c btsdio uvcvideo videodev v4l2_compat_ioctl32 dm_zero coretemp bridge stp ipv6 llc mspro_block tifm_ms memstick snd_hda_codec_hdmi nvidia(P) tifm_sd tifm_core uio_cif uio hidp bnep btusb sha1_generic sha256_generic sha512_generic tun snd_hda_codec_idt acpi_cpufreq mperf rfcomm rtl8187 eeprom_93cx6 snd_usb_audio snd_hda_intel snd_usbmidi_lib arc4 snd_hda_codec iwlagn mac80211 cfg80211 dell_laptop snd_hwdep snd_rawmidi snd_seq_device hci_uart bluetooth snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_timer intel_agp intel_gtt lis3lv02d firewire_ohci input_polldev snd agpgart rfkill firewire_core psmouse container sdhci_pci sdhci video soundcore processor pcspkr e1000e dell_wmi wmi joydev yenta_socket pcmcia_rsrc pcmcia_core rtc_cmos unix
Pid: 5409, comm: X Tainted: P 3.1.10-h2 #7
Call Trace:
[<ffffffff81046a7b>] ? warn_slowpath_common+0x7b/0xc0
[<ffffffff810238c2>] ? __ioremap_caller+0x302/0x380
[<ffffffff812d1b23>] ? pci_get_subsys+0x83/0xc0
[<ffffffffa0945852>] ? _nv014280rm+0xf9/0x119 [nvidia]
[<ffffffffa02b520e>] ? _nv009386rm+0x89/0x142 [nvidia]
[<ffffffffa02b5360>] ? _nv013856rm+0x99/0xcb [nvidia]
[<ffffffffa02b57f6>] ? _nv013896rm+0x58/0x9e [nvidia]
[<ffffffffa02b0a28>] ? _nv013866rm+0xbe/0x2f0 [nvidia]
[<ffffffffa02b0d05>] ? _nv013901rm+0xab/0x174 [nvidia]
[<ffffffffa02b0e1e>] ? _nv013865rm+0x50/0x5d [nvidia]
[<ffffffffa02b7cd2>] ? _nv013841rm+0xa27/0xb65 [nvidia]
[<ffffffffa095952d>] ? _nv012140rm+0x174/0x681 [nvidia]
[<ffffffffa09594ab>] ? _nv012140rm+0xf2/0x681 [nvidia]
[<ffffffffa02f9c41>] ? _nv003904rm+0x1e5/0x1e4b [nvidia]
[<ffffffffa06cb362>] ? _nv003929rm+0xa698/0xcd14 [nvidia]
[<ffffffffa06c9e59>] ? _nv003929rm+0x918f/0xcd14 [nvidia]
[<ffffffffa027b156>] ? _nv009666rm+0xd/0x12 [nvidia]
[<ffffffffa095924c>] ? _nv014334rm+0x7ad/0x91a [nvidia]
[<ffffffffa095a33f>] ? _nv001081rm+0x4e4/0x702 [nvidia]
[<ffffffffa0950d34>] ? rm_init_adapter+0x9e/0x1b6 [nvidia]
[<ffffffffa0972ec4>] ? nv_kern_open+0x3f4/0x790 [nvidia]
[<ffffffff810e826d>] ? chrdev_open+0xbd/0x1b0
[<ffffffff810e81b0>] ? cdev_put+0x30/0x30
[<ffffffff810e2442>] ? __dentry_open+0x212/0x330
[<ffffffff810edf4e>] ? path_get+0x1e/0x30
[<ffffffff810f258c>] ? do_last.isra.37+0x28c/0x850
[<ffffffff810f0b35>] ? path_init+0x2e5/0x3d0
[<ffffffff810f2c5b>] ? path_openat+0xcb/0x3b0
[<ffffffff810f3075>] ? do_filp_open+0x45/0xb0
[<ffffffff810fe7a6>] ? alloc_fd+0x46/0x130
[<ffffffff810e3717>] ? do_sys_open+0xf7/0x1e0
[<ffffffff814f43fb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 8aab32925ec66bc1 ]---
Attached Files
File Type: gz nvidia-bug-report.log.gz (61.3 KB, 71 views)
wodor is offline   Reply With Quote
Old 02-14-12, 10:28 AM   #2
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi,
On 295.20 I have that same problem.

best regards,
wodor is offline   Reply With Quote
Old 02-14-12, 03:17 PM   #3
danix
NVIDIA Corporation
 
danix's Avatar
 
Join Date: Feb 2010
Location: Santa Clara, CA
Posts: 237
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Do you have the same problem if your kernel is configured without efifb?
danix is offline   Reply With Quote
Old 02-14-12, 04:47 PM   #4
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi, I'll investigate it. Additionally I have in kernel fbcon.

grep -i FRAMEBUFFER_CONSOLE .config

CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y

best regards,
wodor is offline   Reply With Quote
Old 02-14-12, 05:38 PM   #5
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

I investigated it and :

When I boot system via grub-efi x86_64:

- with fbcon and efifb - error appear
- without fbcon - error appear ( and I don't have visible text console - only black screen)
- without efifb - error appear ( and I don't have visible text console - only black screen)

When I boot THAT SAME OS with THAT SAME KERNEL by grub2 legacy (from MBR):

- with fbcon and efifb - NO error
- without fbcon - no error
- without efifb - no error

configs from grubs:

UEFI:

function load_video {
insmod video
insmod videotest
insmod video_bochs
insmod video_cirrus
insmod video_fb
}

menuentry "Arch Linux 3.1.10" {
set root=(arch-arch)
load_video
insmod efi_gop
insmod efi_uga
linux /boot/vmlinuz-3.1.10 root=/dev/mapper/arch-arch ro nouveau.modeset=0 acpi_sleep=nonvs resume=/dev/mapper/arch-swap pcie_aspm=force.
initrd /boot/vmlinuz-3.1.10-h2.img
}




legacy:


menuentry "Arch Linux 3.1.10" {
set root=(arch-arch)
linux /boot/vmlinuz-3.1.10 root=/dev/mapper/arch-arch ro nouveau.modeset=0 acpi_sleep=nonvs resume=/dev/mapper/arch-swap pcie_aspm=force
initrd /boot/vmlinuz-3.1.10-h2.img
}

best regards,
wodor is offline   Reply With Quote
Old 02-17-12, 08:28 AM   #6
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi,
Do you investigate it ? Maybe you wan't something more ?

best regards,
wodor is offline   Reply With Quote
Old 02-17-12, 09:05 AM   #7
mephist0
Registered User
 
Join Date: Jan 2010
Posts: 11
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi,

I think my Problem is excatly the same. I have UEFI, too. But I didnt test to boot to BIOS mode. Grub is UEFI only installed.

It was kinda tricky to install UEFI on that Intel motherboard.

So, if you need more info. Let us know.

Best Regards,

meph
mephist0 is offline   Reply With Quote
Old 02-20-12, 04:38 AM   #8
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

I switched to legacy boot but I will try resolve problems. Under UEFI boot I have additionally random problems with suspend and sometimes system hang after disks sync (waiting for something 30s or more) when I reboot machine.

best regards,
wodor is offline   Reply With Quote

Old 03-06-12, 08:30 AM   #9
wodor
Registered User
 
Join Date: Nov 2005
Location: betelgeuse
Posts: 19
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

Hi,
With last kernel 3.3.0-rc6 I still have this issue. Problem appear when I startup Xorg, no when I load module. I tested many configurations on efi and I always have that same error.

Nvidia, what is your opinion?

best regards,
wodor is offline   Reply With Quote
Old 03-14-12, 09:34 AM   #10
mephist0
Registered User
 
Join Date: Jan 2010
Posts: 11
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

I switched back to BIOS mode yesterday. (reformated and did a clean reinstall of gentoo + windows) (ofcourse, I did make backups )

The driver 290.10 works so far.

I didnt test the driver 295.20, yet.

PS: Windows 7 boots faster in BIOS mode


//edit: Using uvesafb with 2560x1600-32@60.
When I boot with UEFI and efifb only 800x600 is possible. Other resolutions are mac only?!
mephist0 is offline   Reply With Quote
Old 04-06-12, 12:50 PM   #11
tekdoc
Registered User
 
Join Date: Apr 2012
Posts: 1
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

I just switched to GRUB2 UEFI boot from GRUB2 BIOS and I am seeing the same error with the 295.33 driver and kernel 3.2.14. I am using an Asrock Z68 Pro3m motherboard and 8600GTS GPU. I can confirm error was not present with BIOS boot.

I have also noticed my framebuffer console resolution is now limited to a maximum of 1024x768; with BIOS boot I had a high resolution, widescreen framebuffer console. I don't know if this is a limitation of UEFI boot or maybe related to this driver bug.
tekdoc is offline   Reply With Quote
Old 04-06-12, 01:02 PM   #12
jeisom
Registered User
 
Join Date: Dec 2005
Location: My own little world
Posts: 117
Default Re: Bug with UEFI - DELL E6410 - linux 3.1.10 - nv 290.10

I got a similar warning/same with my Asus M5A97 EVO motherboard and uefi. I'm am using kernel 3.3.0 and nvidia driver 295.33.

Code:
Apr  4 01:25:00 predator kernel: [   77.885026] ------------[ cut here ]------------
Apr  4 01:25:00 predator kernel: [   77.885032] WARNING: at arch/x86/mm/ioremap.c:102 __ioremap_caller+0x302/0x380()
Apr  4 01:25:00 predator kernel: [   77.885034] Hardware name: To be filled by O.E.M.
Apr  4 01:25:00 predator kernel: [   77.885035] Modules linked in: tda18271 s5h1411 vboxnetflt(O) vboxnetadp(O) vboxdrv(O) nxt200x saa7
134_dvb videobuf_dvb tuner_simple tuner_types tuner saa7134 firewire_sbp2 snd_hda_codec_hdmi rt2800usb snd_hda_codec_realtek snd_hda_in
tel rt2x00usb rt2800lib snd_hda_codec uvcvideo rt2x00lib mceusb videobuf2_vmalloc snd_usb_audio snd_usbmidi_lib videobuf2_memops videob
uf2_core ir_rc6_decoder snd_rawmidi usblp snd_seq_device snd_hwdep snd_pcm saa7164 snd_page_alloc snd_timer snd dvb_core videobuf_dma_s
g videobuf_core tveeprom soundcore v4l2_common firewire_ohci videodev nvidia(PO) firewire_core v4l2_compat_ioctl32
Apr  4 01:25:00 predator kernel: [   77.885064] Pid: 3693, comm: X Tainted: P           O 3.3.0 #1
Apr  4 01:25:00 predator kernel: [   77.885066] Call Trace:
Apr  4 01:25:00 predator kernel: [   77.885069]  [<ffffffff8102f73a>] warn_slowpath_common+0x7a/0xb0
Apr  4 01:25:00 predator kernel: [   77.885173]  [<ffffffffa075f655>] ? os_map_kernel_space+0x75/0xd0 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885175]  [<ffffffff8102f785>] warn_slowpath_null+0x15/0x20
Apr  4 01:25:00 predator kernel: [   77.885177]  [<ffffffff81025622>] __ioremap_caller+0x302/0x380
Apr  4 01:25:00 predator kernel: [   77.885181]  [<ffffffff814486d5>] ? pci_conf1_read+0xc5/0x120
Apr  4 01:25:00 predator kernel: [   77.885183]  [<ffffffff810256cf>] ioremap_cache+0xf/0x20
Apr  4 01:25:00 predator kernel: [   77.885235]  [<ffffffffa075f655>] os_map_kernel_space+0x75/0xd0 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885290]  [<ffffffffa07285e1>] _nv014562rm+0xeb/0x10b [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885335]  [<ffffffffa007e36a>] ? _nv009523rm+0x89/0x140 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885380]  [<ffffffffa007e4d9>] ? _nv014128rm+0xb8/0x102 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885425]  [<ffffffffa007e987>] ? _nv014168rm+0x58/0x9e [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885471]  [<ffffffffa00798f8>] ? _nv014138rm+0xbe/0x2f0 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885515]  [<ffffffffa0079bd5>] ? _nv014173rm+0xab/0x174 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885560]  [<ffffffffa0079cee>] ? _nv014137rm+0x50/0x5d [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885606]  [<ffffffffa0080d56>] ? _nv014113rm+0x9ef/0xb29 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885659]  [<ffffffffa073c4df>] ? _nv012385rm+0x174/0x662 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885713]  [<ffffffffa073c45d>] ? _nv012385rm+0xf2/0x662 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885764]  [<ffffffffa00c7c81>] ? _nv003971rm+0x1e5/0x1deb [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885873]  [<ffffffffa04a6b5b>] ? _nv003996rm+0xa9ae/0xd0b8 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.885983]  [<ffffffffa04a525d>] ? _nv003996rm+0x90b0/0xd0b8 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886013]  [<ffffffffa004447e>] ? _nv009815rm+0x25/0x40 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886090]  [<ffffffffa073c1f1>] ? _nv014619rm+0x7c8/0x942 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886143]  [<ffffffffa073d341>] ? _nv001088rm+0x522/0x7a1 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886197]  [<ffffffffa0733d3c>] ? rm_init_adapter+0xae/0x1bb [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886205]  [<ffffffff8108eeea>] ? __setup_irq+0x2aa/0x4d0
Apr  4 01:25:00 predator kernel: [   77.886266]  [<ffffffffa07566bc>] ? nv_kern_open+0x3fc/0x790 [nvidia]
Apr  4 01:25:00 predator kernel: [   77.886275]  [<ffffffff810ec8a0>] ? chrdev_open+0x110/0x210
Apr  4 01:25:00 predator kernel: [   77.886282]  [<ffffffff810ec790>] ? cdev_put+0x30/0x30
Apr  4 01:25:00 predator kernel: [   77.886291]  [<ffffffff810e6506>] ? __dentry_open+0x296/0x370
Apr  4 01:25:00 predator kernel: [   77.886299]  [<ffffffff81582535>] ? sub_preempt_count+0x95/0xd0
Apr  4 01:25:00 predator kernel: [   77.886308]  [<ffffffff810e76e9>] ? nameidata_to_filp+0x69/0x80
Apr  4 01:25:00 predator kernel: [   77.886315]  [<ffffffff810f6fb4>] ? do_last+0x304/0x910
Apr  4 01:25:00 predator kernel: [   77.886323]  [<ffffffff810f76ce>] ? path_openat+0xce/0x3c0
Apr  4 01:25:00 predator kernel: [   77.886331]  [<ffffffff81038f82>] ? capable+0x12/0x20
Apr  4 01:25:00 predator kernel: [   77.886339]  [<ffffffff810f7acd>] ? do_filp_open+0x3d/0xa0
Apr  4 01:25:00 predator kernel: [   77.886347]  [<ffffffff81582535>] ? sub_preempt_count+0x95/0xd0
Apr  4 01:25:00 predator kernel: [   77.886356]  [<ffffffff8157ecd1>] ? _raw_spin_unlock+0x11/0x40
Apr  4 01:25:00 predator kernel: [   77.886363]  [<ffffffff81103ba4>] ? alloc_fd+0xe4/0x130
Apr  4 01:25:00 predator kernel: [   77.886372]  [<ffffffff810e77f3>] ? do_sys_open+0xf3/0x1d0
Apr  4 01:25:00 predator kernel: [   77.886379]  [<ffffffff810f2bdd>] ? path_put+0x1d/0x30
Apr  4 01:25:00 predator kernel: [   77.886388]  [<ffffffff810e78ec>] ? sys_open+0x1c/0x20
Apr  4 01:25:00 predator kernel: [   77.886396]  [<ffffffff81584822>] ? system_call_fastpath+0x16/0x1b
Apr  4 01:25:00 predator kernel: [   77.886402] ---[ end trace cf48103275eca63f ]---
jeisom is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 10:17 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.