linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: 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: Sun, 14 Mar 2010 12:51:38 +0100	[thread overview]
Message-ID: <m2tysjw27p.fsf@whitebox.home> (raw)
In-Reply-To: <alpine.DEB.2.01.1003140431040.5493@bogon.housecafe.de> (Christian Kujau's message of "Sun, 14 Mar 2010 04:46:07 -0700 (PDT)")

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.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2010-03-14 11:51 UTC|newest]

Thread overview: 7+ 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 10:39   ` Christian Kujau
2010-03-14 11:24     ` Alexey Dobriyan
2010-03-14 11:46       ` Christian Kujau
2010-03-14 11:51         ` Andreas Schwab [this message]
2010-03-15  3:23           ` Benjamin Herrenschmidt

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=m2tysjw27p.fsf@whitebox.home \
    --to=schwab@linux-m68k.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=lists@nerdbynature.de \
    /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).