linux-kernel - Re: [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3

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:	Mon, 3 Mar 2008 17:30:11 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	travis@....com, mingo@...e.hu, tglx@...utronix.de, ak@...e.de,
	clameter@....com, steiner@....com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3

On Mon, 3 Mar 2008 17:02:35 -0800
Andrew Morton <akpm@...ux-foundation.org> wrote:

> I was unable to bisect it more finely than this:
> 
> init-move-setup-of-nr_cpu_ids-to-as-early-as-possible-v3.patch
> generic-percpu-infrastructure-to-rebase-the-per-cpu-area-to-zero-v3.patch OK
> x86_64-fold-pda-into-per-cpu-area-v3.patch
> x86_64-fold-pda-into-per-cpu-area-v3-fix.patch				
> x86_64-cleanup-non-smp-usage-of-cpu-maps-v3.patch			BAD
> 
> because when x86_64-cleanup-non-smp-usage-of-cpu-maps-v3.patch was removed
> the machine hung quite early, when playing around with TSC calibration I
> think.

This just happened again with the patches dropped, so it is a separate bug -
just another regression.

I now recall that it has been happening on every fifth-odd boot for a few
weeks now.  The machine prints

Time: tsc clocksource has been installed

then five instances of "system 00:01: iomem range 0x...", then it hangs. 
ie: it never prints "system 00:01: iomem range 0xfe600000-0xfe6fffff has
been reserved" from http://userweb.kernel.org/~akpm/dmesg-akpm2.txt.

It may have some correlation with whether the machine was booted via
poweron versus `reboot -f', dunno.

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