linux-kernel - Re: e1000e: repeated eth0: Error reading PHY register

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120126231913.GB24483@hexapodia.org>
Date:	Thu, 26 Jan 2012 15:19:13 -0800
From:	Andy Isaacson <adi@...apodia.org>
To:	"Allan, Bruce W" <bruce.w.allan@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: Re: e1000e: repeated eth0: Error reading PHY register

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
--
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/