Debian-facile

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

[RESOLU] problème de sortie veille ou hibernation

bonjour, 

Je rencontre un problème avec le pilote graphique nouveau,  ce n'est pas systématique mais très souvent, blocage écran à la sortie veille ou hibernation, semble t'il un conflit plage mémoire.


syslog

'sleeping') [20 10 37]
Feb 18 08:14:57 debian NetworkManager[706]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 18 08:14:57 debian kernel: [191029.687414] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 18 08:14:57 debian kernel: [191029.688514] tg3 0000:05:00.0: irq 47 for MSI/MSI-X
Feb 18 08:14:57 debian NetworkManager[706]: <info> (eth0): preparing device
Feb 18 08:14:57 debian kernel: [191029.797056] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 18 08:14:57 debian kernel: [191029.808398] iwlwifi 0000:04:00.0: L1 Enabled - LTR Disabled
Feb 18 08:14:57 debian kernel: [191029.811340] iwlwifi 0000:04:00.0: Radio type=0x1-0x2-0x0
Feb 18 08:14:57 debian kernel: [191029.911892] iwlwifi 0000:04:00.0: L1 Enabled - LTR Disabled
Feb 18 08:14:57 debian kernel: [191029.914873] iwlwifi 0000:04:00.0: Radio type=0x1-0x2-0x0
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0): preparing device
Feb 18 08:14:57 debian kernel: [191029.945064] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 18 08:14:57 debian NetworkManager[706]: <info> NetworkManager state is now DISCONNECTED
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0) supports 5 scan SSIDs
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: starting -> ready
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: ready -> disconnected
Feb 18 08:14:57 debian NetworkManager[706]: <info> (wlan0) supports 5 scan SSIDs
Feb 18 08:15:00 debian NetworkManager[706]: <info> Auto-activating connection 'dlink'.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) starting connection 'dlink'
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> NetworkManager state is now CONNECTING
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0/wireless): access point 'dlink' has security, but secrets are required.
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0/wireless): connection 'dlink' has security, and secrets exist.  No new secrets needed.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Config: added 'ssid' value 'dlink'
Feb 18 08:15:00 debian NetworkManager[706]: <info> Config: added 'scan_ssid' value '1'
Feb 18 08:15:00 debian NetworkManager[706]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 18 08:15:00 debian NetworkManager[706]: <info> Config: added 'psk' value '<omitted>'
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: disconnected -> inactive
Feb 18 08:15:00 debian NetworkManager[706]: <info> Config: set interface ap_scan to 1
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: SME: Trying to authenticate with 34:08:04:dd:45:9c (SSID='dlink' freq=2452 MHz)
Feb 18 08:15:00 debian kernel: [191033.075972] wlan0: authenticate with 34:08:04:dd:45:9c
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: Trying to associate with 34:08:04:dd:45:9c (SSID='dlink' freq=2452 MHz)
Feb 18 08:15:00 debian kernel: [191033.077181] wlan0: send auth to 34:08:04:dd:45:9c (try 1/3)
Feb 18 08:15:00 debian kernel: [191033.079561] wlan0: authenticated
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: inactive -> associating
Feb 18 08:15:00 debian kernel: [191033.080050] wlan0: associate with 34:08:04:dd:45:9c (try 1/3)
Feb 18 08:15:00 debian kernel: [191033.084326] wlan0: RX AssocResp from 34:08:04:dd:45:9c (capab=0xc31 status=0 aid=3)
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: Associated with 34:08:04:dd:45:9c
Feb 18 08:15:00 debian kernel: [191033.094176] wlan0: associated
Feb 18 08:15:00 debian kernel: [191033.094242] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 18 08:15:00 debian kernel: [191033.094325] cfg80211: Calling CRDA for country: GB
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Feb 18 08:15:00 debian kernel: [191033.100424] cfg80211: Regulatory domain changed to country: GB
Feb 18 08:15:00 debian kernel: [191033.100430] cfg80211:  DFS Master region: ETSI
Feb 18 08:15:00 debian kernel: [191033.100433] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 18 08:15:00 debian kernel: [191033.100438] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 18 08:15:00 debian kernel: [191033.100443] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 18 08:15:00 debian kernel: [191033.100448] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 18 08:15:00 debian kernel: [191033.100452] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
Feb 18 08:15:00 debian kernel: [191033.100457] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: WPA: Key negotiation completed with 34:08:04:dd:45:9c [PTK=CCMP GTK=TKIP]
Feb 18 08:15:00 debian wpa_supplicant[995]: wlan0: CTRL-EVENT-CONNECTED - Connection to 34:08:04:dd:45:9c completed [id=0 id_str=]
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'dlink'.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb 18 08:15:00 debian NetworkManager[706]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb 18 08:15:00 debian NetworkManager[706]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Feb 18 08:15:00 debian avahi-daemon[721]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.102.
Feb 18 08:15:00 debian avahi-daemon[721]: New relevant interface wlan0.IPv4 for mDNS.
Feb 18 08:15:00 debian avahi-daemon[721]: Registering new address record for 192.168.0.102 on wlan0.IPv4.
Feb 18 08:15:01 debian NetworkManager[706]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 18 08:15:01 debian NetworkManager[706]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Feb 18 08:15:01 debian NetworkManager[706]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 18 08:15:01 debian NetworkManager[706]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 18 08:15:01 debian NetworkManager[706]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb 18 08:15:01 debian NetworkManager[706]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb 18 08:15:01 debian NetworkManager[706]: <info> Policy set 'dlink' (wlan0) as default for IPv4 routing and DNS.
Feb 18 08:15:01 debian NetworkManager[706]: <info> Activation (wlan0) successful, device activated.
Feb 18 08:15:01 debian dbus[724]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 18 08:15:01 debian dbus[724]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 18 08:15:01 debian nm-dispatcher: Dispatching action 'up' for wlan0
Feb 18 08:15:02 debian avahi-daemon[721]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::222:faff:fe27:aaca.
Feb 18 08:15:02 debian avahi-daemon[721]: New relevant interface wlan0.IPv6 for mDNS.
Feb 18 08:15:02 debian avahi-daemon[721]: Registering new address record for fe80::222:faff:fe27:aaca on wlan0.*.
Feb 18 08:15:03 debian sshd[9127]: Received SIGHUP; restarting.
 

