archive mirror
 help / color / mirror / Atom feed
From: Elek Robert <>
Subject: A little offtopic: uClinux on i960
Date: Thu, 26 Sep 2002 11:53:03 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)


I know it's a little offtopic, but i think that the problem is based on
some structural details of linux kernel, so i hope someone will have any


I have a strange problem. I'm using a special own-designed hardware with
i960CF cpu, and with uClinux 2.0.35 i960 port.

previously i've changed some mail with a guy working with an i960 port,
but unfortunately i've lost his email address due to a HD crash.
If you are reading this, please answer :)

So my questions (the description of my scenario) :

the kernel seems to boot up properly, with scsi initialization (reads the
partition table well) and initrd mounting.

the problem begins with the execve syscall. in the original entry.S at
the syscall there was no flushreg, so i placed on there, to save the
register contents to memory, but it did not help..

so loading the flat binary is ok, i've dumped the memory and it seems good.
calling start_thread fills the pfp of the calling thread to a newly created
stack frame, and it seems ok too, according to the dump.

but cpu does not start to execute the code at the new IP, even if the IP is
in bios, so the code can't be altered. The curiosity is that it sometimes
works - and i don't know why. My idea is that it has something to do with
interrupt stack / supervisor stack - but i'm not sure.
But when it does not execute the code at the new IP, the CPU hangs, it does
not accept IRQ requests, nothing.

previously i had a strange error (now fixed) that bdflush hanged randomly,
depending on if the size of the gzipped kernel was odd or even (!)
i inserted a code to clear the contents of the whole memory to 0, and
now it works stable. strange for me.

Any ideas for solving the 'syscall problem' are welcome, also anything
about to previous error mentioned above could be good for me, as it
could help me understanding the cause of my problem.

Thanks in advance..


                 reply	other threads:[~2002-09-26  9:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: A little offtopic: uClinux on i960' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).