On 2019-01-23 8:43 p.m., He Zhe wrote:
On 1/24/19 1:13 AM, Bruce Ashfield wrote:
On 1/23/19 2:45 AM, zhe...@windriver.com wrote:
From: He Zhe
https://lore.kernel.org/lkml/41c574bfdce7490597079dae8f328...@svr-chch-ex1.atlnz.lc/
The initialization code of interrupt backoff work might
On 1/24/19 1:13 AM, Bruce Ashfield wrote:
> On 1/23/19 2:45 AM, zhe...@windriver.com wrote:
>> From: He Zhe
>>
>> https://lore.kernel.org/lkml/41c574bfdce7490597079dae8f328...@svr-chch-ex1.atlnz.lc/
>>
>> The initialization code of interrupt backoff work might reference NULL
>> pointer and
On 1/23/19 2:45 AM, zhe...@windriver.com wrote:
From: He Zhe
https://lore.kernel.org/lkml/41c574bfdce7490597079dae8f328...@svr-chch-ex1.atlnz.lc/
The initialization code of interrupt backoff work might reference NULL
pointer and cause the following crash, if no port was found.
[ 10.017727]
From: He Zhe
https://lore.kernel.org/lkml/41c574bfdce7490597079dae8f328...@svr-chch-ex1.atlnz.lc/
The initialization code of interrupt backoff work might reference NULL
pointer and cause the following crash, if no port was found.
[ 10.017727] CPU 0 Unable to handle kernel paging request at
