| 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: <061C8A8601E8EE4CA8D8FD6990CEA891274F01BE@ORSMSX102.amr.corp.intel.com> Date: Thu, 12 Jul 2012 03:07:40 +0000 From: "Dave, Tushar N" <tushar.n.dave@...el.com> To: Joe Jin <joe.jin@...cle.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 >-----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. -Tushar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists