From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Yu Subject: Re: 82571EB: Detected Hardware Unit Hang Date: Wed, 14 Nov 2012 11:37:13 +0800 Message-ID: <50A311E9.9030702@gmail.com> References: <509B5038.8090304@oracle.com> <061C8A8601E8EE4CA8D8FD6990CEA89133487884@ORSMSX102.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Joe Jin , "e1000-devel@lists.sf.net" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Mary Mcgrath To: "Dave, Tushar N" Return-path: In-Reply-To: <061C8A8601E8EE4CA8D8FD6990CEA89133487884@ORSMSX102.amr.corp.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org =E4=BA=8E 2012=E5=B9=B411=E6=9C=8809=E6=97=A5 04:35, Dave, Tushar N =E5= =86=99=E9=81=93: >> -----Original Message----- >> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.= org] >> On Behalf Of Joe Jin >> Sent: Wednesday, November 07, 2012 10:25 PM >> To: e1000-devel@lists.sf.net >> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Mary Mcgra= th >> Subject: 82571EB: Detected Hardware Unit Hang >> >> Hi list, >> >> IHAC reported "82571EB Detected Hardware Unit Hang" on HP ProLiant D= L360 >> G6, and have to reboot the server to recover: >> >> e1000e 0000:06:00.1: eth3: Detected Hardware Unit Hang: >> TDH <1a> >> TDT <1a> >> next_to_use <1a> >> next_to_clean <18> >> buffer_info[next_to_clean]: >> time_stamp <10047a74e> >> next_to_watch <18> >> jiffies <10047a88c> >> next_to_watch.status <1> >> MAC Status <80383> >> PHY Status <792d> >> PHY 1000BASE-T Status <3800> >> PHY Extended Status <3000> >> PCI Status <10> >> >> With newer kernel 2.0.0.1 the issue still reproducible. >> >> Device info: >> 06:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ether= net >> Controller (Copper) (rev 06) >> 06:00.1 0200: 8086:10bc (rev 06) >> >> I compared lspci output before and after the issue, different as bel= ow: >> 06:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ether= net >> Controller (Copper) (rev 06) >> Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port >> Gigabit Server Adapter >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ >> Stepping- SERR- FastB2B- DisINTx- >> - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- >> SERR- > + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- >> +SERR- > Are you sure this is not similar issue as before that you reported. > i.e. > On Mon, 2012-07-09 at 16:51 +0800, Joe Jin wrote: >> I'm seeing a Unit Hang even with the latest e1000e driver 2.0.0 when >> doing scp test. this issue is easy do reproduced on SUN FIRE X2270 M= 2, >> just copy a big file (>500M) from another server will hit it at once= =2E > > All devices in path from root complex to 82571, should have *same* ma= x payload size otherwise it can cause hang. > Can you double check this? > We also found such hang problem on 82599EB (ixgbe driver) in RHEL6.3 kernel, we ever tried to upgrade to latest version (3.8.21 or 3.10.17), but it still happens. Is it probably also due to wrong "max payload size" set in BIOS? Thanks Yu > -Tushar > -- > To unsubscribe from this list: send the line "unsubscribe linux-kerne= l" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >