On 11/12/14(Thu) 11:31, frantisek holop wrote:
> i think this page fault is triggered by jenkins
> during resume.
> login: kernel: page fault trap, code=0
> Stopped at in_selectsrc+0xd8: movl 0xf0(%esi),%ebx
> ddb{0}> trace
> in_selectsrc(f617cdc8,d80b6714,d35d9270,d8cfac44,d8cfac34) at
> in_selectsrc+0xd8
>
> udp_output(d8cfabfc,d80b6900,d80b6700,0,0) at udp_output+0xf8
> sosend(d7f881c8,d80b6700,f617ce90,d80b6900,0) at sosend+0x44b
> sendit(d84f4b40,103,f617cef4,0,f617cf80) at sendit+0x1e1
> sys_sendto(d84f4b40,f617cf60,f617cf80,d0568b5a,d84f4b40) at sys_sendto+0x6c
> syscall() at syscall+0x144
> --- syscall (number 259) ---
> 0x2:
> ddb{0}>
>
>
> screenshots:
> obiit.org/f/pagefault0.jpg
> obiit.org/f/pagefault1.jpg
>
> the running java process is jenkins.
> i cannot reproduce it all the time, but now it has
> happened twice: suspend at the end of the day,
> go to sleep, next day resume, page fault.
> both times when i was using jenkins.
>
> i can provide more information when it happens again,
> just let me know what exactly...
Well... what's your dmesg?
What's your network configuration, more explicitly are you using any USB
device and how?
What kind of test is jenkins running? How is it multicast related?
