From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: "Mark Hatle" <fray@mvista.com>, "Stephan Linke" <Stephan.Linke@epygi.de>
Cc: "Bret Indrelee" <Bret.Indrelee@qlogic.com>,
"Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: "printk" does not print
Date: Mon, 3 Mar 2003 19:51:40 +0100 [thread overview]
Message-ID: <008101c2e1b5$edf3c020$0700a8c0@pc005> (raw)
In-Reply-To: 3E6384F6.9090701@mvista.com
After setting up the right log level, printk now works!
many thanks to all
Gianfranco
----- Original Message -----
From: "Mark Hatle" <fray@mvista.com>
To: "Stephan Linke" <Stephan.Linke@epygi.de>
Cc: "Bret Indrelee" <Bret.Indrelee@qlogic.com>; "Linuxppc-Embedded"
<linuxppc-embedded@lists.linuxppc.org>
Sent: Monday, March 03, 2003 5:38 PM
Subject: Re: "printk" does not print
>
> Stephan Linke wrote:
> > Hi,
> >
> > if your startup skript changes the console log level in
/proc/sys/kernel/printk maybe not all messages are displayed on console. But
> > you can still look into /var/log/messages.
>
> ...assuming you have klogd/syslogd installed and running...
>
> --Mark
>
> > Regards, Stephan
> >
> >
> >>-----Original Message-----
> >>From: owner-linuxppc-embedded@lists.linuxppc.org
> >>[mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Bret
> >>Indrelee
> >>Sent: Montag, 3. Marz 2003 15:46
> >>To: Ing.Gianfranco Morandi
> >>Cc: LinuxPPC
> >>Subject: Re: "printk" does not print
> >>
> >>
> >>
> >>On Mon, 3 Mar 2003, Ing.Gianfranco Morandi wrote:
> >>
> >>>Hi to all,
> >>>
> >>>I'm trying to trace the execution path of a custom ISDN driver, and I
have
> >>>used some printk() instructions to give some messages out.
> >>>
> >>>Now, everything is going well, but when I try to open the ttyI0 device
(or
> >>>ttyIx it is the same) the printk() that I have placed into the file
> >>>isdn_tty.c does not print any messages. I am sure that such procedure
has
> >>>been executed because I have placed a breakpoint on the
"isdn_tty_open()"
> >>>and the program stopped.
> >>>
> >>>Anybody has an idea what happens?
> >>
> >>You probably neglected to set a KERN_ level.
> >>
> >>See if they are in your dmesg or messages file, you might be sending
them
> >>to syslog but not the screen.
> >>
> >>-Bret
> >>
> >>--
> >>Bret Indrelee QLogic Corporation
> >>Bret.Indrelee@qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN
55346
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-03-03 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 14:15 "printk" does not print Ing.Gianfranco Morandi
2003-03-03 14:46 ` Bret Indrelee
2003-03-03 16:02 ` Stephan Linke
2003-03-03 16:38 ` Mark Hatle
2003-03-03 18:51 ` Ing.Gianfranco Morandi [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='008101c2e1b5$edf3c020$0700a8c0@pc005' \
--to=gianfranco.morandi@euro-studio.it \
--cc=Bret.Indrelee@qlogic.com \
--cc=Stephan.Linke@epygi.de \
--cc=fray@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).