From: Michael Ellerman <michael@ellerman.id.au>
To: ron_madrid@sbcglobal.net
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Bootlog bug?
Date: Fri, 27 Mar 2009 09:51:27 +1100 [thread overview]
Message-ID: <1238107887.15460.3.camel@localhost> (raw)
In-Reply-To: <736813.1073.qm@web83507.mail.sp1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
On Thu, 2009-03-26 at 11:25 -0700, Ron Madrid wrote:
> I have a little problem with my boot messages. I'm not sure what this
> is, but does anyone have any ideas as to what it could be or what
> further information I could give to help track this down. As of now
> this is not manifesting itself, but I don't know what it might do.
You have ended up with a duplicate device, or duplicate device _name_,
somehow.
This is the warn:
WARN(ret == -EEXIST, KERN_WARNING "sysfs: duplicate filename '%s' "
"can not be created\n", sd->s_name);
Turning on verbose bug info would show you the name.
cheers
> ------------[ cut here ]------------
> Badness at c00bdebc [verbose debug info unavailable]
> NIP: c00bdebc LR: c00bdea4 CTR: 00000000
> REGS: c7827d90 TRAP: 0700 Not tainted (2.6.27)
> MSR: 00029032 <EE,ME,IR,DR> CR: 22022042 XER: 20000000
> TASK = c7816400[1] 'swapper' THREAD: c7826000
> GPR00: c00bdea4 c7827e40 c7816400 ffffffef c7800dcc c7800afc c7811540 00000000
> GPR08: 000001e0 c03c0000 00000040 00000000 82044048 10101400 07ffb000 00000000
> GPR16: 07ff0350 07ff59b4 00000000 00000000 00000000 c03ac84c c03ac820 c7857210
> GPR24: 00000000 00000000 00000000 00000001 c7811540 fffffffe c78b4480 c7827e58
> NIP [c00bdebc] sysfs_add_one+0x28/0x30
> LR [c00bdea4] sysfs_add_one+0x10/0x30
> Call Trace:
> [c7827e40] [c00bdea4] sysfs_add_one+0x10/0x30 (unreliable)
> [c7827e50] [c00bf12c] sysfs_do_create_link+0xac/0x15c
> [c7827e80] [c01a09b4] bus_add_device+0xf4/0x190
> [c7827ea0] [c019f1a0] device_add+0x38c/0x5c8
> [c7827ef0] [c0225db4] of_device_register+0x24/0x34
> [c7827f00] [c0009844] of_platform_device_create+0x44/0x74
> [c7827f10] [c00098ec] of_platform_bus_create+0x78/0xc8
> [c7827f30] [c0009a5c] of_platform_bus_probe+0x120/0x150
> [c7827f50] [c037a3e4] __machine_initcall_mpc831x_rdb_declare_of_platform_devices+0x4c/0x60
> [c7827f60] [c0003874] do_one_initcall+0x38/0x188
> [c7827fd0] [c036917c] kernel_init+0x88/0xf4
> [c7827ff0] [c0011b10] kernel_thread+0x44/0x60
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-26 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:25 Bootlog bug? Ron Madrid
2009-03-26 22:51 ` Michael Ellerman [this message]
2009-03-30 21:11 ` Ron Madrid
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=1238107887.15460.3.camel@localhost \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/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).