From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Sharma, Karun" <karun.sharma@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: 3.17 kernel crash while loading IPoIB
Date: Tue, 23 Sep 2014 02:05:38 -0700 [thread overview]
Message-ID: <1411463138.26859.168.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <637AD4DF2E595346BAB0DF8C46F3A2B003291F06@BGSMSX101.gar.corp.intel.com>
On Tue, 2014-09-23 at 05:15 +0000, Sharma, Karun wrote:
> Hello:
>
> I am facing an issue wherein kernel 3.17 crashes while loading IPoIB
> module. I guess the issue discussed in this thread
> (https://www.mail-archive.com/linux-rdma@vger.kernel.org/msg20963.html) is similar.
>
> We were able to reproduce the issue with RC6 also. Here are the steps
> I followed:
>
> I compiled and installed 3.17 kernel on top of RHEL 6.5.
> Then I changed rdma.conf to not load IPoIB (If I don't do this, the
> kernel crashes while booting and starting RDMA service.)
> After the server comes up, I just did "modprobe ib_ipoib" and kernel
> crashes.
> Please see below the kernel back trace.
>
> Seeing the announcement, it looks like RC6 will be the last RC for
> 3.17 kernel. Will the release happen with this issue? Is there any
> workaround available for this issue?
> I am not sure what mechanism/process is used to report issue to kernel
> community.
>
> Regards
> Karun
This seems fixed now :
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=257117862634d89de33fec74858b1a0ba5ab444b
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b49fe36208b45f76dfbcfcd3afd952a33fa9f5ce
next prev parent reply other threads:[~2014-09-23 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 5:15 Sharma, Karun
2014-09-23 9:05 ` Eric Dumazet [this message]
2014-09-23 11:11 ` Sharma, Karun
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=1411463138.26859.168.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=karun.sharma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®