Sie sind nicht angemeldet.

[gelöst] xy ungelöst

tux-fan

Fortgeschrittener

  • »tux-fan« ist männlich
  • »tux-fan« ist der Autor dieses Themas

Beiträge: 209

  • Nachricht senden

1

17.02.2015, 21:26

xy ungelöst

Hallo Forum,

kann jemand damit was anfangen?
Hab den kernel auf 3.18 aktualisiert nun das. Scheint mit nvidia zusammen zu hängen.

Mit journalctl -r finde ich das.

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84

Feb 17 21:09:19 tuxvaio kernel: ---[ end trace 2abe64800a68c6fe ]---                                                                                                                                 
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff81a9cd2d>] system_call_fastpath+0x16/0x1b                                                                                                                 
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff81182fa1>] SyS_ioctl+0x81/0xa0                                                                                                                            
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8116f85b>] ? do_sys_open+0x19b/0x220                                                                                                                      
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8117ff44>] ? putname+0x24/0x40                                                                                                                            
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8117fce1>] ? final_putname+0x21/0x50                                                                                                                      
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff81182d48>] do_vfs_ioctl+0x2c8/0x4a0                                                                                                                       
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff81180855>] ? do_filp_open+0x35/0xb0                                                                                                                       
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffffa05e4e00>] ? drm_noop+0x30/0x30 [drm]                                                                                                                     
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffffa05e49ec>] drm_ioctl+0x27c/0x660 [drm]                                                                                                                    
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8117f192>] ? path_openat+0xb2/0x6f0                                                                                                                       
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffffa05e4f7e>] drm_setversion+0x17e/0x190 [drm]
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8107c941>] warn_slowpath_fmt+0x41/0x50
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff8107c8d7>] warn_slowpath_common+0x77/0xa0
Feb 17 21:09:19 tuxvaio kernel:  [<ffffffff81a94632>] dump_stack+0x4e/0x71
Feb 17 21:09:19 tuxvaio kernel: Call Trace:
Feb 17 21:09:19 tuxvaio kernel:  ffff88004364fdf8 ffff8800bcd72000 ffff880100854e40 ffff8800bcd72000
Feb 17 21:09:19 tuxvaio kernel:  ffff88004364fd08 ffff88004364fcf8 ffffffff8107c8d7 ffff88004364fd68
Feb 17 21:09:19 tuxvaio kernel:  0000000000000009 ffff88004364fcb8 ffffffff81a94632 0000000000000007
Feb 17 21:09:19 tuxvaio kernel: Hardware name: Sony Corporation VPCF13E4E/VAIO, BIOS R0180Y9 09/03/2010
Feb 17 21:09:19 tuxvaio kernel: CPU: 2 PID: 20664 Comm: X Tainted: P        W  O   3.18.3-ck #1
Feb 17 21:09:19 tuxvaio kernel:  grace sunrpc jfs reiserfs sl811_hcd hid_generic xhci_plat_hcd ohci_pci ohci_hcd uhci_hcd sx8 imm parport pata_pcmcia pcmcia firewire_core xhci_pci xhci_hcd ehci_pci
Feb 17 21:09:19 tuxvaio kernel:  nvidia(PO) drm rfcomm ctr ccm bnep joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep sn
Feb 17 21:09:19 tuxvaio kernel: Modules linked in:
Feb 17 21:09:19 tuxvaio kernel: No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Feb 17 21:09:19 tuxvaio kernel: WARNING: CPU: 2 PID: 20664 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190 [drm]()
Feb 17 21:09:19 tuxvaio kernel: ------------[ cut here ]------------
Feb 17 21:09:18 tuxvaio acpid[2415]: 1 client rule loaded
Feb 17 21:09:18 tuxvaio acpid[2415]: client connected from 20664[0:0]
Feb 17 21:09:18 tuxvaio kernel: ---[ end trace 2abe64800a68c6fd ]---
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81a9cd2d>] system_call_fastpath+0x16/0x1b
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81182fa1>] SyS_ioctl+0x81/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8116f85b>] ? do_sys_open+0x19b/0x220
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117ff44>] ? putname+0x24/0x40
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117fce1>] ? final_putname+0x21/0x50
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81182d48>] do_vfs_ioctl+0x2c8/0x4a0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81180855>] ? do_filp_open+0x35/0xb0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e4e00>] ? drm_noop+0x30/0x30 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8118076a>] ? user_path_at_empty+0x5a/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e49ec>] drm_ioctl+0x27c/0x660 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117f192>] ? path_openat+0xb2/0x6f0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e4f7e>] drm_setversion+0x17e/0x190 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8107c941>] warn_slowpath_fmt+0x41/0x50
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8107c8d7>] warn_slowpath_common+0x77/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81a94632>] dump_stack+0x4e/0x71
Feb 17 21:09:18 tuxvaio kernel: Call Trace:
Feb 17 21:09:18 tuxvaio kernel:  ffff88004364fdf8 ffff8800bcd72000 ffff88009b2b4f00 ffff8800bcd72000
Feb 17 21:09:18 tuxvaio kernel:  ffff88004364fd08 ffff88004364fcf8 ffffffff8107c8d7 ffff88004364fd68
Feb 17 21:09:18 tuxvaio kernel:  0000000000000009 ffff88004364fcb8 ffffffff81a94632 0000000000000007
Feb 17 21:09:18 tuxvaio kernel: Hardware name: Sony Corporation VPCF13E4E/VAIO, BIOS R0180Y9 09/03/2010
Feb 17 21:09:18 tuxvaio kernel: CPU: 2 PID: 20664 Comm: X Tainted: P        W  O   3.18.3-ck #1
Feb 17 21:09:18 tuxvaio kernel:  fuse xfs nfs lockd grace sunrpc jfs reiserfs sl811_hcd hid_generic xhci_plat_hcd ohci_pci ohci_hcd uhci_hcd sx8 imm parport pata_pcmcia pcmcia firewire_core xhci_pc
Feb 17 21:09:18 tuxvaio kernel: Modules linked in: nvidia(PO) drm rfcomm ctr ccm bnep joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_
Feb 17 21:09:18 tuxvaio kernel: No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Feb 17 21:09:18 tuxvaio kernel: WARNING: CPU: 2 PID: 20664 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190 [drm]()
Feb 17 21:09:18 tuxvaio kernel: ------------[ cut here ]------------
Feb 17 21:09:18 tuxvaio kernel: ---[ end trace 2abe64800a68c6fc ]---
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81a9cd2d>] system_call_fastpath+0x16/0x1b
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81182fa1>] SyS_ioctl+0x81/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8116f85b>] ? do_sys_open+0x19b/0x220
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117ff44>] ? putname+0x24/0x40
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117fce1>] ? final_putname+0x21/0x50
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81182d48>] do_vfs_ioctl+0x2c8/0x4a0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81180855>] ? do_filp_open+0x35/0xb0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e4e00>] ? drm_noop+0x30/0x30 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8118076a>] ? user_path_at_empty+0x5a/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e49ec>] drm_ioctl+0x27c/0x660 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8117f192>] ? path_openat+0xb2/0x6f0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffffa05e4f7e>] drm_setversion+0x17e/0x190 [drm]
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8107c941>] warn_slowpath_fmt+0x41/0x50
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff8107c8d7>] warn_slowpath_common+0x77/0xa0
Feb 17 21:09:18 tuxvaio kernel:  [<ffffffff81a94632>] dump_stack+0x4e/0x71
Feb 17 21:09:18 tuxvaio kernel: Call Trace:
Feb 17 21:09:18 tuxvaio kernel:  ffff88004364fdf8 ffff8800bcd72000 ffff88009b2b4f00 ffff8800bcd72000
Feb 17 21:09:18 tuxvaio kernel:  ffff88004364fd08 ffff88004364fcf8 ffffffff8107c8d7 ffff88004364fd68
Feb 17 21:09:18 tuxvaio kernel:  0000000000000009 ffff88004364fcb8 ffffffff81a94632 0000000000000007
Feb 17 21:09:18 tuxvaio kernel: Hardware name: Sony Corporation VPCF13E4E/VAIO, BIOS R0180Y9 09/03/2010
Feb 17 21:09:18 tuxvaio kernel: CPU: 2 PID: 20664 Comm: X Tainted: P        W  O   3.18.3-ck #1
Feb 17 21:09:18 tuxvaio kernel:  grace sunrpc jfs reiserfs sl811_hcd hid_generic xhci_plat_hcd ohci_pci ohci_hcd uhci_hcd sx8 imm parport pata_pcmcia pcmcia firewire_core xhci_pci xhci_hcd ehci_pci
Feb 17 21:09:18 tuxvaio kernel:  nvidia(PO) drm rfcomm ctr ccm bnep joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep sn
Feb 17 21:09:18 tuxvaio kernel: Modules linked in:
Feb 17 21:09:18 tuxvaio kernel: No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Feb 17 21:09:18 tuxvaio kernel: WARNING: CPU: 2 PID: 20664 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190 [drm]()
Feb 17 21:09:18 tuxvaio kernel: ------------[ cut here ]------------
Letz fetz, sprach der Frosch und sprang in den Ventilator.....

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »tux-fan« (18.02.2015, 20:04)

