Andrew,
> So what you should do before generating the leak tool output is to put
> heavy memory pressure on the machine to try to get it to free up as much of
> that pagecache as possible. bzero(malloc(lots)) will do it - create a real
> swapstorm, then do swapoff to kill remaining swapcache
Andrew,
So what you should do before generating the leak tool output is to put
heavy memory pressure on the machine to try to get it to free up as much of
that pagecache as possible. bzero(malloc(lots)) will do it - create a real
swapstorm, then do swapoff to kill remaining swapcache as
> I'm trying the little leak tracking patch from Alexander Nyberg now.
Here are the results (only backtraces with more than 10k counts
included). The leak was at 1G of memory at the time I ran this, so its
safe to say 10k page allocations ain't enough to explain it :-)
I also attach a hacked
Randy,
> I have applied the patch from Linus for the leak in
> free_pipe_info()
...
> Do you have today's memleak patch applied? (cut-n-paste below).
yes :-)
I'm trying the little leak tracking patch from Alexander Nyberg now.
Cheers, Tridge
-
To unsubscribe from this list: send the line
I've fixed up the problems I had with raid, and am now testing the
recent xattr changes with dbench and nbench.
The problem I've hit now is a severe memory leak. I have applied the
patch from Linus for the leak in free_pipe_info(), and still I'm
leaking memory at the rate of about
Andreas,
I'm starting to think the bug I saw is hardware error. I just got this
while trying to reproduce it tonight:
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : firmware status is 4000 4
Jan 24 02:43:32 dev4-003 kernel: scsi: Device
I've fixed up the problems I had with raid, and am now testing the
recent xattr changes with dbench and nbench.
The problem I've hit now is a severe memory leak. I have applied the
patch from Linus for the leak in free_pipe_info(), and still I'm
leaking memory at the rate of about
Randy,
I have applied the patch from Linus for the leak in
free_pipe_info()
...
Do you have today's memleak patch applied? (cut-n-paste below).
yes :-)
I'm trying the little leak tracking patch from Alexander Nyberg now.
Cheers, Tridge
-
To unsubscribe from this list: send the line
I'm trying the little leak tracking patch from Alexander Nyberg now.
Here are the results (only backtraces with more than 10k counts
included). The leak was at 1G of memory at the time I ran this, so its
safe to say 10k page allocations ain't enough to explain it :-)
I also attach a hacked
Andreas,
I'm starting to think the bug I saw is hardware error. I just got this
while trying to reproduce it tonight:
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : firmware status is 4000 4
Jan 24 02:43:32 dev4-003 kernel: scsi: Device
Andreas,
> Tridge, can you beat the code some more?
>
> Andrew has the five fixes in 2.6.11-rc1-mm2.
It seemed to pass dbench runs OK, but then I started simultaneously
running dbench and nbench on two different disks (I have a new test
machine with more disks available). I am getting
Andreas,
> Tridge, can you beat the code some more?
> Andrew has the five fixes in 2.6.11-rc1-mm2.
sorry for the delay. I've started to test 2.6.11-rc1-mm2 tonight. No
problems so far.
Cheers, Tridge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Andreas,
Tridge, can you beat the code some more?
Andrew has the five fixes in 2.6.11-rc1-mm2.
sorry for the delay. I've started to test 2.6.11-rc1-mm2 tonight. No
problems so far.
Cheers, Tridge
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Andreas,
Tridge, can you beat the code some more?
Andrew has the five fixes in 2.6.11-rc1-mm2.
It seemed to pass dbench runs OK, but then I started simultaneously
running dbench and nbench on two different disks (I have a new test
machine with more disks available). I am getting failures
Junichi Morita and I have worked out how to access the crusoe
"longrun" settings on the crusoe based VAIO. This allows you to enable
power saving mode and slow the cpu down. It should help battery life a
lot.
the following will enable power saving and set the cpu to the slowest
speed:
setpci
Junichi Morita and I have worked out how to access the crusoe
"longrun" settings on the crusoe based VAIO. This allows you to enable
power saving mode and slow the cpu down. It should help battery life a
lot.
the following will enable power saving and set the cpu to the slowest
speed:
setpci
16 matches
Mail list logo
