From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, dev-null@telus.net
Subject: Re: [Bugme-new] [Bug 9269] New: bonding module cannot enslave ethernet devices provided by sunhme
Date: Wed, 31 Oct 2007 15:37:32 -0700 [thread overview]
Message-ID: <20071031153732.cb950b28.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9269-10286@http.bugzilla.kernel.org/>
On Wed, 31 Oct 2007 14:35:56 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9269
>
> Summary: bonding module cannot enslave ethernet devices provided
> by sunhme
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.18-3
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: dev-null@telus.net
>
>
> Most recent kernel where this bug did not occur: N/A
> Distribution: Debian 4.0r1/stable (Etch)
> Hardware Environment: Sun Netra T1 105 (sparc64)
> Software Environment:
> Problem Description:
> bonding module cannot enslave ethernet devices provided by sunhme - link
> status is never reported via netif_carrier_on/netif_carrier_off which makes
> sunhme not usable as a slave to the bonding module
>
> Steps to reproduce:
> modprobe sunhme
> modprobe bonding
> ifconfig bond0 up
> ifconfig eth0 up
> # wait for link to be up
> ifenslave bond0 eth0
> # bond0 never comes up and keeps waiting for link
>
parent reply other threads:[~2007-10-31 22:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-9269-10286@http.bugzilla.kernel.org/>]
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=20071031153732.cb950b28.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dev-null@telus.net \
--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 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.