>-----Original Message----- >From: Joe Jin [mailto:joe....@oracle.com] >Sent: Wednesday, November 14, 2012 4:33 PM >To: Dave, Tushar N >Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux- >ker...@vger.kernel.org; Mary Mcgrath >Subject: Re: 82571EB: Detected Hardware Unit Hang > >On 11/14/12 11:45, Dave, Tushar N wrote: >>> -----Original Message----- >>> From: Joe Jin [mailto:joe....@oracle.com] >>> Sent: Tuesday, November 13, 2012 6:48 PM >>> To: Dave, Tushar N >>> Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux- >>> ker...@vger.kernel.org; Mary Mcgrath >>> Subject: Re: 82571EB: Detected Hardware Unit Hang >>> >>> On 11/09/12 04:35, Dave, Tushar N wrote: >>>> All devices in path from root complex to 82571, should have *same* >>>> max >>> payload size otherwise it can cause hang. >>>> Can you double check this? >>> >>> Hi Tushar, >>> >>> Checked with hardware vendor and they said no way to modify the max >>> payload size from BIOS, can I modify it from driver side? >> >> If you want to change value for 82571 device you can do it from eeprom >but for other upstream devices I am not sure. I will check with my team. > >Hi Tushar, > >Would you please help to fine the offset of max payload size in eeprom? >I'd like to have a try to modify it by ethtool.
It is defined using bit 8 of word 0x1A. Bit value 0 = 128B , bit value 1 = 256B -Tushar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
