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: <C4A61A5CA4AD2246942F4BA6F20ACB80435776D3@ALVA-EXMB04.alv.autoliv.int> Date: Thu, 14 Aug 2014 14:43:56 +0000 From: Mattis Lorentzon <Mattis.Lorentzon@...oliv.com> To: Fabio Estevam <festevam@...il.com> CC: Russell King - ARM Linux <linux@....linux.org.uk>, Fredrik Noring <fredrik.noring@...oliv.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: RE: Oops: 17 SMP ARM (v3.16-rc2) Fabio and Russell, > A working theory is that the switch (3Com Switch 4400) triggers the > degeneration of the network stack from which Linux does not seem to > recover, even if we later bypass the switch and directly connect the board to > the server machine. After a few more tests we have finally been able to trigger the exact same stalls on the Sabrelite board with a direct network connection (i.e. without the switch). Best regards, Mattis Lorentzon *************************************************************** Consider the environment before printing this message. To read Autoliv's Information and Confidentiality Notice, follow this link: http://www.autoliv.com/disclaimer.html ***************************************************************
Powered by blists - more mailing lists