dyle

Erleuchteter

  • »dyle« ist männlich

Beiträge: 4 869

  • Nachricht senden

2

18.02.2015, 09:43

IIRC ist der aktuelle nvidia-driver noch nicht mir kernel-3.18 und darüber kompatibel.

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

$ grep -A 10 3.18 /usr/portage/x11-drivers/nvidia-drivers/nvidia-drivers-346.35.ebuild 
        if use kernel_linux && kernel_is ge 3 18 ; then
                ewarn "Gentoo supports kernels which are supported by NVIDIA"
                ewarn "which are limited to the following kernels:"
                ewarn "<sys-kernel/gentoo-sources-3.18"
                ewarn "<sys-kernel/vanilla-sources-3.18"
                ewarn ""
                ewarn "You are free to utilize epatch_user to provide whatever"
                ewarn "support you feel is appropriate, but will not receive"
                ewarn "support as a result of those changes."
                ewarn ""
                ewarn "Do not file a bug report about this."
        fi

        # Since Nvidia ships 3 different series of drivers, we need to give the user
        # some kind of guidance as to what version they should install. This tries


edit: diese Meldung solltest du aber bekommen, wenn du nach einem neuen Kernel ein

Quellcode

 
1

# emerge @module-rebuild
absetzt.
http://www.dyle.org
IM-Account (Jabber!) sind auf meiner HP ...
There is no place like /home

