From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k hang on rmmod after fw crash in 4.13.3+ hacks
Date: Tue, 10 Oct 2017 12:43:11 -0700 [thread overview]
Message-ID: <8ee59286-42a6-7396-d420-185fefd72b57@candelatech.com> (raw)
In-Reply-To: <d18529ba-1d91-e9c6-4719-4586e6b5b287@candelatech.com>
On 10/10/2017 12:07 PM, Ben Greear wrote:
> I loaded a crashing firmware (it crashes early since it ran OOM), and
> then tried to rmmod it. rmmod hangs, with this stack:
Looks like this is a hang related to napi, and I had a patch from an
older kernel that is probably not needed anymore...maybe it causes the
issue. I'll test with that removed...
Thanks,
Ben
>
> [root@ben-ota-2 ~]# cat /proc/32491/stack
> [<ffffffff8113c51d>] flush_work+0x1fd/0x2d0
> [<ffffffff8113f031>] __cancel_work_timer+0x111/0x190
> [<ffffffff8113f0bb>] cancel_work_sync+0xb/0x10
> [<ffffffffa0b0a054>] ath10k_core_unregister+0x14/0xa0 [ath10k_core]
> [<ffffffffa07c7dcd>] ath10k_pci_remove+0x2d/0x70 [ath10k_pci]
> [<ffffffff81528834>] pci_device_remove+0x34/0xb0
> [<ffffffff81656b18>] device_release_driver_internal+0x158/0x210
> [<ffffffff81656c1b>] driver_detach+0x3b/0x80
> [<ffffffff81655ad3>] bus_remove_driver+0x53/0xd0
> [<ffffffff81657737>] driver_unregister+0x27/0x40
> [<ffffffff81526ff4>] pci_unregister_driver+0x24/0x90
> [<ffffffffa07ca922>] ath10k_pci_exit+0x10/0x6ee [ath10k_pci]
> [<ffffffff811c64c1>] SyS_delete_module+0x1e1/0x2a0
> [<ffffffff81003d34>] do_syscall_64+0x64/0x140
> [<ffffffff819b77c9>] entry_SYSCALL64_slow_path+0x25/0x25
> [<ffffffffffffffff>] 0xffffffffffffffff
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2017-10-10 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 19:07 ath10k hang on rmmod after fw crash in 4.13.3+ hacks Ben Greear
2017-10-10 19:43 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ee59286-42a6-7396-d420-185fefd72b57@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox