From: Berend De Schouwer <berend.de.schouwer@gmail•com>
To: Siva Reddy Kallam <siva.kallam@broadcom•com>
Cc: Linux Netdev List <netdev@vger•kernel.org>
Subject: Re: tg3 pxe weirdness
Date: Wed, 27 Sep 2017 12:05:17 +0200 [thread overview]
Message-ID: <1506506717.18177.136.camel@gmail.com> (raw)
In-Reply-To: <CAMet4B6mZ8SyCT7W2j4OBEUDiy3ZupYKWXBFti0nXoxm51_6kg@mail.gmail.com>
On Mon, 2017-09-25 at 15:11 +0530, Siva Reddy Kallam wrote:
> On Fri, Sep 22, 2017 at 9:04 PM, Berend De Schouwer
> <berend.de.schouwer@gmail•com> wrote:
> > On Fri, 2017-09-22 at 11:51 +0530, Siva Reddy Kallam wrote:
> > >
> > >
> > > Can you please share below details?
> > > 1) Model and Manufacturer of the system
> > > 2) Linux distro/kernel used?
> >
> > 4.13.3 gets a little further, but after some more data is
> > transferred
> > the tg3 driver still crashes. This is unfortunately before I've
> > got a
> > writeable filesystem.
> >
> > The last line is:
> > tg3 0000:01:00.0: tg3_stop_block timed out, ofs=4c00 enable_bit=2
> >
> > I've got some ideas to get the full dmesg.
> >
> > As with the other kernels it works OK on 1Gbps, but not slower
> > switches.
>
> I am suspecting with link aware mode, the clock speed could be slow
> and boot code does not
> complete within the expected time with lower link speeds. So,
> Providing a patch to override clock.
> Can you please try with attached debug patch and provide us the
> feedback with 100M link?
> If it solves this issue, we will work on proper changes.
This does work on 4.13.3 and PXE for me.
I've tested on 1 Gbps, 100 Mbps and 10 Mbps. I've done some
preliminary testing (eg. large file copies.)
next prev parent reply other threads:[~2017-09-27 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:41 tg3 pxe weirdness Siva Reddy Kallam
2017-09-27 10:05 ` Berend De Schouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-27 10:31 Siva Reddy Kallam
2017-09-22 6:21 Siva Reddy Kallam
2017-09-22 7:28 ` Berend De Schouwer
2017-09-22 12:56 ` Berend De Schouwer
2017-09-22 13:20 ` Berend De Schouwer
2017-09-22 15:34 ` Berend De Schouwer
2017-09-21 14:23 Berend De Schouwer
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=1506506717.18177.136.camel@gmail.com \
--to=berend.de.schouwer@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=siva.kallam@broadcom$(echo .)com \
/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