From: "Michael Chan" <mchan@broadcom.com>
To: "Rik van Riel" <riel@redhat.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27-rc5-mm1
Date: Mon, 15 Sep 2008 16:00:58 -0700 [thread overview]
Message-ID: <1221519658.11021.13.camel@HP1> (raw)
In-Reply-To: <20080915180130.10995b90@cuia.bos.redhat.com>
On Mon, 2008-09-15 at 15:01 -0700, Rik van Riel wrote:
> On Thu, 4 Sep 2008 22:40:04 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.27-rc5/2.6.27-rc5-mm1/
>
> The bnx2 driver has stopped working on 2.6.27-rc5-mm1.
>
> Plain 2.6.27-rc5 works. Reversing the bnx2 changes in -mm1 does not
> fix the issue, so something less obvious is going on.
>
> # ifup eth0
> Determining IP information for eth0...SIOCSIFFLAGS: Invalid argument
> SIOCSIFFLAGS: Invalid argument
> SIOCSIFFLAGS: Invalid argument
> # ifconfig eth0 up
> SIOCSIFFLAGS: Invalid argument
>
> Bringing up the interface fails with -EINVAL. Specifically, the
> SIOCSIFFLAGS ioctl is returning -EINVAL:
>
> ioctl(4, SIOCSIFFLAGS, 0x7fffc841cc40) = -1 EINVAL (Invalid argument)
>
> I am running an x86-64 kernel on a Dell pe1950 with these network chips
> on the mainboard:
>
> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
> 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
>
Does dmesg show anything when you run ifup?
next prev parent reply other threads:[~2008-09-15 23:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 5:40 2.6.27-rc5-mm1 Andrew Morton
2008-09-05 7:20 ` 2.6.27-rc5-mm1 Takashi Iwai
2008-09-05 7:50 ` 2.6.27-rc5-mm1 Alexander Beregalov
2008-09-05 8:25 ` 2.6.27-rc5-mm1 Andrew Morton
2008-09-05 12:39 ` 2.6.27-rc5-mm1: rmmod ide-cd_mod: tried to init an initialized object, something is seriously wrong Mariusz Kozlowski
2008-09-05 13:28 ` Rafael J. Wysocki
2008-09-05 13:44 ` Mariusz Kozlowski
2008-09-05 16:25 ` Mariusz Kozlowski
2008-09-06 12:35 ` FUJITA Tomonori
2008-09-08 8:43 ` Jens Axboe
2008-09-08 9:27 ` Jens Axboe
2008-09-09 9:07 ` Mariusz Kozlowski
2008-09-09 10:29 ` Jens Axboe
2008-09-09 12:14 ` Mariusz Kozlowski
2008-09-09 13:21 ` Jens Axboe
2008-09-05 17:26 ` 2.6.27-rc5-mm1: list corruption during blk_add_timer() Alexey Dobriyan
2008-09-05 19:40 ` Andrew Morton
2008-09-08 9:30 ` Jens Axboe
2008-09-05 19:32 ` [PATCH -mm] Fix dev_load() compilation again Alexey Dobriyan
2008-09-05 19:54 ` Hiroshi Shimamoto
2008-09-07 4:08 ` Stephen Rothwell
2008-09-08 22:17 ` Andrew Morton
2008-09-09 6:27 ` Johannes Berg
2008-09-09 11:07 ` 2.6.27-rc5-mm1 Dmitri Vorobiev
2008-09-11 10:16 ` 2.6.27-rc5-mm1 Dmitri Vorobiev
2008-09-11 14:59 ` 2.6.27-rc5-mm1 Kevin D. Kissell
2008-09-15 22:01 ` 2.6.27-rc5-mm1 Rik van Riel
2008-09-15 23:00 ` Michael Chan [this message]
2008-09-16 18:09 ` 2.6.27-rc5-mm1 Rik van Riel
2008-09-16 23:01 ` 2.6.27-rc5-mm1 Rik van Riel
2008-09-17 19:23 ` 2.6.27-rc5-mm1 Benjamin Li
[not found] ` <1221667442-4495-1-git-send-email-benli@broadcom.com>
[not found] ` <1221667442-4495-2-git-send-email-benli@broadcom.com>
2008-09-18 23:46 ` [PATCH] bnx2: Promote vector field in bnx2_irq structure from u16 to unsigned int David Miller
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=1221519658.11021.13.camel@HP1 \
--to=mchan@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox