From: Ben Hutchings <bhutchings@solarflare.com>
To: satpal parmar <systems.satpal@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: PTP + H/W time stamping + CONFIG_PREEMPT_RT_FULL == Oops in slab
Date: Thu, 21 Jun 2012 17:58:02 +0100 [thread overview]
Message-ID: <1340297882.2736.14.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <CAGgcXb662=PbdJaMff1QfBhW06mYXgNvM1o6snunZMe=Q36Q7A@mail.gmail.com>
On Thu, 2012-06-21 at 20:09 +0530, satpal parmar wrote:
> Hi All!
>
> Recently I successfully integrated a certain
> (http://sourceforge.net/scm/?type=svn&group_id=503885) open source
> implementation of PTP protocol with Linux 3.0.1 running on ARM based
> SoC. Since Phy (Phyter DP 83640) on board supported H/W time
> stamping support I am using for that for the same. Integration worked
> smoothly until I applied RT patch and enabled full preemption
> (CONFIG_PREEMPT_RT_FULL).
[...]
> kernel BUG at /home/satpal/sandbox/console_p/trunk/bts/source/vendor/linux/mm/slab.c:3205!
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> pgd = e9e08000
> [00000000] *pgd=ae31c831, *pte=00000000, *ppte=00000000
> Internal error: Oops: 817 [#1] PREEMPT
> Modules linked in:
> CPU: 0 Not tainted (3.0.1-rt11-svn7595 #29)
[...]
I suggest you re-test with 3.0.35-rt56; there have been many bug fixes.
Also might this 'vendor' kernel include its own changes to mm, net, etc.
that are not in mainline?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-06-21 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 14:39 PTP + H/W time stamping + CONFIG_PREEMPT_RT_FULL == Oops in slab satpal parmar
2012-06-21 16:58 ` Ben Hutchings [this message]
2012-06-21 19:54 ` Richard Cochran
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=1340297882.2736.14.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=systems.satpal@gmail.com \
/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