From: Andi Kleen <ak@suse.de>
To: Mike Galbraith <efault@gmx.de>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.18-rc7-mm1
Date: Thu, 21 Sep 2006 11:44:58 +0200 [thread overview]
Message-ID: <200609211144.58950.ak@suse.de> (raw)
In-Reply-To: <1158762221.6512.10.camel@Homer.simpson.net>
On Wednesday 20 September 2006 16:23, Mike Galbraith wrote:
> On Tue, 2006-09-19 at 13:36 -0700, 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?
> >
> > Perhaps an `strace -f ifup' or whatever would tell us what's failing.
>
> FYI, it`s SuSE`s /sbin/getcfg binary that doesn't like the changes. It
> sees /sys/class/net/eth0 as a symlink, and reels off into sys/block (?)
> looking for a directory.
It's a known problem. It's actually libsysfs' fault which somehow manages
to not support symlinks properly. Unfortunately getcfg made the mistake of using libsysfs
instead of accessing /sys directly
-Andi
prev parent reply other threads:[~2006-09-21 9:45 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
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 ` Andi Kleen [this message]
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=200609211144.58950.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).