linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike Dyer <mike.dyer@provision-comm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8313E RDB: Badness at fs/sysfs/dir.c:463
Date: Wed, 15 Oct 2008 11:06:25 +0100	[thread overview]
Message-ID: <1224065185.457.31.camel@mike-linux.provision-comm.com> (raw)
In-Reply-To: <22A97B63-36D5-44BA-8F49-BAF5870FA08A@kernel.crashing.org>

Hi Kumar,

On Tue, 2008-10-14 at 09:35 -0500, Kumar Gala wrote: 
> On Oct 14, 2008, at 9:12 AM, Mike Dyer wrote:
> 
> > Hi All,
> >
> > Apologies for the bad formatting of the previous message...
> >
> > I've just pulled the 2.6.27 kernel from git and am trying it out on  
> > my MPC8313E RDB dev kit.  I get the following badness during boot  
> > (the complete boot record is attached later) :
> 
> can you enable kernel symbols in your build (CONFIG_KALLSYMS)

I can, but it no longer boots...  Will keep trying.

I've gone through my system.map and pulled out the call stack, if that
helps.  I put a printk in sysfs_add_one, and it appears it is being
called with sd->s_name = 'e00082a8.dma'

> ------------[ cut here ]------------
> Badness at c00c5b50 [verbose debug info unavailable]
> NIP: c00c5b50 LR: c00c5b38 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: c00c5b38 c7827e40 c7816400 ffffffef c7800e5c c7800b7c c7811570 00000000 
> GPR08: 000001a0 c0370000 00000048 00000000 82044048 100b224c 07ffb000 00000000 
> GPR16: 07ff09e0 07ff94c8 00000000 00000000 00000000 c035a76c c035a740 c7ace610 
> GPR24: 00000000 00000000 00000000 00000001 c7811570 fffffffe c7acdc00 c7827e58 
> Call Trace:
> [c7827e40] [c00c5b38] 0xc00c5b38 (unreliable) sysfs_add_one
> [c7827e50] [c00c6dc0] 0xc00c6dc0              sysfs_do_create_link
> [c7827e80] [c0182d40] 0xc0182d40              bus_add_device
> [c7827ea0] [c018153c] 0xc018153c              device_add
> [c7827ef0] [c0213a14] 0xc0213a14              of_device_register
> [c7827f00] [c0009818] 0xc0009818              of_platform_device_create
> [c7827f10] [c00098c0] 0xc00098c0              of_platform_bus_create
> [c7827f30] [c0009a30] 0xc0009a30              of_platform_bus_probe
> [c7827f50] [c03281d4] 0xc03281d4              __machine_initcall_mpc831x_rdb_declare_of_platform_devices
> [c7827f60] [c0003874] 0xc0003874              do_one_initcall
> [c7827fd0] [c031317c] 0xc031317c              kernel_init
> [c7827ff0] [c001216c] 0xc001216c              kernel_thread

> 
> - k

Cheers,
Mike

  reply	other threads:[~2008-10-15 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 13:24 MPC8313E RDB: Badness at fs/sysfs/dir.c:463 Mike Dyer
2008-10-14 14:12 ` Mike Dyer
2008-10-14 14:35   ` Kumar Gala
2008-10-15 10:06     ` Mike Dyer [this message]
2008-10-28 15:53       ` Mike Dyer
2008-10-28 16:12         ` Scott Wood
2008-10-28 19:38           ` Joaquin Luna
2008-10-28 20:45             ` Scott Wood

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=1224065185.457.31.camel@mike-linux.provision-comm.com \
    --to=mike.dyer@provision-comm.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.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 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).