Hello
last git master checkout seems correct this problem
Thanks
Nicolas Prochazka.
2012/7/28 nicolas prochazka :
> hello again,
> bisect git gives ( after 13 steps) :
> 58bca4a8fa90fcf9069379653b396b2cec642f7f is the first bad commit
>
> Regards,
> Nicolas Prochazka
>
&g
Hello
last git master checkout seems correct this problem
Thanks
Nicolas Prochazka.
2012/7/28 nicolas prochazka prochazka.nico...@gmail.com:
hello again,
bisect git gives ( after 13 steps) :
58bca4a8fa90fcf9069379653b396b2cec642f7f is the first bad commit
Regards,
Nicolas Prochazka
2012
hello again,
bisect git gives ( after 13 steps) :
58bca4a8fa90fcf9069379653b396b2cec642f7f is the first bad commit
Regards,
Nicolas Prochazka
2012/7/24 Thadeu Lima de Souza Cascardo :
> On Mon, Jul 23, 2012 at 11:15:09PM +0200, nicolas prochazka wrote:
>> Hello,
>> I 'm tr
hello again,
bisect git gives ( after 13 steps) :
58bca4a8fa90fcf9069379653b396b2cec642f7f is the first bad commit
Regards,
Nicolas Prochazka
2012/7/24 Thadeu Lima de Souza Cascardo casca...@linux.vnet.ibm.com:
On Mon, Jul 23, 2012 at 11:15:09PM +0200, nicolas prochazka wrote:
Hello,
I 'm
Hello,
I 'm trying differents versions with differents results
- commit f044db4cb4bf16893812d35b5fbeaaf3e30c9215 : bug is not reproductible
- 3.5rc7 : bug is reproductible(cf new dump )
- master branch : bug is reproductible
Regards,
Nicolas Prochazka
Jul 23 21:10:05 positronic18696
Hello,
I 'm trying differents versions with differents results
- commit f044db4cb4bf16893812d35b5fbeaaf3e30c9215 : bug is not reproductible
- 3.5rc7 : bug is reproductible(cf new dump )
- master branch : bug is reproductible
Regards,
Nicolas Prochazka
Jul 23 21:10:05 positronic18696
Well done
1fd36adcd98c14d2fd97f545293c488775cb2823 : the bug occurs ( cf dump )
1dce27c5aa6770e9d195f2bb7db1db3d4dde5591 : the bug not occurs
Regards,
Nicolas Prochazka.
dump / 1fd36adcd98c14d2fd97f545293c488775cb2823
lloc_fd: slot 71 not NULL!
alloc_fd: slot 71 not NULL!
alloc_fd: slot 71
400, Dave Jones wrote:
>> On Fri, Jul 20, 2012 at 11:56:06AM +0200, nicolas prochazka wrote:
>>
>> > [ 2384.900061] BUG: unable to handle kernel paging request at
>> 0001002f
>>
>> That '1' looks like a random bit flip. Try running memtest86.
>
Hello;
I can reproduce this problem on five differents servers,
I can try a memtest86.
regards,
Nicolas Prochazka.
complete dump :
596.322369] BUG: unable to handle kernel paging request at 0001003b
[ 596.322622] IP: [] tid_fd_revalidate+0x84/0x1a0
[ 596.322828] PGD 7d6c20067 PUD 0
GNU/Linux
Regards,
Nicolas Prochazka.
[ 2384.900061] BUG: unable to handle kernel paging request at 0001002f
[ 2384.900307] IP: [] dup_fd+0x160/0x2e0
[ 2384.905492] PGD 4e9bab067 PUD 0
[ 2384.910010] Oops: 0002 [#4] SMP
[ 2384.910010] CPU 6
[ 2384.910010] Modules linked in: kvm_intel kvm
GNU/Linux
Regards,
Nicolas Prochazka.
[ 2384.900061] BUG: unable to handle kernel paging request at 0001002f
[ 2384.900307] IP: [8115a250] dup_fd+0x160/0x2e0
[ 2384.905492] PGD 4e9bab067 PUD 0
[ 2384.910010] Oops: 0002 [#4] SMP
[ 2384.910010] CPU 6
[ 2384.910010] Modules linked
Hello;
I can reproduce this problem on five differents servers,
I can try a memtest86.
regards,
Nicolas Prochazka.
complete dump :
596.322369] BUG: unable to handle kernel paging request at 0001003b
[ 596.322622] IP: [811a3654] tid_fd_revalidate+0x84/0x1a0
[ 596.322828] PGD
, 2012 at 09:21:53AM -0400, Dave Jones wrote:
On Fri, Jul 20, 2012 at 11:56:06AM +0200, nicolas prochazka wrote:
[ 2384.900061] BUG: unable to handle kernel paging request at
0001002f
That '1' looks like a random bit flip. Try running memtest86.
Looks more a 32-bit value of 1
Well done
1fd36adcd98c14d2fd97f545293c488775cb2823 : the bug occurs ( cf dump )
1dce27c5aa6770e9d195f2bb7db1db3d4dde5591 : the bug not occurs
Regards,
Nicolas Prochazka.
dump / 1fd36adcd98c14d2fd97f545293c488775cb2823
lloc_fd: slot 71 not NULL!
alloc_fd: slot 71 not NULL!
alloc_fd: slot 71
14 matches
Mail list logo