[maemo-developers] N810 Resets

[From: Alex Iliadis]

Hi,

I think there was a bit of a confusion here, I was using the pre-bundled 
internal card shipped with the device with the default filesystem (jffs2). 
(No added MMC card)
Anyway the problem has been solved. As you had originally suggested there 
was a peak point at which my application was trying to use 195MB of memory 
and that's when the reboot of the device occurred. I fixed that by 
manually controlling pythons garbage collector to force it to free memory.

Thanks,
Alex

On Friday 14 December 2007 06:20:01 am you wrote:
> Hi,
>
> ext Alex Iliadis wrote:
> > Hi Eero,
> >
> > On Thursday 13 December 2007 10:16:09 am you wrote:
> >> ext Alex Iliadis wrote:
> >>> On Thursday 13 December 2007 02:25:58 am you wrote:
> >>>> ext Alex Iliadis wrote:
> >>>
> >>> I scrolled a bit further down though and I noticed the following:
> >>>
> >>> Dec 13 09:36:20 Nokia-N810-42-18 kernel: [   18.531250] mmcblk0:
> >>> rw=0, want=4013848, limit=3932160
> >>> Dec 13 09:36:20 Nokia-N810-42-18 kernel: [   18.531250] Buffer I/O
> >>> error on device mmcblk0p1, logical block 501728
> >>> Dec 13 09:36:20 Nokia-N810-42-18 kernel: [   18.531250] attempt to
> >>> access beyond end of device
> >>
> >> Does the reboot happen if you remove the MMC?
> >>
> >> There was earlier some case where an application infinitely reading
> >> corrupted MMC FAT file system could sometimes cause kernel panic, but
> >> that should have been fixed for N810 & Chinook.
> >
> > I think it's an internal one bundled with the device. (I haven't
> > connected any in the slot) Not sure why it's displayed as mmc, but I'm
> > guessing the linux kernel identifies it as one? Maybe somehow it got
> > corrupted and that's what's causing the problems? I'll try to do a
> > clean flash of the system and re-run the application and let you know
> > of the result.
>
> Reflashing doesn't do anything to the MMCs (whether it's the N810
> internal one of something that user can change).  You can format it
> from the file manager or from Desktop after connecting the USB cable.
>
> In Chinook the MMC is mounted as read-only if it's corrupted.
> However if something in system is accessing it incessantly, it's
> possible that this can cause some instability.
>
>
> Btw. As everybody knows, the MicroSoft FAT file system used on
> the memory cards wasn't designed to be robust.  If you unplug
> the USB cable without "safely remove" step, remove MMC otherwise
> when it's being written, take battery out when device is on or
> device HW (not SW) watchdog reboots it, the MMC FAT filesystem
> will get corrupted.  (These aren't a problem with the internal
> JFFS2 filesystem)
>
>
> 	- Eero