From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754226Ab2AZXTP (ORCPT ); Thu, 26 Jan 2012 18:19:15 -0500 Received: from straum.hexapodia.org ([207.7.131.186]:58450 "EHLO straum.hexapodia.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751257Ab2AZXTO (ORCPT ); Thu, 26 Jan 2012 18:19:14 -0500 Date: Thu, 26 Jan 2012 15:19:13 -0800 From: Andy Isaacson To: "Allan, Bruce W" Cc: "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "e1000-devel@lists.sourceforge.net" Subject: Re: e1000e: repeated eth0: Error reading PHY register Message-ID: <20120126231913.GB24483@hexapodia.org> References: <20120125092101.GA10626@hexapodia.org> <804857E1F29AAC47BF68C404FC60A1842437C3@ORSMSX102.amr.corp.intel.com> <20120125191616.GJ21370@hexapodia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120125191616.GJ21370@hexapodia.org> X-Old-GPG-Fingerprint: 1914 0645 FD53 C18E EEEF C402 4A69 B1F3 68D2 A63F X-GPG-Fingerprint: A5FC 6141 F76D B6B1 C81F 0FB7 AFA0 A45F ED3D 116D X-GPG-Key-URL: http://web.hexapodia.org/~adi/gpg.txt X-Domestic-Surveillance: money launder bomb tax evasion User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 25, 2012 at 11:16:16AM -0800, Andy Isaacson wrote: > On Wed, Jan 25, 2012 at 05:00:29PM +0000, Allan, Bruce W wrote: > > >On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these: > > > > > >[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register > > > > Please file a bug with this information at > > http://sourceforge.net/tracker/?group_id=42302&atid=447449 > > Man sourceforge sure has jumped the shark; their signup form requires > "job title" and "company size". I wonder how many other CEOs of 20,000+ > employee companies bother to report ethernet driver bugs. > > And we don't have "bugs", we have "artifacts". Sigh. > > Anyways, here you go: > https://sourceforge.net/tracker/?func=detail&aid=3479714&group_id=42302&atid=447449 Hi Bruce, Please stop requiring us to use the sourceforge issue tracker. 1. It requires answers to irrelevant and annoying questions to create an account (which is required to report or comment on bugs). 2. It doesn't properly handle whitespace-aligned text, making the bug history very annoying to read. And the font it chooses doesn't distinguish between l, I, and 1. 3. the email it sends me shows my text with ^M (yes, two bytes, caret M, in a text/plain, charset=UTF-8, quoted-printable message body) at the lineendings. I don't even want to speculate how they managed to fuck that up. 4. the email it sends contains the entire bug: [1000 lines of Description text] [newest comment] [previous comment] ... [oldest comment] So you have to navigate to the middle of the email to find the new text. 5. It does not support comment-via-email. Not related to the issue tracker per se, but also annoying: 6. Your engineers want me to triage using some out-of-tree driver with some vendor-specific custom install process. I am happy to test git trees or apply patches, but I don't have time or inclination to deal with vendor build+install scripts. Thanks, -andy