On 06/08/14 13:18, Liu hua wrote:
> On 2014/8/6 17:46, Marc Zyngier wrote:
>> Hi Liu,
>>
>> On 06/08/14 09:43, Liu hua wrote:
>>> 于 2014/8/4 17:43, Marc Zyngier 写道:
Hi Liu,
On 04/08/14 05:17, Liu Hua wrote:
> When using kdump on ARM platform, if kernel panics in interrupt handler
On 2014/8/6 17:46, Marc Zyngier wrote:
> Hi Liu,
>
> On 06/08/14 09:43, Liu hua wrote:
>> 于 2014/8/4 17:43, Marc Zyngier 写道:
>>> Hi Liu,
>>>
>>> On 04/08/14 05:17, Liu Hua wrote:
When using kdump on ARM platform, if kernel panics in interrupt handler
(maybe PPI), the capture kernel can n
Hi Liu,
On 06/08/14 09:43, Liu hua wrote:
> 于 2014/8/4 17:43, Marc Zyngier 写道:
>> Hi Liu,
>>
>> On 04/08/14 05:17, Liu Hua wrote:
>>> When using kdump on ARM platform, if kernel panics in interrupt handler
>>> (maybe PPI), the capture kernel can not recive certain interrupt, and
>>> fails to boot
于 2014/8/4 17:43, Marc Zyngier 写道:
> Hi Liu,
>
> On 04/08/14 05:17, Liu Hua wrote:
>> When using kdump on ARM platform, if kernel panics in interrupt handler
>> (maybe PPI), the capture kernel can not recive certain interrupt, and
>> fails to boot.
>>
>> On this situation, We have read register G
Hi Liu,
On 04/08/14 05:17, Liu Hua wrote:
> When using kdump on ARM platform, if kernel panics in interrupt handler
> (maybe PPI), the capture kernel can not recive certain interrupt, and
> fails to boot.
>
> On this situation, We have read register GICC_IAR. But we have no chance
> to write rel
When using kdump on ARM platform, if kernel panics in interrupt handler
(maybe PPI), the capture kernel can not recive certain interrupt, and
fails to boot.
On this situation, We have read register GICC_IAR. But we have no chance
to write relative bit to register GICC_EOIR (kernel paniced before)
6 matches
Mail list logo