From: Vivek Goyal <vgoyal@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: commit 8c86e70acead629aacb4afcd818add66bf6844d9 hangs SPARC64 LDOMs
Date: Fri, 05 Sep 2014 16:23:01 +0000 [thread overview]
Message-ID: <20140905162301.GI6331@redhat.com> (raw)
In-Reply-To: <5409D2C3.6010806@oracle.com>
Hi David,
I put one more commit on top in -rc3 to fix UML crash.
commit 800df627e2eabaf4a921d342a1d5162c843b7fc2
Author: Vivek Goyal <vgoyal@redhat.com>
Date: Fri Aug 29 15:18:29 2014 -0700
resource: fix the case of null pointer access
Can you try applying this patch on top of net-next and see if helps
fix the issue.
If not, then it probably is a different issue. Is there anything on
the console? I will need to know some more information to figure out
what's wrong.
Thanks
Vivek
On Fri, Sep 05, 2014 at 11:12:03AM -0400, David L Stevens wrote:
>
> I was trying to rebase some patches to the latest net-next and I found that the LDOMs
> (Solaris virtual machines) hang on boot.
>
> git bisect narrowed to commit 8c86e70acead629aacb4afcd818add66bf6844d9 and reverting
> that makes it work again.
>
> commit 8c86e70acead629aacb4afcd818add66bf6844d9
> Author: Vivek Goyal <vgoyal@redhat.com>
> Date: Fri Aug 8 14:25:50 2014 -0700
>
> resource: provide new functions to walk through resources
>
> I have added two more functions to walk through resources.
>
> +-DLS
next prev parent reply other threads:[~2014-09-05 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 15:12 commit 8c86e70acead629aacb4afcd818add66bf6844d9 hangs SPARC64 LDOMs David L Stevens
2014-09-05 16:23 ` Vivek Goyal [this message]
2014-09-05 16:46 ` David L Stevens
2014-09-05 17:10 ` David L Stevens
2014-09-05 17:53 ` David Miller
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=20140905162301.GI6331@redhat.com \
--to=vgoyal@redhat.com \
--cc=sparclinux@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 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.