On Thu, 28 Jan 2021 17:22:30 +0000 "Luck, Tony" <tony.luck@xxxxxxxxx> wrote: > > Getting a full memory dump after a machine check generally isn't > all that useful anyway. The problem was (almost certainly) h/w, so > not much benefit in decoding the dump to find which code was running > when the h/w signalled. The purpose I try to collect the coredump log is not to identify what the backtrace is, I want to confirm if this panic is really needed, there are too many panics in production environment with MCA Recovery Enabled, and no kernel log is collected, in some way we can't find the benifits from MCA recovery, And for purley this feature cost too much. And the unexpected NMI for fatal memory error is not the right way to get work done. This is not right, and shouldn't happen. > A second bite at getting the error logs from the death of the first > kernel is worth it though. I am not smart enough to get the point. I have paid a lot of time for this patch, I need an result even it doesn't work. so i like the reply like this: 1. this patch is meaningless, and should be rejected. 2. this issue is real, but we need other methond, not this patch. 3. the patch need to improve. Thanks Aili Yao
