Call Trace and scary messages on kernel 2.6.27-rc5

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

123 more lines

On Sep 08 2008, Rogério Brito wrote:

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:

(...)

I obviously forgot to attach the files in the previous e-mail. :-(

Here they are.


Thanks again 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

Hello Rogerio,

Rogério Brito wrote onTue Sep 9 10:47:29 EST 2008:

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 at 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

[...]

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.

Try this patch:

http://lists.infradead.org/pipermail/linux-mtd/2008-August/022874.html

bye
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

On Mon, 8 Sep 2008 21:47:29 -0300
Rog=C3=A9rio Brito [off-list ref] wrote:

Hi there.
=20
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:

[snip]

This is a known problem.

Check patch bb23b431db7405f6d79f989ad0236bf6428ba1cb in Linus' tree, it
should correct the traces you see.

Regards,

	M.
--=20
And if you don't know where you're going, any road will take you there.

Thanks to both Mark and Heiko.

On Sep 09 2008, Marc Zyngier wrote:

On Mon, 8 Sep 2008 21:47:29 -0300 Rogério Brito [off-list ref] wrote:

quoted

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:

This is a known problem.

Check patch bb23b431db7405f6d79f989ad0236bf6428ba1cb in Linus' tree, it
should correct the traces you see.

I just downloaded the 2.6.27-rc6 kernel that was updated today and I
recompiled things and everything went fine regarding the MTD device.

Thank you very much for the informative messages.


Regards, 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