Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

forcedeth: cat /sys/class/net/eth0/carrier = Invalid argument

216 views
Skip to first unread message

Justin P. mattock

unread,
Mar 22, 2010, 1:40:01 PM3/22/10
to
I've pushed my kernel from the latest HEAD to 2.6.31
and am still seeing:
cat /sys/class/net/eth0/carrier
cat: carrier: Invalid argument

with my other machine using sky2
the same results is:
cat /sys/class/net/eth0/carrier

0

is there anything on this? before I start
a bisect.(looking through bugzilla, I couldn't
see anything related).

Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

David Miller

unread,
Mar 23, 2010, 12:00:02 AM3/23/10
to
From: "Justin P. mattock" <justin...@gmail.com>
Date: Mon, 22 Mar 2010 10:36:18 -0700

> I've pushed my kernel from the latest HEAD to 2.6.31
> and am still seeing:
> cat /sys/class/net/eth0/carrier
> cat: carrier: Invalid argument
>
> with my other machine using sky2
> the same results is:
> cat /sys/class/net/eth0/carrier
> 0
>
> is there anything on this? before I start
> a bisect.(looking through bugzilla, I couldn't
> see anything related).

A device is not able to indicate carrier accurately when
the device is not currently running.

So you will get an -EINVAL until the device is brought up.

The reason is that most drivers don't even probe the link
or negotiate link speed and flow control until the device
is brought up. Many don't even power up the PHY when the
device is down, in order to save power.

So the behavior you observe is completely expected.

Justin P. Mattock

unread,
Mar 23, 2010, 12:10:02 AM3/23/10
to
On 03/22/2010 08:51 PM, David Miller wrote:
> From: "Justin P. mattock"<justin...@gmail.com>
> Date: Mon, 22 Mar 2010 10:36:18 -0700
>
>> I've pushed my kernel from the latest HEAD to 2.6.31
>> and am still seeing:
>> cat /sys/class/net/eth0/carrier
>> cat: carrier: Invalid argument
>>
>> with my other machine using sky2
>> the same results is:
>> cat /sys/class/net/eth0/carrier
>> 0
>>
>> is there anything on this? before I start
>> a bisect.(looking through bugzilla, I couldn't
>> see anything related).
>
> A device is not able to indicate carrier accurately when
> the device is not currently running.
>
> So you will get an -EINVAL until the device is brought up.

ah.. the machine was up and running but nothing was running
(no dhclient, streaming music, etc..)
now
just ran the machine with ethernet,(up and running) and carrier reported 1

>
> The reason is that most drivers don't even probe the link
> or negotiate link speed and flow control until the device
> is brought up. Many don't even power up the PHY when the
> device is down, in order to save power.
>
> So the behavior you observe is completely expected.
>


cool, this had me confused.

Thanks for the info on this..
(no bisect for this).


Justin P. Mattock

0 new messages