linux-kernel - Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

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: <20060728233851.GA35643@muc.de>
Date:	Sat, 29 Jul 2006 01:38:51 +0200
From:	Andi Kleen <ak@....de>
To:	Andrew Morton <akpm@...l.org>
Cc:	Paul Fulghum <paulkf@...rogate.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

> > syslog from working 2.6.18-rc2 located at:
> > http://www.microgate.com/ftp/linux/test/syslog

What happened to the new lines? It looks like a bad alphabet soup

Do you perhaps have a boot log from before 2.6.17 (e.g. 2.6.16)? 
Preferably with newlines.

> 
> A bisection search would be useful, if you have the time.  I'd zero in on
> the x86_64 tree initially.  Perhaps x86_64-mm-i386-io-apic-access.patch.

It's remove-timer-fallback likely. I was working on that already.

Some boards go into the timer fallback path since 2.6.17/64bit for so 
far unknown reasons and that doesn't work anymore because I removed the 
fallback path.

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