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] [day] [month] [year] [list]

Date:	Tue, 4 Mar 2008 16:45:38 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	travis@....com, 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 Tue, 4 Mar 2008 09:35:07 +0100
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > 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.
> 
> the tsc thing seems to be an accidental proximity to me.
> 
> such a hard hang has a basic system setup feel to it: the PCI changes in 
> 2.6.25 or perhaps some ACPI changes. But it could also be timer related 
> (although in that case it typically doesnt hang in the middle of a 
> system setup sequence)
> 
> i'd say pci=nommconf, but your dmesg has this:
> 
>   PCI: Not using MMCONFIG.
> 
> but, what does seem to be new in your dmesg (i happen to have a historic 
> dmesg-akpm2.txt of yours saved away) is:
> 
>   hpet0: at MMIO 0xfed00000, IRQs 2, 8, 11
>   hpet0: 3 64-bit timers, 14318180 Hz
> 
> was hpet active on this box before? Try hpet=disable perhaps - does that 
> change anything? (But ... this is still a 10% chance suggestion, there's 
> way too many other possibilities for such bugs to occur.)
> 

I dunno - the machine does this rarely and today seems to be the day on
which it likes to produce its long-occurring doesnt-reboot-at-all problem,
which is different, and might be a BIOS thing.

Now current mainline is giving me this:

zsh: exec format error: /opt/crosstool/gcc-4.0.2-glibc-2.3.6/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc

and /usr/bin/sum matches that binary on a different machine.

I think I'll go home and knit a sweater or something.
--
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/