Re: [PATCH 1/4] ath10k: provide firmware crash info via debugfs.

[Kalle Valo <kvalo@qca.qualcomm.com>]

Ben Greear <greearb@candelatech.com> writes:

> On 06/05/2014 11:55 PM, Kalle Valo wrote:
>> greearb@candelatech.com writes:
>> 
>>> From: Ben Greear <greearb@candelatech.com>
>>>
>>> Store the firmware crash registers and last 128 or so
>>> firmware debug-log ids and present them to user-space
>>> via debugfs.
>>>
>>> Should help with figuring out why the firmware crashed.
>>>
>>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>> 
>> [...]
>> 
>>> +	dump_data->kernel_ver_code = LINUX_VERSION_CODE;
>>> +	strncpy(dump_data->kernel_ver, VERMAGIC_STRING,
>>> +		sizeof(dump_data->kernel_ver) - 1);
>> 
>> Other thing nice to have here is the kernel timestamp in the kernel log
>> "[123456.4321]". How difficult would it be to add that to the dump?
>
> It's easy to get the time-of-day, if that is what you mean.

That's actually seconds from boot, not wall time:

[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 2793.393 MHz processor
[    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 5586.78 BogoMIP
S (lpj=27933930)
[    0.000009] pid_max: default: 32768 minimum: 301
[    0.000016] ACPI: Core revision 20140214
[    0.023399] ACPI: All ACPI Tables successfully acquired

There's function print_time() which prints the time and the timestamp
apparently comes from local_clock().

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k