[Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 5422 bytes --]

Hello All,
I am currently porting Adeos-ipipe on one of my MIPS architecture. I am
using I-Pipe 1.5-01, X86 as reference to my porting. So Far I did relevant
changes in
1.Interrupts handlers
2. System calls
3. Pagefault Handler
Except Exception handling, I mean critcial bug events.
With this changes I am able to Boot Linux kernel and also able to mount
Ramdisk successfully.

But the Issues is running user processes.
1. When it start executing user /sbin/Init Process I see few grep errors
which are given below, and these errors are not to be seen when IPIPE is
disabled.
2. I do get "#" Prompt on my console, but after few commands I see that
kernel hangs, and obvious it does not  take any input from serial console.
I also noticed that Ethernet interrupts getting disabled.


More Information of my Development Platform
Target board: MIPS Malta
Linux Kernel: 2.6.10
Timer: Up counter
PIC: i8259

Here is the LOG, I hope someone can help me.


Initial ramdisk at: 0x802c7000 (2379776 bytes)
Built 1 zonelists
Kernel command line: console=ttyS0,38400n8 rw
Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
Primary data cache 16kB, 4-way, linesize 16 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 512 (order: 9, 8192 bytes)
CPU frequency 10.00 MHz
Using 5.000 MHz high precision timer.
I-pipe 1.5-01: pipeline enabled.
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 59392k/60112k available (1519k kernel code, 632k reserved, 2632k
data, 152k init, 0k highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Checking for 'wait' instruction...  available.
spawn_desched_task(00000000)
desched cpu_callback 3/00000000
ksoftirqd started up.
desched cpu_callback 2/00000000
checking if image is initramfs...desched thread 0 started up.
it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 2324k freed
Linux NoNET1.0 for Linux 2.6
Can't analyze prologue code at 8027a018
Initializing Cryptographic API
rtc: SRM (post-2000) epoch (2000) detected
Real Time Clock Driver v1.12a
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
?ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:0a.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x2040-0x2047, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x2048-0x204f, BIOS settings: hdc:pio, hdd:pio
physmap flash device: 400000 at 1e000000
phys_mapped_flash: Found 2 x16 devices at 0x0 in 32-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
___caller_usermodelhelper: Path = /sbin/modprobe
RedBoot partition parsing not available
Using physmap partition definition
Creating 3 MTD partitions on "phys_mapped_flash":
0x00000000-0x00100000 : "YAMON"
0x00100000-0x003e0000 : "User FS"
0x003e0000-0x00400000 : "Board Config"
atkbd.c: keyboard reset failed on isa0060/serio1
atkbd.c: keyboard reset failed on isa0060/serio0
RAMDISK: Compressed image found at block 0
RAMDISK: incomplete write (-28 != 32768) 8388608
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing prom memory: 956kb freed
Freeing unused kernel memory: 1108k freed
Opening console
Opening console is successfull and executing /sbin/init
Algorithmics/MIPS FPU Emulator v1.5
INIT: version 2.85 booting
grep: error while loading shared libraries: libc.so.6: failed to map segment
from shared object: Error 4090
0
/etc/rc.d/rcS.d/S03mountvirtfs: 211: mkdir: Unknown error 4011
udev requires hotplug support, not started.
grep: error while loading shared libraries: libc.so.6: cannot map zero-fill
pages: Error 4090
mkdir: error while loading shared libraries: libcrypt.so.1: cannot open
shared object file: Error 4005
mkdir: error while loading shared libraries: libc.so.6: cannot stat shared
object: Error 4215
mount: error while loading shared libraries: /lib/libgcc_s.so.1: invalid ELF
header
none on /var/run type tmpfs (rw)
none on /tmp type tmpfs (rw)
/bin/sh: error while loading shared libraries: libcrypt.so.1: cannot open
shared object file: Error 4005
Kernel hotplug support not enabled.
INIT: Entering runlevel: 3
/bin/sh: error while loading shared libraries: libc.so.6: cannot map
zero-fill pages: Error 4090





INIT: error reading initrequest




(none) login: root






login[69]: root login  on `console'


# cd /
?
-------------------HANG-----------------------


Regards
Subbu

[-- Attachment #2: Type: text/html, Size: 12035 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Philippe Gerum]

On Tue, 2007-01-16 at 15:49 +0530, Subramani Venkatesh wrote:
> Hello All,
> I am currently porting Adeos-ipipe on one of my MIPS architecture. I
> am using I-Pipe 1.5-01, X86 as reference to my porting. So Far I did
> relevant changes in
> 1.Interrupts handlers
> 2. System calls
> 3. Pagefault Handler 
> Except Exception handling, I mean critcial bug events.
> With this changes I am able to Boot Linux kernel and also able to
> mount Ramdisk successfully.
> 

[...]

> Opening console is successfull and executing /sbin/init
> Algorithmics/MIPS FPU Emulator v1.5
> INIT: version 2.85 booting
> grep: error while loading shared libraries: libc.so.6: failed to map
> segment from shared object: Error 4090

There is likely something fishy in the syscall interception path from
arch/mips/kernel/entry.S; all the syscalls seem to return error values
mistakenly once the pipelining is in effect. You may want to check your
changes in this area.

Btw, it would be nice to work in an open manner and post your code on
this list if you want to ask for help about it here. Contribution has to
work both ways. TIA,

-- 
Philippe.

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

Hello Philipe,
Sorry I have to post it again, as I sent only to rpm@xenomai.org, I hope now
it reaches to all the adeos-main list.

Thank you very much for your response, I will look into the return values of
the of the syscall. I apologize for not working on open, as I am still in
the development, but definetly would like to share the code on Open source
by beginning of the feb, as I have been restricted.
I would like to all your support then and now to answer open source
questions that would arise, as well as to complete my port.


Regards
Subbu

On 1/16/07, Philippe Gerum <rpm@xenomai.org> wrote:
>
> On Tue, 2007-01-16 at 15:49 +0530, Subramani Venkatesh wrote:
> > Hello All,
> > I am currently porting Adeos-ipipe on one of my MIPS architecture. I
> > am using I-Pipe 1.5-01, X86 as reference to my porting. So Far I did
> > relevant changes in
> > 1.Interrupts handlers
> > 2. System calls
> > 3. Pagefault Handler
> > Except Exception handling, I mean critcial bug events.
> > With this changes I am able to Boot Linux kernel and also able to
> > mount Ramdisk successfully.
> >
>
> [...]
>
> > Opening console is successfull and executing /sbin/init
> > Algorithmics/MIPS FPU Emulator v1.5
> > INIT: version 2.85 booting
> > grep: error while loading shared libraries: libc.so.6: failed to map
> > segment from shared object: Error 4090
>
> There is likely something fishy in the syscall interception path from
> arch/mips/kernel/entry.S; all the syscalls seem to return error values
> mistakenly once the pipelining is in effect. You may want to check your
> changes in this area.
>
> Btw, it would be nice to work in an open manner and post your code on
> this list if you want to ask for help about it here. Contribution has to
> work both ways. TIA,
>
> --
> Philippe.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2220 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

Subramani Venkatesh wrote:
> ...
> More Information of my Development Platform
> Target board: MIPS Malta
> Linux Kernel: 2.6.10

Hmm, the Linux MIPS community around the Malta board seems to track the
mainline kernel quite closely. What constrained you to pick such an old
kernel as platform?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

Hello Jan,
Due to Linux distributer and support on Custom board Mips-malta I have to go
to this version of Linux. The customized linux helps my board to boot
successfully with Kernel Pre-emption and without Kernel pre-emption.
But I will be soon working on Open Source Linux too. As I don't see many
changes I am suppose to do.

Regards
Subbu

On 1/16/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>
> Subramani Venkatesh wrote:
> > ...
> > More Information of my Development Platform
> > Target board: MIPS Malta
> > Linux Kernel: 2.6.10
>
> Hmm, the Linux MIPS community around the Malta board seems to track the
> mainline kernel quite closely. What constrained you to pick such an old
> kernel as platform?
>
> Jan
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

BTW Jan, may I know how different is the IPIPE port on the Linux-2.6.10 and
the current IPIPE port on Linux-2.6.16 or Linux-2.6.18.

Subbu

On 1/16/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>
> Subramani Venkatesh wrote:
> > ...
> > More Information of my Development Platform
> > Target board: MIPS Malta
> > Linux Kernel: 2.6.10
>
> Hmm, the Linux MIPS community around the Malta board seems to track the
> mainline kernel quite closely. What constrained you to pick such an old
> kernel as platform?
>
> Jan
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 836 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

Subramani Venkatesh wrote:
> Hello Jan,
> Due to Linux distributer and support on Custom board Mips-malta I have
> to go
> to this version of Linux. The customized linux helps my board to boot
> successfully with Kernel Pre-emption and without Kernel pre-emption.
> But I will be soon working on Open Source Linux too. As I don't see many
> changes I am suppose to do.

I see (I was just curious). Once we have one stable version, upgrading
is "just" another milestone. :)

BTW, make sure that your contractor/employer officially permits you to
contribute code back that you developed for his project. More and more
companies understand how Open Source works, but some (specifically
larger ones) still have formalisms even for Open Source contributions in
place that may require additional steps first.

Looking forward to yet another I-pipe port,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

Subramani Venkatesh wrote:
> BTW Jan, may I know how different is the IPIPE port on the Linux-2.6.10 and
> the current IPIPE port on Linux-2.6.16 or Linux-2.6.18.

As you already picked a fairly new I-pipe core (1.5), the differences
will be around the kernel subsystems that changed meanwhile. Philippe
may better comment on details, still I guess no one here has tracked the
MIPS development to be aware of important changes there. Aspects to
check are specifically the timer and the IRQ subsystems. Both are under
heavy reconstruction recently, heading toward more generic
implementation which is a Good Thing also for I-pipe.

When you upgrade, going to head (then likely 2.6.20) is recommended to
avoid doing work twice - given that this kernel is stable in vanilla
form for you.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

You are right about the formalities, will let you know how it turns out.
Thank you very much for your response.

Cheers
Subbu



On 1/16/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>
> Subramani Venkatesh wrote:
> > Hello Jan,
> > Due to Linux distributer and support on Custom board Mips-malta I have
> > to go
> > to this version of Linux. The customized linux helps my board to boot
> > successfully with Kernel Pre-emption and without Kernel pre-emption.
> > But I will be soon working on Open Source Linux too. As I don't see many
> > changes I am suppose to do.
>
> I see (I was just curious). Once we have one stable version, upgrading
> is "just" another milestone. :)
>
> BTW, make sure that your contractor/employer officially permits you to
> contribute code back that you developed for his project. More and more
> companies understand how Open Source works, but some (specifically
> larger ones) still have formalisms even for Open Source contributions in
> place that may require additional steps first.
>
> Looking forward to yet another I-pipe port,
> Jan
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1439 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

Well Jan, with respect to PIC(i8259) I don't see many changes as compared to
code in Linux-2.6 on X86. But timer and whole Interrupt system changes. Will
look closely in it.  Have to put more effort on System calls as Phillipe
said, Will look into it and have to write test code with other customozed
domain like Registering with timer interrupt and try passing it to Linux
after handling it.

Subbu

On 1/16/07, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>
> Subramani Venkatesh wrote:
> > BTW Jan, may I know how different is the IPIPE port on the Linux-2.6.10and
> > the current IPIPE port on Linux-2.6.16 or Linux-2.6.18.
>
> As you already picked a fairly new I-pipe core (1.5), the differences
> will be around the kernel subsystems that changed meanwhile. Philippe
> may better comment on details, still I guess no one here has tracked the
> MIPS development to be aware of important changes there. Aspects to
> check are specifically the timer and the IRQ subsystems. Both are under
> heavy reconstruction recently, heading toward more generic
> implementation which is a Good Thing also for I-pipe.
>
> When you upgrade, going to head (then likely 2.6.20) is recommended to
> avoid doing work twice - given that this kernel is stable in vanilla
> form for you.
>
> Jan
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1611 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[somshekar kadam]

Hi Phillipe , 

  Thanks A lot for Helping on the MIPS Port for Adoes.

Thanks And Regards
Neelu

--- Philippe Gerum <rpm@xenomai.org> wrote:

> On Tue, 2007-01-16 at 15:49 +0530, Subramani
> Venkatesh wrote:
> > Hello All,
> > I am currently porting Adeos-ipipe on one of my
> MIPS architecture. I
> > am using I-Pipe 1.5-01, X86 as reference to my
> porting. So Far I did
> > relevant changes in
> > 1.Interrupts handlers
> > 2. System calls
> > 3. Pagefault Handler 
> > Except Exception handling, I mean critcial bug
> events.
> > With this changes I am able to Boot Linux kernel
> and also able to
> > mount Ramdisk successfully.
> > 
> 
> [...]
> 
> > Opening console is successfull and executing
> /sbin/init
> > Algorithmics/MIPS FPU Emulator v1.5
> > INIT: version 2.85 booting
> > grep: error while loading shared libraries:
> libc.so.6: failed to map
> > segment from shared object: Error 4090
> 
> There is likely something fishy in the syscall
> interception path from
> arch/mips/kernel/entry.S; all the syscalls seem to
> return error values
> mistakenly once the pipelining is in effect. You may
> want to check your
> changes in this area.
> 
> Btw, it would be nice to work in an open manner and
> post your code on
> this list if you want to ask for help about it here.
> Contribution has to
> work both ways. TIA,
> 
> -- 
> Philippe.
> 
> 
> 
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
> 



		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]

Hello Philippe,
I would like to thank you once again for the HINT.
Now I avoided changes to system call calling __ipipe_syscall_root from my
assembly code and tested the same, well it not giving any errors as sent you
yesterday, this concludes there is a problem in a way of calling
__ipipe_syscall_root, I guess my stack is getting corrupted, i will make
sure my stack is saved before calling __ipipe_syscall_root and resolve the
issues.
I thank you once again.

Cheers
Subbu

On 1/16/07, Philippe Gerum <rpm@xenomai.org> wrote:
>
> On Tue, 2007-01-16 at 15:49 +0530, Subramani Venkatesh wrote:
> > Hello All,
> > I am currently porting Adeos-ipipe on one of my MIPS architecture. I
> > am using I-Pipe 1.5-01, X86 as reference to my porting. So Far I did
> > relevant changes in
> > 1.Interrupts handlers
> > 2. System calls
> > 3. Pagefault Handler
> > Except Exception handling, I mean critcial bug events.
> > With this changes I am able to Boot Linux kernel and also able to
> > mount Ramdisk successfully.
> >
>
> [...]
>
> > Opening console is successfull and executing /sbin/init
> > Algorithmics/MIPS FPU Emulator v1.5
> > INIT: version 2.85 booting
> > grep: error while loading shared libraries: libc.so.6: failed to map
> > segment from shared object: Error 4090
>
> There is likely something fishy in the syscall interception path from
> arch/mips/kernel/entry.S; all the syscalls seem to return error values
> mistakenly once the pipelining is in effect. You may want to check your
> changes in this area.
>
> Btw, it would be nice to work in an open manner and post your code on
> this list if you want to ask for help about it here. Contribution has to
> work both ways. TIA,
>
> --
> Philippe.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2099 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Philippe Gerum]

On Wed, 2007-01-17 at 16:23 +0530, Subramani Venkatesh wrote:
> Hello Philippe,
> I would like to thank you once again for the HINT.
> Now I avoided changes to system call calling __ipipe_syscall_root from
> my assembly code and tested the same, well it not giving any errors as
> sent you yesterday, this concludes there is a problem in a way of
> calling __ipipe_syscall_root, I guess my stack is getting corrupted, i
> will make sure my stack is saved before calling __ipipe_syscall_root
> and resolve the issues. 

You should also check whether substituting inline code from asmmacro.h
like local_irq_enable/disable with the I-pipe stall/unstall calls had
any bad side-effect on the register set. Maybe t0 is not the only
register affected by such operations anymore.

> I thank you once again.
> 
> Cheers
> Subbu
> 
> On 1/16/07, Philippe Gerum <rpm@xenomai.org> wrote: 
>         On Tue, 2007-01-16 at 15:49 +0530, Subramani Venkatesh wrote:
>         > Hello All,
>         > I am currently porting Adeos-ipipe on one of my MIPS
>         architecture. I 
>         > am using I-Pipe 1.5-01, X86 as reference to my porting. So
>         Far I did
>         > relevant changes in
>         > 1.Interrupts handlers
>         > 2. System calls
>         > 3. Pagefault Handler
>         > Except Exception handling, I mean critcial bug events. 
>         > With this changes I am able to Boot Linux kernel and also
>         able to
>         > mount Ramdisk successfully.
>         >
>         
>         [...]
>         
>         > Opening console is successfull and executing /sbin/init
>         > Algorithmics/MIPS FPU Emulator v1.5
>         > INIT: version 2.85 booting
>         > grep: error while loading shared libraries: libc.so.6:
>         failed to map
>         > segment from shared object: Error 4090
>         
>         There is likely something fishy in the syscall interception
>         path from 
>         arch/mips/kernel/entry.S; all the syscalls seem to return
>         error values
>         mistakenly once the pipelining is in effect. You may want to
>         check your
>         changes in this area.
>         
>         Btw, it would be nice to work in an open manner and post your
>         code on 
>         this list if you want to ask for help about it here.
>         Contribution has to
>         work both ways. TIA,
>         
>         --
>         Philippe.
>         
>         
> 
-- 
Philippe.

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 3320 bytes --]

Phillipe,
I will surely look into this, so far local_irq_enable/disable i.e unstall
and stall routines did not cause  problem in my assembly code. But I was
facing this particular system call issue due to use of stack as arguments to
the __ipipe_syscall_root  and also in my case the venilla kernel is using
the same register for syscall number and return value, during this case when
Iam  trying to save intial system call number on stack and once
__ipipe_syscall_root is done I am reading it back, this may be corrupting
stack, so I think I need to put more effort to resolve this and oragnize it.
BTW  phillipe at this stage can I go testing timer interrupts using by other
domain, which registers as priority domain than linux ?

Regards
Subbu


On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
>
> On Wed, 2007-01-17 at 16:23 +0530, Subramani Venkatesh wrote:
> > Hello Philippe,
> > I would like to thank you once again for the HINT.
> > Now I avoided changes to system call calling __ipipe_syscall_root from
> > my assembly code and tested the same, well it not giving any errors as
> > sent you yesterday, this concludes there is a problem in a way of
> > calling __ipipe_syscall_root, I guess my stack is getting corrupted, i
> > will make sure my stack is saved before calling __ipipe_syscall_root
> > and resolve the issues.
>
> You should also check whether substituting inline code from asmmacro.h
> like local_irq_enable/disable with the I-pipe stall/unstall calls had
> any bad side-effect on the register set. Maybe t0 is not the only
> register affected by such operations anymore.
>
> > I thank you once again.
> >
> > Cheers
> > Subbu
> >
> > On 1/16/07, Philippe Gerum <rpm@xenomai.org> wrote:
> >         On Tue, 2007-01-16 at 15:49 +0530, Subramani Venkatesh wrote:
> >         > Hello All,
> >         > I am currently porting Adeos-ipipe on one of my MIPS
> >         architecture. I
> >         > am using I-Pipe 1.5-01, X86 as reference to my porting. So
> >         Far I did
> >         > relevant changes in
> >         > 1.Interrupts handlers
> >         > 2. System calls
> >         > 3. Pagefault Handler
> >         > Except Exception handling, I mean critcial bug events.
> >         > With this changes I am able to Boot Linux kernel and also
> >         able to
> >         > mount Ramdisk successfully.
> >         >
> >
> >         [...]
> >
> >         > Opening console is successfull and executing /sbin/init
> >         > Algorithmics/MIPS FPU Emulator v1.5
> >         > INIT: version 2.85 booting
> >         > grep: error while loading shared libraries: libc.so.6:
> >         failed to map
> >         > segment from shared object: Error 4090
> >
> >         There is likely something fishy in the syscall interception
> >         path from
> >         arch/mips/kernel/entry.S; all the syscalls seem to return
> >         error values
> >         mistakenly once the pipelining is in effect. You may want to
> >         check your
> >         changes in this area.
> >
> >         Btw, it would be nice to work in an open manner and post your
> >         code on
> >         this list if you want to ask for help about it here.
> >         Contribution has to
> >         work both ways. TIA,
> >
> >         --
> >         Philippe.
> >
> >
> >
> --
> Philippe.
>
>
>

[-- Attachment #2: Type: text/html, Size: 5418 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Philippe Gerum]

On Wed, 2007-01-17 at 20:30 +0530, Subramani Venkatesh wrote:
> Phillipe,
> I will surely look into this, so far local_irq_enable/disable i.e
> unstall and stall routines did not cause  problem in my assembly code.
> But I was facing this particular system call issue due to use of stack
> as arguments to the __ipipe_syscall_root  and also in my case the
> venilla kernel is using the same register for syscall number and
> return value, during this case when Iam  trying to save intial system
> call number on stack and once __ipipe_syscall_root is done I am
> reading it back, this may be corrupting stack, so I think I need to
> put more effort to resolve this and oragnize it. 
> BTW  phillipe at this stage can I go testing timer interrupts using by
> other domain, which registers as priority domain than linux ? 

If the interrupt exit path does not suffer from unexpected register
cloberring, yes.

> 
> Regards
> Subbu
> 
> 
> On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
>         On Wed, 2007-01-17 at 16:23 +0530, Subramani Venkatesh wrote:
>         > Hello Philippe,
>         > I would like to thank you once again for the HINT.
>         > Now I avoided changes to system call calling
>         __ipipe_syscall_root from 
>         > my assembly code and tested the same, well it not giving any
>         errors as
>         > sent you yesterday, this concludes there is a problem in a
>         way of
>         > calling __ipipe_syscall_root, I guess my stack is getting
>         corrupted, i 
>         > will make sure my stack is saved before calling
>         __ipipe_syscall_root
>         > and resolve the issues.
>         
>         You should also check whether substituting inline code from
>         asmmacro.h
>         like local_irq_enable/disable with the I-pipe stall/unstall
>         calls had 
>         any bad side-effect on the register set. Maybe t0 is not the
>         only
>         register affected by such operations anymore.
>         
>         > I thank you once again.
>         >
>         > Cheers
>         > Subbu
>         >
>         > On 1/16/07, Philippe Gerum < rpm@xenomai.org> wrote:
>         >         On Tue, 2007-01-16 at 15:49 +0530, Subramani
>         Venkatesh wrote:
>         >         > Hello All,
>         >         > I am currently porting Adeos-ipipe on one of my
>         MIPS 
>         >         architecture. I
>         >         > am using I-Pipe 1.5-01, X86 as reference to my
>         porting. So
>         >         Far I did
>         >         > relevant changes in
>         >         > 1.Interrupts handlers 
>         >         > 2. System calls
>         >         > 3. Pagefault Handler
>         >         > Except Exception handling, I mean critcial bug
>         events.
>         >         > With this changes I am able to Boot Linux kernel
>         and also 
>         >         able to
>         >         > mount Ramdisk successfully.
>         >         >
>         >
>         >         [...]
>         >
>         >         > Opening console is successfull and
>         executing /sbin/init
>         >         > Algorithmics/MIPS FPU Emulator v1.5
>         >         > INIT: version 2.85 booting
>         >         > grep: error while loading shared libraries:
>         libc.so.6:
>         >         failed to map
>         >         > segment from shared object: Error 4090
>         >
>         >         There is likely something fishy in the syscall
>         interception
>         >         path from
>         >         arch/mips/kernel/entry.S; all the syscalls seem to
>         return
>         >         error values
>         >         mistakenly once the pipelining is in effect. You may
>         want to 
>         >         check your
>         >         changes in this area.
>         >
>         >         Btw, it would be nice to work in an open manner and
>         post your
>         >         code on
>         >         this list if you want to ask for help about it
>         here. 
>         >         Contribution has to
>         >         work both ways. TIA,
>         >
>         >         --
>         >         Philippe.
>         >
>         >
>         >
>         --
>         Philippe.
>         
>         
> 
-- 
Philippe.

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 4867 bytes --]

Phillipe,
Can you tell me how exactly unexpected cloberring take place, what is effect
on timers and scheduler.
Also I would like to know during the course of returning from
__ipipe_handle_irq/__ipipe_grab_irq, if it is a root_domain and root domains
is stalled, what will be the effect of this on my scheduler or entire
system.

Regards
Subbu

On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
>
> On Wed, 2007-01-17 at 20:30 +0530, Subramani Venkatesh wrote:
> > Phillipe,
> > I will surely look into this, so far local_irq_enable/disable i.e
> > unstall and stall routines did not cause  problem in my assembly code.
> > But I was facing this particular system call issue due to use of stack
> > as arguments to the __ipipe_syscall_root  and also in my case the
> > venilla kernel is using the same register for syscall number and
> > return value, during this case when Iam  trying to save intial system
> > call number on stack and once __ipipe_syscall_root is done I am
> > reading it back, this may be corrupting stack, so I think I need to
> > put more effort to resolve this and oragnize it.
> > BTW  phillipe at this stage can I go testing timer interrupts using by
> > other domain, which registers as priority domain than linux ?
>
> If the interrupt exit path does not suffer from unexpected register
> cloberring, yes.
>
> >
> > Regards
> > Subbu
> >
> >
> > On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
> >         On Wed, 2007-01-17 at 16:23 +0530, Subramani Venkatesh wrote:
> >         > Hello Philippe,
> >         > I would like to thank you once again for the HINT.
> >         > Now I avoided changes to system call calling
> >         __ipipe_syscall_root from
> >         > my assembly code and tested the same, well it not giving any
> >         errors as
> >         > sent you yesterday, this concludes there is a problem in a
> >         way of
> >         > calling __ipipe_syscall_root, I guess my stack is getting
> >         corrupted, i
> >         > will make sure my stack is saved before calling
> >         __ipipe_syscall_root
> >         > and resolve the issues.
> >
> >         You should also check whether substituting inline code from
> >         asmmacro.h
> >         like local_irq_enable/disable with the I-pipe stall/unstall
> >         calls had
> >         any bad side-effect on the register set. Maybe t0 is not the
> >         only
> >         register affected by such operations anymore.
> >
> >         > I thank you once again.
> >         >
> >         > Cheers
> >         > Subbu
> >         >
> >         > On 1/16/07, Philippe Gerum < rpm@xenomai.org> wrote:
> >         >         On Tue, 2007-01-16 at 15:49 +0530, Subramani
> >         Venkatesh wrote:
> >         >         > Hello All,
> >         >         > I am currently porting Adeos-ipipe on one of my
> >         MIPS
> >         >         architecture. I
> >         >         > am using I-Pipe 1.5-01, X86 as reference to my
> >         porting. So
> >         >         Far I did
> >         >         > relevant changes in
> >         >         > 1.Interrupts handlers
> >         >         > 2. System calls
> >         >         > 3. Pagefault Handler
> >         >         > Except Exception handling, I mean critcial bug
> >         events.
> >         >         > With this changes I am able to Boot Linux kernel
> >         and also
> >         >         able to
> >         >         > mount Ramdisk successfully.
> >         >         >
> >         >
> >         >         [...]
> >         >
> >         >         > Opening console is successfull and
> >         executing /sbin/init
> >         >         > Algorithmics/MIPS FPU Emulator v1.5
> >         >         > INIT: version 2.85 booting
> >         >         > grep: error while loading shared libraries:
> >         libc.so.6:
> >         >         failed to map
> >         >         > segment from shared object: Error 4090
> >         >
> >         >         There is likely something fishy in the syscall
> >         interception
> >         >         path from
> >         >         arch/mips/kernel/entry.S; all the syscalls seem to
> >         return
> >         >         error values
> >         >         mistakenly once the pipelining is in effect. You may
> >         want to
> >         >         check your
> >         >         changes in this area.
> >         >
> >         >         Btw, it would be nice to work in an open manner and
> >         post your
> >         >         code on
> >         >         this list if you want to ask for help about it
> >         here.
> >         >         Contribution has to
> >         >         work both ways. TIA,
> >         >
> >         >         --
> >         >         Philippe.
> >         >
> >         >
> >         >
> >         --
> >         Philippe.
> >
> >
> >
> --
> Philippe.
>
>
>

[-- Attachment #2: Type: text/html, Size: 10805 bytes --]

Re: [Adeos-main] Porting IPIPE on MIPS Architecture, User Process running error, Kernel hangs.

[Subramani Venkatesh]

[-- Attachment #1: Type: text/plain, Size: 5643 bytes --]

Hello Phillipe,
I would like to thank you for your information on porting Adeos.
Now I registered my Custom domain, virtualizing Timer Interrupt with the
same resolution of Linux, during this time I made use of one of my 7
Segment display to make sure the interrupt handlers of TestDomain displays
Adeos, and I could achieve it too.

I have not tested __ipipe_tune_timer yet, I have one query about it,

Correct if I am wrong. So far my understandig is
1.  __ipipe_tune_timer, manged by the control domain to less resolution than
Linux is responsilbe to call __ipipe_propagate_irq to Linux at regular
interval of HZ.
2. During the course of tuning timer, the current tick count is saved in a
variable to make sure the get_timeoffset should not go wrong during the time
of getting date on Linux.

May I know if there is something more I should understand,also I could read
that in Xenomai, Aperiodic and Periodic Timer playing big role, so the
clarifications with you will help me to get out of few doubts and move on to
fine tuning of Adeos and also understanding in porting of xenomai and it
dependency.

Regards
Subbu

On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
>
> On Wed, 2007-01-17 at 20:30 +0530, Subramani Venkatesh wrote:
> > Phillipe,
> > I will surely look into this, so far local_irq_enable/disable i.e
> > unstall and stall routines did not cause  problem in my assembly code.
> > But I was facing this particular system call issue due to use of stack
> > as arguments to the __ipipe_syscall_root  and also in my case the
> > venilla kernel is using the same register for syscall number and
> > return value, during this case when Iam  trying to save intial system
> > call number on stack and once __ipipe_syscall_root is done I am
> > reading it back, this may be corrupting stack, so I think I need to
> > put more effort to resolve this and oragnize it.
> > BTW  phillipe at this stage can I go testing timer interrupts using by
> > other domain, which registers as priority domain than linux ?
>
> If the interrupt exit path does not suffer from unexpected register
> cloberring, yes.
>
> >
> > Regards
> > Subbu
> >
> >
> > On 1/17/07, Philippe Gerum <rpm@xenomai.org> wrote:
> >         On Wed, 2007-01-17 at 16:23 +0530, Subramani Venkatesh wrote:
> >         > Hello Philippe,
> >         > I would like to thank you once again for the HINT.
> >         > Now I avoided changes to system call calling
> >         __ipipe_syscall_root from
> >         > my assembly code and tested the same, well it not giving any
> >         errors as
> >         > sent you yesterday, this concludes there is a problem in a
> >         way of
> >         > calling __ipipe_syscall_root, I guess my stack is getting
> >         corrupted, i
> >         > will make sure my stack is saved before calling
> >         __ipipe_syscall_root
> >         > and resolve the issues.
> >
> >         You should also check whether substituting inline code from
> >         asmmacro.h
> >         like local_irq_enable/disable with the I-pipe stall/unstall
> >         calls had
> >         any bad side-effect on the register set. Maybe t0 is not the
> >         only
> >         register affected by such operations anymore.
> >
> >         > I thank you once again.
> >         >
> >         > Cheers
> >         > Subbu
> >         >
> >         > On 1/16/07, Philippe Gerum < rpm@xenomai.org> wrote:
> >         >         On Tue, 2007-01-16 at 15:49 +0530, Subramani
> >         Venkatesh wrote:
> >         >         > Hello All,
> >         >         > I am currently porting Adeos-ipipe on one of my
> >         MIPS
> >         >         architecture. I
> >         >         > am using I-Pipe 1.5-01, X86 as reference to my
> >         porting. So
> >         >         Far I did
> >         >         > relevant changes in
> >         >         > 1.Interrupts handlers
> >         >         > 2. System calls
> >         >         > 3. Pagefault Handler
> >         >         > Except Exception handling, I mean critcial bug
> >         events.
> >         >         > With this changes I am able to Boot Linux kernel
> >         and also
> >         >         able to
> >         >         > mount Ramdisk successfully.
> >         >         >
> >         >
> >         >         [...]
> >         >
> >         >         > Opening console is successfull and
> >         executing /sbin/init
> >         >         > Algorithmics/MIPS FPU Emulator v1.5
> >         >         > INIT: version 2.85 booting
> >         >         > grep: error while loading shared libraries:
> >         libc.so.6:
> >         >         failed to map
> >         >         > segment from shared object: Error 4090
> >         >
> >         >         There is likely something fishy in the syscall
> >         interception
> >         >         path from
> >         >         arch/mips/kernel/entry.S; all the syscalls seem to
> >         return
> >         >         error values
> >         >         mistakenly once the pipelining is in effect. You may
> >         want to
> >         >         check your
> >         >         changes in this area.
> >         >
> >         >         Btw, it would be nice to work in an open manner and
> >         post your
> >         >         code on
> >         >         this list if you want to ask for help about it
> >         here.
> >         >         Contribution has to
> >         >         work both ways. TIA,
> >         >
> >         >         --
> >         >         Philippe.
> >         >
> >         >
> >         >
> >         --
> >         Philippe.
> >
> >
> >
> --
> Philippe.
>
>
>

[-- Attachment #2: Type: text/html, Size: 11619 bytes --]