Autore Topic: problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2  (Letto 4326 volte)

Offline dinolib

  • *
  • Post: 3226
  • Reputazione: 110
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #30 il: 14 Febbraio 2012 ore 11:16 »
anche se non ci sono errori. Magari sapere le ultime cose eseguite è utile x capire dove si blocca.

Offline kdekda

  • *
  • Post: 441
  • Reputazione: 22
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #31 il: 15 Febbraio 2012 ore 12:20 »
rieccomi, dato che non ne venivo a capo mi sono impacchettato i driver 290.10 (quelli che avevo prima): funzionano perfettamente! se serve posso postarne il PKGBUILD.

Cmq, questi sono le righe relative ai vari blocchi recuperate dai vari log:
kernel.log (dove si vede anche il crash di vlc dovuti ai driver video)
Codice: [Seleziona]
...Feb 13 22:17:00 chakra-pc kernel: [ 2149.905654] vlc[2887]: segfault at c ip b278bea3 sp ac9110f0 error 6 in libnvidia-tls.so.295.20[b278b000+3000]
Feb 13 23:18:47 chakra-pc kernel: [ 5856.656992] wlan0: deauthenticating from 00:19:3e:3e:89:be by local choice (reason=3)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.676283] cfg80211: Calling CRDA to update world regulatory domain
Feb 13 23:18:47 chakra-pc kernel: [ 5856.690737] b44 ssb0:0: eth0: powering down PHY
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701553] cfg80211: World regulatory domain updated:
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701556] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701559] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701562] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701564] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701567] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701570] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:48 chakra-pc kernel: [ 5858.096862] EXT4-fs (sda1): re-mounted. Opts: commit=0
...
messages.log
Codice: [Seleziona]
Feb 13 23:18:08 chakra-pc dbus[703]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 13 23:18:08 chakra-pc dbus[703]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> sleep requested (sleeping: no  enabled: yes)
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> sleeping or disabling...
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (wlan0): now unmanaged
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (wlan0): deactivating device (reason 'sleeping') [37]
Feb 13 23:18:47 chakra-pc avahi-daemon[754]: Withdrawing address record for 192.168.1.101 on wlan0.
Feb 13 23:18:47 chakra-pc avahi-daemon[754]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.101.
Feb 13 23:18:47 chakra-pc avahi-daemon[754]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (wlan0): cleaning up...
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (wlan0): taking down device.
Feb 13 23:18:47 chakra-pc kernel: [ 5856.676283] cfg80211: Calling CRDA to update world regulatory domain
Feb 13 23:18:47 chakra-pc avahi-daemon[754]: Withdrawing address record for fe80::21c:bfff:fe37:549 on wlan0.
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (eth0): now unmanaged
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (eth0): cleaning up...
Feb 13 23:18:47 chakra-pc NetworkManager[729]: <info> (eth0): taking down device.
Feb 13 23:18:47 chakra-pc dbus[703]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.690737] b44 ssb0:0: eth0: powering down PHY
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701553] cfg80211: World regulatory domain updated:
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701556] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701559] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701562] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701564] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701567] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc kernel: [ 5856.701570] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 13 23:18:47 chakra-pc dbus[703]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 13 23:18:48 chakra-pc kernel: [ 5858.096862] EXT4-fs (sda1): re-mounted. Opts: commit=0

altri log possono servire? (quello dello xorg  ormai è già riferito alla situazione attuale con i driver 290)
« Ultima modifica: 15 Febbraio 2012 ore 12:30 da kdekda »

