Hi and thanks for your reply :)
On Friday 12 October 2007, you wrote:
> i have no quick ideas - the behavior you are seeing is quite unexpected.
> Could you try the current sched-devel code:
>
>
> http://redhat.com/~mingo/cfs-scheduler/devel/sched-devel-combo-v2.6.23.patc
>h
Maybe I messed
Hi and thanks for your reply :)
On Friday 12 October 2007, you wrote:
i have no quick ideas - the behavior you are seeing is quite unexpected.
Could you try the current sched-devel code:
http://redhat.com/~mingo/cfs-scheduler/devel/sched-devel-combo-v2.6.23.patc
h
Maybe I messed something
Hi =)
On Thursday 11 October 2007, Helmut Toplizer wrote:
> Hi!
>
> I had similar behavior in the kernel releases since I can think of.
It doesn't happen before 2.6.23.
> (You may find some reports about at
> http://marc.info/?a=11350857446=1=2)
>
> Maybe your problem is similar.
>
> Here's
Hi =)
On Thursday 11 October 2007, Helmut Toplizer wrote:
Hi!
I had similar behavior in the kernel releases since I can think of.
It doesn't happen before 2.6.23.
(You may find some reports about at
http://marc.info/?a=11350857446r=1w=2)
Maybe your problem is similar.
Here's what
Hi :)
I have two harddisks with encfs on top of reiserfs between which I could copy
data at ~22MB/s before the upgrade from 2.6.22 to 2.6.23.
After the upgrade the transfer rate stuck at ~14MB/s and changing nice values
did not help anything.
And now the funny part:
I noticed the transfer
Hi :)
I have two harddisks with encfs on top of reiserfs between which I could copy
data at ~22MB/s before the upgrade from 2.6.22 to 2.6.23.
After the upgrade the transfer rate stuck at ~14MB/s and changing nice values
did not help anything.
And now the funny part:
I noticed the transfer
Hello,
after running a few instances of bittorent-curses on 2.6.22 - 2.6.22.3 it
takes about 15min to 2hrs for my System to hang. 2.6.21.7 is definately fine,
2.6.21 probably (ran for 4hrs without hanging).
If I'm lucky the Oops below makes it to my syslog (unfortunately SysRq-{p,s,i}
doesn't
Hello,
after running a few instances of bittorent-curses on 2.6.22 - 2.6.22.3 it
takes about 15min to 2hrs for my System to hang. 2.6.21.7 is definately fine,
2.6.21 probably (ran for 4hrs without hanging).
If I'm lucky the Oops below makes it to my syslog (unfortunately SysRq-{p,s,i}
doesn't
8 matches
Mail list logo
