You are not logged in.

#1 2014-10-28 21:33:36

fabioticconi
Member
Registered: 2013-09-11
Posts: 6

[SOLVED] Nvidia 330m with driver 340xx: black screen

Hi, I've been battling with this since last upgrade and had to rollback to nouveau drivers.

When installing nvidia-340xx, it gets loaded correctly (checked with lsmod). It does also start the X server (checked Xorg.0.log and lightdm logs).

However, the screen stays black. I've tried several config changes and grub options to no avail. Anyone had this problem? Any inputs at all?

To be clear, I'm able to correctly install the driver: as a proof, I've installed 304xx and it worked fine (although it had some glitches when running games - nouveau is doing a bit better).

I've tried it on both linux and linux-lts, updating the initramfs accordingly. I've also tried nvidia-340xx-dkms, using nvidia-hook in mkinitcpio.conf - same result. Loaded, but black screen.

Thanks for any help/suggestion you can give.

Last edited by fabioticconi (2014-12-20 00:58:18)

Offline

#2 2014-10-28 23:04:43

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

What model nVidia card do you have? nVidia has recently dropped support for some cards in the latest 343.xx release, so we need to see if it's possible yours was one that needs 340.xx or even 304.xx.


Matt

"It is very difficult to educate the educated."

Offline

#3 2014-10-28 23:06:29

fabioticconi
Member
Registered: 2013-09-11
Posts: 6

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Forgot to say, my bad. It's a 330m, supported by 340xx.

EDIT: actually, I didn't forget: it's in the post title big_smile

Last edited by fabioticconi (2014-10-28 23:06:53)

Offline

#4 2014-11-03 20:52:34

jakub
Member
Registered: 2013-09-14
Posts: 151

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Something went really wrong with driver 340 (just after splitting nvidia into nvidia and nvidia-340xx). There is some problem with monitor detection. In my case it looks like I can start X only with external monitor disconnected. Having it connected I can't start X (both laptop and external screen stay blank). This is my thread: https://bbs.archlinux.org/viewtopic.php?id=188527
Also check also this one on nvidia devtalk: https://devtalk.nvidia.com/default/topi … x-ubunt/2/

Last edited by jakub (2014-11-03 20:53:10)

Offline

#5 2014-11-03 21:06:52

fabioticconi
Member
Registered: 2013-09-11
Posts: 6

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Thanks jakub. I guess we just have to wait for the nvidia guys to fix then. Damn.

Offline

#6 2014-11-12 20:22:23

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2)

With this GPU, everything works fine with the stock kernel, but I mostly don't use the stock kernel. That's where the problems start, because the same version of the NVidia driver shows a black screen (no error messages anywhere in the logs, no response to keyboard etc.) when starting the X-server with my kernel configuration. It's the same kernel configuration that has worked fine for me for years, but after moving to kernel 3.17.2 and NVidia 340.58, something went badly wrong.

Anyway, the key question is: How does the stock kernel resolve the issue? Why does it make a difference? I would like to make my modified kernel work again, but I can't find any differences relevant to the GPU in the kernel configuration. The only thing I noticed was the VGA arbiter turned on in the stock kernel whereas my modified kernel has it switched off. But presumably, switching the arbiter on didn't change anything at all. This is just a plain old NVidia, no Optimus crap that might need that arbiter.

So, to sum up, some unrelated configuration options (present by chance in the Arch stock kernel) might make (again, by chance) the NVidia driver 340.58 work...

Offline

#7 2014-11-12 21:59:43

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Gotcha!

Nov 12 20:37:37 octopus kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000328
Nov 12 20:37:38 octopus kernel: IP: [<ffffffffa0b7347b>] _nv006515rm+0x4b/0xc0 [nvidia]
Nov 12 20:37:38 octopus kernel: PGD 3e6dd1067 PUD 3c6541067 PMD 0 
Nov 12 20:37:38 octopus kernel: Oops: 0000 [#1] PREEMPT SMP 
Nov 12 20:37:38 octopus kernel: Modules linked in: nvidia(PO) drm ext4 jbd2 mbcache twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common serpent_sse2_x86_64 serpent_generic blo
Nov 12 20:37:38 octopus kernel:  snd_hda_controller thinkpad_acpi snd_hda_codec snd_pcm snd_timer iTCO_wdt iTCO_vendor_support i7core_edac nvram edac_core tpm_tis evdev snd psmouse mxm_wmi 
Nov 12 20:37:38 octopus kernel: CPU: 4 PID: 16169 Comm: Xorg.bin Tainted: P           O   3.17.2-AP+ #1
Nov 12 20:37:38 octopus kernel: Hardware name: LENOVO 43193BG/43193BG, BIOS 6NET80WW (1.41 ) 11/29/2011
Nov 12 20:37:38 octopus kernel: task: ffff880422f50000 ti: ffff880401cd0000 task.ti: ffff880401cd0000
Nov 12 20:37:38 octopus kernel: RIP: 0010:[<ffffffffa0b7347b>]  [<ffffffffa0b7347b>] _nv006515rm+0x4b/0xc0 [nvidia]
Nov 12 20:37:38 octopus kernel: RSP: 0018:ffff880401cd3a40  EFLAGS: 00010286
Nov 12 20:37:38 octopus kernel: RAX: 0000000000000000 RBX: ffff8803d56e0008 RCX: 0000000000000000
Nov 12 20:37:38 octopus kernel: RDX: 0000000000000000 RSI: 0000000000000056 RDI: 0000000000000000
Nov 12 20:37:38 octopus kernel: RBP: ffff8803f2faaf00 R08: 0000000000000002 R09: ffff880427c8e288
Nov 12 20:37:38 octopus kernel: R10: ffff8800ab424008 R11: 0000000000000008 R12: 0000000000000000
Nov 12 20:37:38 octopus kernel: R13: 0000000000000000 R14: ffff8803d5670008 R15: 0000000000000002
Nov 12 20:37:38 octopus kernel: FS:  00007f48a32578c0(0000) GS:ffff88043fd00000(0000) knlGS:0000000000000000
Nov 12 20:37:38 octopus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 12 20:37:38 octopus kernel: CR2: 0000000000000328 CR3: 00000003e6dcc000 CR4: 00000000000007e0
Nov 12 20:37:38 octopus kernel: Stack:
Nov 12 20:37:38 octopus kernel:  ffff880422780008 ffff880422780008 ffff8803d56e0008 ffff8803d5670008
Nov 12 20:37:38 octopus kernel:  ffff8800ab424008 ffffffffa0b5f596 000000000000000a ffff8803d5670008
Nov 12 20:37:38 octopus kernel:  ffff8803d56e0008 ffff8800b2ede008 ffff880422ffa008 ffffffffa0b58e46
Nov 12 20:37:38 octopus kernel: Call Trace:
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0b5f596>] ? _nv007058rm+0x406/0x920 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0b58e46>] ? _nv007054rm+0xa6/0x2c0 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0c1157f>] ? _nv008900rm+0x3d0f/0x5c10 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e0d5fb>] ? _nv009251rm+0x3b/0x60 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e8a649>] ? _nv013594rm+0xa79/0xb90 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e8b51f>] ? _nv000781rm+0x32f/0x650 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e8335a>] ? rm_init_adapter+0x6a/0x100 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e9353b>] ? nvidia_open+0x1eb/0x940 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffff8128b5c1>] ? kobj_lookup+0x111/0x170
Nov 12 20:37:38 octopus kernel:  [<ffffffffa0e9dbef>] ? nvidia_frontend_open+0x3f/0x90 [nvidia]
Nov 12 20:37:38 octopus kernel:  [<ffffffff81125ca6>] ? chrdev_open+0x96/0x1c0
Nov 12 20:37:38 octopus kernel:  [<ffffffff81125c10>] ? cdev_put+0x30/0x30
Nov 12 20:37:38 octopus kernel:  [<ffffffff8111f341>] ? do_dentry_open+0x1c1/0x310
Nov 12 20:37:38 octopus kernel:  [<ffffffff8111f4b8>] ? finish_open+0x28/0x40
Nov 12 20:37:38 octopus kernel:  [<ffffffff81130184>] ? do_last.isra.45+0x214/0x10c0
Nov 12 20:37:38 octopus kernel:  [<ffffffff8112c340>] ? link_path_walk+0x80/0xed0
Nov 12 20:37:38 octopus kernel:  [<ffffffff8112c340>] ? link_path_walk+0x80/0xed0
Nov 12 20:37:38 octopus kernel:  [<ffffffff811310e2>] ? path_openat+0xb2/0x650
Nov 12 20:37:38 octopus kernel:  [<ffffffff8112d22e>] ? path_lookupat+0x9e/0xd60
Nov 12 20:37:38 octopus kernel:  [<ffffffff81131d15>] ? do_filp_open+0x35/0xa0
Nov 12 20:37:38 octopus kernel:  [<ffffffff8111f743>] ? chown_common.isra.11+0xe3/0x150
Nov 12 20:37:38 octopus kernel:  [<ffffffff8113de27>] ? __alloc_fd+0x97/0x120
Nov 12 20:37:38 octopus kernel:  [<ffffffff81120d85>] ? do_sys_open+0x125/0x210
Nov 12 20:37:38 octopus kernel:  [<ffffffff8138d6d1>] ? tracesys+0xd4/0xd9
Nov 12 20:37:38 octopus kernel: Code: 20 c7 83 5c 18 00 00 00 00 00 00 49 89 c5 eb 18 44 89 e2 48 89 de 4c 89 f7 ff 93 a0 05 00 00 01 83 5c 18 00 00 41 ff c4 4c 89 ef <41> ff 95 28 03 00 00
Nov 12 20:37:38 octopus kernel: RIP  [<ffffffffa0b7347b>] _nv006515rm+0x4b/0xc0 [nvidia]
Nov 12 20:37:38 octopus kernel:  RSP <ffff880401cd3a40>
Nov 12 20:37:38 octopus kernel: CR2: 0000000000000328
Nov 12 20:37:38 octopus kernel: ---[ end trace a4c41e936d7c5540 ]---

