From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: mpm@selenic.com, shemminger@linux-foundation.org,
linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: solution to printk() blocking interrupts?
Date: Mon, 22 Sep 2008 18:39:21 +0400 [thread overview]
Message-ID: <48D7AE19.1020309@ru.mvista.com> (raw)
In-Reply-To: <48D77D44.80304@ru.mvista.com>
Hello, I wrote:
Not sure if Stephen was the right person to CC, including Matt now...
>>>> What controls this? "carrier detect appears untrustworthy, waiting 4
>>>> seconds"
>>>> Get that fixed and this patch could be useful,
>>> Does the driver properly uses netif_carrier_on/off to signal the
>>> system when the link is up/down ?
>> Implementing the poll_controller() method in the network driver is
>> usually
>> Looks like the answer is "no"...
> Hm... it uses phylib, so probably it does that. That message and a 4 s
> pause appears if the carrier is seen in <10 ms after opening the device.
Oops, not 10 -- 100 ms (HZ / 10).
> Maybe this threshold needs to be changed?
Seems like too much indeed.
WBR, Sergei
next prev parent reply other threads:[~2008-09-22 14:39 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
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 [this message]
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=48D7AE19.1020309@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=mpm@selenic.com \
--cc=shemminger@linux-foundation.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 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.