linux-kernel - Re: 2.6.27-rc5-mm1

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: <1221519658.11021.13.camel@HP1>
Date:	Mon, 15 Sep 2008 16:00:58 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Rik van Riel" <riel@...hat.com>
cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27-rc5-mm1


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@...ux-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?


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