From: "Raúl Sánchez Siles" <rss@barracuda.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AT91 Kernel oops when loading kernel from dataflash.
Date: Wed, 8 Nov 2006 19:45:33 +0100 [thread overview]
Message-ID: <200611081945.36688.rss@barracuda.es> (raw)
Hello all:
This is the first time I write to the list, and I appreciate the big help it
gives us users.
We're using an AT91RM9200 based board called Portux920T. We have now a quite
stable kernel and u-boot configuration which I attach. We manage to include a
dataflash inside the portux board and get it to work. At least almost, please
read on.
When doing big transfers in memory (10M), we have some kernel oopses(see
panic.log.zip attached). The oops comes up in the function __wake_up_common
in the file kernel/sched.c
The steps to reproduce this are the following:
1- Start the first bootloader (used the binary provided by atmel).
2- Make the first bootloader start u-boot(1.1.6).
3- U-boot downloads kernel(2.6.18) from _dataflash_ into RAM.
4- Rest of booting till shell prompt.
5- Execute for example: dd if=/dev/zero of=/root/borrar bs=1k count=10k
6- Oops!
If we substitute step 3 for U-boot downloads kernel from _parallel flash_
into RAM, the Oops won't happen.
The kernel has been patched with the latest maxim(2.6.18) patchset for the
AT91RM9200 microcontroller. The u-boot configuration is also attached
(portux920T.h).
We have also tried using different first stage bootloaders we could find.
Even we compile it ourselves using the RAM initialisation code taken from the
u-boot. We also have tested several toolchains, from emdebian to the one
provided by portux.
We have 64MB Ram and we have tried using 64MB 32bit wide and 32MB 16bit
wide. Flash and Dataflash are both 4MB.
We will much appreciated whatever info or test that could take out from this
works but... situation. Thank you very much.
Regards,
--
Ra?l S?nchez Siles
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-2.6.18.2.gz
Type: application/x-gzip
Size: 7586 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061108/b6633d0a/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: portux920T.h.gz
Type: application/x-gzip
Size: 3064 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061108/b6633d0a/attachment-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: panic.log.gz
Type: application/x-gzip
Size: 6518 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061108/b6633d0a/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061108/b6633d0a/attachment.pgp
next reply other threads:[~2006-11-08 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 18:45 Raúl Sánchez Siles [this message]
2006-11-09 7:02 ` [U-Boot-Users] AT91 Kernel oops when loading kernel from dataflash Ulf Samuelsson
2006-11-13 10:30 ` Raúl Sánchez Siles
2006-11-15 16:08 ` Raúl Sánchez Siles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611081945.36688.rss@barracuda.es \
--to=rss@barracuda.es \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox