From: Anil Nair <anilcoll90@gmail.com>
To: linux-wireless@ver.kernel.org, ath10k@lists.infradead.org
Cc: mcroce@redhat.com
Subject: Re: PROBLEM: Issue with wireless driver after resume from suspend.
Date: Tue, 14 Nov 2017 10:14:44 +0530 [thread overview]
Message-ID: <20171114044444.GA4030@gmail.com> (raw)
In-Reply-To: <CAGnkfhz=XJUQrXJR-ZbNxk+gBN_bh8+qYzv=_V_KhV0mV2+tmg@mail.gmail.com>
On Tue, Oct 31, 2017 at 05:10:25PM +0100, Matteo Croce wrote:
> On Tue, Oct 31, 2017 at 7:51 AM, Anil Nair <anilcoll90@gmail.com> wrote:
> > Hi All,
> >
> > I am having a issue with the wireless driver in my laptop. Attached information
> > pertaining to the issue.
> >
> > [1.] One line summary of the problem:
> >
> > Wifi not working after resuming from suspend state.
> >
> > [2.] Full description of the problem/report:
> >
> > I had put my laptop in suspend mode, after resmuing the laptop from suspend
> > mode wifi stopped working, or rather not responding I tried switching the
> > airplane mode on then off still no effect.
> >
> > [3.] Keywords (i.e., modules, networking, kernel):
> >
> > Networking particularly Wireless Networking.
> >
> > [4.] Kernel information
> >
> > 4.13.5
> >
> > [4.1.] Kernel version (from /proc/version):
> >
> > Linux version 4.13.5anil-1017 (root@anilnair-lenovo)
> > (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5))
> > #1 SMP Sat Oct 14 12:30:16 IST 2017
> >
> > [4.2.] Kernel .config file:
> >
> > Attached in the below mail file named config_kernel.txt
> >
> > [5.] Most recent kernel version which did not have the bug:
> >
> > 4.4.0
> >
> > [6.] Output of Oops.. message (if applicable) with symbolic information
> > resolved (see Documentation/admin-guide/oops-tracing.rst)
> >
> > Attached in the below mail file named error_log.txt
> >
> > [8.1.] Software (add the output of the ver_linux script here)
> >
> > Attached in the below mail file named software_version.txt
> >
> > [8.2.] Processor information (from /proc/cpuinfo):
> >
> > Attached in the below mail file named cpu_config.txt
> >
> > [8.3.] Module information (from /proc/modules):
> >
> > Attached in the below mail file named modules_config.txt
> >
> > [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> >
> > Attached in the below mail file named ioports_config.txt,iomem_config.txt,
> >
> > [8.5.] PCI information ('lspci -vvv' as root)
> >
> > Attached in the below mail file named pci_config.txt
> >
> > [8.6.] SCSI information (from /proc/scsi/scsi)
> >
> > Attached in the below mail file named cpu_config.txt
> >
> > [X.] Other notes, patches, fixes, workarounds:
> >
> > A reboot fixes the issue.
> >
> > All Files are compressed in the tar and sent.
> > Let me know what went wrong and how can i fix it.
> > Let me know if any further information is required.
> >
> > Thanking You.
> >
> > --
> > Regards,
> > Anil Nair
> >
>
> I have the same issue with ath10k and kernel 4.13.10.
> If I suspend the system when the card is up it won't work anymore
> until I rmmod and modprobe ath10k_pci again.
> rmmod after suspend can take up to 10 minutes and sometimes crashes the system.
> Removing the driver _before_ suspend and inserting it back after
> resume actually works and it's what I'm using as not-so-temporary
> workaround.
>
> Regards,
> --
> Matteo Croce
> per aspera ad upstream
Hi,
Ping a reminder regarding this issue.
if the issue has been fixed in the recent kernel release do let me know i would to try it out.
--
Regards,
Anil Nair
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2017-11-14 4:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171031065122.GA24662@gmail.com>
[not found] ` <1509434604.4492.192.camel@coelho.fi>
2017-10-31 8:31 ` PROBLEM: Issue with wireless driver after resume from suspend Kalle Valo
2017-10-31 12:32 ` Anil Nair
2017-10-31 16:10 ` Matteo Croce
2017-11-14 4:44 ` Anil Nair [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=20171114044444.GA4030@gmail.com \
--to=anilcoll90@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@ver.kernel.org \
--cc=mcroce@redhat.com \
/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