This happens with my kernel configuration right after loading the NVidia module. Actually it sometimes happens more than once per boot. For some reason the NVidia module loaded into the stock kernel doesn't exhibit this problem.

Anyway, this is what causes the black screen. The kernel is then in an undefined state, i.e., Alt+PrtSc+R restores at least the response to CapsLock ;-) and other magic keys also work, but the display remains dead, i.e., no console, no framebuffer, nothing.

Offline

#8 2014-12-20 00:15:24

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Update: The curent nvidia-340xx still has the same problem. (Just tried it today.) It surprises me that this hasn't been already reported somewhere at least a hundred times...

It would be great to have a separate ArchLinux package that would stick with the last working version of the driver, which was 340.46. Otherwise it's necessary to ignore all the NVidia-related packages on each system update and compile the old ones manually using AUR.

BTW, it seems odd to me that this problem is not reported anywhere on the web. Are there really no users of slighlty dated (~5 years old) laptops with NVidia cards? My Lenovo W510 with 16 gigs of RAM and with a Core i7 is still perfectly usable. After all, old computers might get more and more common now that Moore's law doesn't hold any more.

Edit: I posted the issue on the NVidia forums with a link back to this thread. Let's hope that this gets resolved sooner or later.

Last edited by andrej.podzimek (2014-12-20 00:44:19)

Offline

#9 2014-12-20 00:57:00

fabioticconi
Member
Registered: 2013-09-11
Posts: 6

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