Offline kdekda

  • *
  • Post: 441
  • Reputazione: 22
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #32 il: 06 Marzo 2012 ore 22:40 »
senza pensarci ho aggiornato (doh!) anche i driver nvidia..
Ora con i driver 295.20 e kernel 3.2.8 (ma anche con il kernel lts) mi è impossibile spegnere il pc, mentre la sospensione funziona. Ecco un log di quanto succede quando provo a spegnere (sia tramite gui che tramite terminale)
Codice: [Seleziona]
Mar  5 11:25:03 chakra-pc kernel: [ 2116.238120] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=240034 jiffies)
Mar  5 11:25:03 chakra-pc kernel: [ 2116.238130] INFO: Stall ended before state dump start
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313050] INFO: task dhcpcd:2140 blocked for more than 120 seconds.
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313053] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313056] dhcpcd          D 00000001     0  2140    536 0x00000004
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313061]  f2161da4 00000086 f4cc2900 00000001 f4cc2900 ed7236aa 000001c3 000000c3
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313067]  c06ba300 f2161dac c06ba300 f5807300 edafcd20 edafd180 00000212 00000212
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313073]  f2161d98 c038c82d 00000212 f2161dec 219a9ae9 371ebb2f d9605479 8a4c5761
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313079] Call Trace:
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313087]  [<c038c82d>] ? mix_pool_bytes_extract+0x11d/0x130
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313092]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313095]  [<c04bf175>] schedule_timeout+0x265/0x2e0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313099]  [<c04be007>] wait_for_common+0x97/0x120
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313103]  [<c0143a80>] ? try_to_wake_up+0x210/0x210
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313107]  [<c01bba00>] ? __call_rcu+0x120/0x120
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313111]  [<c04be0a7>] wait_for_completion+0x17/0x20
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313114]  [<c01650d4>] wait_rcu_gp+0x34/0x40
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313117]  [<c01650e0>] ? wait_rcu_gp+0x40/0x40
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313120]  [<c01ba5d2>] synchronize_rcu+0x22/0x30
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313124]  [<c03e2c06>] synchronize_net+0x16/0x30
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313127]  [<c04957a9>] __unregister_prot_hook+0x89/0xb0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313131]  [<c0497544>] packet_do_bind.part.38+0xd4/0xf0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313134]  [<c049769c>] packet_bind+0x9c/0xa0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313137]  [<c03d42d8>] sys_bind+0xb8/0xe0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313141]  [<c03d531b>] sys_socketcall+0xab/0x2c0
Mar  5 11:25:48 chakra-pc kernel: [ 2160.313144]  [<c04c1d5f>] sysenter_do_call+0x12/0x28
Mar  5 11:26:44 chakra-pc dbus[510]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar  5 11:26:44 chakra-pc dbus[510]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar  5 11:27:34 chakra-pc kernel: [ 2267.000351] b44 ssb0:0: eth0: Link is down
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314081] INFO: task dhcpcd:2140 blocked for more than 120 seconds.
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314087] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314091] dhcpcd          D 00000001     0  2140    536 0x00000004
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314100]  f2161da4 00000086 f4cc2900 00000001 f4cc2900 ed7236aa 000001c3 000000c3
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314111]  c06ba300 f2161dac c06ba300 f5807300 edafcd20 edafd180 00000212 00000212
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314122]  f2161d98 c038c82d 00000212 f2161dec 219a9ae9 371ebb2f d9605479 8a4c5761
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314134] Call Trace:
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314146]  [<c038c82d>] ? mix_pool_bytes_extract+0x11d/0x130
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314154]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314159]  [<c04bf175>] schedule_timeout+0x265/0x2e0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314167]  [<c04be007>] wait_for_common+0x97/0x120
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314174]  [<c0143a80>] ? try_to_wake_up+0x210/0x210
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314181]  [<c01bba00>] ? __call_rcu+0x120/0x120
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314187]  [<c04be0a7>] wait_for_completion+0x17/0x20
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314193]  [<c01650d4>] wait_rcu_gp+0x34/0x40
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314198]  [<c01650e0>] ? wait_rcu_gp+0x40/0x40
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314204]  [<c01ba5d2>] synchronize_rcu+0x22/0x30
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314210]  [<c03e2c06>] synchronize_net+0x16/0x30
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314216]  [<c04957a9>] __unregister_prot_hook+0x89/0xb0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314222]  [<c0497544>] packet_do_bind.part.38+0xd4/0xf0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314228]  [<c049769c>] packet_bind+0x9c/0xa0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314233]  [<c03d42d8>] sys_bind+0xb8/0xe0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314240]  [<c03d531b>] sys_socketcall+0xab/0x2c0
Mar  5 11:27:48 chakra-pc kernel: [ 2280.314246]  [<c04c1d5f>] sysenter_do_call+0x12/0x28
Mar  5 11:28:04 chakra-pc kernel: [ 2296.270232] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=420066 jiffies)
Mar  5 11:28:04 chakra-pc kernel: [ 2296.270242] INFO: Stall ended before state dump start
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314058] INFO: task plasma-desktop:1456 blocked for more than 120 seconds.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314063] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314066] plasma-desktop  D f227fdf8     0  1456      1 0x00000004
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314071]  f227fe08 00000086 00000002 f227fdf8 c016ff0a 00001000 f63558a0 00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314077]  c06ba300 f63558c0 c06ba300 f5807300 f1abe760 c05eb020 c04bffd6 f53b2080
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314084]  c061062c 00000292 00b96930 c029552e 0000001c 000000d0 c02954b6 c03d6bec
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314090] Call Trace:
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314098]  [<c016ff0a>] ? in_group_p+0x2a/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314103]  [<c04bffd6>] ? __mutex_lock_slowpath+0x216/0x2f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314108]  [<c029552e>] ? sysfs_open_file+0x18e/0x250
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314111]  [<c02954b6>] ? sysfs_open_file+0x116/0x250
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314115]  [<c03d6bec>] ? sk_prot_alloc+0x2c/0x210
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314118]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314121]  [<c04bfee0>] __mutex_lock_slowpath+0x120/0x2f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314124]  [<c04c00c0>] mutex_lock+0x10/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314128]  [<c03f3b72>] rtnl_lock+0x12/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314132]  [<c049aa35>] wext_handle_ioctl+0x55/0x220
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314136]  [<c03e8e49>] dev_ioctl+0xb9/0x530
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314139]  [<c03d6c1c>] ? sk_prot_alloc+0x5c/0x210
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314144]  [<c02ac6f4>] ? security_file_alloc+0x14/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314148]  [<c02380fe>] ? get_empty_filp+0x8e/0x1c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314151]  [<c03d2320>] ? sock_fasync+0x90/0x90
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314154]  [<c03d24d3>] sock_ioctl+0x1b3/0x290
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314157]  [<c03d2320>] ? sock_fasync+0x90/0x90
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314160]  [<c0246b36>] do_vfs_ioctl+0x86/0x570
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314163]  [<c02352fc>] ? fd_install+0x4c/0x60
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314166]  [<c03d2fb4>] ? sock_map_fd+0x24/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314169]  [<c03d405d>] ? sys_socket+0x4d/0x80
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314172]  [<c03d52e2>] ? sys_socketcall+0x72/0x2c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314175]  [<c0238356>] ? fget_light+0x76/0xe0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314178]  [<c024708f>] sys_ioctl+0x6f/0x80
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314182]  [<c04c1d5f>] sysenter_do_call+0x12/0x28
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314185]  [<c04c0000>] ? __mutex_lock_slowpath+0x240/0x2f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314189] INFO: task dropbox:1740 blocked for more than 120 seconds.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314191] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314193] dropbox         D 00000000     0  1740   1345 0x00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314197]  f1b9bcfc 00000086 00000100 00000000 00000001 ddc2188c 0000020f f64299c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314203]  c06ba300 f1b9bcf0 c06ba300 f5807300 f1eb55e0 f4952bc0 00000000 00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314209]  f21ce800 000f0101 00000000 00000001 eb23d6c0 00070001 80150008 eb23d180
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314214] Call Trace:
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314218]  [<c03db29a>] ? skb_release_data+0xaa/0xb0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314221]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314224]  [<c04bfee0>] __mutex_lock_slowpath+0x120/0x2f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314227]  [<c04c00c0>] mutex_lock+0x10/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314230]  [<c03f3b72>] rtnl_lock+0x12/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314233]  [<c03f3b90>] rtnetlink_rcv+0x10/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314236]  [<c04087dd>] netlink_unicast+0x24d/0x290
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314239]  [<c0408ab8>] netlink_sendmsg+0x1e8/0x320
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314242]  [<c03d2ae7>] sock_sendmsg+0xf7/0x120
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314247]  [<c02f1119>] ? copy_to_user+0x39/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314251]  [<c02265c1>] ? __kmalloc+0x191/0x1e0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314255]  [<c01339a5>] ? __wake_up+0x45/0x60
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314258]  [<c02f1265>] ? _copy_from_user+0x35/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314261]  [<c03d3ffc>] ? move_addr_to_kernel+0x4c/0x60
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314264]  [<c03d4a1e>] sys_sendto+0x10e/0x150
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314268]  [<c0238250>] ? alloc_file+0x20/0xb0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314271]  [<c03d2f24>] ? sock_alloc_file+0x84/0xf0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314274]  [<c02352fc>] ? fd_install+0x4c/0x60
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314276]  [<c03d2fb4>] ? sock_map_fd+0x24/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314279]  [<c03d5420>] sys_socketcall+0x1b0/0x2c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314283]  [<c04c1d5f>] sysenter_do_call+0x12/0x28
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314295] INFO: task kworker/1:2:2139 blocked for more than 120 seconds.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314297] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314299] kworker/1:2     D ed9dde98     0  2139      2 0x00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314303]  ed9ddea8 00000046 00000002 ed9dde98 00100100 00200200 c06348f8 00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314308]  c06ba300 ed9dde48 c06ba300 f5a07300 edafc8c0 f545b020 c04bffd6 00000000
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314314]  c05f266c 00000246 edafc8c0 22222222 22222222 c05f2664 ed9dde88 00000246
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314320] Call Trace:
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314323]  [<c04bffd6>] ? __mutex_lock_slowpath+0x216/0x2f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314327]  [<c04bfdbd>] ? mutex_unlock+0xd/0x10
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314330]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314333]  [<c01bb65d>] synchronize_rcu_expedited+0xbd/0x1e0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314337]  [<c0168080>] ? abort_exclusive_wait+0x80/0x80
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314341]  [<c03e2c15>] synchronize_net+0x25/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314345]  [<c03ff80c>] dev_deactivate_many+0x1dc/0x1f0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314348]  [<c03ff844>] dev_deactivate+0x24/0x40
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314351]  [<c03f58ea>] linkwatch_do_dev+0x6a/0xb0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314354]  [<c03f5bab>] __linkwatch_run_queue+0xcb/0x180
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314357]  [<c03f5c80>] linkwatch_event+0x20/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314360]  [<c0162c3a>] process_one_work+0xfa/0x3e0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314364]  [<c0160e07>] ? destroy_worker+0x77/0xa0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314368]  [<c03f5c60>] ? __linkwatch_run_queue+0x180/0x180
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314371]  [<c0163404>] worker_thread+0x124/0x2c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314373]  [<c01632e0>] ? manage_workers.isra.27+0x1e0/0x1e0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314377]  [<c01679ad>] kthread+0x6d/0x80
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314380]  [<c0167940>] ? kthread_worker_fn+0x160/0x160
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314383]  [<c04c22fe>] kernel_thread_helper+0x6/0x10
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314385] INFO: task dhcpcd:2140 blocked for more than 120 seconds.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314387] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314389] dhcpcd          D 00000001     0  2140    536 0x00000004
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314393]  f2161da4 00000086 f4cc2900 00000001 f4cc2900 ed7236aa 000001c3 000000c3
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314399]  c06ba300 f2161dac c06ba300 f5807300 edafcd20 edafd180 00000212 00000212
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314405]  f2161d98 c038c82d 00000212 f2161dec 219a9ae9 371ebb2f d9605479 8a4c5761
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314410] Call Trace:
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314414]  [<c038c82d>] ? mix_pool_bytes_extract+0x11d/0x130
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314418]  [<c04bebc5>] schedule+0x35/0x50
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314420]  [<c04bf175>] schedule_timeout+0x265/0x2e0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314424]  [<c04be007>] wait_for_common+0x97/0x120
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314428]  [<c0143a80>] ? try_to_wake_up+0x210/0x210
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314431]  [<c01bba00>] ? __call_rcu+0x120/0x120
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314434]  [<c04be0a7>] wait_for_completion+0x17/0x20
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314437]  [<c01650d4>] wait_rcu_gp+0x34/0x40
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314440]  [<c01650e0>] ? wait_rcu_gp+0x40/0x40
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314443]  [<c01ba5d2>] synchronize_rcu+0x22/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314446]  [<c03e2c06>] synchronize_net+0x16/0x30
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314449]  [<c04957a9>] __unregister_prot_hook+0x89/0xb0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314452]  [<c0497544>] packet_do_bind.part.38+0xd4/0xf0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314455]  [<c049769c>] packet_bind+0x9c/0xa0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314458]  [<c03d42d8>] sys_bind+0xb8/0xe0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314461]  [<c03d531b>] sys_socketcall+0xab/0x2c0
Mar  5 11:29:48 chakra-pc kernel: [ 2400.314464]  [<c04c1d5f>] sysenter_do_call+0x12/0x28
Vorrei cercare di capire perchè questi problemi.. forza, brain storming!!
a
(con i driver open nessun problema, poi riproverò con i 290.10)

