Re: [Familiar] A possible explanatation of the CRC ERROR bug.

yes i had the problem. It seems reboot after next flash (Booldr, Kernel ,
Root) is necessary. sometime before,i want to reinstall my iPaq under linux,
with linux on, and i don't arrive. The solution to "clean" all the
filesystem, reboot, re-load the bootloader, reboot, load kernel, reboot,
load root reboot was my only solution to get the system working. before i
had a lot of dump / crc errors ... (i thunk my files where crash, but it was
the same i use before to install !)

Philippe
Email / Philippe@choup.net

----- Original Message -----
From: "Marc Rogers" <marc@avbroadband.com>
To: <ipaq@handhelds.org>
Cc: <familiar@handhelds.org>; <intimate@handhelds.org>
Sent: Saturday, July 28, 2001 8:40 AM
Subject: [Familiar] A possible explanatation of the CRC ERROR bug.

> I have seen posted on this list a few comments about a CRC bug that
> occurs while loading a new kernel / root into the bootloader. The only
> answer to this bug that I have seen is that "eventually it works".
>
>
> http://www.handhelds.org/pipermail/ipaq/2001-March/005278.html
> http://www.handhelds.org/pipermail/ipaq/2001-April/006092.html
> http://www.handhelds.org/pipermail/ipaq/2001-April/006099.html
>
> are 3 examples of posts refering to this bug.
>
> Last night I was hit by this bug. Many thanks to those on #ipaq,
> #handhelds.org, #intimate and #familiar who gave suppport and advice.
>
> Especially to nikos, who pointed me in the right direction.
>
> There appears to be some kind of bug relating to prolonged flashing of
> ipaqs. Quite possibly heat related. This also explains why longer flashes
> have been a little hit and miss.
>
> As an experiment I switched the ipaq off and reflashed the kernel and
root.
> No problems. Then I proceeded to use the ipaq for an hour and subsequently
> reflashed it a further 4 times. The same kernel image was used each times,
> and the md5sums have been verified. After the third flash, the system
> failed to boot with crc errors.
>
> at the bottom of this email i will paste a transcript of that failed boot.
>
> Workaround:
> The best workaround currently seems to be to rest the ipaq between
flashes,
> and to only flash when the ipaq has been off for a while.
>
>
> Hope this helps.
>
>
> Marc Rogers
>
>
>
> ----------------------------begin crc
> error.log---------------------------------
> boot> boot> boot
> booting flash...
> kernel_magic=E1A00000
> kernel_region_words[9]=016F2818
> Linux ELF flash_imgstart=50080000 size=000C0000 dest=C0000000
offset=00008000
> MMU Control=C19F4071
> copying Linux kernel ... done
> linuxEntryPoint: C0008000
> kernel_image_dest: C0000000
> kernel_image_offset: 00008000
> C0008000: E1A00000
> C0008004: E1A00000
> C0008008: E1A00000
> C000800C: E1A00000
> C0008010: E1A00000
> C0008014: E1A00000
> C0008018: E1A00000
> C000801C: E1A00000
> C0008020: EA000002
> C0008024: 016F2818
> root_filesystem_name=ramdisk
> argc=00000002
> args=noinitrd root=/dev/mtdblock/3 init=/linuxrc console=ttySA0
> setting boot parameters
> get_param: could not find parameter system_rev
> Setting up Linux parameters at address=C0000100
> using_ramdisk=00000001
> initrd_start=346C7466
> dram_size=04000000
> nr_pages=00004000
> command line is: noinitrd root=/dev/mtdblock/3 init=/linuxrc
console=ttySA0
> linuxEntryPoint=C0008000
> Booting Linux image
> Uncompressing Linux....................................................
>
> crc error
>
> -- System halted
>
> _______________________________________________
> Familiar mailing list
> Familiar@handhelds.org
> http://handhelds.org/mailman/listinfo/familiar
> irc://irc.openprojects.net #familiar
>
Received on Sat Jul 28 01:36:49 2001