> [...]
>
Hi, ulf
We find this bug on Intel-C3230RK platform for very small probability.
Whereas I can easily reproduce this case if I add a mdelay(1) or
longer delay as Jialing did.
This patch seems useful to me. Should we push it forward? :)
>>>
>>>
>>> It
在 2015/8/28 18:22, Jialing Fu 写道:
[...]
Hi, ulf
We find this bug on Intel-C3230RK platform for very small probability.
Whereas I can easily reproduce this case if I add a mdelay(1) or
longer delay as Jialing did.
This patch seems useful to me. Should we push it forward? :)
It seems like
[...]
>>> Hi, ulf
>>>
>>> We find this bug on Intel-C3230RK platform for very small probability.
>>>
>>> Whereas I can easily reproduce this case if I add a mdelay(1) or
>>> longer delay as Jialing did.
>>>
>>> This patch seems useful to me. Should we push it forward? :)
>>
>>
>> It seems like
[...]
>>> Hi, ulf
>>>
>>> We find this bug on Intel-C3230RK platform for very small probability.
>>>
>>> Whereas I can easily reproduce this case if I add a mdelay(1) or longer
>>> delay as Jialing did.
>>>
>>> This patch seems useful to me. Should we push it forward? :)
>>
>>
>> It seems like a
在 2015/8/28 16:55, Ulf Hansson 写道:
On 28 August 2015 at 05:25, Shawn Lin wrote:
On 2015/8/28 11:13, Shawn Lin wrote:
From: Jialing Fu
The following panic is captured in ker3.14, but the issue still exists
in latest kernel.
On 28 August 2015 at 05:25, Shawn Lin wrote:
> On 2015/8/28 11:13, Shawn Lin wrote:
>>
>> From: Jialing Fu
>>
>> The following panic is captured in ker3.14, but the issue still exists
>> in latest kernel.
>> -
>> [ 20.738217] c
On 2015/8/28 11:13, Shawn Lin wrote:
From: Jialing Fu
The following panic is captured in ker3.14, but the issue still exists
in latest kernel.
-
[ 20.738217] c0 3136 (Compiler) Unable to handle kernel NULL pointer
dereferenc
From: Jialing Fu
The following panic is captured in ker3.14, but the issue still exists
in latest kernel.
-
[ 20.738217] c0 3136 (Compiler) Unable to handle kernel NULL pointer
dereference
at virtual address 0578
..
[