dans kern.log  on peut y voir ces lignes, conflit plage mémoire    PMBA et GPIO, existe t'il une technique particulière pour résoudre ce problème ACPI ?  je n'avais pas ce problème sous Wheezy.

Feb 18 08:31:46 debian kernel: [   14.605655] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMBA) (20140424/utaddress-254)
Feb 18 08:31:46 debian kernel: [   14.605664] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 18 08:31:46 debian kernel: [   14.605669] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053B (\GPIO) (20140424/utaddress-254)
Feb 18 08:31:46 debian kernel: [   14.605673] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 18 08:31:46 debian kernel: [   14.605675] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053B (\GPIO) (20140424/utaddress-254)
Feb 18 08:31:46 debian kernel: [   14.605679] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 18 08:31:46 debian kernel: [   14.605680] lpc_ich: Resource conflict(s) found affecting gpio_ich

Dernière modification par nikau (21-02-2016 14:39:17)

anonyme

Invité

Re : [RESOLU] problème de sortie veille ou hibernation

un probleme avec ta carte graphique , essaie d installer le paquet nvidia-detect

apt-get install nvidia-detect
 

et lance en console

nvidia-detect
 

poste le retour ici

si tu connais ta carte , donne la reference aussi (nvidia-detect devrait nous le dire aussi )

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

voilà le retour,  nvidia-detect, il recommande d'installer nvidia-driver, je vais faire ça alors.. merci je ne connaissais pas nvidia-detect.. @+

Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96M [GeForce GT 130M] [10de:0652] (rev a1)
Your card is supported by the default drivers and legacy driver series 304.
It is recommended to install the
    nvidia-driver
package.

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

bon le driver n'est plus nouveau mais nvidia,  (j'avais un écran noir, j'ai refais xorg.conf en suivant le wiki en mode console tty  (plus de Xserver) et heureusement un nomodeset m'a sorti d'affaire, pourtant  lsmod m'indique que les autres modules sont bien chargés ...bizarre mais bon...

lsmod

