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

 

 

 

A stop job is running on shutdown/reboot

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

A stop job is running on shutdown/reboot

#1 Post by whitebunnyflock »

Just installed Debian stretch on my Carrizo AMD A10-8700P

As I have an Atheros QCA9377 wireless card I installed firmware-atheros as well as for my Realtek ethernet adapter I installed firmware-realtek.

I converted this to a "Buster" system and since I did that I have been having a hard time shutting down. It takes approximately 8 minutes and 30 seconds to shutdown. It tells me the following stop jobs are running:

A stop job is running for network manager
A stop job is running for wpa supplicant
A stop job is running for raise network interfaces

This section of shutting down runs for about 6 minutes when it seemingly kills everything. I set my journalctl logs to be persistent and this is what i get on the most recent reboot:

Oct 15 08:08:17 DebianLaptop systemd[1]: Stopped CUPS Scheduler.
Oct 15 08:08:17 DebianLaptop NetworkManager[552]: <info> [1508076497.0198] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 731
Oct 15 08:08:17 DebianLaptop NetworkManager[552]: <info> [1508076497.0199] dhcp4 (wlp2s0): state changed bound -> done
Oct 15 08:08:17 DebianLaptop dbus-daemon[534]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Oct 15 08:09:08 DebianLaptop kernel: INFO: task kworker/u8:0:5 blocked for more than 120 seconds.
Oct 15 08:09:08 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:09:08 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:09:08 DebianLaptop kernel: kworker/u8:0 D 0 5 2 0x00000000
Oct 15 08:09:08 DebianLaptop kernel: Workqueue: phy0 ieee80211_ba_session_work [mac80211]
Oct 15 08:09:08 DebianLaptop kernel: Call Trace:
Oct 15 08:09:08 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:09:08 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:09:08 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:09:08 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:09:08 DebianLaptop kernel: ? __ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct 15 08:09:08 DebianLaptop kernel: ? __ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct 15 08:09:08 DebianLaptop kernel: ? dequeue_entity+0xe4/0x470
Oct 15 08:09:08 DebianLaptop kernel: ? ieee80211_ba_session_work+0x154/0x240 [mac80211]
Oct 15 08:09:08 DebianLaptop kernel: ? __schedule+0x3d0/0x860
Oct 15 08:09:08 DebianLaptop kernel: ? process_one_work+0x181/0x370
Oct 15 08:09:08 DebianLaptop kernel: ? worker_thread+0x4d/0x3a0
Oct 15 08:09:08 DebianLaptop kernel: ? kthread+0xfc/0x130
Oct 15 08:09:08 DebianLaptop kernel: ? process_one_work+0x370/0x370
Oct 15 08:09:08 DebianLaptop kernel: ? kthread_create_on_node+0x70/0x70
Oct 15 08:09:08 DebianLaptop kernel: ? ret_from_fork+0x25/0x30
Oct 15 08:09:46 DebianLaptop systemd[1]: networking.service: Stopping timed out. Terminating.
Oct 15 08:09:46 DebianLaptop systemd[1]: networking.service: Control process exited, code=killed status=15
Oct 15 08:09:46 DebianLaptop systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing.
Oct 15 08:09:46 DebianLaptop systemd[1]: wpa_supplicant.service: Killing process 644 (wpa_supplicant) with signal SIGKILL.
Oct 15 08:09:46 DebianLaptop systemd[1]: NetworkManager.service: State 'stop-sigterm' timed out. Killing.
Oct 15 08:09:46 DebianLaptop systemd[1]: NetworkManager.service: Killing process 552 (NetworkManager) with signal SIGKILL.
Oct 15 08:11:09 DebianLaptop kernel: INFO: task kworker/u8:0:5 blocked for more than 120 seconds.
Oct 15 08:11:09 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:11:09 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:11:09 DebianLaptop kernel: kworker/u8:0 D 0 5 2 0x00000000
Oct 15 08:11:09 DebianLaptop kernel: Workqueue: phy0 ieee80211_ba_session_work [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: Call Trace:
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:11:09 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:11:09 DebianLaptop kernel: ? __ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? __ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? dequeue_entity+0xe4/0x470
Oct 15 08:11:09 DebianLaptop kernel: ? ieee80211_ba_session_work+0x154/0x240 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3d0/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x181/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? worker_thread+0x4d/0x3a0
Oct 15 08:11:09 DebianLaptop kernel: ? kthread+0xfc/0x130
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x370/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? kthread_create_on_node+0x70/0x70
Oct 15 08:11:09 DebianLaptop kernel: ? ret_from_fork+0x25/0x30
Oct 15 08:11:09 DebianLaptop kernel: INFO: task NetworkManager:552 blocked for more than 120 seconds.
Oct 15 08:11:09 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:11:09 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:11:09 DebianLaptop kernel: NetworkManager D 0 552 1 0x00000004
Oct 15 08:11:09 DebianLaptop kernel: Call Trace:
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:11:09 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:11:09 DebianLaptop kernel: ? ip6mr_sk_done+0x1b/0xd0
Oct 15 08:11:09 DebianLaptop kernel: ? ip6mr_sk_done+0x1b/0xd0
Oct 15 08:11:09 DebianLaptop kernel: ? rawv6_close+0x19/0x30
Oct 15 08:11:09 DebianLaptop kernel: ? inet_release+0x36/0x60
Oct 15 08:11:09 DebianLaptop kernel: ? sock_release+0x1a/0x70
Oct 15 08:11:09 DebianLaptop kernel: ? sock_close+0xe/0x20
Oct 15 08:11:09 DebianLaptop kernel: ? __fput+0xd5/0x210
Oct 15 08:11:09 DebianLaptop kernel: ? task_work_run+0x79/0xa0
Oct 15 08:11:09 DebianLaptop kernel: ? exit_to_usermode_loop+0xbb/0xc0
Oct 15 08:11:09 DebianLaptop kernel: ? syscall_return_slowpath+0x54/0x60
Oct 15 08:11:09 DebianLaptop kernel: ? system_call_fast_compare_end+0x95/0x97
Oct 15 08:11:09 DebianLaptop kernel: INFO: task wpa_supplicant:644 blocked for more than 120 seconds.
Oct 15 08:11:09 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:11:09 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:11:09 DebianLaptop kernel: wpa_supplicant D 0 644 1 0x00000004
Oct 15 08:11:09 DebianLaptop kernel: Call Trace:
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:11:09 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:11:09 DebianLaptop kernel: ? check_preempt_wakeup+0x103/0x250
Oct 15 08:11:09 DebianLaptop kernel: ? __ieee80211_stop_tx_ba_session+0x22/0x50 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? __ieee80211_stop_tx_ba_session+0x22/0x50 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? ieee80211_sta_tear_down_BA_sessions+0x2d/0x60 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? __sta_info_destroy_part1+0x45/0x560 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? __sta_info_flush+0x136/0x1a0 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? ieee80211_set_disassoc+0xb3/0x3a0 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? ieee80211_mgd_deauth+0x113/0x230 [mac80211]
Oct 15 08:11:09 DebianLaptop kernel: ? cfg80211_mlme_deauth+0xb0/0x1d0 [cfg80211]
Oct 15 08:11:09 DebianLaptop kernel: ? nl80211_deauthenticate+0x11b/0x160 [cfg80211]
Oct 15 08:11:09 DebianLaptop kernel: ? genl_family_rcv_msg+0x1e0/0x380
Oct 15 08:11:09 DebianLaptop kernel: ? enqueue_entity+0x110/0x6e0
Oct 15 08:11:09 DebianLaptop kernel: ? genl_rcv_msg+0x47/0x90
Oct 15 08:11:09 DebianLaptop kernel: ? genl_family_rcv_msg+0x380/0x380
Oct 15 08:11:09 DebianLaptop kernel: ? netlink_rcv_skb+0xe7/0x120
Oct 15 08:11:09 DebianLaptop kernel: ? genl_rcv+0x24/0x40
Oct 15 08:11:09 DebianLaptop kernel: ? netlink_unicast+0x184/0x230
Oct 15 08:11:09 DebianLaptop kernel: ? netlink_sendmsg+0x2cb/0x3b0
Oct 15 08:11:09 DebianLaptop kernel: ? sock_sendmsg+0x30/0x40
Oct 15 08:11:09 DebianLaptop kernel: ? ___sys_sendmsg+0x2d7/0x2f0
Oct 15 08:11:09 DebianLaptop kernel: ? legitimize_path.isra.24+0x28/0x50
Oct 15 08:11:09 DebianLaptop kernel: ? path_parentat+0x3e/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? filename_parentat+0x111/0x1b0
Oct 15 08:11:09 DebianLaptop kernel: ? d_walk+0xdc/0x2d0
Oct 15 08:11:09 DebianLaptop kernel: ? d_lru_del+0x50/0x50
Oct 15 08:11:09 DebianLaptop kernel: ? __sys_sendmsg+0x51/0x90
Oct 15 08:11:09 DebianLaptop kernel: ? __sys_sendmsg+0x51/0x90
Oct 15 08:11:09 DebianLaptop kernel: ? system_call_fast_compare_end+0xc/0x97
Oct 15 08:11:09 DebianLaptop kernel: INFO: task kworker/3:0:5278 blocked for more than 120 seconds.
Oct 15 08:11:09 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:11:09 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:11:09 DebianLaptop kernel: kworker/3:0 D 0 5278 2 0x00000000
Oct 15 08:11:09 DebianLaptop kernel: Workqueue: events cfg80211_mlme_unreg_wk [cfg80211]
Oct 15 08:11:09 DebianLaptop kernel: Call Trace:
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:11:09 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:11:09 DebianLaptop kernel: ? cfg80211_mlme_unreg_wk+0xe/0x20 [cfg80211]
Oct 15 08:11:09 DebianLaptop kernel: ? cfg80211_mlme_unreg_wk+0xe/0x20 [cfg80211]
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x181/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? worker_thread+0x4d/0x3a0
Oct 15 08:11:09 DebianLaptop kernel: ? kthread+0xfc/0x130
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x370/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? kthread_create_on_node+0x70/0x70
Oct 15 08:11:09 DebianLaptop kernel: ? ret_from_fork+0x25/0x30
Oct 15 08:11:09 DebianLaptop kernel: INFO: task kworker/3:2:6347 blocked for more than 120 seconds.
Oct 15 08:11:09 DebianLaptop kernel: Not tainted 4.13.0-1-amd64 #1 Debian 4.13.4-1
Oct 15 08:11:09 DebianLaptop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 15 08:11:09 DebianLaptop kernel: kworker/3:2 D 0 6347 2 0x00000000
Oct 15 08:11:09 DebianLaptop kernel: Workqueue: events linkwatch_event
Oct 15 08:11:09 DebianLaptop kernel: Call Trace:
Oct 15 08:11:09 DebianLaptop kernel: ? __schedule+0x3c8/0x860
Oct 15 08:11:09 DebianLaptop kernel: ? schedule+0x32/0x80
Oct 15 08:11:09 DebianLaptop kernel: ? schedule_preempt_disabled+0xa/0x10
Oct 15 08:11:09 DebianLaptop kernel: ? __mutex_lock.isra.1+0x2c3/0x4f0
Oct 15 08:11:09 DebianLaptop kernel: ? linkwatch_event+0xa/0x30
Oct 15 08:11:09 DebianLaptop kernel: ? linkwatch_event+0xa/0x30
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x181/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? worker_thread+0x4d/0x3a0
Oct 15 08:11:09 DebianLaptop kernel: ? kthread+0xfc/0x130
Oct 15 08:11:09 DebianLaptop kernel: ? process_one_work+0x370/0x370
Oct 15 08:11:09 DebianLaptop kernel: ? kthread_create_on_node+0x70/0x70
Oct 15 08:11:09 DebianLaptop kernel: ? ret_from_fork+0x25/0x30
Oct 15 08:11:17 DebianLaptop systemd[1]: networking.service: State 'stop-final-sigterm' timed out. Killing.
Oct 15 08:11:17 DebianLaptop systemd[1]: networking.service: Killing process 6411 (iwconfig) with signal SIGKILL.
Oct 15 08:11:17 DebianLaptop systemd[1]: NetworkManager.service: Processes still around after SIGKILL. Ignoring.
Oct 15 08:11:17 DebianLaptop systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring.
Oct 15 08:12:47 DebianLaptop systemd[1]: networking.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 15 08:12:47 DebianLaptop systemd[1]: Stopped Raise network interfaces.
Oct 15 08:12:47 DebianLaptop systemd[1]: networking.service: Unit entered failed state.
Oct 15 08:12:47 DebianLaptop systemd[1]: networking.service: Failed with result 'timeout'.
Oct 15 08:12:47 DebianLaptop systemd[1]: wpa_supplicant.service: State 'stop-final-sigterm' timed out. Killing.
Oct 15 08:12:47 DebianLaptop systemd[1]: wpa_supplicant.service: Killing process 644 (wpa_supplicant) with signal SIGKILL.
Oct 15 08:12:47 DebianLaptop systemd[1]: NetworkManager.service: State 'stop-final-sigterm' timed out. Killing.
Oct 15 08:12:47 DebianLaptop systemd[1]: NetworkManager.service: Killing process 552 (NetworkManager) with signal SIGKILL.
Oct 15 08:14:17 DebianLaptop systemd[1]: wpa_supplicant.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 15 08:14:17 DebianLaptop systemd[1]: Stopped WPA supplicant.
Oct 15 08:14:17 DebianLaptop systemd[1]: wpa_supplicant.service: Unit entered failed state.
Oct 15 08:14:17 DebianLaptop systemd[1]: wpa_supplicant.service: Failed with result 'timeout'.
Oct 15 08:14:17 DebianLaptop systemd[1]: NetworkManager.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 15 08:14:17 DebianLaptop systemd[1]: Stopped Network Manager.
Oct 15 08:14:17 DebianLaptop systemd[1]: NetworkManager.service: Unit entered failed state.
Oct 15 08:14:17 DebianLaptop systemd[1]: NetworkManager.service: Failed with result 'timeout'.

Obviously just the part of the log where this all happens. I need any help I can get trying to figure out why these processes are having a hard time shutting down.

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: A stop job is running on shutdown/reboot

#2 Post by L_V »

whitebunnyflock wrote:Just installed Debian stretch on my Carrizo AMD A10-8700P
I converted this to a "Buster"
You are so fast.
Testing is for testing, and you now test: it's a good training.

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#3 Post by whitebunnyflock »

L_V wrote:
whitebunnyflock wrote:Just installed Debian stretch on my Carrizo AMD A10-8700P
I converted this to a "Buster"
You are so fast.
Testing is for testing, and you now test: it's a good training.

I have been running debian stable for years and this testing thing is new to me. I don't have the first clue how to test. Would you have a starting point for testing this? Should i be submitting a bug report?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: A stop job is running on shutdown/reboot

#4 Post by Head_on_a_Stick »

whitebunnyflock wrote:Should i be submitting a bug report?
Probably not, the most likely cause here is an incorrect (or incomplete) transition to testing.

May I ask: why do you want to use one of Debian's development branches?

What exactly is wrong with Debian stable?

EDIT: also, please use code tags when posting terminal or log output, it makes it *much* more readable ;)
deadbang

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#5 Post by whitebunnyflock »

