| 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
| ||
|
Date: Tue, 9 Dec 2014 19:33:34 +0000 From: Chris Conley <cconley@...tec.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: smsc911x: loopback test causing oops Hello all, I'm trying to find out what the USE_PHY_WORK_AROUND ifdef is for. I looked in the git logs and this workaround was introduced with the initial checkin of the driver files, and not explained. What was the hardware problem it was meant to handle? And is it valid for only certain chips? (i.e. the SMSC9221I, which is what we're using on this platform). We are seeing the loopback test fail w/ invalid packet size, and at some point during the loopback test after that, we get a kernel oops for invalid address. And the address is very invalid (e.g. 48fa0569, fa65a8c4). We were seeing this and another problem with irq_spinlocks after the probe returned for the 2nd instance of the phy, but that was fixed by backporting the current 3.18 driver to the linux-fslc_3.14.14 kernel. Initially it looked like the backport fixed all of the problems, but one remained after over the weekend testing. If the platform is direct-connect plugged into another platform, the oops happens in loopback again. The driver seems fine w/ the loopback disabled (no data xfer problems, etc), but I wanted to find out why it was there in the first place before forcing it off in a production environment. Thanks, //Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists