public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: CONFIG_PRINTK_TIME broken on git HEAD ?
Date: Wed, 7 May 2008 15:41:55 -0700	[thread overview]
Message-ID: <20080507154155.2b472bb1.akpm@linux-foundation.org> (raw)
In-Reply-To: <48222C7C.2050807@googlemail.com>

On Thu, 08 May 2008 00:26:04 +0200
Gabriel C <nix.or.die@googlemail.com> wrote:

> Hi all,
> 
> I've updated today to 2.6.26-rc1-00166-gc0a1811 , running an 64bit kernel at the moment.

Which kernel were you runing previously?

> dmesg shows here :
> 
> ...
> 
> 
> [    0.000000] Allocating PCI resources starting at d0000000 (gap: cf600000:2f800000)
> [    0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
> [    0.000000] PERCPU: Allocating 42756 bytes of per cpu data
> [    0.000000] NR_CPUS: 8, nr_cpu_ids: 4
> [4294014.506571] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1010753
> [4294014.506571] Kernel command line: root=/dev/sdb1 ro debug vga=0x317
> [4294014.506571] Initializing CPU#0
> [4294014.506571] Preemptible RCU implementation.
> [4294014.506571] PID hash table entries: 4096 (order: 12, 32768 bytes) 
> 
> ...                                                                                     
> 
> 
> Is this a known issue ?
> 

Not to me.

  reply	other threads:[~2008-05-07 22:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 22:26 CONFIG_PRINTK_TIME broken on git HEAD ? Gabriel C
2008-05-07 22:41 ` Andrew Morton [this message]
2008-05-07 22:57   ` Gabriel C
2008-05-08 11:00     ` Gabriel C
2008-05-08 11:13       ` Peter Zijlstra
2008-05-08 11:21         ` Gabriel C
2008-05-09  9:39           ` Peter Zijlstra
2008-05-09  9:42             ` Ingo Molnar
2008-05-09 12:21               ` Gabriel C
2008-05-09 12:13             ` Gabriel C

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=20080507154155.2b472bb1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@googlemail.com \
    --cc=rjw@sisk.pl \
    /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