From: renevant@internode.on.net
To: renevant@internode.on.net
Cc: netdev@vger.kernel.org
Subject: Re: ax88179 regression
Date: Sun, 09 Feb 2014 18:51:27 +1100 [thread overview]
Message-ID: <1613065.q9aFchjqPg@athas> (raw)
In-Reply-To: <1519315.vRJdGOYKiP@athas>
Absolute last post from me.
I migrated to a Intel Sandy Bridge based system to test. Definitely something
going on with the AMD based system, could be power supply/motherboard bios
related.
On the Intel system the ax88179 still locked up one time. I rebuilt with for-
usb-linus tree merged and I reverted:
2a100047481a5c7430c72883b586eb6f2df34812
xhci: remove conversion from generic to pci device in xhci_mem.c
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a100047481a5c7430c72883b586eb6f2df34812
I can't say for sure if this commit is a problem but this kernel build has
been up now for several hours without an issue and i've put it through paces
that usually lock up the nic.
Regards,
Will Trives
On Saturday 08 February 2014 14:56:17 renevant@internode.on.net wrote:
> Everything is still working at commit
> 63a67a72d63dd077c2313cf19eb29d8e4bfa6963
>
> At this point i'm beginning to think all the issues i've been having are
> motherboard bios and compiler flag issues.
>
> Regards,
>
> Will Trives
>
> On Saturday 08 February 2014 12:56:10 renevant@internode.on.net wrote:
> > Hello,
> >
> > I have finally nailed down my other issues and i'm at a point where I can
> > bisect from a point that is 100% stable and working.
> >
> >
> > I am currently running a kernel checked out at commit
> > d194c031994d3fc1038fa09e9e92d9be24a21921
> >
> > A point in 3.12rc4
> >
> > At this point the ax88179 works without issue even with scatter gather
> > turned on. So somewhere from this point something goes wrong and there is
> > some condition that exists that can lock up the nic.
> >
> >
> > I will keep bisecting at report my findings.
> >
> >
> > Regards,
> >
> > Will Trives
prev parent reply other threads:[~2014-02-09 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 1:56 ax88179 regression renevant
2014-02-08 3:56 ` renevant
2014-02-09 7:51 ` renevant [this message]
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=1613065.q9aFchjqPg@athas \
--to=renevant@internode.on.net \
--cc=netdev@vger.kernel.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).