linux-kernel - [BUG, Regression, bisected] Marvell 88E8055 NIC (sky2) fails to detect carrier after resume from S3

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <op.wgg9f1g716tawo@esprimo>
Date:	Mon, 25 Jun 2012 23:17:51 +0200
From:	"Michal Zatloukal" <myxal.mxl@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	snanda@...omium.org
Subject: [BUG, Regression, bisected] Marvell 88E8055 NIC (sky2) fails to
 detect carrier after resume from S3

Hello.
Note: Please CC me into replies, I'm not subscribed. Thank you.

I'm the reporter of Ubuntu bug 1007841
<https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007841> and would
like to bring attention to it here, since it's in upstream kernel as well.
You can find all details collected by apport there. The gist of the
problem is, since around 3.2 (I haven't kept up-to-date and mostly used
2.6.35 on the machine), whenever I wake up the laptop from S3 by opening
the lid, the NIC loses carrier detection and it's reported as always down.

I have done bisection (my first, so don't automatically assume it's done
correctly ;-)  and have found the offending commit to be:

commit 7afe1845dd1e7c90828c942daed7e57ffa7c38d6
Author: Sameer Nanda <snanda@...omium.org>
Date: Mon Jul 25 17:13:29 2011 -0700

init: skip calibration delay if previously done

Hence, CCing author.
Let me know if I should supply any more info.

Best Regards,
Michal Zatloukal

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/
--
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/