From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: solution to printk() blocking interrupts?
Date: Mon, 22 Sep 2008 02:21:36 +0400 [thread overview]
Message-ID: <48D6C8F0.4060808@ru.mvista.com> (raw)
In-Reply-To: <9e4733910809211443l5638887aw856377d39fcca85c@mail.gmail.com>
Hello.
Jon Smirl wrote:
> On Sun, Sep 21, 2008 at 4:53 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
>
>> Does anyone have a solution to the problem of printk() to a serial
>> console blocking interrupts for too long? I'm losing interrupts I need
>> because my hardware is getting overrun.
>>
>
> netconsole is not an option on mpc5200....
>
> Kernel command line: console=ttyPSC0,115200 rw debug root=/dev/nfs
> ip=dhcp nfsroot=192.168.1.4:/home/OSELAS.BSP-Phytec-phyCORE-MPC5200B-tiny-6/root,v3,tcp
> netconsole=6666@192.168.1.11/eth0,514@192.168.1.4/00:19:d1:e4:0f:8d
> netconsole: local port 6666
> netconsole: local IP 192.168.1.11
> netconsole: interface eth0
> netconsole: remote port 514
> netconsole: remote IP 192.168.1.4
> netconsole: remote ethernet address 00:19:d1:e4:0f:8d
> netconsole: eth0 doesn't support polling, aborting.
> netconsole: cleaning up
>
Implementing the poll_controller() method in the network driver is
usually staightforward.
WBR, Sergei
next prev parent reply other threads:[~2008-09-21 22:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 20:53 solution to printk() blocking interrupts? Jon Smirl
2008-09-21 21:43 ` Jon Smirl
2008-09-21 22:21 ` Sergei Shtylyov [this message]
2008-09-21 23:34 ` Jon Smirl
2008-09-22 5:17 ` Benjamin Herrenschmidt
2008-09-22 11:04 ` Sergei Shtylyov
2008-09-22 11:11 ` Sergei Shtylyov
2008-09-22 14:39 ` Sergei Shtylyov
2008-09-22 14:45 ` Jon Smirl
2008-09-22 14:59 ` Sergei Shtylyov
2008-09-22 21:27 ` Benjamin Herrenschmidt
2008-09-22 10:03 ` Sergei Shtylyov
2008-09-22 11:01 ` Sergei Shtylyov
2008-09-22 11:21 ` Sergei Shtylyov
2008-09-22 13:45 ` Jon Smirl
2008-09-23 5:46 ` Benjamin Herrenschmidt
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=48D6C8F0.4060808@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jonsmirl@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.