On 6/6/2018 12:53 AM, Brian Norris wrote:
Unfortunately, devcoredump is a bit lacking in documentation. Arend was
writing a bit for the new trigger mechanism at least.
I did indeed write ABI doc for user-space trigger mechanism and you
brought up the need to have ABI doc for devcoredump. I
On 6/6/2018 7:04 PM, Ben Greear wrote:
On 06/05/2018 03:53 PM, Brian Norris wrote:
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
On 06/05/2018 03:53 PM, Brian Norris wrote:
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
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
