linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: Pradyumna Sampath <pradysam@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-rt-users@vger.kernel.org
Subject: Re: Kernel module crashed in 2.6.33.7-rt30
Date: Thu, 27 Jan 2011 14:08:35 +0530	[thread overview]
Message-ID: <AANLkTikceiY2yZHBkHbuhUs+mvRhAfHY2hMLmaXMmy=u@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinW4koreUTXS_ieXb9wGVUKhebTgLvkfEMP4O6y@mail.gmail.com>

Hi,

I was using a older version of RT patch. After going through the
thread that you mentioned I moved to the latest one. But still the
crash happens for me.
Also I don't have iptables running in my system.
And another thing is that, my kernel module always stops when it is
trying to acquire a spinlock (spin_lock_irqsave) which is shared with
code in the ISR. Is there any way to see the information about the
lock, like who is holding the lock??

Does this give some insight into my actual problem?

Thanks
Vikram


2011/1/27 Pradyumna Sampath <pradysam@gmail.com>
>
> Hi,
>
> 2011/1/27 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> > [readded linux-rt-users to recipients]
> >
> > Hello,
> >
> > On Thu, Jan 27, 2011 at 01:23:47PM +0530, Vikram Narayanan wrote:
> >> I have checked my config. DEBUG_BUGVERBOSE is already enabled. Any other
> >> ideas on how to debug this?
> >> Can you give an overview of why this happens?
> > sorry, I don't have much clue about x86.
> <snip ...>
>
> Im remember that at sometime there was a similar thread on LKML
> regarding a bug with RT together with nf/iptables. But I presume that
> was fixed.
>
> You could lkml archives for that thread or try disabling iptables.
>
> best regards
> /prady
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-01-27  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  7:39 Kernel module crashed in 2.6.33.7-rt30 Vikram
2011-01-25 16:21 ` Uwe Kleine-König
     [not found]   ` <AANLkTikQW6mkV_a6umKY0NnoinD-UnJQK4Gm+kxuKfCa@mail.gmail.com>
2011-01-27  7:59     ` Uwe Kleine-König
2011-01-27  8:05       ` Pradyumna Sampath
2011-01-27  8:38         ` Vikram Narayanan [this message]
2011-01-27  9:20           ` Uwe Kleine-König
     [not found]             ` <AANLkTimYnhQ_4+=PJogMts65iLsoNcE60NTdnfDwVtJx@mail.gmail.com>
2011-01-28  7:57               ` [solved] " Uwe Kleine-König
2011-01-28 17:07                 ` Madovsky

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='AANLkTikceiY2yZHBkHbuhUs+mvRhAfHY2hMLmaXMmy=u@mail.gmail.com' \
    --to=vikram186@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pradysam@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).