linux-kernel - Re: 2.6.20-rc6-mm3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070131132245.GA26066@elte.hu>
Date:	Wed, 31 Jan 2007 14:22:45 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Karsten Wiese <fzu@...gehoertderstaat.de>
Cc:	Andrew Morton <akpm@...l.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: 2.6.20-rc6-mm3


* Karsten Wiese <fzu@...gehoertderstaat.de> wrote:

> Similar weirdness here on rc6-mm2 and rc6-rt*: resume from disk waits 
> unduly long.

i'm wondering whether the jiffies update fix from Thomas fixes this bug 
for you.

If not then do you have a serial console enabled?

> Some waiting times from rc6-rt6 from memory:
> 
> Config		| HZ			| NO_HZ + HRESTIMERS
> cmos clock unchanged	| 2s			| 6s
> cmos clock += 10min	| 			| 2 minutes
> cmos clock += 2 month	| 20s			| > 4minutes, test interrupted

i've seen something like this on -rt (and incorrectly attributed it to 
-rt) when running on a system which has a serial port and which has a 
kernel console on that serial port. What happens is that after resume 
(and straight after console suspend) every serial character printed 
takes /alot/ of time - and resume does print a number of kernel messages 
to the console. I didnt get any further in debugging this though, but 
disabling the serial console made the problem go away.

a possibly related thing: the serial code is sensitive to jiffies 
updates and timers, i saw that during early revisions of the dynticks 
code - but the specifics escape me.

the slowdown could also be something like the kernel somehow wrapping 
around jiffies and thus doing /alot/ of jiffy ticks? Or it could be a 
miscalculation in the amount of jiffies that need updating, resulting in 
a similar number of loops in the jiffy update code.

(i'll try to figure out this regression - but wanted to describe to you 
the known things so far, maybe you'll figure it out faster than me.)

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/