From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Sureshvs <sureshvs@datapatterns.co.in>
Cc: Srikanth <srikanth.ramarao@datapatterns.co.in>, xenomai@xenomai.org
Subject: Re: [Xenomai] Reg:Linux-3.10.32-xen-2.6.3 kernel panic
Date: Tue, 30 Dec 2014 14:08:32 +0100 [thread overview]
Message-ID: <20141230130832.GC1966@daedalus> (raw)
In-Reply-To: <C162583A9AFD46C5BE6BF944025F777B@itd206>
On Tue, Dec 30, 2014 at 04:34:59PM +0530, Sureshvs wrote:
> Hi
>
> Arch: powerpc 32bit
> Target Processor : 8641D
> Linux kernel: 3.10.32 with SMP
> Xenomai : 2.6.3
> Boot parameter root=/dev/nfs rw nfsroot=10.5.2.26:/opt/fc17fs_sband ip=10.5.2.20:10.5.2.26:10.5.18.4:255.255.255.0:VPX1234:eth0:off console=ttyS0,115200
>
>
> While testing 1553B Linux driver with SMP kernel option enabled we are getting oops message mentioned below.\
> We are not getting any problem in non-smp mode.
>
> We are using spin_lock_irqsave for updating the global status between ISR and task.
> While debugging we found that spin_lock_irqsave is giving problem.so kindly help us to solve the problem as soon as possible.
Your driver should probably be using the RTDM API and the spinlock
it provides:
https://xenomai.org/documentation/xenomai-2.6/html/api/group__rtdmsync.html#ga985473873f9e32af688fe8a23634693d
If you insist on using spin_lock_irqsave, you should note that
Linux spinlocks are obviously not safe to be called from real-time
domain, so, you should define the spinlock as ipipe_spinlock_t.
Also note that calling your kernel -xen- may be confusing, as xen is
something which exists, very distinct from xenomai.
--
Gilles.
prev parent reply other threads:[~2014-12-30 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 11:04 [Xenomai] Reg:Linux-3.10.32-xen-2.6.3 kernel panic Sureshvs
2014-12-30 13:08 ` Gilles Chanteperdrix [this message]
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=20141230130832.GC1966@daedalus \
--to=gilles.chanteperdrix@xenomai.org \
--cc=srikanth.ramarao@datapatterns.co.in \
--cc=sureshvs@datapatterns.co.in \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.