Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> Maybe, but the actual error here is to do with the "format" of the jffs2 |> partition. It can be broken in kernel but I think we would have heard |> about it before, 2.6.28 is "old" now in kernel terms. | | well, so the best i can do is backup my data and recreate/reformat the | jiffs2 fs in flash -- with which parameters exactly? What I would try is a precooked jffs2 image with summaries, download it and then DFU it in via NOR U-Boot. Eg, http://downloads.freesmartphone.org/fso-unstable/images/om-gta02/ Actually what I would really do is run from uSD on a normal ext3 filesystem, but that's not to the point :-) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmgnWwACgkQOjLpvpq7dMp7AACfXm7WW43DeYR1zYodGL0yk+xI Z6kAnRGyGXul0HaXVLy1MoAdid0ZAsvq =7lbr -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
> Maybe, but the actual error here is to do with the "format" of the jffs2 > partition. It can be broken in kernel but I think we would have heard > about it before, 2.6.28 is "old" now in kernel terms. well, so the best i can do is backup my data and recreate/reformat the jiffs2 fs in flash -- with which parameters exactly? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> Dunno what you can do about it, but the guy who owns the process for |> generating the jffs2 image for Debian may get a hint from this to change |> how he generates it. jffs2 mount should be a few seconds not 120. | | oh, that's no flashed image or so. | it is the jiffs the fr came with. months ago i deleted everything and | copied my files over (the most crucial parts of debian: /sbin/ /lib/ ...) | from teh sd install. | with 2.6.24 i have never seen those errors. wouldn't that rather be some | kernel (2.6.28) related problem? Maybe, but the actual error here is to do with the "format" of the jffs2 partition. It can be broken in kernel but I think we would have heard about it before, 2.6.28 is "old" now in kernel terms. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmgI9sACgkQOjLpvpq7dMq8hQCfcEOQ4srllKrAKCOjberbitNe +8EAnA6NrUqJxfjkWeBUrpqOgHcTXjiN =l802 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
> Dunno what you can do about it, but the guy who owns the process for > generating the jffs2 image for Debian may get a hint from this to change > how he generates it. jffs2 mount should be a few seconds not 120. oh, that's no flashed image or so. it is the jiffs the fr came with. months ago i deleted everything and copied my files over (the most crucial parts of debian: /sbin/ /lib/ ...) from teh sd install. with 2.6.24 i have never seen those errors. wouldn't that rather be some kernel (2.6.28) related problem? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> It seems that it takes a long long while to mount the jffs2 partition |> you have. The first thing "CPU 0 stall" is just a comment that you seem |> to be stuck for two minutes, then the second thing is a diagnostic |> talking about what you are stuck on. It seems you are stuck on mounting |> the jffs2 partition. |> |> Lastly the jffs2 warning about summaries... IIRC this is to do with how |> the jffs2 filesystem image was composed when it was built there was |> something about slow mount and broken summaries when the jffs2 image was |> created with wrong block size as I recall. | | ok ... | so, what to do about it? Dunno what you can do about it, but the guy who owns the process for generating the jffs2 image for Debian may get a hint from this to change how he generates it. jffs2 mount should be a few seconds not 120. Particularly as I recall the parameters for generating GTA01 and GTA02 images differ due to NAND block differences. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEUEARECAAYFAkmgHSEACgkQOjLpvpq7dMpRvgCeNH/9MURwGqCUfwz4BkXK1yD9 rVAAmMtyHNuXwFOIEJhnWGusE4io46s= =ctYF -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
> It seems that it takes a long long while to mount the jffs2 partition > you have. The first thing "CPU 0 stall" is just a comment that you seem > to be stuck for two minutes, then the second thing is a diagnostic > talking about what you are stuck on. It seems you are stuck on mounting > the jffs2 partition. > > Lastly the jffs2 warning about summaries... IIRC this is to do with how > the jffs2 filesystem image was composed when it was built there was > something about slow mount and broken summaries when the jffs2 image was > created with wrong block size as I recall. ok ... so, what to do about it? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | i just found out that 2.6.28 is avaliable in debian and immediately | upgraded -- booting now shows a lot of weird messages jiffs2 related, | from which i can't make anything. | [21474543.18] RCU detected CPU 0 stall (t=4294908636/600 jiffies) | [21474543.18] [] (dump_stack+0x0/0x14) from [] | [21474543.18] [] (jffs2_add_fd_to_list+0x0/0xb8) from | [] (jffs2_sum_scan_sumnode+0x4c8/0x704) | [ 52.285000] JFFS2 warning: (1663) jffs2_sum_write_data: Not enough | space for summary, padsize = -778 | [ 300.005000] fbcon_event_notify action=12, data=c7831df4 | [ 300.005000] jbt6k74 spi2.0: jbt6k74 normal Well the last two lines are harmless, just about blanking the LCM. It seems that it takes a long long while to mount the jffs2 partition you have. The first thing "CPU 0 stall" is just a comment that you seem to be stuck for two minutes, then the second thing is a diagnostic talking about what you are stuck on. It seems you are stuck on mounting the jffs2 partition. Lastly the jffs2 warning about summaries... IIRC this is to do with how the jffs2 filesystem image was composed when it was built there was something about slow mount and broken summaries when the jffs2 image was created with wrong block size as I recall. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmgErMACgkQOjLpvpq7dMoiTwCeKhODgROWeHwydDQSl7JMg8HI G2UAniIT5LWB7FRXyKtHkSFSFlRg5Rdy =t/rT -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[debian/fso] 2.6.28-20090105.git69b2aa26 weird jiffs2 messages in dmesg
i just found out that 2.6.28 is avaliable in debian and immediately upgraded -- booting now shows a lot of weird messages jiffs2 related, from which i can't make anything. the last three lines appeared while i was typing this mail ... [21474540.115000] glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz). Bus width=0 [21474540.13] SD power -> 3200mV [21474540.13] glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 [21474540.14] glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 [21474540.15] glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 [21474540.155000] pcf50633-rtc pcf50633-rtc: setting system clock to 2009-02-21 14:19:54 UTC (1235225994) [21474540.16] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474540.165000] glamo-mci glamo-mci.0: Error after cmd: 0x120 [21474540.17] pcf50633 0-0073: INT1=0x80 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x80 [21474543.18] RCU detected CPU 0 stall (t=4294908636/600 jiffies) [21474543.18] [] (dump_stack+0x0/0x14) from [] (__rcu_pending+0x80/0x224) [21474543.18] [] (__rcu_pending+0x0/0x224) from [] (rcu_pending+0x18/0x4c) [21474543.18] r7:001e r6:c781c020 r5: r4: [21474543.18] [] (rcu_pending+0x0/0x4c) from [] (update_process_times+0x40/0x64) [21474543.18] [] (update_process_times+0x0/0x64) from [] (timer_tick+0x100/0x128) [21474543.18] r6: r5: r4:c03c6bd0 [21474543.18] [] (timer_tick+0x0/0x128) from [] (s3c2410_timer_interrupt+0x10/0x18) [21474543.18] r4:c03c43e4 [21474543.18] [] (s3c2410_timer_interrupt+0x0/0x18) from [] (handle_IRQ_event+0x2c/0x68) [21474543.18] [] (handle_IRQ_event+0x0/0x68) from [] (handle_edge_irq+0x12c/0x178) [21474543.18] r7:c03c7d34 r6:c03c43e4 r5:001e r4:c03c7d00 [21474543.18] [] (handle_edge_irq+0x0/0x178) from [] (__exception_text_start+0x64/0x84) [21474543.18] r8:0001 r7:0002 r6:4000 r5: r4:001e [21474543.18] [] (__exception_text_start+0x0/0x84) from [] (__irq_svc+0x38/0xc8) [21474543.18] Exception stack(0xc781fbf8 to 0xc781fc40) [21474543.18] fbe0: c7a33c00 c70ce220 [21474543.18] fc00: 1ef08742 b6fe1649 c7af7a20 c70ce220 c7af7a24 c70ce235 c7a33c00 c7a38908 [21474543.18] fc20: c7a719f0 c781fc64 c781fc68 c781fc40 c0155c60 c01479f4 0013 [21474543.18] r5:f400 r4: [21474543.18] [] (jffs2_add_fd_to_list+0x0/0xb8) from [] (jffs2_sum_scan_sumnode+0x4c8/0x704) [21474543.18] r8:c7a33c00 r7:c7abd940 r6: r5:c70ce220 r4:c7abfab2 [21474543.18] [] (jffs2_sum_scan_sumnode+0x0/0x704) from [] (jffs2_scan_medium+0x3a0/0x1494) [21474543.18] [] (jffs2_scan_medium+0x0/0x1494) from [] (jffs2_do_mount_fs+0x18c/0x55c) [21474543.18] [] (jffs2_do_mount_fs+0x0/0x55c) from [] (jffs2_do_fill_super+0x134/0x21c) [21474543.18] [] (jffs2_do_fill_super+0x0/0x21c) from [] (jffs2_fill_super+0xc8/0xfc) [21474543.18] r7: r6:0001 r5:c7a3e000 r4:c7a33c00 [21474543.18] [] (jffs2_fill_super+0x0/0xfc) from [] (get_sb_mtd_aux+0x64/0xc8) [21474543.18] r7:c780e2a0 r6: r5:8000 r4:c7a3e000 [21474543.18] [] (get_sb_mtd_aux+0x0/0xc8) from [] (get_sb_mtd+0x16c/0x198) [21474543.18] r8: r7:8000 r6:c7a32000 r5:c7a32000 r4:01f6 [21474543.18] [] (get_sb_mtd+0x0/0x198) from [] (jffs2_get_sb+0x24/0x30) [21474543.18] [] (jffs2_get_sb+0x0/0x30) from [] (vfs_kern_mount+0x58/0xac) [21474543.18] [] (vfs_kern_mount+0x0/0xac) from [] (do_kern_mount+0x40/0xdc) [21474543.18] r8:c03cb964 r7:c7a4 r6: r5:c7a32000 r4:8000 [21474543.18] [] (do_kern_mount+0x0/0xdc) from [] (do_mount+0x6b4/0x70c) [21474543.18] r8:8000 r7: r6: r5:8000 r4:c7a32000 [21474543.18] [] (do_mount+0x0/0x70c) from [] (sys_mount+0x90/0xdc) [21474543.18] [] (sys_mount+0x0/0xdc) from [] (mount_block_root+0x108/0x2ac) [21474543.18] r7:8000 r6:c78fa000 r5:c0027880 r4:c78fa000 [21474543.18] [] (mount_block_root+0x0/0x2ac) from [] (mount_root+0x54/0x6c) [21474543.18] [] (mount_root+0x0/0x6c) from [] (prepare_namespace+0x174/0x1d8) [21474543.18] r5:c0027838 r4:c03e7628 [21474543.18] [] (prepare_namespace+0x0/0x1d8) from [] (kernel_init+0xc4/0xf0) [21474543.18] r5:c0026644 r4:c03e7618 [21474543.18] [] (kernel_init+0x0/0xf0) from [] (do_exit+0x0/0x6e8) [21474543.18] r5: r4: [21474544.075000] jffs2_scan_inode_node(): CRC failed on node at 0x0f11a7c4: Read 0x, calculated 0x9c47de52 [21474544.08] Empty flash at 0x0f11a808 ends at 0x0f11b000 [21474544.64] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474544.645000] glamo-mci glamo-mci.0: Error a
