| View previous topic :: View next topic |
| Author |
Message |
RayOfLight
Tux's lil' helper
Joined: 27 Aug 2013
Posts: 108
Location: Catalunya
|
 Posted: Tue Apr 15, 2014 2:56 pm Post subject: (updated) Bug in nvidia or bumblebee, not in adobe-flash |
 |
|
Hey, I think I found a bug in adobe-flash!  (damn blobs)
I have a nvidia-optimus amd64 gentoo install with kernel 3.14, I also have bbswitch, bumblebee and nvidia-drivers-337.12. I'm using xorg-server-1.15.0 with kde 4.11.5.
So, each time I boot up my system it stands very quiet and apparently working, I can optirun glxspheres (optirun works) or start a normal web browsing session with Opera, no problems until I go to youtube.com.
Then, my /var/log/messages gets flooded with:
| Code: | Apr 15 16:30:17 zenbook kernel: [ 313.182963] ------------[ cut here ]------------
Apr 15 16:30:17 zenbook kernel: [ 313.182972] WARNING: CPU: 0 PID: 16231 at fs/proc/generic.c:315 proc_register+0xc8/0x150()
Apr 15 16:30:17 zenbook kernel: [ 313.182974] [b]proc_dir_entry 'driver/nvidia' already registered[/b]
Apr 15 16:30:17 zenbook kernel: [ 313.182975] Modules linked in: nvidia(PO+) bbswitch(O) fuse uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_core bluetooth 6lowpan_iphc asus_nb_wmi asus_wmi x86_pkg_temp_thermal pcspkr int3403_thermal wmi [last unloaded: nvidia]
Apr 15 16:30:17 zenbook kernel: [ 313.182991] CPU: 0 PID: 16231 Comm: modprobe Tainted: P W O 3.14.0-gentoo #1
Apr 15 16:30:17 zenbook kernel: [ 313.182993] Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.212 09/17/2012
Apr 15 16:30:17 zenbook kernel: [ 313.182995] 0000000000000009 ffff88020c01bb68 ffffffffa389ff25 0000000000000002
Apr 15 16:30:17 zenbook kernel: [ 313.182998] ffff88020c01bbb8 ffff88020c01bba8 ffffffffa30ad337 ffff88020c01bb88
Apr 15 16:30:17 zenbook kernel: [ 313.183001] ffff88020c018b73 ffff88020c018b00 ffff8802a340a980 0000000000000000
Apr 15 16:30:17 zenbook kernel: [ 313.183005] Call Trace:
Apr 15 16:30:17 zenbook kernel: [ 313.183011] [<ffffffffa389ff25>] dump_stack+0x4f/0x7c
Apr 15 16:30:17 zenbook kernel: [ 313.183016] [<ffffffffa30ad337>] warn_slowpath_common+0x87/0xb0
Apr 15 16:30:17 zenbook kernel: [ 313.183019] [<ffffffffa30ad401>] warn_slowpath_fmt+0x41/0x50
Apr 15 16:30:17 zenbook kernel: [ 313.183022] [<ffffffffa3214be1>] ? proc_alloc_inum+0x51/0xc0
Apr 15 16:30:17 zenbook kernel: [ 313.183025] [<ffffffffa3214d18>] proc_register+0xc8/0x150
Apr 15 16:30:17 zenbook kernel: [ 313.183028] [<ffffffffa3214e9d>] proc_mkdir_data+0x4d/0x70
Apr 15 16:30:17 zenbook kernel: [ 313.183031] [<ffffffffa3214eee>] proc_mkdir_mode+0xe/0x10
Apr 15 16:30:17 zenbook kernel: [ 313.183133] [<ffffffffc1c81c7a>] nv_register_procfs+0x3a/0x1b0 [nvidia]
Apr 15 16:30:17 zenbook kernel: [ 313.183174] [<ffffffffc214d296>] nvidia_init_module+0x296/0x7ae [nvidia]
Apr 15 16:30:17 zenbook kernel: [ 313.183229] [<ffffffffc214d7c3>] ? nv_drm_init+0x15/0x15 [nvidia]
Apr 15 16:30:17 zenbook kernel: [ 313.183270] [<ffffffffc214d849>] nvidia_frontend_init_module+0x86/0xb8 [nvidia]
Apr 15 16:30:17 zenbook kernel: [ 313.183274] [<ffffffffa300034a>] do_one_initcall+0xfa/0x140
Apr 15 16:30:17 zenbook kernel: [ 313.183279] [<ffffffffa30d320e>] ? __blocking_notifier_call_chain+0x5e/0x80
Apr 15 16:30:17 zenbook kernel: [ 313.183282] [<ffffffffa3114470>] load_module+0x1900/0x21a0
Apr 15 16:30:17 zenbook kernel: [ 313.183285] [<ffffffffa3110db0>] ? show_initstate+0x50/0x50
Apr 15 16:30:17 zenbook kernel: [ 313.183288] [<ffffffffa3114e56>] SyS_finit_module+0x86/0x90
Apr 15 16:30:17 zenbook kernel: [ 313.183293] [<ffffffffa38b0562>] system_call_fastpath+0x16/0x1b
Apr 15 16:30:17 zenbook kernel: [ 313.183295] ---[ end trace 28498b86e830ac41 ]---
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:1140)
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: installed in this system is not supported by the 337.12
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: NVIDIA Linux driver release. Please see 'Appendix
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: A - Supported NVIDIA GPU Products' in this release's
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: README, available on the Linux driver download page
Apr 15 16:30:17 zenbook kernel: [ 313.184391] NVRM: at www.nvidia.com.
Apr 15 16:30:17 zenbook kernel: [ 313.184405] nvidia: probe of 0000:01:00.0 failed with error -1
Apr 15 16:30:17 zenbook kernel: [ 313.184552] NVRM: The NVIDIA probe routine failed for 1 device(s).
Apr 15 16:30:17 zenbook kernel: [ 313.184554] NVRM: None of the NVIDIA graphics adapters were initialized!
Apr 15 16:30:17 zenbook kernel: [ 313.184556] [drm] Module unloaded
Apr 15 16:30:17 zenbook kernel: [ 313.185889] NVRM: NVIDIA init module failed! |
every 3.5 ms, so I think flooded is an understatement as I have GBs of useless logs now.
I've updated my kernel, nvidia-drivers, bbswitch and bumblebee to what I think are the latest but it keeps happening.
The first way I've been able to stop this is with "pkill -9 udev" but I don't think it's very nice to my system...
After killing it, I can go to a Youtube video and adjust its settings to disable HW acceleration and after a reboot It seems not to happen again.
So after all, I think adobe-flash-11.2.202.350, has some amazingly well done while routine that keeps insmodding nvidia.ko no matter what and already has taken half life of my beloved SSD. Well done, paid programmer.
Can anybody test this one and/or provide any insight? TIA
Edit: FWIW, It seems that adobe flash is just a trigger for a root-privileged process to misbehave, probably bumblebee, more updates in Bug 508196
Last edited by RayOfLight on Sun Apr 20, 2014 5:21 am; edited 1 time in total |
|
| Back to top |
|
 |