Module                  Size  Used by
ctr                    12927  1
ccm                    17577  1
binfmt_misc            16949  1
nf_conntrack_netlink    35433  0
nf_conntrack           87424  1 nf_conntrack_netlink
nfnetlink              12989  6 nf_conntrack_netlink
dm_crypt               22595  1
xts                    12679  1
gf128mul               12970  1 xts
algif_skcipher         13008  0
af_alg                 12988  1 algif_skcipher
dm_mod                 89405  3 dm_crypt
nvidia              10520178  32
joydev                 17063  0
uvcvideo               79005  0
videobuf2_vmalloc      12816  1 uvcvideo
videobuf2_memops       12519  1 videobuf2_vmalloc
iTCO_wdt               12831  0
coretemp               12820  0
videobuf2_core         47787  1 uvcvideo
acer_wmi               30174  0
iTCO_vendor_support    12649  1 iTCO_wdt
v4l2_common            12995  1 videobuf2_core
snd_usb_audio         135354  1
sparse_keymap          12818  1 acer_wmi
mxm_wmi                12515  0
videodev              126451  3 uvcvideo,v4l2_common,videobuf2_core
media                  18305  2 uvcvideo,videodev
snd_hda_codec_hdmi     45118  1
evdev                  17445  17
pcspkr                 12595  0
snd_usbmidi_lib        23388  1 snd_usb_audio
arc4                   12536  2
drm                   249955  3 nvidia
snd_hda_codec_realtek    67127  1
snd_rawmidi            26806  1 snd_usbmidi_lib
snd_seq_device         13132  1 snd_rawmidi
psmouse                99249  0
iwldvm                135156  0
mac80211              474277  1 iwldvm
iwlwifi                96547  1 iwldvm
serio_raw              12849  0
snd_hda_codec_generic    63181  1 snd_hda_codec_realtek
i2c_i801               16965  0
i2c_core               46012  5 drm,i2c_i801,nvidia,v4l2_common,videodev
snd_hda_intel          26327  5
snd_hda_controller     26646  1 snd_hda_intel
snd_hda_codec         104500  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
snd_hwdep              13148  2 snd_usb_audio,snd_hda_codec
lpc_ich                20768  0
snd_pcm                88662  5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
mfd_core               12601  1 lpc_ich
snd_timer              26614  1 snd_pcm
ac                     12715  0
snd                    65244  24 snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
battery                13356  0
cfg80211              405538  3 iwlwifi,mac80211,iwldvm
rfkill                 18867  3 cfg80211,acer_wmi
shpchp                 31121  0
soundcore              13026  2 snd,snd_hda_codec
wmi                    17339  2 acer_wmi,mxm_wmi
video                  18096  1 acer_wmi
button                 12944  0
acpi_cpufreq           17218  0
processor              28221  3 acpi_cpufreq
fuse                   83350  1
ecryptfs               89223  0
parport_pc             26300  0
ppdev                  16782  0
lp                     17074  0
parport                35749  3 lp,ppdev,parport_pc
autofs4                35529  2
ext4                  473802  3
crc16                  12343  1 ext4
mbcache                17171  1 ext4
jbd2                   82522  1 ext4
hid_generic            12393  0
usbhid                 44460  0
hid                   102264  2 hid_generic,usbhid
sg                     29973  0
sd_mod                 44356  5
crc_t10dif             12431  1 sd_mod
crct10dif_generic      12581  1
sr_mod                 21903  0
cdrom                  47424  1 sr_mod
crct10dif_common       12356  2 crct10dif_generic,crc_t10dif
ata_generic            12490  0
ata_piix               33592  4
libata                177508  2 ata_generic,ata_piix
scsi_mod              191405  4 sg,libata,sd_mod,sr_mod
tg3                   164481  0
ptp                    17692  1 tg3
pps_core               17225  1 ptp
libphy                 32268  1 tg3
thermal                17559  0
thermal_sys            27642  3 video,thermal,processor
ehci_pci               12512  0
uhci_hcd               43499  0
ehci_hcd               69837  1 ehci_pci
usbcore               195427  7 uhci_hcd,snd_usb_audio,uvcvideo,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid
usb_common             12440  1 usbcore

 

*-display              
       description: VGA compatible controller
       produit: G96M [GeForce GT 130M]
       fabriquant: NVIDIA Corporation
       identifiant matériel: 0
       information bus: pci@0000:01:00.0
       version: a1
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       ressources: irq:47 mémoire:d2000000-d2ffffff mémoire:c0000000-cfffffff mémoire:d0000000-d1ffffff portE/S:4000(taille=128)
 

     mais j'ai toujours le warning dans kern.log

