I'm running:
PU~Quad core Intel Core i5-2400 CPU (-MCP-) clocked at 1600.000 Mhz Kernel~3.5-1.towo-siduction-amd64 x86_64 Up~2 days Mem~1156.5/7872.3MB HDD~500.1GB(41.8% used) Procs~185 Client~Shell inxi~1.8.13
with KDE.
For the past 2 kernel releases, I've been experiencing "hangs" that last for a couple of seconds. Is there any diagnostic data I can collect to help see what is causing the "hangs". It doesn't happen often, and it does come back. There is no greying/diming
No replies? Oh well....
I've installed the Liquorix kernel:
CPU~Quad core Intel Core i5-2400 CPU (-MCP-) clocked at 1600.000 Mhz Kernel~3.4.0-9.dmz.1-liquorix-amd64 x86_64 Up~1:13 Mem~1256.2/7935.6MB HDD~500.1GB(41.1% used) Procs~193 Client~Shell inxi~1.8.13
And so far, no pauses. I haven't used Liquorix in a log time. I had hoped to stick with towo's kernel.
--Hinto
Noone else reported anything the like. So no idea, sorry.
And dmesg/kern.log are obvious candidates to sift through.
greetz
devil
Not a problem.
I'm still an avid user.
I do run a dual head and a win7 vm guest that I hit pretty hard.
The obvious bottlenecks to me are video and scheduling.
I'm pretty sure it's not video, so Liquorix changes the scheduling.
So far, no pauses.
-Hinto
I did get pauses on the Liquorix kernel. However, the new 3.6-0.towo-siduction-amd64 performs great. (no pauses)
-Hinto
I've been using the noop scheduler on my overclocked i7-950, which is installed on an SSD. I have not seen anything resembling a pause with any of the 3.6 kernels.
Right... That's been my observation on 3.6. Two days and no pauses.
-Hinto