too slow login screen showing

- - ALL UNSTABLE / TESTING THREADS SHOULD BE POSTED HERE - -
This sub-forum is the dedicated area for the ongoing Unstable/Testing releases of Debian. Advanced, or Experienced User support only. Use the software, give, and take advice with caution.
Post Reply
Message
Author
alirezaimi
Posts: 145
Joined: 2011-01-12 16:25

too slow login screen showing

#1 Post by alirezaimi »

Hi
when i turn on my laptop or when back from suspended state , the login screen on gdm3 is getting too much time to start and show login screen or lock screen when back from sleep mode .
when i turn on laptop , after loading kernel and modules , stuck in black scren with one _ sowing for some minutes and then show login screen .
when i turn on laptop from sleep mode, for one second show lock screen and go to black screen and with press any buttons nothing happened for long time and after some minutes show lock screen and everything is ok .

too many time that i struggling with this problem on my laptop , acer 5741 with 8 g ram and core i5 cpu .

some info :
turn on dmesg log :
app.php/pastebin/?mode=view&s=52

turn on sleep mode dmesg log :

Code: Select all

[Tue Oct 24 11:09:59 2023] PM: suspend entry (deep)
[Tue Oct 24 11:09:59 2023] Filesystems sync: 0.016 seconds
[Tue Oct 24 11:10:40 2023] rfkill: input handler enabled
[Tue Oct 24 11:10:55 2023] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[Tue Oct 24 11:10:55 2023] (NULL device *): firmware: direct-loading firmware regulatory.db
[Tue Oct 24 11:10:55 2023] Freezing user space processes
[Tue Oct 24 11:10:55 2023] Freezing user space processes completed (elapsed 0.005 seconds)
[Tue Oct 24 11:10:55 2023] OOM killer disabled.
[Tue Oct 24 11:10:55 2023] Freezing remaining freezable tasks
[Tue Oct 24 11:10:55 2023] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[Tue Oct 24 11:10:55 2023] printk: Suspending console(s) (use no_console_suspend to debug)
[Tue Oct 24 11:10:55 2023] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[Tue Oct 24 11:10:55 2023] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[Tue Oct 24 11:10:55 2023] sd 0:0:0:0: [sda] Stopping disk
[Tue Oct 24 11:10:55 2023] sd 1:0:0:0: [sdb] Stopping disk
[Tue Oct 24 11:10:58 2023] ACPI: EC: interrupt blocked
[Tue Oct 24 11:10:58 2023] ACPI: PM: Preparing to enter system sleep state S3
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[Tue Oct 24 11:10:58 2023] ACPI: EC: event blocked
[Tue Oct 24 11:10:58 2023] ACPI: EC: EC stopped
[Tue Oct 24 11:10:58 2023] ACPI: PM: Saving platform NVS memory
[Tue Oct 24 11:10:58 2023] Disabling non-boot CPUs ...
[Tue Oct 24 11:10:58 2023] smpboot: CPU 1 is now offline
[Tue Oct 24 11:10:58 2023] smpboot: CPU 2 is now offline
[Tue Oct 24 11:10:58 2023] smpboot: CPU 3 is now offline
[Tue Oct 24 11:10:58 2023] ACPI: PM: Low-level resume complete
[Tue Oct 24 11:10:58 2023] ACPI: EC: EC started
[Tue Oct 24 11:10:58 2023] ACPI: PM: Restoring platform NVS memory
[Tue Oct 24 11:10:58 2023] Enabling non-boot CPUs ...
[Tue Oct 24 11:10:58 2023] smpboot: Booting Node 0 Processor 1 APIC 0x1
[Tue Oct 24 11:10:58 2023] CPU1 is up
[Tue Oct 24 11:10:58 2023] smpboot: Booting Node 0 Processor 2 APIC 0x4
[Tue Oct 24 11:10:58 2023] CPU2 is up
[Tue Oct 24 11:10:58 2023] smpboot: Booting Node 0 Processor 3 APIC 0x5
[Tue Oct 24 11:10:58 2023] CPU3 is up
[Tue Oct 24 11:10:58 2023] ACPI: PM: Waking up from system sleep state S3
[Tue Oct 24 11:10:58 2023] ACPI: EC: interrupt unblocked
[Tue Oct 24 11:10:58 2023] [drm] PCIE GART of 1024M enabled (table at 0x000000000014C000).
[Tue Oct 24 11:10:58 2023] radeon 0000:01:00.0: WB enabled
[Tue Oct 24 11:10:58 2023] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00
[Tue Oct 24 11:10:58 2023] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c
[Tue Oct 24 11:10:58 2023] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418
[Tue Oct 24 11:10:58 2023] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[Tue Oct 24 11:10:58 2023] debugfs: File 'radeon_ring_dma1' in directory '0' already present!
[Tue Oct 24 11:10:58 2023] [drm] ring test on 0 succeeded in 1 usecs
[Tue Oct 24 11:10:58 2023] [drm] ring test on 3 succeeded in 3 usecs
[Tue Oct 24 11:10:58 2023] debugfs: File 'radeon_ring_uvd' in directory '0' already present!
[Tue Oct 24 11:10:58 2023] [drm] ring test on 5 succeeded in 1 usecs
[Tue Oct 24 11:10:58 2023] [drm] UVD initialized successfully.
[Tue Oct 24 11:10:58 2023] [drm] ib test on ring 0 succeeded in 0 usecs
[Tue Oct 24 11:10:58 2023] [drm] ib test on ring 3 succeeded in 0 usecs
[Tue Oct 24 11:10:58 2023] usb 1-1.1: reset high-speed USB device number 5 using ehci-pci
[Tue Oct 24 11:10:58 2023] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Tue Oct 24 11:10:58 2023] ata1.00: configured for UDMA/133
[Tue Oct 24 11:10:59 2023] ACPI: EC: event unblocked
[Tue Oct 24 11:10:59 2023] [drm] ib test on ring 5 succeeded
[Tue Oct 24 11:11:00 2023] psmouse serio1: synaptics: queried max coordinates: x [..5772], y [..5086]
[Tue Oct 24 11:11:01 2023] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Tue Oct 24 11:11:01 2023] ata2.00: configured for UDMA/133
[Tue Oct 24 11:11:17 2023] OOM killer enabled.
[Tue Oct 24 11:11:17 2023] Restarting tasks ... done.
[Tue Oct 24 11:11:17 2023] random: crng reseeded on system resumption
[Tue Oct 24 11:11:18 2023] PM: suspend exit
[Tue Oct 24 11:11:19 2023] rfkill: input handler disabled

