Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1628414
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing |
| Date | 2017-04-21 20:20 +0200 |
| Message-ID | <tyLjY-Fc-29@gated-at.bofh.it> (permalink) |
| References | <txKpX-3KK-7@gated-at.bofh.it> <txKzD-3PB-7@gated-at.bofh.it> <tyFRg-5KO-11@gated-at.bofh.it> <tyLjY-Fc-31@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Apr 21, 2017 at 10:04:35AM -0600, Baicar, Tyler wrote:
> This is basically what I already had in v14...you asked to move it into a
> different if-statement? https://lkml.org/lkml/2017/4/12/397
Well, clearly I've been smoking some nasty potent sh*t. :-\
/me goes and looks at the spec:
"Bit 0 – Timestamp is precise if this bit is set and correlates to the
time of the error event."
So why are we even printing the timestamp when !precise?
IOW, I think we should do:
if (!(timestamp[3] & 0x1))
printk("%stimestamp imprecise\n", pfx);
else {
sec = ..
min = ...
...
}
and print the actual values only when the timestamp is precise.
Otherwise it has *some* values which could just as well be completely
random. And it's not like we're reporting the error tomorrow - it is
mostly a couple of seconds from logging to the fw pushing it out...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V15 00/11] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64 Tyler Baicar <tbaicar@codeaurora.org> - 2017-04-19 01:10 +0200
[PATCH V15 04/11] efi: parse ARM processor error Tyler Baicar <tbaicar@codeaurora.org> - 2017-04-19 01:10 +0200
Re: [PATCH V15 04/11] efi: parse ARM processor error Borislav Petkov <bp@alien8.de> - 2017-04-21 20:30 +0200
Re: [PATCH V15 04/11] efi: parse ARM processor error "Baicar, Tyler" <tbaicar@codeaurora.org> - 2017-04-21 20:30 +0200
Re: [PATCH V15 04/11] efi: parse ARM processor error Borislav Petkov <bp@alien8.de> - 2017-04-24 20:00 +0200
[PATCH V15 05/11] arm64: exception: handle Synchronous External Abort Tyler Baicar <tbaicar@codeaurora.org> - 2017-04-19 01:10 +0200
[PATCH V15 03/11] cper: add timestamp print to CPER status printing Tyler Baicar <tbaicar@codeaurora.org> - 2017-04-19 01:20 +0200
Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing Borislav Petkov <bp@alien8.de> - 2017-04-21 14:30 +0200
Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing Borislav Petkov <bp@alien8.de> - 2017-04-21 20:20 +0200
Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing "Baicar, Tyler" <tbaicar@codeaurora.org> - 2017-04-21 20:20 +0200
Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing Borislav Petkov <bp@alien8.de> - 2017-04-21 20:30 +0200
Re: [PATCH V15 03/11] cper: add timestamp print to CPER status printing "Baicar, Tyler" <tbaicar@codeaurora.org> - 2017-04-21 20:50 +0200
csiph-web