Feb 18 16:27:45 debian kernel: [    8.737900] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMBA) (20140424/utaddress-254)
Feb 18 16:27:45 debian kernel: [    8.737912] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053B (\GPIO) (20140424/utaddress-254)
Feb 18 16:27:45 debian kernel: [    8.737918] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053B (\GPIO) (20140424/utaddress-254)
Feb 18 16:27:45 debian kernel: [    8.737924] lpc_ich: Resource conflict(s) found affecting gpio_ich
 

toutefois pour l'instant je laisse comme cela,  et je tiens au courant si la sortie de veille rebloque...ce n'est pas systématique..

anonyme

Invité

Re : [RESOLU] problème de sortie veille ou hibernation

pour enlever le message de l acpi , il te faut installer le driver 304  => Your card is supported by the default drivers and legacy driver series 304.

avec des cartes anciennes il y a des soucis avec nouveau (selon le model )

le paquet s appelle  xserver-xorg-video-nvidia-legacy-304xx    (voir le tuto nvidia du wiki D_F pour la procédure) section legacy

Dernière modification par anonyme (18-02-2016 17:06:19)

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

maintenant c'est pire, impossible de mettre en veille, dans syslog au moment ou j'essaie de mettre en veille...freeze et retour sur le bureau..

Feb 18 17:02:21 debian kernel: [ 2094.572561] (NULL device *): firmware: direct-loading firmware iwlwifi-5000-5.ucode
Feb 18 17:02:21 debian kernel: [ 2094.572656] Freezing user space processes ...
Feb 18 17:02:21 debian kernel: [ 2114.581895] Freezing of tasks failed after 20.009 seconds (1 tasks refusing to freeze, wq_busy=0):
Feb 18 17:02:21 debian kernel: [ 2114.582102] avidemux0:sink  D ffff88013999d178     0  1809      1 0x00000004
Feb 18 17:02:21 debian kernel: [ 2114.582106]  ffff88013999cd20 0000000000000086 0000000000012f00 ffff880134ab3fd8
Feb 18 17:02:21 debian kernel: [ 2114.582109]  0000000000012f00 ffff88013999cd20 ffff88013fc137b0 ffff88013ffc6a48
Feb 18 17:02:21 debian kernel: [ 2114.582112]  ffff880134ab3d90 0000000000000082 ffffffff8113ce10 ffffea0003965738
Feb 18 17:02:21 debian kernel: [ 2114.582115] Call Trace:
Feb 18 17:02:21 debian kernel: [ 2114.582122]  [<ffffffff8113ce10>] ? sleep_on_page+0x10/0x10
Feb 18 17:02:21 debian kernel: [ 2114.582127]  [<ffffffff815107c9>] ? io_schedule+0x99/0x120
Feb 18 17:02:21 debian kernel: [ 2114.582130]  [<ffffffff8113ce1a>] ? sleep_on_page_killable+0xa/0x40
Feb 18 17:02:21 debian kernel: [ 2114.582132]  [<ffffffff81510c51>] ? __wait_on_bit_lock+0x41/0xa0
Feb 18 17:02:21 debian kernel: [ 2114.582136]  [<ffffffff8113cf7a>] ? __lock_page_killable+0x6a/0x70
Feb 18 17:02:21 debian kernel: [ 2114.582139]  [<ffffffff810a7bd0>] ? autoremove_wake_function+0x30/0x30
Feb 18 17:02:21 debian kernel: [ 2114.582142]  [<ffffffff8113eb78>] ? generic_file_read_iter+0x388/0x5e0
Feb 18 17:02:21 debian kernel: [ 2114.582146]  [<ffffffff8109c3c0>] ? update_curr+0x90/0x120
Feb 18 17:02:21 debian kernel: [ 2114.582150]  [<ffffffff811a7d81>] ? new_sync_read+0x71/0xa0
Feb 18 17:02:21 debian kernel: [ 2114.582153]  [<ffffffff811a83d3>] ? vfs_read+0x93/0x170
Feb 18 17:02:21 debian kernel: [ 2114.582156]  [<ffffffff811a9002>] ? SyS_read+0x42/0xa0
Feb 18 17:02:21 debian kernel: [ 2114.582158]  [<ffffffff811a8083>] ? SyS_lseek+0x43/0xa0
Feb 18 17:02:21 debian kernel: [ 2114.582161]  [<ffffffff81513d0d>] ? system_call_fast_compare_end+0x10/0x15
Feb 18 17:02:21 debian kernel: [ 2114.582165]
Feb 18 17:02:21 debian rtkit-daemon[1342]: The canary thread is apparently starving. Taking action.
Feb 18 17:02:21 debian rtkit-daemon[1342]: Demoting known real-time threads.
Feb 18 17:02:21 debian rtkit-daemon[1342]: Successfully demoted thread 1408 of process 1340 (/usr/bin/pulseaudio).
Feb 18 17:02:21 debian rtkit-daemon[1342]: Successfully demoted thread 1407 of process 1340 (/usr/bin/pulseaudio).
Feb 18 17:02:21 debian rtkit-daemon[1342]: Successfully demoted thread 1405 of process 1340 (/usr/bin/pulseaudio).
Feb 18 17:02:21 debian rtkit-daemon[1342]: Successfully demoted thread 1340 of process 1340 (/usr/bin/pulseaudio).
Feb 18 17:02:21 debian rtkit-daemon[1342]: Demoted 4 threads.
Feb 18 17:02:21 debian kernel: [ 2114.582166] Restarting tasks ... done.
Feb 18 17:02:21 debian kernel: [ 2114.606466] video LNXVIDEO:00: Restoring backlight state
Feb 18 17:02:23 debian kernel: [ 2116.072901] PM: Syncing filesystems ... done.
Feb 18 17:02:23 debian kernel: [ 2116.190185] PM: Preparing system for freeze sleep
Feb 18 17:02:24 debian acpid: client 1026[0:0] has disconnected
Feb 18 17:02:24 debian acpid: client connected from 1026[0:0]
Feb 18 17:02:24 debian acpid: 1 client rule loaded
 

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

