Hrm, I'll have to try that in my Copious Free Time™.lagalopex wrote:They perhaps found something: http://bugzilla.kernel.org/show_bug.cgi?id=12309#c360

Hrm, I'll have to try that in my Copious Free Time™.lagalopex wrote:They perhaps found something: http://bugzilla.kernel.org/show_bug.cgi?id=12309#c360



Could it be that genpatches is not helping?Sujao wrote:Just compiled 2.6.30-gentoo-r1. Tested only one thing that was really annoying me and it is still there. I start mmg (the muxer gui for the Matroska container that uses mkvmerge) and remux a 6.9GB file. I choose the movie and just let mkvmerge read it and write it again to hdd (from xfs to xfs) After about 15s the system locks up as usual.
So maybe other minor things are solved but the main problem is unchanged.




I'm right there with youLepaca Kliffoth wrote:I have no fucking idea, it takes too damn long to test this stuff


Code: Select all
# grep -i _dirty /etc/laptop-mode/laptop-mode.conf
LM_DIRTY_RATIO=20
NOLM_DIRTY_RATIO=10
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=2
I have only ran 64bit on workstations and servers. My laptops run OSX, Ubuntu and Gentoo 32bit. (BTW. One of my laptops is a Toshiba Protege 3010. and it is _thinner_ than a mac air! I have measured... to bad is just 300mhz and 900MB RAM.Yamakuzure wrote: Could it be, that most (or all) of us having these heavy disk access problems work with laptops?

Rats. Then this is another useless trace, it has nothing to do with the hardware layout.Yzzyx wrote:I have only ran 64bit on workstations and servers.Yamakuzure wrote: Could it be, that most (or all) of us having these heavy disk access problems work with laptops?

It has been your own post: XDdevsk wrote:Can you please elaborate on that? How is this supposed to work? Just numlock in a window with 'top' running? is it?Yamakuzure wrote: *but* awakening processes out of wait state via num lock in top now works!![]()
On my laptop it does not work when pressing numlock on an attached USB keyboard, I have to use the laptops own keys for that. (aka PS2)devsk wrote:someone claimed that they hit numlock to get their processes out of 'D' (disk sleep, directly relates to the IO Wait % number you see in the top output) state. Its bizarre!!
http://lkml.org/lkml/2009/4/5/197
Code: Select all
# for file in $(ls /proc/sys/vm/*dirty*) ; do echo -n "${file} : " ; cat ${file} ; done
/proc/sys/vm/dirty_background_bytes : 0
/proc/sys/vm/dirty_background_ratio : 2
/proc/sys/vm/dirty_bytes : 0
/proc/sys/vm/dirty_expire_centisecs : 3000
/proc/sys/vm/dirty_ratio : 10
/proc/sys/vm/dirty_writeback_centisecs : 500
I guess the thing is, that top does not react if the keyboard isn't PS2. Using my USB keyboard did nothing, but someone hinted about PS2-kb and that eventually worked.devsk wrote:LOL. yeah, I know but it never really worked for me. I thought I wasn't doing it right. And once I heard you used it, I was curious.

