Configuring shared memory

2001-05-11 Thread Sriram V

Hi,

Can somebody please tell me how to configure the amount of shared memory 
that a 2.2.x kernel allocates? Kindly copy to my e-mail address 
([EMAIL PROTECTED]).

Thanks,
Sriram
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



cpu freq framework tests

2013-10-30 Thread Sriram V
Hi,

I would like to test cpu freq framework including the ondemand governor
on my new platform.

are there any automated tools available for this on a busybox filesystem.


-- 
Regards,
Sriram
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


mutex ownership tracking

2014-01-20 Thread Sriram V
Hello,

What is the importance of ownership tracking of mutex? Why is it
mandatory that the task which
locked must unlock it to escape lockdep.


-- 
Regards,
Sriram
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Question on debugging Alignment trap

2017-08-24 Thread Sriram V
Hi,

I am debugging a random alignment trap in a 3.12 Kernel.
I am not sure what could cause the alighment trap. Has anyone seen
this issue before


[147278.696759] Alignment trap: not handling instruction e1901f9f at
[]
[147278.714884] Unhandled fault: alignment exception (0x001) at 0xff7f
[147278.725921] Internal error: : 1 [#1] PREEMPT SMP ARM
[147278.731321] Modules linked in: omaplfb(O) pvrsrvkm(O)
pruss_remoteproc remoteproc virtio virtio_ring
[147278.741197] CPU: 0 PID: 21706 Comm: zygote Tainted: G   O
3.12.20+ #1
[147278.748893] task: ea86ebc0 ti: ec6cc000 task.ti: ec6cc000
[147278.754749] PC is at __destroy_inode+0xfc/0x14c
[147278.759676] LR is at _raw_spin_unlock+0x30/0x50
[147278.764596] pc : []lr : []psr: a00f0013
[147278.764596] sp : ec6cdd40  ip : ec6cdcf0  fp : ec6cdd54
[147278.777007] r10: dc0e77e0  r9 : e13b0c90  r8 : dc0e7778
[147278.782663] r7 : c06ed8f4  r6 : c06ed8f4  r5 : ece67b80  r4 : ece67b28
[147278.789705] r3 :   r2 : ec6cdcf0  r1 :   r0 : ff7f
[147278.796750] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM
Segment user


Disassembly of the vmlinux shows that it might come from inside atomic.h

c010ad08 <__destroy_inode+0xf0> e3a03000mov r3, #0
c010ad0c <__destroy_inode+0xf4> ee073fbamcr 15, 0, r3,
cr7, cr10, {5}
/home/build/kernel/arch/arm/include/asm/atomic.h:100

__asm__ __volatile__("@ atomic_sub_return\n"
c010ad10 <__destroy_inode+0xf8> e1901f9fldrex   r1, [r0]
c010ad14 <__destroy_inode+0xfc> e2411001sub r1, r1, #1
c010ad18 <__destroy_inode+0x100> e1802f91   strex   r2, r1, [r0]
c010ad1c <__destroy_inode+0x104> e332   teq r2, #0
c010ad20 <__destroy_inode+0x108> 1afa   bne c010ad10
<__destroy_inode+0xf8>
/home/build/kernel/arch/arm/include/asm/atomic.h:110
"   bne 1b"
: "=&r" (result), "=&r" (tmp), "+Qo" (v->counter)
: "r" (&v->counter), "Ir" (i)
: "cc");

smp_mb();
c010ad24 <__destroy_inode+0x10c> ee073fba   mcr 15, 0, r3,
cr7, cr10, {5}
posix_acl_release():


Not sure what the issue here is. I would need some help in
understanding what the problem.


Thanks for your help.

Regards,
Sriram


Re: Question on debugging Alignment trap

2017-08-25 Thread Sriram V
 2b72a04c9c22f45a ]---
[147279.245817] Kernel panic - not syncing: Fatal exception

On Fri, Aug 25, 2017 at 1:14 AM, Sriram V  wrote:
> Hi,
>
> I am debugging a random alignment trap in a 3.12 Kernel.
> I am not sure what could cause the alighment trap. Has anyone seen
> this issue before
>
>
> [147278.696759] Alignment trap: not handling instruction e1901f9f at
> []
> [147278.714884] Unhandled fault: alignment exception (0x001) at 0xff7f
> [147278.725921] Internal error: : 1 [#1] PREEMPT SMP ARM
> [147278.731321] Modules linked in: omaplfb(O) pvrsrvkm(O)
> pruss_remoteproc remoteproc virtio virtio_ring
> [147278.741197] CPU: 0 PID: 21706 Comm: zygote Tainted: G   O
> 3.12.20+ #1
> [147278.748893] task: ea86ebc0 ti: ec6cc000 task.ti: ec6cc000
> [147278.754749] PC is at __destroy_inode+0xfc/0x14c
> [147278.759676] LR is at _raw_spin_unlock+0x30/0x50
> [147278.764596] pc : []lr : []psr: a00f0013
> [147278.764596] sp : ec6cdd40  ip : ec6cdcf0  fp : ec6cdd54
> [147278.777007] r10: dc0e77e0  r9 : e13b0c90  r8 : dc0e7778
> [147278.782663] r7 : c06ed8f4  r6 : c06ed8f4  r5 : ece67b80  r4 : ece67b28
> [147278.789705] r3 :   r2 : ec6cdcf0  r1 :   r0 : ff7f
> [147278.796750] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM
> Segment user
>
>
> Disassembly of the vmlinux shows that it might come from inside atomic.h
>
> c010ad08 <__destroy_inode+0xf0> e3a03000mov r3, #0
> c010ad0c <__destroy_inode+0xf4> ee073fbamcr 15, 0, r3,
> cr7, cr10, {5}
> /home/build/kernel/arch/arm/include/asm/atomic.h:100
>
> __asm__ __volatile__("@ atomic_sub_return\n"
> c010ad10 <__destroy_inode+0xf8> e1901f9fldrex   r1, [r0]
> c010ad14 <__destroy_inode+0xfc> e2411001sub r1, r1, #1
> c010ad18 <__destroy_inode+0x100> e1802f91   strex   r2, r1, [r0]
> c010ad1c <__destroy_inode+0x104> e332   teq r2, #0
> c010ad20 <__destroy_inode+0x108> 1afa   bne c010ad10
> <__destroy_inode+0xf8>
> /home/build/kernel/arch/arm/include/asm/atomic.h:110
> "   bne 1b"
> : "=&r" (result), "=&r" (tmp), "+Qo" (v->counter)
> : "r" (&v->counter), "Ir" (i)
> : "cc");
>
> smp_mb();
> c010ad24 <__destroy_inode+0x10c> ee073fba   mcr 15, 0, r3,
> cr7, cr10, {5}
> posix_acl_release():
>
>
> Not sure what the issue here is. I would need some help in
> understanding what the problem.
>
>
> Thanks for your help.
>
> Regards,
> Sriram


Kernel Panic sysrq questions

2017-08-18 Thread Sriram V
Hi,

1. I am testing my watchdog driver. The driver uses the internal
watchdog (Internal to SOC).
2. I use a single core SOC.
3. I have a workqueue which pets the watchdog every 60 seconds.
4. I trigger a kernel crash by doing a echo c > /proc/sysrq-trigger to
trigger  a kernel crash
5. Even after the crash, I observe that the workqueue gets
periodically executed. (I have a printk
inside the workqueue before the pet as a result the watchdog does
not reset the board.

My Understanding is When a fatal panic happens, The Kernel is in
frozen state (no workques
or tasks get executed).

Is my understanding correct or am i missing something here.


Thanks,

Regards,
Sriram