public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Dean Roe <roe@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 printk_clock()
Date: Thu, 02 Feb 2006 21:22:40 +0000	[thread overview]
Message-ID: <20060202212240.GA17176@sgi.com> (raw)
In-Reply-To: <20060202204422.GA27082@sgi.com>

On Thu, Feb 02, 2006 at 02:44:22PM -0600, Jack Steiner wrote:
> We are seeing kernel hangs in early boot if CONFIG_PRINTK_TIME is
> enabled. The hang is caused by a reference in sched_clock() to 
> the percpu data area before it is initialized. 
> 
> I know there was discussion about this late last summer & I thought
> Tony posted a patch. Does anyone recall the status.
> 
> AFAICT, we see failures on SN systems but other IA64 systems work ok.
> 
> ---
> Jack

Jack, I think this is the thread you are looking for:
    http://marc.theaimsgroup.com/?l=linux-ia64&m\x112422250517703&w=2

Dean

-- 
Dean Roe
Silicon Graphics, Inc.
roe@sgi.com

  reply	other threads:[~2006-02-02 21:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 20:44 ia64 printk_clock() Jack Steiner
2006-02-02 21:22 ` Dean Roe [this message]
2006-02-02 21:46 ` Luck, Tony
2006-02-02 21:50 ` Jack Steiner
2006-02-02 22:29 ` Luck, Tony
2006-02-02 22:52 ` Chen, Kenneth W
2006-02-03 17:43 ` Chen, Kenneth W
2006-02-03 18:04 ` Luck, Tony
2006-02-03 18:30 ` Chen, Kenneth W
2006-02-03 18:43 ` Luck, Tony
2006-02-03 18:55 ` Chen, Kenneth W
2006-02-04  0:16 ` Keith Owens
2006-02-04  0:28 ` Chen, Kenneth W
2006-02-04  0:32 ` Luck, Tony
2006-02-04  0:36 ` Keith Owens
2006-02-06 18:14 ` Luck, Tony
2006-02-06 18:34 ` Chen, Kenneth W
2006-02-06 20:40 ` Magenheimer, Dan (HP Labs Fort Collins)
2006-02-06 21:37 ` Chen, Kenneth W
2006-02-07 11:11 ` Jes Sorensen
2006-02-08  0:05 ` Luck, Tony
2006-02-08  6:29 ` Jes Sorensen
2006-02-08 18:18 ` Luck, Tony

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=20060202212240.GA17176@sgi.com \
    --to=roe@sgi.com \
    --cc=linux-ia64@vger.kernel.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