From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
PJ Waskiew
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
craig@haquarter.de
Subject: Re: [Bugme-new] [Bug 16383] New: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
Date: Wed, 21 Jul 2010 13:48:43 -0700 [thread overview]
Message-ID: <20100721134843.f8b5b217.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16383-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 14 Jul 2010 00:44:51 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16383
>
> Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.35
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Network
> AssignedTo: drivers_network@kernel-bugs.osdl.org
> ReportedBy: craig@haquarter.de
> Regression: Yes
>
>
> Created an attachment (id=27094)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=27094)
> .config
>
> Networking stops working with 2.6.35 (tested rc-3 and rc5).
This is a post-2.6.34 regression, guys. There's some more info in bugzilla.
> # egrep "(e1000|eth)" dmesg-2.6.34.1
> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> e1000e 0000:00:19.0: setting latency timer to 64
> 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
>
> # egrep "(e1000|eth)" dmesg-2.6.35-rc5
> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> e1000e 0000:00:19.0: setting latency timer to 64
> e1000e 0000:00:19.0: (unregistered net_device): Failed to initialize MSI
> interrupts. Falling back to legacy interrupts.
> e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
> e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
>
> I hadn't set CONFIG_PCI_MSI but enabling it on 2.6.35-rc5 made no difference.
>
next parent reply other threads:[~2010-07-21 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16383-10286@https.bugzilla.kernel.org/>
2010-07-21 20:48 ` Andrew Morton [this message]
2010-07-21 21:43 ` [Bugme-new] [Bug 16383] New: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5 Tantilov, Emil S
2010-07-22 0:06 ` Craig
2010-08-02 21:23 ` Craig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100721134843.f8b5b217.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=craig@haquarter.de \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).