lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <4FFE40A9.4060807@oracle.com> Date: Thu, 12 Jul 2012 11:12:41 +0800 From: Joe Jin <joe.jin@...cle.com> To: "Dave, Tushar N" <tushar.n.dave@...el.com> CC: "e1000-devel@...ts.sf.net" <e1000-devel@...ts.sf.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: 82571EB: Detected Hardware Unit Hang On 07/12/12 11:07, Dave, Tushar N wrote: >> -----Original Message----- >> From: Joe Jin [mailto:joe.jin@...cle.com] >> Sent: Wednesday, July 11, 2012 7:58 PM >> To: Dave, Tushar N >> Cc: e1000-devel@...ts.sf.net; netdev@...r.kernel.org; linux- >> kernel@...r.kernel.org >> Subject: Re: 82571EB: Detected Hardware Unit Hang >> >> On 07/12/12 10:52, Dave, Tushar N wrote: >>> What is the exact error messages in BIOS log? >> >> Error message from BIOS event log: >> 07/12/12 05:54:00 >> PCI Express Non-Fatal Error >> >> Thanks, >> Joe > > Thanks. Well, I will check with team tomorrow if this (max payload size) can be treated as solution to this issue. > We can know more about what exact non-fatal error occurred if we capture bus trace. > We should check the eeprom on this device to make sure they are up-to-date. > Send me the full eeprom dump in a file and I will confirm with team that it is up-to-date. > Thanks for your work. > Hi Tushar, Please find eeprom from attachment. Thanks a lot of your help, Joe Download attachment "eeprom.raw" of type "image/x-panasonic-raw" (8192 bytes) View attachment "eeprom.readable" of type "text/plain" (29215 bytes)
Powered by blists - more mailing lists