netdev - Re: 3.0.0rc6: ethtool not working without a cable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1309966010.2712.4.camel@bwh-desktop>
Date:	Wed, 06 Jul 2011 16:26:50 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
Cc:	netdev@...r.kernel.org,
	e1000-devel <e1000-devel@...ts.sourceforge.net>
Subject: Re: 3.0.0rc6: ethtool not working without a cable

On Wed, 2011-07-06 at 16:53 +0200, Arkadiusz Miskiewicz wrote:
> On Wednesday 06 of July 2011, Ben Hutchings wrote:
> > On Wed, 2011-07-06 at 13:38 +0200, Arkadiusz Miskiewicz wrote:
> > > 3.0.0rc6, thinkpad t400 notebook.
> > > 
> > > If there is no cable then ethtool reports no device. It wasn't that
> > > before AFAIK.
> > > 
> > > ethtool version 2.6.36
> > > 
> > > 
> > > cable disconnected:
> > > 
> > > [root@...0 ~]# ethtool eth0
> > > Settings for eth0:
> > > Cannot get device settings: No such device
> > > Cannot get wake-on-lan settings: No such device
> > > Cannot get message level: No such device
> > > Cannot get link status: No such device
> > > No data available
> > > zsh: exit 75    ethtool eth0
> > > [root@...0 ~]# ethtool -i eth0
> > > Cannot get driver information: No such device
> > > zsh: exit 71    ethtool -i eth0
> > 
> > [...]
> > 
> > Then there really isn't a device under that name.  Maybe the driver is
> > getting a bogus MAC address, so that the device is renamed by udev.
> 
> No, no, device exists:
> 
> [arekm@...0 ~]$ ip l
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state 
> DOWN qlen 1000
>     link/ether 00:21:86:a2:19:06 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc sfq state UP qlen 
> 1000
>     link/ether 00:16:eb:05:5d:08 brd ff:ff:ff:ff:ff:ff
> [arekm@...0 ~]$ ethtool eth0
> Settings for eth0:
> Cannot get device settings: No such device
> Cannot get wake-on-lan settings: No such device
> Cannot get message level: No such device
> Cannot get link status: No such device
> No data available
> zsh: exit 75    ethtool eth0
> [arekm@...0 ~]$

Then the only other explanation I can think of is that the driver has
'detached' the device due to some kind of error.  The ethtool core does
have a check for that.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html