Messages in this thread | | | Date | Tue, 4 Mar 2008 09:35:07 +0100 | From | Ingo Molnar <> | Subject | Re: [PATCH 2/2] x86_64: Cleanup non-smp usage of cpu maps v3 |
| |
* 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.)
Ingo
| |