From: "Leonidas ." <leonidas137@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Garbled printk output on 2.7.27 - No multi line printks
Date: Tue, 27 Oct 2009 00:24:43 -0700 [thread overview]
Message-ID: <f22d86810910270024o4cd69265v61536afedc0e510b@mail.gmail.com> (raw)
Hi,
I am trying a simple char driver and for debug purposes I have added
lot of printks
in my module. The module is rather heavily being used by my test app which does
hundreds of open/read/write calls. The driver just copies and prints
incoming/outgoing
buffers.
I see a lot of garbled output in /var/log/messages
E.g.
Oct 27 00:18:47 ubuntu-vm kernel: [ 4903.382917] returned buf "Hello"
Oct 27 00:18:47 ubuntu-vm kernel: [ 4903.382925] returned buf "Hello"
Oct 27 00:18:47 ubuntu-vm kernel: [ 4903.383033] returned buf "Hello"
reeeeeeeeeexeeeeeeexteeeexeeeeeeeeeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeeeeeeeeeexeeeeeeeeeexteexeeeeeeeeexeeeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeeeexeeeeeeeeeeeexeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeeeeeeeeeeexeeeeeeeeeexteeeeeeeeeeeeeeexeeeext
for 8902 Hello
Oct 27 00:18:47 ubuntu-vm kernel: [ d
Oct 27 00:18:47 ubuntu-vm kernel: dddddddd
Oct 27 00:18:47 ubuntu-vm kernel:
ddddddddn3eexeeeeeeeeeeeeeeeexeeeeeeeeeeeeexeeeeexteeeeeeexeeeeeeeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeexeeeeeeeeeeexeeeeeeeeeeeeexeeeeeeeeeeeeeexeeeeeeeeeexeeeeexeeeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeeeeeeeeeeeeexeeeeeeeeeexeeeeeeeeeeeeeeeeexeeeeeeeext
for 8903 Hello
My loglevel is KERN_INFO, my understanding was a multiline printk
might cause garbled output
on SMPs but a single line printk is always protected using a semaphore.
-Leo.
reply other threads:[~2009-10-27 7:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f22d86810910270024o4cd69265v61536afedc0e510b@mail.gmail.com \
--to=leonidas137@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®