From: "Stephan Linke" <Stephan.Linke@epygi•de>
To: "Bret Indrelee" <Bret.Indrelee@qlogic•com>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists•linuxppc.org>
Subject: RE: "printk" does not print
Date: Mon, 3 Mar 2003 17:02:40 +0100 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJCEEBCOAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0303030845140.27359-100000@localhost.localdomain>
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.
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/
next prev parent reply other threads:[~2003-03-03 16:02 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 [this message]
2003-03-03 16:38 ` Mark Hatle
2003-03-03 18:51 ` Ing.Gianfranco Morandi
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=FCEAKDJJAPHPLJFINDAJCEEBCOAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi$(echo .)de \
--cc=Bret.Indrelee@qlogic$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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