From: Greg KH <greg@kroah•com>
To: Pratyush Anand <pratyush.anand@st•com>
Cc: Pratyush Anand <pratyush.anand@gmail•com>,
"e1000-devel@lists•sourceforge.net"
<e1000-devel@lists•sourceforge.net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
Shiraz HASHIM <shiraz.hashim@st•com>,
Deepak SIKRI <deepak.sikri@st•com>,
Bhavna YADAV <bhavna.yadav@st•com>,
"linux-pci@vger•kernel.org" <linux-pci@vger•kernel.org>,
linux.nics@intel•com
Subject: Re: Detected Hardware Unit Hang on Intel Wired Ethernet
Date: Thu, 5 Jan 2012 08:46:06 -0800 [thread overview]
Message-ID: <20120105164606.GC26153@kroah.com> (raw)
In-Reply-To: <4F05276F.6040708@st.com>
On Thu, Jan 05, 2012 at 10:00:39AM +0530, Pratyush Anand wrote:
> On 1/5/2012 12:52 AM, Greg KH wrote:
> >On Wed, Jan 04, 2012 at 04:31:36PM +0530, Pratyush Anand wrote:
> >>Adding PCI mailing list too, as problem is coming only when MSI is enabled.
> >>
> >>If I connect an PCIe analyzer, I see that at the time of issue
> >>MRd(64) for 32 words has been issued with a wrong 64 bit address
> >>from ethernet card to my RC.
> >>In the normal course it always issues MRd(32) only.
> >
> >Bug in your pcie firmware controller?
> >
> >.
> >
>
> when you say "Bug in your pcie firmware controller?", is it RC's
> software or EP's software?
I don't know, but I would place the bet on your motherboard controller,
not the device.
greg k-h
next prev parent reply other threads:[~2012-01-05 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:48 Detected Hardware Unit Hang on Intel Wired Ethernet Pratyush Anand
2012-01-04 11:01 ` Pratyush Anand
2012-01-04 19:22 ` Greg KH
2012-01-05 4:30 ` Pratyush Anand
2012-01-05 16:46 ` Greg KH [this message]
2012-01-05 23:54 ` Dave, Tushar N
2012-01-06 4:25 ` Pratyush Anand
2012-01-06 18:55 ` Dave, Tushar N
2012-01-10 4:20 ` Pratyush Anand
2012-01-11 1:10 ` Dave, Tushar N
2012-01-11 3:33 ` Pratyush Anand
2012-01-11 3:48 ` Dave, Tushar N
2012-01-26 21:27 ` Dave, Tushar N
2012-01-27 8:03 ` Pratyush Anand
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=20120105164606.GC26153@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=bhavna.yadav@st$(echo .)com \
--cc=deepak.sikri@st$(echo .)com \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux.nics@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pratyush.anand@gmail$(echo .)com \
--cc=pratyush.anand@st$(echo .)com \
--cc=shiraz.hashim@st$(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