| View previous topic :: View next topic |
| Author |
Message |
Cr0t
l33t
Joined: 27 Apr 2002
Posts: 944
Location: USA
|
 Posted: Fri Oct 19, 2018 11:57 pm Post subject: slow X startup with nvidia-drivers |
 |
|
This is an older nvidia video card, which is running with the latest supported drivers. I have not had any issues until a couple of months ago. | Code: | 02:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce GT 520M] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. GF119M [GeForce GT 520M]
Kernel driver in use: nvidia
Kernel modules: nvidia_drm, nvidia
02:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. GF119 HDMI Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel |
It takes a really long time until X starts while the nvidia-drivers are loading. | Code: | [ 8.310876] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
[ 8.328898] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 8.328906] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 8.328910] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[ 8.328916] iwlwifi 0000:04:00.0: Detected Intel(R) Centrino(R) Wireless-N 130 BGN, REV=0xB0
[ 8.329064] snd_hda_codec_realtek hdaudioC0D2: mono: mono_out=0x0
[ 8.329070] snd_hda_codec_realtek hdaudioC0D2: dig-out=0x1e/0x0
[ 8.329074] snd_hda_codec_realtek hdaudioC0D2: inputs:
[ 8.329083] snd_hda_codec_realtek hdaudioC0D2: Mic=0x18
[ 8.371476] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input3
[ 8.371761] input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
[ 8.372073] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
[ 8.412437] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 8.586344] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1c.1/0000:02:00.1/sound/card1/input6
[ 8.605527] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1c.1/0000:02:00.1/sound/card1/input7
[ 8.741607] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000e0000-0x000effff window]
[ 8.770911] caller 0xffffffffa08d4bb7 mapping multiple BARs
[ 8.959126] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 8.979686] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[ 10.132463] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
[ 10.154630] caller 0xffffffffa08eeab3 mapping multiple BARs
[ 11.079378] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.079382] Bluetooth: BNEP filters: protocol multicast
[ 11.079391] Bluetooth: BNEP socket layer initialized
[ 11.763375] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.786390] eth0: 0xffffc90000149000, 00:01:2e:48:6c:6d, IRQ 26
[ 12.033855] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.069145] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 15.150470] r8168: eth0: link up
[ 15.171060] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 21.862739] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[ 445.500004] random: crng init done
[ 445.500287] random: 7 urandom warning(s) missed due to ratelimiting
[ 446.375567] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
[ 446.375577] caller 0xffffffffa08eeab3 mapping multiple BARs
[ 446.754281] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.87 Tue Aug 21 16:16:14 PDT 2018
[ 508.641501] snd_hda_intel 0000:02:00.1: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. |
Take a look at the startup time.
Has anyone observed the same issue?
_________________
cya |
|
| Back to top |
|
 |
russK
l33t
Joined: 27 Jun 2006
Posts: 665
|
| Posted: Sat Oct 20, 2018 12:27 am Post subject: |
|
|
Cr0t,
Did you upgrade your kernel around that time?
The gap in your dmesg lines ends with | Code: | [ 445.500004] random: crng init done
|
https://www.google.com/search?q=random+crng+init+done+hangs
Many people having similar delay, not necessarily nvidia related.
HTH |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
|
| Back to top |
|
|
Cr0t
l33t
Joined: 27 Apr 2002
Posts: 944
Location: USA
|
| Posted: Sat Oct 20, 2018 12:39 pm Post subject: |
|
|
I tried 'rngd' last night, but that did not help. Just now, I tried 'haveged' and it works great!
Thank You!
_________________
cya |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
