From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Jon Smirl <jonsmirl@gmail•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:59:00 +0400 [thread overview]
Message-ID: <48D7B2B4.6020900@ru.mvista.com> (raw)
In-Reply-To: <9e4733910809220745i59a10185rffe1fdcda1916eb0@mail.gmail.com>
Jon Smirl 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.
> The link is coming up, but it appears that netconsole has already
> decided to wait 4s.
> mpc52xx MII bus: probed
> net eth0: Using PHY at MDIO address 0
> 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: device eth0 not up yet, forcing it
> net eth0: attached phy 0 to driver Generic PHY
> netconsole: carrier detect appears untrustworthy, waiting 4 seconds
Netpoll code decides to wait 4 secs after seeing that carrier is OK before
100 ms passed...
> PHY: f0003000:00 - Link is Up - 100/Full
...but it's only reported to be OK later. So indeed, the carrier reported
by the driver appears untrustworthy. ;-)
WBR, Sergei
next prev parent reply other threads:[~2008-09-22 14:59 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
2008-09-22 14:45 ` Jon Smirl
2008-09-22 14:59 ` Sergei Shtylyov [this message]
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=48D7B2B4.6020900@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=jonsmirl@gmail$(echo .)com \
--cc=mpm@selenic$(echo .)com \
--cc=shemminger@linux-foundation$(echo .)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