From: "Rafael J. Wysocki" <rjw@sisk•pl>
To: Andrew Morton <akpm@osdl•org>
Cc: linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
Greg KH <greg@kroah•com>
Subject: Re: 2.6.18-rc7-mm1: networking breakage on HPC nx6325 + SUSE 10.1
Date: Wed, 20 Sep 2006 00:06:52 +0200 [thread overview]
Message-ID: <200609200006.53138.rjw@sisk.pl> (raw)
In-Reply-To: <200609192330.34769.rjw@sisk.pl>
On Tuesday, 19 September 2006 23:30, Rafael J. Wysocki wrote:
> On Tuesday, 19 September 2006 22:36, Andrew Morton wrote:
> > On Tue, 19 Sep 2006 22:25:21 +0200
> > "Rafael J. Wysocki" <rjw@sisk•pl> wrote:
> >
> > > > - It took maybe ten hours solid work to get this dogpile vaguely
> > > > compiling and limping to a login prompt on x86, x86_64 and powerpc.
> > > > I guess it's worth briefly testing if you're keen.
> > >
> > > It's not that bad, but unfortunately the networking doesn't work on my system
> > > (HPC nx6325 + SUSE 10.1 w/ updates, 64-bit). Apparently, the interfaces don't
> > > get configured (both tg3 and bcm43xx are affected).
> >
> > Is there anything interesting in the dmesg output?
>
> Not to me. :-)
>
> > Perhaps an `strace -f ifup' or whatever would tell us what's failing.
>
> Well, I can configure the interfaces manually, with ifconfig, but the SUSE's
> configuration tools don't work. For example, "ifup eth0" tells me that
> "No configuration found for eth0" and that's all.
>
> Also, powersaved segfaults at startup so I think the problem is with hal
> vs sysfs (again).
>
> The output of dmesg after a fresh boot and the "strace ifup eth0" output
> are attached.
I _guess_ the problem is caused by
gregkh-driver-network-class_device-to-device.patch, but I can't verify this,
because the kernel (obviously) doesn't compile if I revert it.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-09-19 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060919012848.4482666d.akpm@osdl.org>
[not found] ` <200609192225.21801.rjw@sisk.pl>
2006-09-19 20:36 ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 21:30 ` 2.6.18-rc7-mm1: networking breakage on HPC nx6325 + SUSE 10.1 Rafael J. Wysocki
2006-09-19 22:06 ` Rafael J. Wysocki [this message]
2006-09-19 22:06 ` David Miller
2006-09-19 22:30 ` Greg KH
2006-09-19 22:56 ` Rafael J. Wysocki
2006-09-20 2:28 ` Greg KH
2006-09-20 1:31 ` Dmitry Torokhov
2006-09-20 1:03 ` Valdis.Kletnieks
2006-09-20 14:23 ` 2.6.18-rc7-mm1 Mike Galbraith
2006-09-20 13:18 ` 2.6.18-rc7-mm1 Rafael J. Wysocki
2006-09-21 9:44 ` 2.6.18-rc7-mm1 Andi Kleen
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=200609200006.53138.rjw@sisk.pl \
--to=rjw@sisk$(echo .)pl \
--cc=akpm@osdl$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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