Head_on_a_Stick wrote:
whitebunnyflock wrote:Should i be submitting a bug report?
Probably not, the most likely cause here is an incorrect (or incomplete) transition to testing.

May I ask: why do you want to use one of Debian's development branches?

What exactly is wrong with Debian stable?
mainly because I helped to test kernel code to enable AMD_IOMMU and that code works and now is in kernel 4.13. Also because I want firefox newer than version 45 as 45 is so slow and mozilla has made major leaps since then.

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#6 Post by whitebunnyflock »

whitebunnyflock wrote:
Head_on_a_Stick wrote:
whitebunnyflock wrote:Should i be submitting a bug report?
Probably not, the most likely cause here is an incorrect (or incomplete) transition to testing.

May I ask: why do you want to use one of Debian's development branches?

What exactly is wrong with Debian stable?
also because kernel 4.9 doesn't run properly on my hardware (hard freezing and the like)

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: A stop job is running on shutdown/reboot

#7 Post by Head_on_a_Stick »

The backported kernel is on 4.12 atm but buster is on 4.13 so it should make it through soon.

https://packages.debian.org/stretch-bac ... mage-amd64

https://backports.debian.org/Instructions/

For newer FF, just install the upstream version locally:

https://download.mozilla.org/?product=f ... lang=en-GB
deadbang

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: A stop job is running on shutdown/reboot

