English
Ask Your Question
0

It takes too long to show gnome login prompt when opening the laptop lid

asked 2017-12-03 17:12:45 +0000

updated 2017-12-06 09:27:26 +0000

When opening laptop lid (after suspending) It takes up to a minutes before gnome password prompt is shown. The display shows the lock screen background but cannot do anything (no sliding, the battery/sound icons are not responding). Then after few moments its unfreezes and everything is back to normal. Sometimes if it takes too long I press ctrl+alt+F3 to show the command line prompt, and then ctrl+alt+f1 and it speeds up the recovery process.

Please advice how to diagnose the problem.

Problem occurs on laptop with Fedora 27 after update from Fedora 26 (which worked fine).

EDIT: Adding dmesg output on 6 Dec 2017

Ok, this is the dmesg. There is nothing updated in /var/log durign that time. The last updated log is dnf.log and hwkey.log

From dmesg:

[281785.244704] brcmsmac bcma0:1 wlp2s0b1: disabling VHT as WMM/QoS is not supported by the AP
[281785.245390] wlp2s0b1: associate with e4:8d:8c:fb:42:cf (try 1/3)
[281785.249409] wlp2s0b1: RX AssocResp from e4:8d:8c:fb:42:cf (capab=0x431 status=0 aid=1)
[281785.250171] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated
[281785.250176] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement)
[281785.250188] wlp2s0b1: associated
[281785.251135] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready
[281791.590523] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
>>>>>>>>>>>>> lid closed <<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>> lid opened <<<<<<<<<<<<<<<<
[282032.979272] pci_bus 0000:0b: Allocating resources
[282032.979296] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[282032.979300] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[282032.979306] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
[282032.979310] pci 0000:00:1e.0:   bridge window [mem 0xf7400000-0xf75fffff 64bit pref]
[282032.992002] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[282032.992009] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[282032.992016] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
[282032.992021] pci 0000:00:1e.0:   bridge window [mem 0xf7400000-0xf75fffff 64bit pref]
[282032.992054] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[282032.992058] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[282032.992064] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
[282032.992069] pci 0000:00:1e.0:   bridge window [mem 0xf7400000-0xf75fffff 64bit pref]
[282032.992388] pci_bus 0000:01: Allocating resources
[282032.992407] pci_bus 0000:02: Allocating resources
[282032.992430] pci_bus 0000:03: Allocating resources
[282032.992502] pci_bus 0000:05: Allocating resources
[282032.992516] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[282032.992520] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[282032.992526] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
[282032.992531] pci 0000:00:1e.0:   bridge window [mem 0xf7400000-0xf75fffff 64bit pref]
[282032.992563] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[282032.992567] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[282032.992573] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
[282032.992577] pci 0000:00:1e.0:   bridge window [mem 0xf7400000-0xf75fffff 64bit ...
(more)
edit retag flag offensive close merge delete

4 answers

Sort by ยป oldest newest most voted
0

answered 2017-12-08 06:23:27 +0000

maracheeam gravatar image

Try not to mount that when you reboot, try doing it manually I think there is an option you can set it to mount after reboot or hibernate.

I will check that or you can google it meanwhile.

Regards,

edit flag offensive delete link more
0

answered 2017-12-07 23:58:56 +0000

It may be coincidence, but the last time when there was significant freeze (around 2 minutes) I noticed that in the dmesg log there is timeout message from the samba mounts for the same amount of time.

[282179.691831] CIFS VFS: Server 10.1.52.25 has not responded in 120 seconds. Reconnecting...
[282197.036283] CIFS VFS: Free previous auth_key.response = ffff971f09be9900
[283033.137624] pci_bus 0000:0b: Allocating resources
[283033.137650] pci 0000:00:1e.0: PCI bridge to [bus 0b]
[283033.137654] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[283033.137661] pci 0000:00:1e.0:   bridge window [mem 0xf7200000-0xf73fffff]
edit flag offensive delete link more
0

answered 2017-12-07 09:50:03 +0000

maracheeam gravatar image

Hello,

I am not sure because I don't have F27 install yet to check this issue, but it could be related to some driver's issue,

We need some with more expertise so they can tell you what logs they might need to solve this issue.

I try to find something that's might help you.

Regards,

edit flag offensive delete link more
0

answered 2017-12-05 08:02:09 +0000

maracheeam gravatar image

Hello,

Check in dmesg, or in the /var/log folder see which logs get updated after login time stamp,

See your memory usage and swap. post here, hope we can find a fix.

Regards,

edit flag offensive delete link more

Comments

Thanks, I attached the dmesg output in the original post.

thexman ( 2017-12-06 09:28:29 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Stats

Asked: 2017-12-03 17:12:45 +0000

Seen: 36 times

Last updated: Dec 06