Offline vellerofonte

  • *
  • Post: 1374
  • Reputazione: 58
  • #Chakra: Kde for life
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #33 il: 06 Marzo 2012 ore 22:49 »
E' ormai lampante come gli ultimi aggiornamenti abbiano fatto letteralmente un macello dal punto di vista driver  :o

Ci sono svariati post di problemi riconducibili ai driver e che si risolvono installando gli open (come ho fatto io tra l'altro)...

A questo punto spero vivamente che lo sviluppo degli open sia portato avanti celermente, sembra siano ormai ad un passo dall'implementare anche una gestione energetica degna di tale nome.

Offline kdekda

  • *
  • Post: 441
  • Reputazione: 22
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #34 il: 06 Marzo 2012 ore 22:59 »
è appunto la gestione energetica che mi preoccupa, il mio portatile non ha mai fatto così tanto rumore!!

Offline Cylon

  • *
  • Post: 1960
  • Reputazione: 78
  • CYbernetic Life fOrm Node
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #35 il: 06 Marzo 2012 ore 23:04 »
avete provato anche con i driver lts?
We are the Cylons. Lower your firewalll and surrender.Your PC will adapt to service our GNU/Linux systems. Resistance is futile. Extermination of human race has began!
                                                                     Non rispondo a PM

Offline vellerofonte

  • *
  • Post: 1374
  • Reputazione: 58
  • #Chakra: Kde for life
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #36 il: 06 Marzo 2012 ore 23:44 »
avete provato anche con i driver lts?

Domanda credo banale, ma i driver LTS possono essere installati indipendentemente dal kernel o richiedono di essere installati su un kernel LTS?

Offline kdekda

  • *
  • Post: 441
  • Reputazione: 22
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #37 il: 06 Marzo 2012 ore 23:50 »
credo che dipendano dal kernel lts. Cmq sono la tessa versione driver (295.20 se non ricordo male).


E si, stessi problemi!

Offline Cylon

  • *
  • Post: 1960
  • Reputazione: 78
  • CYbernetic Life fOrm Node
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #38 il: 06 Marzo 2012 ore 23:51 »
basta vedere tra le dipendenze dei pacchetti dei dirver lts,,, quindi si, dipendono dal kernel-lts.

ma poi che senso ha mettere i driver lts della stessa versione dei driver "normali"....

PS: ma per chakra non esiste un repository dove sono salvate le vecchie versioni dei pacchetti, come in arch, da dove poi fare il downgrade?
« Ultima modifica: 06 Marzo 2012 ore 23:57 da Cylon »
We are the Cylons. Lower your firewalll and surrender.Your PC will adapt to service our GNU/Linux systems. Resistance is futile. Extermination of human race has began!
                                                                     Non rispondo a PM

Offline kdekda

  • *
  • Post: 441
  • Reputazione: 22
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #39 il: 07 Marzo 2012 ore 08:21 »
no, ma non è un problema avere vecchi pacchetti, io per esempio mi sono impacchettato i 290.10 che andavano. Sarebbe da capire perchè ci sono questi problemi!

Offline vellerofonte

  • *
  • Post: 1374
  • Reputazione: 58
  • #Chakra: Kde for life
    • Mostra profilo
Re:problemi dopo aggiornamento driver nvidia 295.17 e kernel 3.2
« Risposta #40 il: 07 Marzo 2012 ore 09:18 »
Sarebbe da capire perchè ci sono questi problemi!

Esatto  ;)

Intanto spero ci mettano una pezza al più presto, la troppa disinvoltura nel rilasciare aggiornamenti ballerini potrebbe allontanare diversi utenti, in particolare i nuovissimi.

 

Template by Homey | Sito ufficiale | Disclaimer