Hi,
On Tue, Jun 05, 2018 at 03:27:28PM -0700, Ben Greear wrote:
> I have been testing ath10k on 4.16, which uses the devcoredump API
> to notify about dumps.
>
> I am able to see the binary crash dump at /sys/class/devcoredump/devcd2/data,
> for instance, but if I do another crash quickly, I get
I have been testing ath10k on 4.16, which uses the devcoredump API
to notify about dumps.
I am able to see the binary crash dump at /sys/class/devcoredump/devcd2/data,
for instance, but if I do another crash quickly, I get no new uevent sent
and no new crash.
I see there is a 5 minute timer on
Hi Arend,
> Did you miss this series? Any comments?
I think I applied it?
I have - however - often been lazy in sending out "applied" emails, so
there probably wasn't one. Need to finally configure and use Kalle's
script ...
johannes
Hello Eyal Reizer,
The patch 6e91d48371e7: "wlcore: sdio: check for valid platform
device data before suspend" from May 28, 2018, leads to the following
static checker warning:
drivers/net/wireless/ti/wlcore/sdio.c:404 wl1271_suspend()
warn: missing error code here?
This is a static checker fix, not something I have tested. The issue
is that on the second iteration through the loop, we jump forward by
le32_to_cpu(auth_req->length) bytes. The problem is that if the length
is more than "buflen" then we end up with a negative "buflen". A
negative buflen is
>
> * Tony Lindgren [180605 04:22]:
> > * Reizer, Eyal [180603 06:07]:
> > > I have noticed the following recovery a couple of times on my setup
> when the board was
> > > just sitting for a long time with just pings
> > > It starts with a firmware recovery started from the interrupt handler
* Tony Lindgren [180605 04:22]:
> * Reizer, Eyal [180603 06:07]:
> > I have noticed the following recovery a couple of times on my setup when
> > the board was
> > just sitting for a long time with just pings
> > It starts with a firmware recovery started from the interrupt handler but
> >
