Can you try KVM to see if it's also happening there?
Cheers,
John
> -Original Message-
> From: Zoltán Halassy [mailto:cf0...@gmail.com]
> Sent: Wednesday, March 25, 2015 1:55 AM
> To: Ronciak, John
> Cc: e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel]
mail.com]
> >> Sent: Friday, March 20, 2015 2:29 AM
> >> To: e1000-devel@lists.sourceforge.net
> >> Subject: [E1000-devel] Detected Hardware Unit Hang
> >>
> >> I manage a Fujitsu Primergy TX100 S2 server, which has this integrated NIC:
> >>
>
; -Original Message-
>> From: Zoltán Halassy [mailto:cf0...@gmail.com]
>> Sent: Friday, March 20, 2015 2:29 AM
>> To: e1000-devel@lists.sourceforge.net
>> Subject: [E1000-devel] Detected Hardware Unit Hang
>>
>> I manage a Fujitsu Primergy TX100 S
hanks.
Cheers,
John
> -Original Message-
> From: Zoltán Halassy [mailto:cf0...@gmail.com]
> Sent: Friday, March 20, 2015 2:29 AM
> To: e1000-devel@lists.sourceforge.net
> Subject: [E1000-devel] Detected Hardware Unit Hang
>
> I manage a Fujitsu Primergy TX100 S2 server, whi
I manage a Fujitsu Primergy TX100 S2 server, which has this integrated NIC:
00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit
Network Connection [8086:10ef] (rev 05)
Subsystem: Fujitsu Technology Solutions Device [1734:11a6]
Kernel driver in use: e1000e
Using a
Unplugging the cable with netconsole active on the interface results in
neverending:
May 10 17:48:28 nemi kernel: [ 624.809508] e1000e :00:19.0 eth0: Detected
Hardware Unit Hang:
May 10 17:48:28 nemi kernel: [ 624.809508] TDH <0>
May 10 17:48:28 nemi kernel: [ 624.809508
Hello Tushar,
On 1/27/2012 2:57 AM, Dave, Tushar N wrote:
>> -Original Message-
>> From: Pratyush Anand [mailto:pratyush.an...@st.com]
>> Sent: Tuesday, January 10, 2012 7:34 PM
>> To: Dave, Tushar N
>> Cc: Greg KH; Pratyush Anand; e1000-devel@lists.sourceforge.net;
>> net...@vger.kernel.o
>-Original Message-
>From: Pratyush Anand [mailto:pratyush.an...@st.com]
>Sent: Tuesday, January 10, 2012 7:34 PM
>To: Dave, Tushar N
>Cc: Greg KH; Pratyush Anand; e1000-devel@lists.sourceforge.net;
>net...@vger.kernel.org; Shiraz HASHIM; Deepak SIKRI; Bhavna YADAV; linux-
>p...@vger.kernel
>As I said earlier, issue is reproducible if I try to keep my
>rootfilesystem over NFS. So, after the booting, kernel tries to mount
>rootfs over NFS and it crashes. So, I see issue even before I can reach
>to # prompt. How can I use "ethtool -s ethx msglvl 0x3c00" to enable any
>debug message
On 1/11/2012 6:40 AM, Dave, Tushar N wrote:
> Thanks for driver info.
> Because you are running in-kernel driver, we can enable the debug message
> level via ethtool. That will print HW ring info when issue occurs.
>
> Here is the ethtool command to enable debug messages.
> # ethtool -s ethx msglv
Thanks for driver info.
Because you are running in-kernel driver, we can enable the debug message level
via ethtool. That will print HW ring info when issue occurs.
Here is the ethtool command to enable debug messages.
# ethtool -s ethx msglvl 0x3c00
This will enable tx_done, rx_status, pktdata a
On 1/7/2012 12:25 AM, Dave, Tushar N wrote:
> Pratyush,
>
> Sorry I got your name reversed.
> Are you using in-kernel driver or one from Sourceforge.
I am using in-kernel driver from kernel 2.6.37.
> Please send me output of ethtool -i ethx.
root@192.168.1.10:~# ethtool -i eth0
driver: e1000e
ve
Pratyush,
Sorry I got your name reversed.
Are you using in-kernel driver or one from Sourceforge.
Please send me output of ethtool -i ethx.
-Tushar
-Original Message-
From: Pratyush Anand [mailto:pratyush.an...@st.com]
Sent: Thursday, January 05, 2012 8:25 PM
To: Dave, Tushar N
Cc: Greg
Thanks Tushar,
On 1/6/2012 5:24 AM, Dave, Tushar N wrote:
> Anand,
>
> Sorry to hear that you have this issue with card. And yeah, thanks for doing
> the debugging and providing the bus trace.
> I think we should run the debug driver that prints the HW ring details when
> hang occurs. I can prov
Anand,
Sorry to hear that you have this issue with card. And yeah, thanks for doing
the debugging and providing the bus trace.
I think we should run the debug driver that prints the HW ring details when
hang occurs. I can provide you a debug driver. You can then install debug
driver and also l
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 tha
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 w
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 t
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.
Regards
Pr
Hi All,
I am trying to use PCIe based Intel PRO/1000 PT Server Adapter card on
an ARM Corterx A-9 based platform.
I am using linux 2.6.37.
I am trying to mount my rootfile system on NFS using interface of this card.
I see follwing issue while nfs mount
---
20 matches
Mail list logo