To me, it's been actually working fine for a while now. After a few updates I've retried and it worked. If it can be useful, this is the list of stuff I had found, and meticulously did, that was said could help (but didn't, until a few updates later):

removed xorg.conf and all driver-related confs in xorg.conf.d (I didn't have them, but if you do you might want to move them away) - I've only re-put it there when it worked.

/etc/default/grub (this in particular is said to fix problems with older cards and nvidia proprietary drivers.. give it a try, remember to re-install grub after that)

GRUB_CMDLINE_LINUX="rcutree.rcu_idle_gp_delay=1"

/etc/mkinitcpio.conf

MODULES="nvidia"

/etc/modprobe.d/blacklist.conf

blacklist nouveau

Not sure if related, but I've also installed intel microcode, remade the initrams and updated grub: https://wiki.archlinux.org/index.php/microcode

You may also want to re-install your latest kernel after all this. Then reboot, and pray.

Another thing I did, but I'm not sure if it's related again, is when I restarted, after all the above, for my last "hopeful try", I went into the recovery console instead, then from there re-created the initrams and updated grub again. Somewhere I had read that creating the initrams while the nouveau driver was loaded (as it was when I did it from the GUI, of course) could make it go as module in the initrams itself. Not sure if it's a bunch a crap TBH smile

mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.cfg

Then I restarted, and the bloody nvidia logo appeared. And I was happy. tongue if you are stuck, I'd suggest you give it a try at this point.

Best of luck.

ps: of course I assume you have a completely up-to-date system right? pacman -Syua kind of up-to-date smile

Last edited by fabioticconi (2014-12-20 01:01:53)

Offline

#10 2014-12-20 01:01:19

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 29,049
Website

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

fabioticconi wrote:

of course I assume you have a completely up-to-date system right? pacman -Syua kind of up-to-date smile

pacman doesn't have an `-a` option...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#11 2014-12-20 01:03:02

fabioticconi
Member
Registered: 2013-09-11
Posts: 6

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Thanks - I use yaourt, and always forget they don't have the same options. pacman -Syu would do fine.

Offline

#12 2014-12-20 02:18:37

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Hi, thanks for the summary. None of those things helped (and I have already had most of that configuration anyway). (The one with RCU seems to be just a rumor though -- if something like that really helped, there would have to be some terrible RCU abuse bugs in the NVidia driver.)

However, it slowly starts to get obvious that it's not caused by the NVidia driver (alone). I tried to disable NVidia and use nouveau instead. (It used to work on my machine normally, just the performance was bad and there was no dual screen support.) However, nouveau doesn't work any more and it causes exactly the same black screen and hang as NVidia does. It does so even before the X-server is started, i.e., immediately when it initializes its KMS framebuffer screen.

So there's something badly wrong in the kernel and/or both drivers for NVidia and it might well be related to the display backlight, simply because the backlight goes suddenly off in both cases (both with nouveau and with the NVidia blob).

However, there is one difference when I load nvidia directly from the initrd as you suggest: When I try to start the X-server, I'm not getting a complete freeze any more -- I'm getting a WARNING in dmesg instead and as a result of the failed operation that causes the warning, X.org assumes that there is no usable NVidia driver and uses the terrible VESA mode instead. (That's the driver that hasn't been capable to switch to wide screen resolutions for >10 years, just because of some never-ending dispute about an ancient (even older than 10 years) bug in NVidia's screen resolution metadata.)

So now I'm going to search for the warning message to find out whether there's a workaround for this. I'll report back if I find something.

Offline

#13 2014-12-20 02:57:35

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

OK, found it. It was this. (That's because I'm running kernel 3.18 now, just to find out whether the bug might be fixed there. Well, obviously it's not the case.)

After applying the patch and recompiling the NVidia driver, I got exactly the same black screen and hang again. Something is badly wrong with the current kernels and/or the drivers for NVidia. Or perhaps everyone has stopped testing on slightly older hardware. How could otherwise such a critical showstopper bug remain unnoticed for more than a month...?

Offline

#14 2014-12-20 03:08:18

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

So I'm not the only one, it seems. The problem is that threads with very few comments are quite hard to find on the NVidia forums.

Edit: So the last working configuration is 3.17.7 and 340.46. Anything newer fails, simply because 340.46 doesn't compile with a 3.18 kernel and drivers newer than 340.46 have the null pointer dereference bug.

Last edited by andrej.podzimek (2014-12-20 03:50:11)

Offline

#15 2015-01-01 17:29:05

DGAzr
Member
Registered: 2015-01-01
Posts: 1

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

Good afternoon and happy new year! I just registered here to add that I'm experiencing the same behavior on my Quadro K2100 system. Unfortunately for me, the combination of Kernel 3.17.6 and NVIDIA driver 340.46 doesn't even seem to work. I may have created more problems troubleshooting this over the past 12 hours or so, but the behavior is exactly as you've described.

Upon starting X I see the nVidia logo briefly, and then the screen goes black and stays there. The system is still functional, sysrq works, SSH works, and I can cleanly reboot, but there's no recovering the display. I hope a solution is found soon!

Offline

#16 2015-04-04 02:46:00

andrej.podzimek
Member
From: Zürich, Switzerland
Registered: 2005-04-10
Posts: 87

Re: [SOLVED] Nvidia 330m with driver 340xx: black screen

BTW, the problem still persists on 3.19.3 with NVidia 340.76. Next time I'm getting a non-NVidia GPU for sure. This is way out of all tolerable limits and my laptop has been unusable since I don't know when.

[  123.186715] BUG: unable to handle kernel NULL pointer dereference at 0000000000000328
[  123.186871] IP: [<ffffffffa0ac64fb>] _nv006515rm+0x4b/0xc0 [nvidia]
[  123.186873] PGD 4157f0067 PUD 415478067 PMD 0
[  123.186875] Oops: 0000 [#1] PREEMPT SMP
[  123.186909] Modules linked in: nvidia(PO) drm ccm twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common blowfish_generic blowfish_x86_64 blowfish_common cast5_generic cast_common seqiv ctr ecb des3_ede_x86_64 des_generic cbc camellia_generic camellia_x86_64 xcbc hmac sha512_ssse3 sha512_generic sha256_ssse3 sha256_generic md5 md4 algif_hash xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bnep snd_hda_codec_hdmi uvcvideo msr videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev snd_hda_codec_conexant snd_hda_codec_generic arc4 iTCO_wdt iTCO_vendor_support media btusb bluetooth iwldvm mac80211 crc16 mxm_wmi iwlwifi psmouse evdev i7core_edac serio_raw edac_core cfg80211 i2c_i801 lpc_ich mfd_core thinkpad_acpi tpm_tis snd_hda_intel nvram tpm rfkill
[  123.186943]  snd_hda_controller battery video rtc_cmos ac snd_hda_codec wmi snd_pcm snd_timer e1000e snd ptp soundcore pps_core button sch_fq_codel cuse fuse nfs lockd grace sunrpc fscache sg ip6_tables x_tables kvm_intel kvm pcrypt coretemp cpufreq_ondemand acpi_cpufreq processor thermal_sys hwmon shpchp ioatdma dca dm_crypt serpent_sse2_x86_64 serpent_generic lrw glue_helper ablk_helper cryptd xts gf128mul algif_skcipher af_alg btrfs xor raid6_pq dm_mod sr_mod sd_mod cdrom mmc_block crc32c_intel ahci libahci libata scsi_mod firewire_ohci sdhci_pci xhci_pci firewire_core sdhci crc_itu_t led_class xhci_hcd ehci_pci mmc_core ehci_hcd usbcore usb_common ipv6 autofs4
[  123.186946] CPU: 2 PID: 1579 Comm: Xorg Tainted: P           O   3.19.3-AP+ #1
[  123.186947] Hardware name: LENOVO 43193BG/43193BG, BIOS 6NET80WW (1.41 ) 11/29/2011
[  123.186949] task: ffff88042ba25dc0 ti: ffff88041fd44000 task.ti: ffff88041fd44000
[  123.187092] RIP: 0010:[<ffffffffa0ac64fb>]  [<ffffffffa0ac64fb>] _nv006515rm+0x4b/0xc0 [nvidia]
[  123.187093] RSP: 0018:ffff88041fd47a28  EFLAGS: 00010286
[  123.187094] RAX: 0000000000000000 RBX: ffff880412cb8008 RCX: 0000000000000000
[  123.187095] RDX: 0000000000000000 RSI: 0000000000000056 RDI: 0000000000000000
[  123.187096] RBP: ffff88042138af00 R08: 0000000000000002 R09: ffff88042b3bf948
[  123.187097] R10: ffff880421351008 R11: ffffffffa0b620a0 R12: 0000000000000000
[  123.187098] R13: 0000000000000000 R14: ffff880417fb0008 R15: 0000000000000002
[  123.187100] FS:  00007f4fa335f900(0000) GS:ffff88043fc80000(0000) knlGS:0000000000000000
[  123.187101] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  123.187102] CR2: 0000000000000328 CR3: 0000000411d7e000 CR4: 00000000000007e0
[  123.187102] Stack:
[  123.187105]  ffff880411d12008 ffff880411d12008 ffff880412cb8008 ffff880417fb0008
[  123.187106]  0000000000000008 ffffffffa0ab25c6 000000000000000a ffff880417fb0008
[  123.187108]  ffff880412cb8008 ffff880422e0b008 ffff880412cd0008 ffffffffa0aabe56
[  123.187109] Call Trace:
[  123.187248]  [<ffffffffa0ab25c6>] ? _nv007058rm+0x406/0x920 [nvidia]
[  123.187386]  [<ffffffffa0aabe56>] ? _nv007054rm+0xa6/0x2c0 [nvidia]
[  123.187545]  [<ffffffffa0b6460f>] ? _nv008900rm+0x3d0f/0x5c10 [nvidia]
[  123.187630]  [<ffffffffa0d6083b>] ? _nv009251rm+0x3b/0x60 [nvidia]
[  123.187686]  [<ffffffffa0ddd879>] ? _nv013594rm+0xa79/0xb90 [nvidia]
[  123.187741]  [<ffffffffa0dde75f>] ? _nv000780rm+0x32f/0x650 [nvidia]
[  123.187797]  [<ffffffffa0dd65aa>] ? rm_init_adapter+0x6a/0x100 [nvidia]
[  123.187802]  [<ffffffff81089c00>] ? request_threaded_irq+0x30/0x180
[  123.187856]  [<ffffffffa0de6733>] ? nvidia_open+0x1e3/0x930 [nvidia]
[  123.187860]  [<ffffffff812aacd1>] ? kobj_lookup+0x111/0x170
[  123.187912]  [<ffffffffa0df0fff>] ? nvidia_frontend_open+0x3f/0x90 [nvidia]
[  123.187916]  [<ffffffff8112d876>] ? chrdev_open+0x96/0x1c0
[  123.187919]  [<ffffffff8112d7e0>] ? cdev_put+0x30/0x30
[  123.187921]  [<ffffffff81126f71>] ? do_dentry_open+0x1d1/0x320
[  123.187923]  [<ffffffff811377df>] ? do_last.isra.42+0x21f/0x10d0
[  123.187926]  [<ffffffff81116993>] ? kmem_cache_alloc+0xd3/0x170
[  123.187928]  [<ffffffff8113870f>] ? path_openat+0x7f/0x5a0
[  123.187931]  [<ffffffff81139b4b>] ? do_filp_open+0x2b/0x90
[  123.187934]  [<ffffffff81145c77>] ? __alloc_fd+0x97/0x120
[  123.187936]  [<ffffffff81128835>] ? do_sys_open+0x125/0x210
[  123.187940]  [<ffffffff813ae2e5>] ? int_check_syscall_exit_work+0x34/0x3d
[  123.187942]  [<ffffffff813ae0b6>] ? system_call_fastpath+0x16/0x1b
[  123.187961] Code: 20 c7 83 5c 18 00 00 00 00 00 00 49 89 c5 eb 18 44 89 e2 48 89 de 4c 89 f7 ff 93 a0 05 00 00 01 83 5c 18 00 00 41 ff c4 4c 89 ef <41> ff 95 28 03 00 00 44 39 e0 77 d9 4c 89 f7 b9 74 06 10 00 31
[  123.188103] RIP  [<ffffffffa0ac64fb>] _nv006515rm+0x4b/0xc0 [nvidia]
[  123.188103]  RSP <ffff88041fd47a28>
[  123.188104] CR2: 0000000000000328
[  123.188114] ---[ end trace d7e5931ab4cf1a9d ]---

Offline

Board footer

Powered by FluxBB