From: "Dave, Tushar N" <tushar.n.dave@intel.com>
To: Joe Jin <joe.jin@oracle.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel@lists.sf.net" <e1000-devel@lists.sf.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 82571EB: Detected Hardware Unit Hang
Date: Fri, 13 Jul 2012 04:10:51 +0000 [thread overview]
Message-ID: <061C8A8601E8EE4CA8D8FD6990CEA891274F11FF@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <4FFF61BD.1060604@oracle.com>
>-----Original Message-----
>From: Joe Jin [mailto:joe.jin@oracle.com]
>Sent: Thursday, July 12, 2012 4:46 PM
>To: Dave, Tushar N
>Cc: e1000-devel@lists.sf.net; netdev@vger.kernel.org; linux-
>kernel@vger.kernel.org
>Subject: Re: 82571EB: Detected Hardware Unit Hang
>
Thanks for sending full dmesg log. I am still investigating. I think this issue can occur if two PCIe link partner *i.e pcie bridge and pcie device do not have same max payload size.
I need 2 more info.
1) PBA number of the card.
2) full lspci -vvv output of entire system 'after you have changed max payload size to 128'.
Thanks.
-Tushar
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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:[~2012-07-13 4:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 8:51 82571EB: Detected Hardware Unit Hang Joe Jin
2012-07-09 9:21 ` Eric Dumazet
2012-07-09 12:19 ` Joe Jin
2012-07-10 7:40 ` Joe Jin
2012-07-10 18:14 ` Wyborny, Carolyn
2012-07-10 19:02 ` Dave, Tushar N
2012-07-10 19:17 ` Dave, Tushar N
2012-07-11 0:34 ` Joe Jin
2012-07-11 1:18 ` Dave, Tushar N
2012-07-11 1:44 ` Joe Jin
2012-07-11 3:22 ` Dave, Tushar N
2012-07-11 3:29 ` Joe Jin
2012-07-11 4:05 ` Dave, Tushar N
2012-07-11 5:03 ` Joe Jin
2012-07-11 7:11 ` Dave, Tushar N
2012-07-11 7:17 ` Joe Jin
2012-07-11 7:37 ` Dave, Tushar N
2012-07-11 7:38 ` Joe Jin
2012-07-11 7:50 ` Dave, Tushar N
2012-07-11 7:53 ` Joe Jin
2012-07-11 18:51 ` Dave, Tushar N
2012-07-12 2:23 ` Joe Jin
2012-07-12 2:52 ` Dave, Tushar N
2012-07-12 2:57 ` Joe Jin
2012-07-12 3:07 ` Dave, Tushar N
2012-07-12 3:12 ` Joe Jin
2012-07-12 5:57 ` Dave, Tushar N
2012-07-12 6:16 ` Joe Jin
2012-07-12 6:41 ` Dave, Tushar N
2012-07-12 7:10 ` Joe Jin
2012-07-12 18:19 ` Dave, Tushar N
2012-07-12 23:46 ` Joe Jin
2012-07-13 4:10 ` Dave, Tushar N [this message]
2012-07-13 4:33 ` Joe Jin
2012-07-15 3:42 ` Dave, Tushar N
2012-07-15 3:52 ` Joe Jin
2012-07-15 13:35 ` Henrique de Moraes Holschuh
2012-07-16 15:47 ` Ben Hutchings
2012-07-16 16:08 ` Henrique de Moraes Holschuh
2012-07-17 4:48 ` Jon Mason
2012-07-17 4:45 ` Jon Mason
2012-11-08 6:24 Joe Jin
2012-11-08 20:35 ` Dave, Tushar N
2012-11-09 1:22 ` Joe Jin
2012-11-14 2:47 ` Joe Jin
2012-11-14 3:45 ` Dave, Tushar N
2012-11-15 0:32 ` Joe Jin
2012-11-15 20:26 ` Dave, Tushar N
2012-11-19 5:38 ` Joe Jin
2012-11-20 8:59 ` Dave, Tushar N
2012-11-20 13:24 ` Joe Jin
2012-11-26 16:23 ` [E1000-devel] " Fujinaka, Todd
2012-11-27 0:59 ` Joe Jin
2012-11-27 2:06 ` Mary Mcgrath
2012-11-27 17:32 ` [E1000-devel] " Fujinaka, Todd
2012-11-27 18:10 ` Ben Hutchings
2012-11-28 8:31 ` Joe Jin
2012-11-28 15:53 ` Fujinaka, Todd
2012-11-29 3:10 ` Ethan Zhao
2012-11-29 15:52 ` Fujinaka, Todd
2012-12-19 3:04 ` Joe Jin
2012-12-19 5:52 ` Yijing Wang
2012-12-19 6:13 ` Joe Jin
2012-11-20 13:24 ` Joe Jin
2012-11-14 3:37 ` Li Yu
2012-11-14 3:43 ` Dave, Tushar N
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=061C8A8601E8EE4CA8D8FD6990CEA891274F11FF@ORSMSX102.amr.corp.intel.com \
--to=tushar.n.dave@intel.com \
--cc=e1000-devel@lists.sf.net \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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).