From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Gary Zambrano <zambrano@broadcom.com>,
stable@kernel.org, davemorgan353@btinternet.com
Subject: Re: [Bugme-new] [Bug 16503] New: Upgrade to 2.6.34.2 breaks ethernet network
Date: Tue, 3 Aug 2010 13:27:40 -0700 [thread overview]
Message-ID: <20100803132740.946cf78a.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16503-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 3 Aug 2010 20:14:34 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16503
>
> Summary: Upgrade to 2.6.34.2 breaks ethernet network
> Product: Networking
> Version: 2.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: davemorgan353@btinternet.com
> Regression: No
>
>
> Using Arch Linux with fully up-to-date system.
>
> Upgrading kernel from 2.6.34.1 to 2.6.34.2 breaks my ethernet connection. I
> get dhcp timeouts but no errors in the logs regarding the kernel or the card.
>
> Dell Inspiron 1720.
>
> 03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev
> 02)
>
> Downgrading the kernel fixes the issue.
>
There are no changes to b44.c in patch-2.6.34.2. Perhaps you could
generate the dmesg logs for 2.6.34.1 and 2.6.34.2 and run `diff -u'
against them, see if anything interesting pops out?
next parent reply other threads:[~2010-08-03 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16503-10286@https.bugzilla.kernel.org/>
2010-08-03 20:27 ` Andrew Morton [this message]
2010-08-04 18:59 ` [Bugme-new] [Bug 16503] New: Upgrade to 2.6.34.2 breaks ethernet network Dave Morgan
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=20100803132740.946cf78a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=davemorgan353@btinternet.com \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=zambrano@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.