On 05/23/2013 02:53 PM, Jack Wang wrote:
> On 2013年05月23日 19:41, Doug Ledford wrote:
>> On 05/23/2013 11:38 AM, Jack Wang wrote:
>>> Tainted: G O 3.4.23-pserver-hotfix+ #109 System manufacturer
>> ^^^
>>
>> I would try a newer kernel. There are a couple known
On 2013年05月23日 19:41, Doug Ledford wrote:
> On 05/23/2013 11:38 AM, Jack Wang wrote:
>> Tainted: G O 3.4.23-pserver-hotfix+ #109 System manufacturer
> ^^^
>
> I would try a newer kernel. There are a couple known issues fixed since
> this kernel (including a
On 05/23/2013 11:38 AM, Jack Wang wrote:
> Tainted: G O 3.4.23-pserver-hotfix+ #109 System manufacturer
^^^
I would try a newer kernel. There are a couple known issues fixed since
this kernel (including a memory corrupter that was involved with
neighbor list
On 05/21/2013 05:19 PM, Jack Wang wrote:
> On 05/21/2013 02:51 PM, Sebastian Riemer wrote:
>> On 17.05.2013 16:16, Jack Wang wrote:
>>> unable to handle kernel paging request
>>
>> Hi Jack,
>>
>> this should be related to the list corruption in IPoIB as list_del()
>> sets the LIST_POISON1 and LIST_
On 05/21/2013 02:51 PM, Sebastian Riemer wrote:
> On 17.05.2013 16:16, Jack Wang wrote:
>> unable to handle kernel paging request
>
> Hi Jack,
>
> this should be related to the list corruption in IPoIB as list_del()
> sets the LIST_POISON1 and LIST_POISON2 pointers.
> Referencing these results in
On 17.05.2013 16:16, Jack Wang wrote:
> unable to handle kernel paging request
Hi Jack,
this should be related to the list corruption in IPoIB as list_del()
sets the LIST_POISON1 and LIST_POISON2 pointers.
Referencing these results in page faults according to the documentation
in the code.
Cheer
Hi All,
I've saw this before, anyone have suggestion how to fix this.
May 17 16:09:13 ib2 kernel: [ 528.500381] BUG: unable to handle kernel
paging request at 00070a78
May 17 16:09:13 ib2 kernel: [ 528.500529] IP: []
ipoib_cm_tx_handler+0x30/0x2a0 [ib_ipoib]
May 17 16:09:13 ib2 kernel:
