linux-kernel - Re: [patch 0/3] fastboot patches series 1

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]

Date:	Sat, 19 Jul 2008 12:22:43 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Simon Arlott <simon@...e.lp0.eu>, linux-kernel@...r.kernel.org,
	dwalker@...sta.com
Subject: Re: [patch 0/3] fastboot patches series 1

Arjan van de Ven <arjan@...radead.org> writes:
>
> One possible theory is that we now run on both cpus and if they're out
> of sync timewise, things like delays suddenly are shorter than expected
> if time jumps around....

On systems with non synchronized TSC the clocksource watchdog tends
to disable the TSC time source only quite late in boot (on my systems
typically even after kernel boot). So yes this could be a problem.

However he has a AMD QC system where the TSCs are synchronized on the
hardware level and there's also no message from the watchdog disabling
TSC, so this isn't the problem causing this issue. Must be something else.

-Andi

--
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/