From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Christian Kujau <lists@nerdbynature.de>,
linuxppc-dev@ozlabs.org, Alexey Dobriyan <adobriyan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Date: Mon, 15 Mar 2010 14:23:46 +1100 [thread overview]
Message-ID: <1268623426.2209.109.camel@pasglop> (raw)
In-Reply-To: <m2tysjw27p.fsf@whitebox.home>
On Sun, 2010-03-14 at 12:51 +0100, Andreas Schwab wrote:
> Christian Kujau <lists@nerdbynature.de> writes:
>
> > On Sun, 14 Mar 2010 at 13:24, Alexey Dobriyan wrote:
> >> Post "find /proc/device-tree" output.
> >
> > I did upload[0] a tarball of /proc/device-tree, please see below the
> > "find" output.
> >
> > Indeed, there's a /cpus/PowerPC,G4@0/l2-cache and
> > /cpus/PowerPC,G4@0/l2-cache#1 in the device-tree. However, from looking at
> > the logfiles, the
> >
> > device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
>
> That's a red herring, the real problem is this:
>
> name 'pulses/rev'
>
> Of course, this name cannot be found in /proc/device-tree, because it
> wasn't created.
You mean apple stuck a bloody "/" in a name property ? ARGH !
We should just add code to detect that and replace it with a "_" or
something...
Cheers,
Ben.
prev parent reply other threads:[~2010-03-15 4:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 23:53 2.6.34-rc1: Badness at fs/proc/generic.c:316 Christian Kujau
2010-03-14 6:55 ` Alexey Dobriyan
2010-03-14 6:55 ` Alexey Dobriyan
2010-03-14 10:39 ` Christian Kujau
2010-03-14 10:39 ` Christian Kujau
2010-03-14 11:24 ` Alexey Dobriyan
2010-03-14 11:24 ` Alexey Dobriyan
2010-03-14 11:46 ` Christian Kujau
2010-03-14 11:46 ` Christian Kujau
2010-03-14 11:51 ` Andreas Schwab
2010-03-14 11:51 ` Andreas Schwab
2010-03-15 3:23 ` Benjamin Herrenschmidt [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=1268623426.2209.109.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=schwab@linux-m68k.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.