From: "Thomas Hühn" <thomas@net.t-labs.tu-berlin.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: Fwd: Gianfar driver crashes in Kernel v3.10
Date: Fri, 11 Oct 2013 10:59:34 +0200 [thread overview]
Message-ID: <760FFC38-597B-46CB-BA4C-620A1D663C8A@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: 90BE8C5D-E23B-41B5-BB52-8A0C0758931D@net.t-labs.tu-berlin.de
Hi Claudiu,
> Does this show up on a half duplex (100Mb/s) link?
In my testsetup I always used 1GBit Ethernet connections, so no 100MBit =
tested yet.
Should I do so ?
> Could you provide following for the gianfar interface, on your setup:
sure:=20
> # ethtool ethX
root@Bluse-home:~# ethtool eth0
Settings for eth0:
Supported ports: [ ]
Supported link modes: 1000baseT/Full=20
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes: 1000baseT/Full=20
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
> and
> # ethtool -d ethX | grep 500
>=20
root@Bluse-home:~# ethtool -d eth0 | grep 500
0x0500: 00 00 00 3f 00 00 72 05 40 60 50 60 00 a1 f0 37=20
> Is there any other indication before this Oops? Like a tx timeout =
WARN?
>=20
Nothing there about any timeout.
Greetings Thomas
> Thanks,
> Claudiu
>=20
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next parent reply other threads:[~2013-10-11 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90BE8C5D-E23B-41B5-BB52-8A0C0758931D@net.t-labs.tu-berlin.de>
2013-10-11 8:59 ` Thomas Hühn [this message]
2013-10-16 7:10 ` Fwd: Gianfar driver crashes in Kernel v3.10 Claudiu Manoil
2013-10-16 12:44 ` Thomas Hühn
2013-10-31 11:51 ` Thomas Hühn
2013-11-01 11:51 ` Claudiu Manoil
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=760FFC38-597B-46CB-BA4C-620A1D663C8A@net.t-labs.tu-berlin.de \
--to=thomas@net.t-labs.tu-berlin.de \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).