Re: problem starting n800
Hi, ext Neil MacLeod wrote: I deleted a video from the card and then it worked fine. So it seems a bad file can stop the device booting without any hint as to what the problem might be! Is this a bug that is fixed in the next firmware, if not what should i file this against? Yes, it should. Thanks for the clues, Michael This tends to confirm the theory that removing SD cards can help a device that is refusing to boot. Obviously it shouldn't be possible to get a device into such a situation but clearly something is happening in the boot sequence whereby a corrupt fs can prevent the device from booting. Hopefully it's fixed in the next firmware, I don't think anyone has posted technical details about what exactly may be happening and why SD cards result in a boot failure. I think the problem is that when the device mounts the MMC during the boot process, metalayer-crawler gets inotified about that and starts scanning the contents of the MMC. Metalayer-crawler didn't handle possible errors from corrupted (MMC FAT) filesystems well enough and as a result it in worst case ended up up taking all memory and CPU in the device. This is fixed in the next release. It should also now react properly/promptly to user removing the MMC. There might also have been problems with some specific video files. What was the format of the video files which removing helped? - Eero ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: problem starting n800
On 11/03/07, Gustavo Sverzut Barbieri [EMAIL PROTECTED] wrote: On 3/6/07, Eero Tamminen [EMAIL PROTECTED] wrote: Hi, ext Michael Thompson wrote: When i turn on my n800 the progress bar doesn't come up and it never starts. If i remove one of sd cards then it starts. AFTer it booted i typed dmesg in the terminal [ 120.663482] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1452 [ 123.296722] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -822 These should AFAIK be harmless. If i re-insert the card once the n800 is running the card seems fine and has plenty of free space. Any ideas? What extra software you've installed to the device? streamer canola mapper terminal sudoku vnc mplayer gpe calendar nmap xgalaga erminig AFAIK similarly to the builtin crawler, Canola is also using inotify on the memory cards, so that could be triggering the bug on startup too (by starting to go through the card contents when the bootup process mounts it). Canola does use gnomevfs (i don't know if it uses inotify internally). BUT, canola triggers a consistency check after boot, since MMC card may be inexistent or changed. If things are still the same, it'll be just a bunch of stat() calls (one per file), not that slow. I see he has Mapper installed. By default, Mapper recommends /media/mmc1/Maps to store downloaded files and Canola ships with /media/mmc1 as media storage. This will make Canola scans every Map it found, since maps are small JPEG, it stat(), open() and parse it... :-/ You can remove /media/mmc1 from Canola and add more specialized folders, like /media/mmc1/Music (if you have that). I deleted a video from the card and then it worked fine. So it seems a bad file can stop the device booting without any hint as to what the problem might be! Is this a bug that is fixed in the next firmware, if not what should i file this against? Thanks for the clues, Michael ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: problem starting n800
On 3/6/07, Eero Tamminen [EMAIL PROTECTED] wrote: Hi, ext Michael Thompson wrote: When i turn on my n800 the progress bar doesn't come up and it never starts. If i remove one of sd cards then it starts. AFTer it booted i typed dmesg in the terminal [ 120.663482] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1452 [ 123.296722] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -822 These should AFAIK be harmless. If i re-insert the card once the n800 is running the card seems fine and has plenty of free space. Any ideas? What extra software you've installed to the device? streamer canola mapper terminal sudoku vnc mplayer gpe calendar nmap xgalaga erminig AFAIK similarly to the builtin crawler, Canola is also using inotify on the memory cards, so that could be triggering the bug on startup too (by starting to go through the card contents when the bootup process mounts it). Canola does use gnomevfs (i don't know if it uses inotify internally). BUT, canola triggers a consistency check after boot, since MMC card may be inexistent or changed. If things are still the same, it'll be just a bunch of stat() calls (one per file), not that slow. I see he has Mapper installed. By default, Mapper recommends /media/mmc1/Maps to store downloaded files and Canola ships with /media/mmc1 as media storage. This will make Canola scans every Map it found, since maps are small JPEG, it stat(), open() and parse it... :-/ You can remove /media/mmc1 from Canola and add more specialized folders, like /media/mmc1/Music (if you have that). -- Gustavo Sverzut Barbieri -- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 Phone: +1 (347) 624 6296; [EMAIL PROTECTED] GPG: 0xB640E1A2 @ wwwkeys.pgp.net ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: problem starting n800
Hi, ext Michael Thompson wrote: When i turn on my n800 the progress bar doesn't come up and it never starts. If i remove one of sd cards then it starts. AFTer it booted i typed dmesg in the terminal [ 120.663482] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1452 [ 123.296722] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -822 These should AFAIK be harmless. If i re-insert the card once the n800 is running the card seems fine and has plenty of free space. Any ideas? What extra software you've installed to the device? If you fsck your card, are any file system errors reported? - If there are errors, this could be something triggered by the metalayer-crawler misbehaviour (which is fixed in next release) - If no errors are reported or the issue happens also after the card file system is fixed, could you file a bug at maemo.org, include the information about your card brand and manufacturer, and mail the bug id to the list? - Eero ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: problem starting n800
On 05/03/07, Eero Tamminen [EMAIL PROTECTED] wrote: Hi, ext Michael Thompson wrote: When i turn on my n800 the progress bar doesn't come up and it never starts. If i remove one of sd cards then it starts. AFTer it booted i typed dmesg in the terminal [ 120.663482] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1452 [ 123.296722] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -822 These should AFAIK be harmless. If i re-insert the card once the n800 is running the card seems fine and has plenty of free space. Any ideas? What extra software you've installed to the device? streamer canola mapper terminal sudoku vnc mplayer gpe calendar nmap xgalaga erminig If you fsck your card, are any file system errors reported? - If there are errors, this could be something triggered by the metalayer-crawler misbehaviour (which is fixed in next release) fsck in linux and windows disk check bother report no errors. For the record the output was dosfsck 2.11, 12 Mar 2005, FAT32, LFN Checking we can access the last sector of the filesystem Boot sector contents: System ID MSDOS5.0 Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 3863552 bytes per FAT (= 7546 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 7743488 (sector 15124) 965788 data clusters (3955867648 bytes) 63 sectors/track, 128 heads 12 hidden sectors 7741428 sectors total Checking for unused clusters. Checking free cluster summary. /dev/sda1: 264 files, 263612/965788 clusters - If no errors are reported or the issue happens also after the card file system is fixed, could you file a bug at maemo.org, include the information about your card brand and manufacturer, and mail the bug id to the list? Unfortunately this is a no name 4GB SD card. Is there a command I can run on linux to get some more info on the card? ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: problem starting n800
Hi, ext Michael Thompson wrote: When i turn on my n800 the progress bar doesn't come up and it never starts. If i remove one of sd cards then it starts. AFTer it booted i typed dmesg in the terminal [ 120.663482] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1452 [ 123.296722] JFFS2 warning: (1153) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -822 These should AFAIK be harmless. If i re-insert the card once the n800 is running the card seems fine and has plenty of free space. Any ideas? What extra software you've installed to the device? streamer canola mapper terminal sudoku vnc mplayer gpe calendar nmap xgalaga erminig AFAIK similarly to the builtin crawler, Canola is also using inotify on the memory cards, so that could be triggering the bug on startup too (by starting to go through the card contents when the bootup process mounts it). When the next release comes out (with crawler version which handles memory card related errors better), you could check whether things work better (at least when Canola is not installed). If you fsck your card, are any file system errors reported? - If there are errors, this could be something triggered by the metalayer-crawler misbehaviour (which is fixed in next release) fsck in linux and windows disk check bother report no errors. For the record the output was dosfsck 2.11, 12 Mar 2005, FAT32, LFN Checking we can access the last sector of the filesystem Boot sector contents: System ID MSDOS5.0 Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 3863552 bytes per FAT (= 7546 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 7743488 (sector 15124) 965788 data clusters (3955867648 bytes) 63 sectors/track, 128 heads 12 hidden sectors 7741428 sectors total Checking for unused clusters. Checking free cluster summary. /dev/sda1: 264 files, 263612/965788 clusters - If no errors are reported or the issue happens also after the card file system is fixed, could you file a bug at maemo.org http://maemo.org, include the information about your card brand and manufacturer, and mail the bug id to the list? Unfortunately this is a no name 4GB SD card. I.e. unsupported by current releases, only cards upto 2GB are supported... Larger ones working is just luck. Is there a command I can run on linux to get some more info on the card? I think on the device the information would be here: /sys/devices/platform/mmci-omap.1/mmc1:0001/ But it seems to be in numeric format. :-/ - Eero ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
