public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruben Puettmann <ruben@puettmann.net>
To: Andi Kleen <ak@suse.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	coywolf@lovecn.org, coywolf@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.11.7 kernel panic on boot on AMD64
Date: Fri, 29 Apr 2005 16:44:14 +0200	[thread overview]
Message-ID: <20050429144414.GL18972@puettmann.net> (raw)
In-Reply-To: <20050429142947.GD21080@wotan.suse.de>

On Fri, Apr 29, 2005 at 04:29:47PM +0200, Andi Kleen wrote:
> 
> late_time_init is not in my tree. Someone else must have submitted it.
> iirc it was a workaround for some race in the NMI watchdog setup, but
> that has since then be properly fixed.
> 

It is in 2.6.11.7 :

root@dl380g3:[/mnt/kerneltest/linux-2.6.11.7] > grep -r late_time_init *
arch/mips/pmc-sierra/yosemite/setup.c:extern void
(*late_time_init)(void);
arch/mips/pmc-sierra/yosemite/setup.c:static void __init
py_late_time_init(void)
arch/mips/pmc-sierra/yosemite/setup.c:  late_time_init =
py_late_time_init;
arch/mips/vr41xx/nec-cmbvr4133/setup.c:extern void
(*late_time_init)(void);
arch/mips/vr41xx/nec-cmbvr4133/setup.c: late_time_init =
vr4133_serial_init;
arch/i386/kernel/time.c:extern void (*late_time_init)(void);
arch/i386/kernel/time.c:                late_time_init = hpet_time_init;
arch/ppc/platforms/sbc82xx.c:extern void (*late_time_init)(void);
arch/ppc/platforms/sbc82xx.c: * late_time_init() is call after paging
init.
arch/ppc/platforms/sbc82xx.c:   late_time_init          =
sbc82xx_time_init;
init/main.c:void (*late_time_init)(void);
init/main.c:    if (late_time_init)
init/main.c:            late_time_init();


                                Ruben


-- 
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net

  reply	other threads:[~2005-04-29 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 14:03 2.6.11.7 kernel panic on boot on AMD64 Ruben Puettmann
2005-04-27 22:27 ` Randy.Dunlap
2005-04-28  9:05   ` Ruben Puettmann
2005-04-28 15:43     ` Randy.Dunlap
2005-04-28 15:53       ` Ruben Puettmann
2005-04-28 16:38       ` Coywolf Qi Hunt
2005-04-28 16:47         ` Randy.Dunlap
2005-04-29 14:29           ` Andi Kleen
2005-04-29 14:44             ` Ruben Puettmann [this message]
2005-04-29  8:25         ` Ruben Puettmann
2005-04-27 23:40 ` Randy.Dunlap
2005-04-29 10:06 ` Alexander Nyberg
2005-04-29 10:10   ` Andrew Morton
2005-04-29 11:10     ` Ruben Puettmann
2005-04-29 11:45     ` Alexander Nyberg
2005-04-29 14:34       ` Andi Kleen
2005-04-29 14:32   ` Andi Kleen
2005-04-29 14:41     ` Ruben Puettmann
2005-04-29 14:45       ` Andi Kleen
2005-04-29 20:11         ` Alexander Nyberg
2005-05-02 16:42           ` Andi Kleen
2005-04-29 14:44     ` Alexander Nyberg
2005-04-29 14:46       ` Andi Kleen

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=20050429144414.GL18972@puettmann.net \
    --to=ruben@puettmann.net \
    --cc=ak@suse.de \
    --cc=coywolf@gmail.com \
    --cc=coywolf@lovecn.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox