Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Hello.
I have installed Debian Stretch on my HP 355 G2 laptop. The display regularly freezes, sometimes only for several seconds other times for good and I can only cut the power supply to restart it. Both firmware-linux-nonfree and firmware-amd-graphics are installed. Here are my graphics card details:
The processor is Quad core AMD A4-6210 and 4 GB RAM. I did NOT have this issue with Debian Jessie.
Therefore I suspect it has something to do with the driver.
kedaha wrote:I'd try linux-image-amd64 together with firmware-linux-nonfree and firmware-amd-graphics from stretch-backports.
Thank you for your suggestion. I have installed the linux kernel available in backports, firmware packages are the same.
Unfortunately the problem persists. The question is why did this NOT happen with Debian Jessie?
Try removing the xserver-xorg-video-ati package (and amdgpu if you have that) and let the system use the modesetting driver instead, it may be less buggy.
Thank you for your reply. Of course I did search on internet before posting but no working solution found.
I suspect it is a bug in the firmware-amd-graphics package because this package is something new, it did not exist for Debian Jessie.
Head_on_a_Stick wrote:Try removing the xserver-xorg-video-ati package (and amdgpu if you have that) and let the system use the modesetting driver instead, it may be less buggy.
This is what would happen if I purged xserver-xorg-video-ati:
Head_on_a_Stick wrote:Try removing the xserver-xorg-video-ati package (and amdgpu if you have that) and let the system use the modesetting driver instead, it may be less buggy.
I did that and I got a message about "running in rendering mode" and that I "should use that just for debugging".
Anyway I think it has to do with this, when Debian boots I can see among the other lines on the screen these lines:
Dec 3 22:15:24 pc dbus-daemon[898]: Successfully activated service 'org.gnome.gedit'
Dec 3 22:16:10 pc NetworkManager[465]: <info> [1512332170.8295] device (wlo1): set-hw-addr: set MAC address to 8A:BF:89:B5:4B:BD (scanning)
Dec 3 22:16:31 pc kernel: [ 729.158175] INFO: rcu_sched self-detected stall on CPU
Dec 3 22:16:31 pc kernel: [ 729.158195] 1-...: (5250 ticks this GP) idle=766/140000000000001/0 softirq=13776/13776 fqs=2436
Dec 3 22:16:31 pc kernel: [ 729.158199] (t=5251 jiffies g=14732 c=14731 q=1495)
Dec 3 22:16:31 pc kernel: [ 729.158210] NMI backtrace for cpu 1
Dec 3 22:16:31 pc kernel: [ 729.158218] CPU: 1 PID: 465 Comm: NetworkManager Tainted: G L 4.13.0-0.bpo.1-amd64 #1 Debian 4.13.13-1~bpo9+1
Dec 3 22:16:31 pc kernel: [ 729.158220] Hardware name: Hewlett-Packard HP 355 G2/22C1, BIOS F.11 06/02/2015
Dec 3 22:16:31 pc kernel: [ 729.158222] Call Trace:
Dec 3 22:16:31 pc kernel: [ 729.158229] <IRQ>
Dec 3 22:16:31 pc kernel: [ 729.158240] ? dump_stack+0x5c/0x85
Dec 3 22:16:31 pc kernel: [ 729.158247] ? nmi_cpu_backtrace+0xbf/0xd0
Dec 3 22:16:31 pc kernel: [ 729.158252] ? irq_force_complete_move+0x140/0x140
Dec 3 22:16:31 pc kernel: [ 729.158258] ? nmi_trigger_cpumask_backtrace+0xf4/0x120
Dec 3 22:16:31 pc kernel: [ 729.158265] ? rcu_dump_cpu_stacks+0x9c/0xd5
Dec 3 22:16:31 pc kernel: [ 729.158271] ? rcu_check_callbacks+0x7a9/0x8f0
Dec 3 22:16:31 pc kernel: [ 729.158277] ? serio_interrupt+0x4d/0x80
Dec 3 22:16:31 pc kernel: [ 729.158284] ? tick_sched_do_timer+0x40/0x40
Dec 3 22:16:31 pc kernel: [ 729.158290] ? update_process_times+0x28/0x50
Dec 3 22:16:31 pc kernel: [ 729.158294] ? tick_sched_handle+0x23/0x60
Dec 3 22:16:31 pc kernel: [ 729.158299] ? tick_sched_timer+0x34/0x70
Dec 3 22:16:31 pc kernel: [ 729.158304] ? __hrtimer_run_queues+0xdc/0x220
Dec 3 22:16:31 pc kernel: [ 729.158310] ? hrtimer_interrupt+0xa6/0x1f0
Dec 3 22:16:31 pc kernel: [ 729.158316] ? smp_apic_timer_interrupt+0x34/0x50
Dec 3 22:16:31 pc kernel: [ 729.158321] ? apic_timer_interrupt+0x82/0x90
Dec 3 22:16:31 pc kernel: [ 729.158323] </IRQ>
Dec 3 22:16:31 pc kernel: [ 729.158330] ? delay_tsc+0x1f/0x50
Dec 3 22:16:31 pc kernel: [ 729.158342] ? rtl8723_fw_free_to_go+0x98/0x110 [rtl8723_common]
Dec 3 22:16:31 pc kernel: [ 729.158349] ? rtl8723_download_fw+0xb6/0x150 [rtl8723_common]
Dec 3 22:16:31 pc kernel: [ 729.158361] ? rtl8723be_hw_init+0xc6c/0x1760 [rtl8723be]
Dec 3 22:16:31 pc kernel: [ 729.158369] ? rtl_pci_start+0x4c/0xe0 [rtl_pci]
Dec 3 22:16:31 pc kernel: [ 729.158381] ? rtl_op_start+0x4d/0x80 [rtlwifi]
Dec 3 22:16:31 pc kernel: [ 729.158430] ? drv_start+0x3a/0xe0 [mac80211]
Dec 3 22:16:31 pc kernel: [ 729.158475] ? ieee80211_do_open+0x2fd/0x8f0 [mac80211]
Dec 3 22:16:31 pc kernel: [ 729.158519] ? ieee80211_check_concurrent_iface+0x11a/0x1e0 [mac80211]
Dec 3 22:16:31 pc kernel: [ 729.158526] ? __dev_open+0xc2/0x140
Dec 3 22:16:31 pc kernel: [ 729.158531] ? __dev_change_flags+0x96/0x150
Dec 3 22:16:31 pc kernel: [ 729.158535] ? dev_change_flags+0x23/0x60
Dec 3 22:16:31 pc kernel: [ 729.158541] ? do_setlink+0x329/0xcb0
Dec 3 22:16:31 pc kernel: [ 729.158548] ? __kmalloc_reserve.isra.37+0x2e/0x80
Dec 3 22:16:31 pc kernel: [ 729.158555] ? __nla_put+0xc/0x20
Dec 3 22:16:31 pc kernel: [ 729.158560] ? inet6_fill_ifla6_attrs+0x451/0x470
Dec 3 22:16:31 pc kernel: [ 729.158565] ? rtnl_newlink+0x7f6/0x920
Dec 3 22:16:31 pc kernel: [ 729.158573] ? select_idle_sibling+0x2cb/0x440
Dec 3 22:16:31 pc kernel: [ 729.158585] ? security_capable+0x41/0x60
Dec 3 22:16:31 pc kernel: [ 729.158590] ? rtnetlink_rcv_msg+0xe9/0x220
Dec 3 22:16:31 pc kernel: [ 729.158594] ? rtnl_newlink+0x920/0x920
Dec 3 22:16:31 pc kernel: [ 729.158599] ? netlink_rcv_skb+0xe7/0x120
Dec 3 22:16:31 pc kernel: [ 729.158603] ? rtnetlink_rcv+0x24/0x30
Dec 3 22:16:31 pc kernel: [ 729.158607] ? netlink_unicast+0x184/0x230
Dec 3 22:16:31 pc kernel: [ 729.158611] ? netlink_sendmsg+0x2cb/0x3b0
Dec 3 22:16:31 pc kernel: [ 729.158619] ? sock_sendmsg+0x30/0x40
Dec 3 22:16:31 pc kernel: [ 729.158624] ? ___sys_sendmsg+0x2d7/0x2f0
Dec 3 22:16:31 pc kernel: [ 729.158632] ? security_file_free+0x20/0x30
Dec 3 22:16:31 pc kernel: [ 729.158638] ? dput+0xbe/0x1f0
Dec 3 22:16:31 pc kernel: [ 729.158644] ? __sys_sendmsg+0x51/0x90
Dec 3 22:16:31 pc kernel: [ 729.158649] ? __sys_sendmsg+0x51/0x90
Dec 3 22:16:31 pc kernel: [ 729.158657] ? system_call_fast_compare_end+0xc/0x97
Dec 3 22:16:40 pc kernel: [ 737.943943] rtl8723_common: Polling FW ready fail!! REG_MCUFWDL:0x00000006 .
Dec 3 22:16:40 pc kernel: [ 737.943953] rtl8723_common: Firmware is not ready to run!
Dec 3 22:16:41 pc kernel: [ 738.326964] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Dec 3 22:16:41 pc NetworkManager[465]: <info> [1512332201.0036] device (wlo1): supplicant interface state: inactive -> disabled
Dec 3 22:16:41 pc NetworkManager[465]: <info> [1512332201.0235] device (wlo1): supplicant interface state: disabled -> inactive
Dec 3 22:16:41 pc wpa_supplicant[601]: wlo1: Reject scan trigger since one is already pending
Dec 3 22:17:01 pc CRON[1711]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
I did not see these lines when I used Debian Jessie.
I did not see these lines when I used Debian Jessie.
-and-
The question is why did this NOT happen with Debian Jessie?
Nah, asking why it did NOT happen on jessie isn't going to help, unless you still have jessie installed and can compare some log or something. There were boatloads of changes from jessie, it hurt me too, but really stretch is a lot better. I've been tweaking it for about 5 months now, and just now getting back to performance as good as jessie.
I've noticed networkmanager can pretty much freeze me for a few seconds or so when it's doing it's thing, but I have a really slow cpu. I guess the quoted stuff in your last messages would be pretty serious, but I've never seen 'NetworkManager Tainted' or anything similar. Looks like some firmware issue with your wifi.
I've noticed networkmanager can pretty much freeze me for a few seconds or so when it's doing it's thing, but I have a really slow cpu. I guess the quoted stuff in your last messages would be pretty serious, but I've never seen 'NetworkManager Tainted' or anything similar. Looks like some firmware issue with your wifi.
Maybe NetworkManager causes my display to freeze because it usually happens after a while not imediately.
I am trying to get used to this situation until a fix will be available.
The freezing of the display was related to the lack of driver for realtek wireless card. I have installed firmware-realtek and there are no more cpu stall messages during the boot and no more display freezing after login.