All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "Tony Luck" <tony.luck@intel.com>
Cc: "David Miller" <davem@davemloft.net>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Strange hang on ia64 with CONFIG_PRINTK_TIME=y
Date: Wed, 13 Feb 2008 19:47:26 -0800	[thread overview]
Message-ID: <adaprv0rygh.fsf@cisco.com> (raw)
In-Reply-To: <12c511ca0802131933g6aaaec9cidbfbfcac6f394c63@mail.gmail.com> (Tony Luck's message of "Wed, 13 Feb 2008 19:33:42 -0800")

 > I'll take a closer look at what is needed tomorrow.

Hi Tony,

Just curious -- can you reproduce the same problem with
CONFIG_PRINTK_TIME as I'm seeing?  If not I'm happy to test anything
you want to try.

The strange thing is that Ingo's patch to make cpu_clock() a NOP until
after sched_init() didn't fix things for me...

 - R.


  reply	other threads:[~2008-02-14  3:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  6:24 Strange hang on ia64 with CONFIG_PRINTK_TIME=y Roland Dreier
2008-02-13  7:01 ` David Miller
2008-02-13 12:57   ` Ingo Molnar
2008-02-13 13:02     ` Ingo Molnar
2008-02-14  0:26       ` Roland Dreier
2008-02-13 13:03     ` David Miller
2008-02-13 13:06       ` Ingo Molnar
2008-02-14  0:59       ` Tony Luck
2008-02-14  1:04         ` David Miller
2008-02-14  3:33           ` Tony Luck
2008-02-14  3:47             ` Roland Dreier [this message]
2008-02-14 18:24               ` Luck, Tony
2008-02-14 21:27               ` Tony Luck
2008-02-14 22:04                 ` Roland Dreier
2008-02-14 22:23                   ` Luck, Tony
2008-02-15  2:17                     ` Tony Luck
2008-02-19 22:40                       ` Tony Luck
2008-02-20  8:12                         ` Ingo Molnar
2008-02-20  8:15                           ` David Miller
2008-02-20 23:35                         ` Roland Dreier
2008-02-20 23:36                         ` Roland Dreier

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=adaprv0rygh.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tony.luck@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.