pour enlever le message de l acpi , il te faut installer le driver 304  => Your card is supported by the default drivers and legacy driver series 304.

avec des cartes anciennes il y a des soucis avec nouveau (selon le model )

le paquet s appelle  xserver-xorg-video-nvidia-legacy-304xx    (voir le tuto nvidia du wiki D_F pour la procédure) section legacy

ok merci, je vais regarder ça plus tard, ouf  la mise en veille refonctionne, c'était surement le nomodeset qui perturbait ACPI,  j'ai rebooter en mettant simplement cette option:

GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset nouveau.modeset=0"

  et il démarre normalement..


merci pour ton aide,  je reprendrais plus tard avec le paquet  xserver-xorg-video-nvidia-legacy-304, là je fais le break, depuis 13h52 que je suis là-dessus...

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

j'ai installé     xserver-xorg-video-nvidia-legacy-304xx, mais j'ai toujours le message  conflicts with OpRegion dans kern.log  (toutefois j'ai fais beaucoup de mise en veille pour tester, il n'a pas remerdé pour l'instant)

par contre maintenant il y a autre chose:

quand je boot, écran noir alors je vais sur console tty et je fais:

modprobe -r nvidia_current
modprobe nvidia_current
service lightdm start



et  là c'est ok  ....  un idée  ?

quand je fais modprobe -r nvidia_current, j'ai ce message:  (depuis que j'ai installé xserver-xorg-video-nvidia-legacy-304xx)

rmmod :  ERROR Module nvidia_uvm is not currently load
 

edit: j'ai pas encore trouvé l'erreur rmmod de nvidia_uvm alors j'ai mis nvidia_current  dans /etc/modules  et ça fonctionne ainsi.

Dernière modification par nikau (18-02-2016 21:59:17)

anonyme

Invité

Re : [RESOLU] problème de sortie veille ou hibernation

tu a utilisée ce tuto  => https://debian-facile.org/doc:materiel: … ia:accueil
vers la fin tu a la section  => Pilotes propriétaires legacy avec DKMS

Dernière modification par anonyme (18-02-2016 21:57:51)

nikau

Banni(e)

Distrib. : jessie

Noyau : 3.16.0-4-amd64

(G)UI : Xfce 4.10.1

Inscription : 19-10-2011

Re : [RESOLU] problème de sortie veille ou hibernation

tu a utilisée ce tuto  => https://debian-facile.org/doc:materiel: … ia:accueil
vers la fin tu a la section  => Pilotes propriétaires legacy avec DKMS

oui et c'est justement depuis ça que j'ai une erreur rrmod avec nvidia_uvm, tans pis j'ignore cette erreur,  j'ai ajouté nvidia_current dans  /etc/modules    et  ça démarre bien ainsi.

merci à toi,  je vais attendre au moins une semaine pour mettre ce post en résolu, pour l'instant les mise en veille et hibernation sont nickels.