* losing interrupts - printk is bad
@ 2001-03-19 17:12 Matthias Fuchs
2001-03-19 17:29 ` Gabriel Paubert
2001-03-20 12:58 ` Mike Neuhauser
0 siblings, 2 replies; 3+ messages in thread
From: Matthias Fuchs @ 2001-03-19 17:12 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I got a nice problem: I am working on an embedded PPC board (IBM405CR)
with a serial console (115200 baud). While I was testing some new driver
code, I made a lot of prink debugging output - as we all like to do :-)
My problem is, that I always lose some bytes on an other serial port. I
found out that printk waits until the complete format string is send
through the console. That takes about 5 ms for 40 bytes. During this
time printk blocks the interrupts !!! That means some incomming data on
the other serial port can be (and is) lost. This is a very strange
problem.
Well first would be glad to get a good workaround. Well, a 'klogd -c 1'
turn off all the debuggin and printk is much faster, but I need the
debugging output.
Second, could anybody explain t ome, what klogd is doing ? It would be
glad to get klogd read all the debugging output from the kernel and
output the data from user space (well buffered and not blocking the
whole system). It seems that klogd cannot do that, am I right ?
Matthias
--
-------------------------------------------------
\ Matthias Fuchs \
\ esd electronic system design Gmbh \
\ Vahrenwalder Straße 205 \
\ D-30165 Hannover \
\ email: matthias.fuchs@esd-electronics.com \
\ phone: +49-511-37298-0 \
\ fax: +49-511-37298-68 \
--------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: losing interrupts - printk is bad
2001-03-19 17:12 losing interrupts - printk is bad Matthias Fuchs
@ 2001-03-19 17:29 ` Gabriel Paubert
2001-03-20 12:58 ` Mike Neuhauser
1 sibling, 0 replies; 3+ messages in thread
From: Gabriel Paubert @ 2001-03-19 17:29 UTC (permalink / raw)
To: Matthias Fuchs; +Cc: linuxppc-embedded
On Mon, 19 Mar 2001, Matthias Fuchs wrote:
>
> Hi,
>
> I got a nice problem: I am working on an embedded PPC board (IBM405CR)
> with a serial console (115200 baud). While I was testing some new driver
> code, I made a lot of prink debugging output - as we all like to do :-)
> My problem is, that I always lose some bytes on an other serial port. I
> found out that printk waits until the complete format string is send
> through the console. That takes about 5 ms for 40 bytes. During this
> time printk blocks the interrupts !!! That means some incomming data on
> the other serial port can be (and is) lost. This is a very strange
> problem.
>
> Well first would be glad to get a good workaround. Well, a 'klogd -c 1'
> turn off all the debuggin and printk is much faster, but I need the
> debugging output.
>
> Second, could anybody explain t ome, what klogd is doing ? It would be
> glad to get klogd read all the debugging output from the kernel and
> output the data from user space (well buffered and not blocking the
> whole system). It seems that klogd cannot do that, am I right ?
Do you have a nettwork (Ethernet interface) ? I get all my debugging
output in /var/log/messages on another system with properly configured
syslogd. Of course, if has to go through userspace but once you've got
your driver stable enough , it should not be a problem.
Regards,
Gabriel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: losing interrupts - printk is bad
2001-03-19 17:12 losing interrupts - printk is bad Matthias Fuchs
2001-03-19 17:29 ` Gabriel Paubert
@ 2001-03-20 12:58 ` Mike Neuhauser
1 sibling, 0 replies; 3+ messages in thread
From: Mike Neuhauser @ 2001-03-20 12:58 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: Matthias Fuchs
In message <3AB63E12.6D38973E@esd-electronics.com>, Matthias Fuchs writes:
[stuff about losing interrupts during printk to serial console deleted]
> Second, could anybody explain t ome, what klogd is doing ? It would be
> glad to get klogd read all the debugging output from the kernel and
> output the data from user space (well buffered and not blocking the
> whole system). It seems that klogd cannot do that, am I right ?
klogd reads the kernel log messages (i.e. printk messages) either via syscall
or /proc interface and hands them over to syslogd.
Syslogd in turn writes them to a terminal, file, another host on
the network ...
So if you use klogd and syslogd together you can have kernel log message (also
on console if you like) and the other interrupts are not blocked by
printk.
Mike
--
Dr. Michael Neuhauser Phone: +43(1)8958499/17
g.a.m.s. edv-dienstleistungen gmbh Fax: +43(1)8958499/60
Stiegergasse 15-17/8 Email: mike@gams.at
A-1150 Vienna/Austria/Europe
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-03-20 12:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-19 17:12 losing interrupts - printk is bad Matthias Fuchs
2001-03-19 17:29 ` Gabriel Paubert
2001-03-20 12:58 ` Mike Neuhauser
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).