LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: travis@sgi.com, tglx@linutronix.de, ak@suse.de, clameter@sgi.com,
steiner@sgi.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3
Date: Tue, 4 Mar 2008 16:45:38 -0800 [thread overview]
Message-ID: <20080304164538.4de48630.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080304083507.GE5689@elte.hu>
On Tue, 4 Mar 2008 09:35:07 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@linux-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.
next prev parent reply other threads:[~2008-03-05 0:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 20:33 [PATCH 0/2] x86: Optimize percpu accesses v3 Mike Travis
2008-02-19 20:33 ` [PATCH 1/2] x86_64: Fold pda into per cpu area v3 Mike Travis
2008-02-20 12:07 ` Ingo Molnar
2008-02-20 13:16 ` Eric Dumazet
2008-02-20 15:54 ` Mike Travis
2008-02-20 18:57 ` Mike Travis
2008-02-19 20:33 ` [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3 Mike Travis
2008-03-04 1:02 ` Andrew Morton
2008-03-04 1:30 ` Andrew Morton
2008-03-04 8:35 ` Ingo Molnar
2008-03-05 0:45 ` Andrew Morton [this message]
2008-03-04 13:21 ` Mike Travis
2008-02-20 9:15 ` [PATCH 0/2] x86: Optimize percpu accesses v3 Ingo Molnar
2008-02-20 15:28 ` Mike Travis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080304164538.4de48630.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--subject='Re: [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).