From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>,
Aaron Brown <aaron.f.brown@intel.com>
Cc: e1000-devel <e1000-devel@lists.sourceforge.net>,
'Linux Netdev List' <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [bisected regression] e1000e: "Detected Hardware Unit Hang"
Date: Wed, 11 Feb 2015 03:34:00 -0800 [thread overview]
Message-ID: <1423654440.27854.83.camel@jtkirshe-mobl> (raw)
In-Reply-To: <2609782.Mryft1leMQ@storm>
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
On Wed, 2015-02-11 at 12:23 +0100, Thomas Jarosch wrote:
> Hi Jeff,
>
> On Thursday, 15. January 2015 06:59:13 Jeff Kirsher wrote:
> > > Sure, you basically reverted my patch.
> > >
> > > You are not the first to report a problem caused by this patch.
> > >
> > > This patch is known to have uncovered some driver bugs.
> > >
> > > We are not going to revert it. We are going to fix the real bugs.
> > >
> > > Thanks
> >
> > Agreed, we are looking into issue Thomas.
>
> any news from the Intel labs what might be going on here?
>
> We started seeing those hangs on "MSI B85M ECO" boards, too,
> though it's way more sporadic there.
I have not heard anything, so I have added Aaron Brown to see if he has
any additional information.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 441 bytes --]
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
[-- Attachment #3: Type: text/plain, Size: 257 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2015-02-11 11:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 15:32 [bisected regression] e1000e: "Detected Hardware Unit Hang" Thomas Jarosch
2015-01-14 17:20 ` Eric Dumazet
2015-01-15 10:11 ` Thomas Jarosch
2015-01-15 14:43 ` Eric Dumazet
2015-01-15 14:58 ` Thomas Jarosch
2015-01-15 15:25 ` Eric Dumazet
2015-01-15 15:48 ` Thomas Jarosch
2015-01-15 16:00 ` Eric Dumazet
2015-01-15 17:04 ` Thomas Jarosch
2015-01-15 17:20 ` Eric Dumazet
2015-01-15 17:37 ` Thomas Jarosch
2015-01-15 18:24 ` Re: Re: Re: " Eric Dumazet
2015-01-19 16:49 ` Thomas Jarosch
2015-01-15 14:59 ` Jeff Kirsher
2015-02-11 11:23 ` Thomas Jarosch
2015-02-11 11:34 ` Jeff Kirsher [this message]
2015-02-12 23:28 ` Brown, Aaron F
2015-02-13 16:14 ` Thomas Jarosch
2015-02-21 1:59 ` Brown, Aaron F
2015-03-23 13:58 ` Thomas Jarosch
2015-03-23 22:37 ` Brown, Aaron F
2015-05-27 16:00 ` Thomas Jarosch
2015-05-30 1:18 ` Brown, Aaron F
2015-07-29 8:51 ` Thomas Jarosch
2019-05-02 12:58 ` Juliana Rodrigueiro
2015-02-12 1:18 ` nick
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=1423654440.27854.83.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=aaron.f.brown@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=thomas.jarosch@intra2net.com \
/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