mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Randy Dunlap" <rdunlap@xenotime.net>
Cc: gregkh <greg@kroah.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Tiny error in printk output for clocksource : a3:<6>Time: acpi_pm clocksource has been installed.
Date: Wed, 27 Sep 2006 23:38:05 +0200	[thread overview]
Message-ID: <9a8748490609271438n13d822e0x6af0bd06c32c8ae0@mail.gmail.com> (raw)
In-Reply-To: <20060926205415.98b8d95d.rdunlap@xenotime.net>

On 27/09/06, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Wed, 27 Sep 2006 02:36:58 +0200 Jesper Juhl wrote:
>
> > On Wednesday 27 September 2006 02:33, Randy Dunlap wrote:
> > > On Wed, 27 Sep 2006 02:22:18 +0200 Jesper Juhl wrote:
> > >
> > > > I get this in dmesg with 2.6.18-git6 :
> > > >       a3:<6>Time: acpi_pm clocksource has been installed.
> > > >
> > > > Looks like some printk() somewhere is not adding \n correctly after
> > > > outputting a message priority or a message priority too much is
> > > > used... I've not investigated where this happens, but just wanted to
> > > > report it.
> > >
> > > Hi,
> > > How about posting (pasting) some of the message log before that?
> > >
> > Sure, below is the entire dmesg output from this boot of the box
> > (including the line above) :
>
> I suppose that you have CONFIG_PCI_MULTITHREAD_PROBE=y ?

Correct.

> What happens if you change to to =n ?
>
Doing that resolves the issue.

So yes, you are correct in your other posts in this thread that the
problem is caused by multiple printk()'s from different locations
being mixed up.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      parent reply	other threads:[~2006-09-27 21:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  0:22 Jesper Juhl
2006-09-27  0:33 ` Randy Dunlap
2006-09-27  0:36   ` Jesper Juhl
2006-09-27  0:54     ` Randy Dunlap
2006-09-27  1:15       ` Jesper Juhl
2006-09-27  3:54     ` Randy Dunlap
2006-09-27  4:32       ` Greg KH
2006-09-27  4:52         ` Randy Dunlap
2006-09-27  4:56           ` Randy Dunlap
2006-09-27  5:07             ` Greg KH
2006-09-27  5:10             ` Joe Perches
2006-09-27  5:17               ` Randy Dunlap
2006-09-27  5:19                 ` Joe Perches
2006-09-27 15:24                   ` Randy Dunlap
2006-09-28 10:56                 ` Denis Vlasenko
2006-09-28 16:08                   ` Joe Perches
2006-09-28 16:19                     ` Denis Vlasenko
2006-09-28 17:03                       ` Joe Perches
2006-09-28 23:26                       ` Joe Perches
2006-09-27 21:38       ` Jesper Juhl [this message]

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=9a8748490609271438n13d822e0x6af0bd06c32c8ae0@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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

all inboxes | Powered by JetHome®