From: Arvid Brodin <arvid.brodin@alten.se>
To: Gokul C G <gokul.g@kalkitech.in>, <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>
Subject: Re: net/hsr: not working : High-availability Seamless Redundancy (HSRv0)
Date: Tue, 10 Jun 2014 17:37:37 +0200 [thread overview]
Message-ID: <53972641.2070205@alten.se> (raw)
In-Reply-To: <5396FD42.1070100@kalkitech.in>
On 2014-06-10 14:42, Gokul C G wrote:
> Hi,
>
> I am trying to incorporate the changes made for High-availability
> Seamless Redundancy (HSRv0) in linux 3.13 into one of the older
> version Linux 3.0.48 . I had made changes as per patch in 3.0.48
> kernel and modified use of NETLINK_CB(skb_in).portid to
> NETLINK_CB(skb_in).pid and info->snd_portid to info->snd_pid since
> the variable are renamed recently for better readability , added new
> list related macro(like list_for_each_entry_rcu) to old kernel .
>
> I am doing this for a Big-endian system with powerpc architecture
> with real-time functionality enabled . The kernel occurred while
> probing hsr/prp driver and following console information available.
> I had tried to compile HSRv0 driver with kernel and also as kernel
> module , in both cases following crash message found on console.
>
This is of course impossible for anyone else but yourself to debug,
since noone else has access to the exact code you are using.
If you are able to recreate the bug on a current, vanilla kernel,
someone might be able to help.
--
Arvid Brodin | Consultant (Linux)
ALTEN | Knarrarnäsgatan 7 | SE-164 40 Kista | Sweden
arvid.brodin@alten.se | www.alten.se/en/
next parent reply other threads:[~2014-06-10 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5396FD42.1070100@kalkitech.in>
2014-06-10 15:37 ` Arvid Brodin [this message]
[not found] ` <539EC21B.30500@kalkitech.in>
2014-06-18 15:36 ` net/hsr: not working : High-availability Seamless Redundancy (HSRv0) Arvid Brodin
[not found] ` <539EE434.7050901@kalkitech.in>
2014-06-18 16:00 ` Arvid Brodin
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=53972641.2070205@alten.se \
--to=arvid.brodin@alten.se \
--cc=davem@davemloft.net \
--cc=gokul.g@kalkitech.in \
--cc=netdev@vger.kernel.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 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).