#8 Post by Head_on_a_Stick »

whitebunnyflock wrote:mainly because I helped to test kernel code to enable AMD_IOMMU and that code works and now is in kernel 4.13
Debian patch their kernel version extensively, would Arch not be better for that sort of thing?
deadbang

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#9 Post by whitebunnyflock »

I wouldn't want to run Arch just to test problems that AMD had not previously patched for the Carrizo specification. I actually did it in Ubuntu.

I really appreciate the other help though. Would there be a way to get a newer version of Mesa (ie: version 17 +) in stable Debian or would that break stuff?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: A stop job is running on shutdown/reboot

#10 Post by Head_on_a_Stick »

whitebunnyflock wrote:would that break stuff?
^ This.

https://www.archlinux.org/packages/extra/x86_64/mesa/

Just sayin'...

:mrgreen:
deadbang

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#11 Post by whitebunnyflock »

I appreciate it, but Debian or derivatives is a go to for me. So I have now installed Debian stable on this machine and will use my modprobe.blacklist=radeon and modprobe.blacklist=amdgpu on the kernel command line until kernel 4.13 is released into the backports repository.

thanks for all the advice!

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#12 Post by whitebunnyflock »

although manjaro looks pretty good to me.....

whitebunnyflock
Posts: 10
Joined: 2016-12-20 18:50

Re: A stop job is running on shutdown/reboot

#13 Post by whitebunnyflock »

for other people running buster the problem is actually between the kernel and the atheros wi-fi hardware, This is fixed in a later kernel and I am now running 4.13.7 from the mainline kernels and the laptop will now shutdown in about 12 seconds.

Post Reply