Code: Select all

PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Code: Select all

# apt-cache policy gnome-shell gdm3 
gnome-shell:
  Installed: 44.5-2
  Candidate: 44.5-2
  Version table:
 *** 44.5-2 500
        500 http://deb.debian.org/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status
gdm3:
  Installed: 45.0.1-1
  Candidate: 45.0.1-1
  Version table:
 *** 45.0.1-1 500
        500 http://deb.debian.org/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status

User avatar
sunrat
Site admin
Site admin
Posts: 7366
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 133 times
Been thanked: 650 times

Re: too slow login screen showing

#2 Post by sunrat »

Using Testing so moved to the appropriate subforum.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

alirezaimi
Posts: 145
Joined: 2011-01-12 16:25

Re: too slow login screen showing

#3 Post by alirezaimi »

sunrat wrote: 2023-10-24 09:30 Using Testing so moved to the appropriate subforum.
I have this problem on debian stable too .

User avatar
sunrat
Site admin
Site admin
Posts: 7366
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 133 times
Been thanked: 650 times

Re: too slow login screen showing

#4 Post by sunrat »

alirezaimi wrote: 2023-10-24 13:15
sunrat wrote: 2023-10-24 09:30 Using Testing so moved to the appropriate subforum.
I have this problem on debian stable too .
You posted your details for Testing. Concentrate on solving for one version at a time. If you want to post your specs for Stable and work on solving that, we can move it back to the stable subforum.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Aki
Global Moderator
Global Moderator
Posts: 3954
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 109 times
Been thanked: 520 times

Re: too slow login screen showing

#5 Post by Aki »

Hello,

From log you sent, a kernel stack dump appears in relation to wireless connectivity:

Code: Select all

