I just want to fix the failure of kdump with notsc.
I found the bad commit by bisect in kernel upstream.
And I wan to know Other intel processor must disable I/O APIC firstly?
Can you give me a determinate answer to the problem?
BTW, I have sent a patch to fix , but so far, no response. https://lkml.org/lkml/2016/6/29/18
Ping ..., any feedback.
When kernel encounter panic (crash), it will disable APIC in the first kernel, and then start the capture kernel that not be interrupted.
Nope, I just want to fix a bug in kernel, which seems be related to the shutdown sequence between IO-APIC and Local APIC.
I cann't find any SPECs for it, but only erratum AVR31 for "Intel Atom Processor C2000 Product Family Specification Update".My question is , Must we disable I/O APIC firstly for any other intel processor
The bug I have show you in the above message.
Are you reporting this issue as a bug on the CPU or as a bug for the Kernel shutdown sequence between io-apic and local-apic?
If you already submitted a patch for the Kernel, I would assume this pointing out to the Kernel and not to the CPU, is this a correct assumption?
Or do you want to know if you have to shutdown IO-APIC before Local APIC?
By the way, I am moving this community over to the Processors forum.
Thanks for your reply.
I want to know if I have to shutdown IO-APIC before Local APIC.
But It seems that there's no consensus on the shutdown sequence .
Indeed, I put forward a new solution,
which can fix the dump-capture kernel hang and avoid touching the shutdown sequence between io-apic and local-apic .