From: "Rogério Brito" <rbrito@ime.usp.br>
To: linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
linuxppc-embedded@ozlabs.org
Subject: Call Trace and scary messages on kernel 2.6.27-rc5
Date: Mon, 8 Sep 2008 21:47:29 -0300 [thread overview]
Message-ID: <20080909004727.GA6239@ime.usp.br> (raw)
Hi there.
I just compiled a new 2.6.27-rc5 kernel for my standard Kurobox (an
embedded NAS that has an MPC8241 CPU, if I'm not mistaken) and upon
booting, I get these scary messages and Call Traces:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Linux version 2.6.27-rc5.try03 (rbrito@chagas) (gcc version 4.2.0) #4 Mon Sep 8 21:12:13 BRT 2008
(...)
physmap platform flash device: 00400000 at ffc00000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00300000 : "mtd_firmimg"
0x00300000-0x00370000 : "mtd_bootcode"
kobject (c395b278): tried to init an initialized object, something is seriously wrong.
Call Trace:
[c381dc80] [c000806c] show_stack+0x4c/0x16c (unreliable)
[c381dcc0] [c013a308] kobject_init+0x64/0xa4
[c381dcd0] [c013a920] kobject_init_and_add+0x30/0x78
[c381dd10] [c0135574] blk_register_filter+0x4c/0x70
[c381dd20] [c01340a4] add_disk+0x68/0xbc
[c381dd40] [c01b1210] add_mtd_blktrans_dev+0x17c/0x2b4
[c381dd60] [c01b1490] mtdblock_add_mtd+0x60/0x80
[c381dd70] [c01b08d8] blktrans_notify_add+0x44/0x84
[c381dd90] [c01ac118] add_mtd_device+0xa8/0x140
[c381ddb0] [c01ad860] add_mtd_partitions+0x55c/0x6b0
[c381de10] [c01b5cc4] physmap_flash_probe+0x2d8/0x318
[c381de50] [c0175864] platform_drv_probe+0x20/0x30
[c381de60] [c0174748] driver_probe_device+0xb8/0x1e8
[c381de80] [c01738ec] bus_for_each_drv+0x70/0xac
[c381deb0] [c01749c8] device_attach+0x84/0xa8
[c381ded0] [c01736e0] bus_attach_device+0x6c/0x78
[c381dee0] [c01720bc] device_add+0x47c/0x5c8
[c381df30] [c0175d30] platform_device_add+0x14c/0x1b4
[c381df50] [c03245fc] physmap_init+0x30/0x48
[c381df60] [c0003874] do_one_initcall+0x38/0x1a0
[c381dfd0] [c030a17c] kernel_init+0x88/0xf4
[c381dff0] [c000fd4c] kernel_thread+0x44/0x60
0x00370000-0x00380000 : "mtd_status"
kobject (c395b278): tried to init an initialized object, something is seriously wrong.
Call Trace:
[c381dc80] [c000806c] show_stack+0x4c/0x16c (unreliable)
[c381dcc0] [c013a308] kobject_init+0x64/0xa4
[c381dcd0] [c013a920] kobject_init_and_add+0x30/0x78
[c381dd10] [c0135574] blk_register_filter+0x4c/0x70
[c381dd20] [c01340a4] add_disk+0x68/0xbc
[c381dd40] [c01b1210] add_mtd_blktrans_dev+0x17c/0x2b4
[c381dd60] [c01b1490] mtdblock_add_mtd+0x60/0x80
[c381dd70] [c01b08d8] blktrans_notify_add+0x44/0x84
[c381dd90] [c01ac118] add_mtd_device+0xa8/0x140
[c381ddb0] [c01ad860] add_mtd_partitions+0x55c/0x6b0
[c381de10] [c01b5cc4] physmap_flash_probe+0x2d8/0x318
[c381de50] [c0175864] platform_drv_probe+0x20/0x30
[c381de60] [c0174748] driver_probe_device+0xb8/0x1e8
[c381de80] [c01738ec] bus_for_each_drv+0x70/0xac
[c381deb0] [c01749c8] device_attach+0x84/0xa8
[c381ded0] [c01736e0] bus_attach_device+0x6c/0x78
[c381dee0] [c01720bc] device_add+0x47c/0x5c8
[c381df30] [c0175d30] platform_device_add+0x14c/0x1b4
[c381df50] [c03245fc] physmap_init+0x30/0x48
[c381df60] [c0003874] do_one_initcall+0x38/0x1a0
[c381dfd0] [c030a17c] kernel_init+0x88/0xf4
[c381dff0] [c000fd4c] kernel_thread+0x44/0x60
0x00380000-0x00400000 : "mtd_conf"
kobject (c395b278): tried to init an initialized object, something is seriously wrong.
Call Trace:
[c381dc80] [c000806c] show_stack+0x4c/0x16c (unreliable)
[c381dcc0] [c013a308] kobject_init+0x64/0xa4
[c381dcd0] [c013a920] kobject_init_and_add+0x30/0x78
[c381dd10] [c0135574] blk_register_filter+0x4c/0x70
[c381dd20] [c01340a4] add_disk+0x68/0xbc
[c381dd40] [c01b1210] add_mtd_blktrans_dev+0x17c/0x2b4
[c381dd60] [c01b1490] mtdblock_add_mtd+0x60/0x80
[c381dd70] [c01b08d8] blktrans_notify_add+0x44/0x84
[c381dd90] [c01ac118] add_mtd_device+0xa8/0x140
[c381ddb0] [c01ad860] add_mtd_partitions+0x55c/0x6b0
[c381de10] [c01b5cc4] physmap_flash_probe+0x2d8/0x318
[c381de50] [c0175864] platform_drv_probe+0x20/0x30
[c381de60] [c0174748] driver_probe_device+0xb8/0x1e8
[c381de80] [c01738ec] bus_for_each_drv+0x70/0xac
[c381deb0] [c01749c8] device_attach+0x84/0xa8
[c381ded0] [c01736e0] bus_attach_device+0x6c/0x78
[c381dee0] [c01720bc] device_add+0x47c/0x5c8
[c381df30] [c0175d30] platform_device_add+0x14c/0x1b4
[c381df50] [c03245fc] physmap_init+0x30/0x48
[c381df60] [c0003874] do_one_initcall+0x38/0x1a0
[c381dfd0] [c030a17c] kernel_init+0x88/0xf4
[c381dff0] [c000fd4c] kernel_thread+0x44/0x60
0x00000000-0x00400000 : "mtd_allflash"
kobject (c395b278): tried to init an initialized object, something is seriously wrong.
Call Trace:
[c381dc80] [c000806c] show_stack+0x4c/0x16c (unreliable)
[c381dcc0] [c013a308] kobject_init+0x64/0xa4
[c381dcd0] [c013a920] kobject_init_and_add+0x30/0x78
[c381dd10] [c0135574] blk_register_filter+0x4c/0x70
[c381dd20] [c01340a4] add_disk+0x68/0xbc
[c381dd40] [c01b1210] add_mtd_blktrans_dev+0x17c/0x2b4
[c381dd60] [c01b1490] mtdblock_add_mtd+0x60/0x80
[c381dd70] [c01b08d8] blktrans_notify_add+0x44/0x84
[c381dd90] [c01ac118] add_mtd_device+0xa8/0x140
[c381ddb0] [c01ad860] add_mtd_partitions+0x55c/0x6b0
[c381de10] [c01b5cc4] physmap_flash_probe+0x2d8/0x318
[c381de50] [c0175864] platform_drv_probe+0x20/0x30
[c381de60] [c0174748] driver_probe_device+0xb8/0x1e8
[c381de80] [c01738ec] bus_for_each_drv+0x70/0xac
[c381deb0] [c01749c8] device_attach+0x84/0xa8
[c381ded0] [c01736e0] bus_attach_device+0x6c/0x78
[c381dee0] [c01720bc] device_add+0x47c/0x5c8
[c381df30] [c0175d30] platform_device_add+0x14c/0x1b4
[c381df50] [c03245fc] physmap_init+0x30/0x48
[c381df60] [c0003874] do_one_initcall+0x38/0x1a0
[c381dfd0] [c030a17c] kernel_init+0x88/0xf4
[c381dff0] [c000fd4c] kernel_thread+0x44/0x60
0x00310000-0x00400000 : "mtd_data"
kobject (c395b278): tried to init an initialized object, something is seriously wrong.
Call Trace:
[c381dc80] [c000806c] show_stack+0x4c/0x16c (unreliable)
[c381dcc0] [c013a308] kobject_init+0x64/0xa4
[c381dcd0] [c013a920] kobject_init_and_add+0x30/0x78
[c381dd10] [c0135574] blk_register_filter+0x4c/0x70
[c381dd20] [c01340a4] add_disk+0x68/0xbc
[c381dd40] [c01b1210] add_mtd_blktrans_dev+0x17c/0x2b4
[c381dd60] [c01b1490] mtdblock_add_mtd+0x60/0x80
[c381dd70] [c01b08d8] blktrans_notify_add+0x44/0x84
[c381dd90] [c01ac118] add_mtd_device+0xa8/0x140
[c381ddb0] [c01ad860] add_mtd_partitions+0x55c/0x6b0
[c381de10] [c01b5cc4] physmap_flash_probe+0x2d8/0x318
[c381de50] [c0175864] platform_drv_probe+0x20/0x30
[c381de60] [c0174748] driver_probe_device+0xb8/0x1e8
[c381de80] [c01738ec] bus_for_each_drv+0x70/0xac
[c381deb0] [c01749c8] device_attach+0x84/0xa8
[c381ded0] [c01736e0] bus_attach_device+0x6c/0x78
[c381dee0] [c01720bc] device_add+0x47c/0x5c8
[c381df30] [c0175d30] platform_device_add+0x14c/0x1b4
[c381df50] [c03245fc] physmap_init+0x30/0x48
[c381df60] [c0003874] do_one_initcall+0x38/0x1a0
[c381dfd0] [c030a17c] kernel_init+0x88/0xf4
[c381dff0] [c000fd4c] kernel_thread+0x44/0x60
usbmon: debugfs is not available
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I'm attaching the dmesg and my .config to this message if it is needed.
If anything else is needed, please let me know. This kernel was
cross-compiled with my own homebrewed system (I'm using Debian unstable
for x86-64 on the host and Debian testing for powerpc on the target).
I am open to any suggestions. If I can help chasing the cause of such
scary messages in anyway, please let me know.
Thanks in advance, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next reply other threads:[~2008-09-09 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 0:47 Rogério Brito [this message]
2008-09-09 0:52 ` Call Trace and scary messages on kernel 2.6.27-rc5 Rogério Brito
2008-09-09 6:33 ` Heiko Schocher
2008-09-09 20:08 ` Marc Zyngier
2008-09-11 5:34 ` Rogério Brito
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=20080909004727.GA6239@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.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).