[  431.121034] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[  477.643032] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[  809.409235] ------------[ cut here ]------------
[  809.409245] WARNING: CPU: 1 PID: 10 at net/wireless/sme.c:858 __cfg80211_connect_result+0x908/0x920 [cfg80211]
[  809.409413] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device amdgpu amdxcp drm_buddy gpu_sched xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc overlay qrtr bnep btusb btrtl btbcm btintel btmtk bluetooth sha3_generic jitterentropy_rng ctr drbg ansi_cprng ecdh_generic ecc radeon intel_powerclamp uvcvideo videobuf2_vmalloc coretemp uvc videobuf2_memops videobuf2_v4l2 kvm_intel videodev snd_hda_codec_realtek wl(POE) drm_suballoc_helper snd_hda_codec_generic videobuf2_common ledtrig_audio kvm mc drm_display_helper snd_hda_codec_hdmi snd_hda_intel cec snd_intel_dspcfg irqbypass mei_pxp snd_intel_sdw_acpi sha512_ssse3 rc_core snd_hda_codec sha512_generic drm_ttm_helper ttm intel_cstate intel_uncore snd_hda_core cfg80211 iTCO_wdt mxm_wmi drm_kms_helper snd_hwdep
[  809.409533]  at24 snd_pcm intel_pmc_bxt wmi_bmof pcspkr acer_wmi snd_timer iTCO_vendor_support sparse_keymap mei_me i2c_algo_bit binfmt_misc snd mei acpi_cpufreq rfkill intel_ips watchdog soundcore ac button evdev joydev serio_raw sg msr parport_pc ppdev lp parport drm fuse dm_mod loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid sd_mod t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_common ahci libahci libata broadcom bcm_phy_ptp bcm_phy_lib scsi_mod tg3 ehci_pci ehci_hcd i2c_i801 usbcore psmouse crc32c_intel libphy i2c_smbus scsi_common lpc_ich usb_common video battery wmi
[  809.409640] CPU: 1 PID: 10 Comm: kworker/u16:0 Tainted: P           OE      6.5.0-2-amd64 #1  Debian 6.5.6-1
[  809.409646] Hardware name: Acer             Aspire 5741G    /Aspire 5741G    , BIOS V1.23 04/25/2011
[  809.409649] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[  809.409730] RIP: 0010:__cfg80211_connect_result+0x908/0x920 [cfg80211]
[  809.409843] Code: 89 44 1f fe e9 ce fc ff ff e8 64 f3 c4 e2 45 31 ff 0f b7 d0 e9 55 f8 ff ff 4c 89 e7 e8 d1 df ff ff 83 3b 00 0f 85 2b fe ff ff <0f> 0b 48 89 de 4c 89 e7 e8 ab de ff ff e9 cb fa ff ff 66 0f 1f 44
[  809.409846] RSP: 0000:ffff9d410007fda0 EFLAGS: 00010246
[  809.409850] RAX: 0000000000000000 RBX: ffff88a32bb68c18 RCX: 0000000000000000
[  809.409853] RDX: 0000000000000000 RSI: ffffffffa4073ef2 RDI: ffff88a3069c1800
[  809.409855] RBP: ffff9d410007fdf0 R08: 0000000000000000 R09: 0000000000000000
[  809.409858] R10: 0000000000000002 R11: 0000000000000000 R12: ffff88a3069c1800
[  809.409860] R13: ffff88a32bb68c18 R14: ffff88a32bb68fa0 R15: 0000000000000000
[  809.409862] FS:  0000000000000000(0000) GS:ffff88a453c40000(0000) knlGS:0000000000000000
[  809.409865] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  809.409868] CR2: 00007f6682ba8010 CR3: 000000011e420000 CR4: 00000000000006e0
[  809.409871] Call Trace:
[  809.409878]  <TASK>
[  809.409880]  ? __cfg80211_connect_result+0x908/0x920 [cfg80211]
[  809.409993]  ? __warn+0x81/0x130
[  809.410005]  ? __cfg80211_connect_result+0x908/0x920 [cfg80211]
[  809.410118]  ? report_bug+0x191/0x1c0
[  809.410126]  ? handle_bug+0x3c/0x80
[  809.410134]  ? exc_invalid_op+0x17/0x70
[  809.410139]  ? asm_exc_invalid_op+0x1a/0x20
[  809.410147]  ? __cfg80211_connect_result+0x908/0x920 [cfg80211]
[  809.410261]  ? cfg80211_process_wdev_events+0x84/0x1c0 [cfg80211]
[  809.410352]  cfg80211_process_wdev_events+0x84/0x1c0 [cfg80211]
[  809.410446]  cfg80211_process_rdev_events+0x2a/0x40 [cfg80211]
[  809.410536]  cfg80211_event_work+0x29/0x40 [cfg80211]
[  809.410613]  process_one_work+0x1e1/0x3f0
[  809.410620]  worker_thread+0x51/0x390
[  809.410625]  ? __pfx_worker_thread+0x10/0x10
[  809.410629]  kthread+0xf7/0x130
[  809.410635]  ? __pfx_kthread+0x10/0x10
[  809.410639]  ret_from_fork+0x34/0x50
[  809.410646]  ? __pfx_kthread+0x10/0x10
[  809.410650]  ret_from_fork_asm+0x1b/0x30
[  809.410660]  </TASK>
[  809.410662] ---[ end trace 0000000000000000 ]---
[  863.049235] perf: interrupt took too long (3151 > 3136), lowering kernel.perf_event_max_sample_rate to 63250
I don't know if this has anything to do with your problem (there are no log entries about your computer being suspended), but this log message might be worth investigating:

Code: Select all

[  431.121034] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
A full hardware / software configuration description of your computer could be useful to acquire; you can use the command (the inxi package must be installed):

Code: Select all

inxi -Fxxxz
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Post Reply