jhallward
n00b
Joined: 10 Jan 2008
Posts: 3
|
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6098
Location: Dallas area
|
| Posted: Thu Apr 17, 2014 10:38 pm Post subject: |
|
|
I was looking at a youtube earlier and it crashed in the middle of it, but I'm using nouveau instead of nvidia drivers.
I think there's some problem with that particular version of flash, so I masked it and used an earlier flash (from a backup)
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Fri Apr 18, 2014 2:20 am Post subject: |
|
|
| Can you file this bug at Gentoo Bugzilla? Read here how to write a bug report, for more in-depth details and troubleshooting steps you can read our Bugzilla HOWTO. |
|
| Back to top |
|
|
cyberjun
Apprentice
Joined: 06 Nov 2005
Posts: 293
|
| Posted: Fri Apr 18, 2014 4:44 am Post subject: |
|
|
Hi,
I see the exact same issue. I also started seeing this after upgrading to this version of flash (and now there are no other versions of flash in portage). It seems flash tries to insert nvidia module without switching the card on (through bbswitch). Disabling HW acceleration in flash helps.
1. Put EnableLinuxHWVideoDecode=0 in /etc/adobe/mms.cfg
2. Uncheck "Enable HW acceleration" in flash config window.
--cyberjun |
|
| Back to top |
|
|
RayOfLight
Tux's lil' helper
Joined: 27 Aug 2013
Posts: 108
Location: Catalunya
|
| Posted: Sat Apr 19, 2014 11:59 pm Post subject: |
|
|
Thank you everyone, I've created the Bug 508196 and I'm keeping HW acceleration disabled until I downgrade.  |
|
| Back to top |
|
|
cyberjun
Apprentice
Joined: 06 Nov 2005
Posts: 293
|
| Posted: Sun Apr 20, 2014 6:03 am Post subject: |
|
|
I think something (udev probably) tries to insert nvidia module without enabling the Hardware through bbswitch when flash plays with HW acceleration enabled.
--cyberjun |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Sun Apr 20, 2014 10:50 am Post subject: |
|
|
I think the problem should be seen on the other side.
Not why someone try to load the nvidia module, but why someone has removed it, and who is that someone.
-> [last unloaded: nvidia] |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Sun Jun 01, 2014 4:23 pm Post subject: |
|
|
If you are still affect, can you try that as a workaround
|
|
| Back to top |
|
|
|
Multimedia