http://www.gentooforum.de
http://www.gentoofreunde.org

<div>how to annoy a web developer?</span>

remo

Anfänger

Beiträge: 8

  • Nachricht senden

3

18.02.2015, 13:36

naja der 3.18 ist noch bissl verbuggt.
PC-CPU: Intel Core i7-4771 CPU @ 3.50GHz
PC-RAM: 1200MB
Linux -OS: Gentoo
Linux-Kernel: x86_64 Linux 3.18.7-gentoo
Linux-WM: herbstluftwm

boospy

Meister

  • »boospy« ist männlich

Beiträge: 1 518

  • Nachricht senden

4

18.02.2015, 17:12

Tja, deswegen ist ja auch 3.17.8-r1 stable ;)
Gentoo Can Do!

Wiki auf: http://deepdoc.at

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

5

18.02.2015, 17:29

Bezüglich

Zitat von »tux-fan«

Quellcode

 
1
2

Feb 17 21:09:18 tuxvaio kernel: No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Feb 17 21:09:18 tuxvaio kernel: WARNING: CPU: 2 PID: 20664 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190 [drm]()
sollte der im https://bugs.gentoo.org/show_bug.cgi?id=532082#c5 verlinkte Patch helfen.

tux-fan

Fortgeschrittener

  • »tux-fan« ist männlich
  • »tux-fan« ist der Autor dieses Themas

Beiträge: 209

  • Nachricht senden

6

18.02.2015, 19:30

ok danke euch für die vielen Antworten. Werde mal den patch versuchen.
Letz fetz, sprach der Frosch und sprang in den Ventilator.....

tux-fan

Fortgeschrittener

  • »tux-fan« ist männlich
  • »tux-fan« ist der Autor dieses Themas

Beiträge: 209

  • Nachricht senden

7

18.02.2015, 20:03

Letz fetz, sprach der Frosch und sprang in den Ventilator.....

Ähnliche Themen

Verwendete Tags

kernel nvidia

Häufig verwendete Suchbegriffe:

www.my-echo.de mobile-parts-discount.net Andere Architekturen Lob & Kritik Gentoo Linux bka trojaner finden Emerge Probleme softwaregarage.de Drucker Linux Computer und Notebooks