From: Gabriel C <nix.or.die@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>,
Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
dex77@frugalware.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: atk10k Unknown eventid and WARN() on resume with kernel 4.19
Date: Thu, 15 Nov 2018 02:06:47 +0100 [thread overview]
Message-ID: <CAEJqkgiz0-5m5uDUW2vzCatxHPX2Gi6oPQwR_J5Y4fV8iuiguw@mail.gmail.com> (raw)
In-Reply-To: <CAEJqkghgyYMxRc8-wnF-J1CGhuYD2vfVDSiLU1A0fwpXKN7Huw@mail.gmail.com>
Am Mi., 14. Nov. 2018 um 23:16 Uhr schrieb Gabriel C <nix.or.die@gmail.com>:
> > > Hello,
> > >
> > > starting with kernel 4.19 we noticed 'Unknown eventid: xxxx' warnings
> > > on our Laptops.
> > >
> > > ...
> > >
> > > crazy@devnull:~$ dmesg | grep Unknow
> > > [ 7.144998] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [ 7.147758] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > > [ 9.441654] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [ 9.444446] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > > [ 11.770997] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [ 11.773787] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > > [320339.374108] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [320339.377020] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > > [320342.128664] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [320342.131447] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > > [320344.452864] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
> > > [320344.455696] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
> > >
> > > ....
> > >
> > > Both boxes also hits the following WARN*() on resume from S3:
> > >
> > Uh sorry .. Gmail doesn't like long lines it seems.
> > There the WARN() message:
> >
> > http://ftp.frugalware.org/pub/other/people/crazy/warn.txt
> >
> > >
> > > Please let me know if you need an dmesg or any other informations.
>
>
> Added pm list maybe someone there got some idea ?
>
> Also same issue reported there :
> https://bugzilla.kernel.org/show_bug.cgi?id=201499
>
The WARN_ON() on resume seems to be triggered after commit cd93b83ad927b.
BR,
Gabriel C
prev parent reply other threads:[~2018-11-15 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 20:01 atk10k Unknown eventid and WARN() on resume with kernel 4.19 Gabriel C
2018-11-03 20:11 ` Gabriel C
2018-11-14 22:16 ` Gabriel C
2018-11-15 1:06 ` Gabriel C [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=CAEJqkgiz0-5m5uDUW2vzCatxHPX2Gi6oPQwR_J5Y4fV8iuiguw@mail.gmail.com \
--to=nix.or.die@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=dex77@frugalware.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeepc@codeaurora.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).