linux-um archives
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Darren Hart <dvhart@linux.intel.com>,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: kernel 2.6.39 (user mode linux) crashes (2.6.38 works fine)
Date: Fri, 20 May 2011 19:10:12 +0200	[thread overview]
Message-ID: <201105201910.13095.toralf.foerster@gmx.de> (raw)
In-Reply-To: <1305907896.1465.27.camel@gandalf.stny.rr.com>


Steven Rostedt wrote at 18:11:36
> > Wait! This is where we need the WARN_ON_SMP(), do we have that patch in?
> > 
> > I think UML is UP, and that spin_is_locked() will always return false.
> 
> Could you apply these patches:
> 
> 2092e6be WARN_ON_SMP(): Allow use in if() statements on UP
> 29096202 futex: Fix WARN_ON() test for UP
> 
> On top of this commit, and see if the problem goes away. What could have
> happened, is that you have two bugs, with one of them fixed. If the git
> bisect stumbled on this bug, it will show this one, even though later
> on, this code was fixed. If you apply the above two patches and it works
> again, then this isn't the bug you are looking for.
> 
> -- Steve
Right - applying those 2 commits on top of v2.6.38-rc8-1-g2e12978 works - now 
the issue is away.

And yes - now I've to look for the other of two bugs, which was introduced 
between the tags v2.6.38 and v2.6.39, I think.

Is there's an easy way to check, whether a given checked out git tree contains 
a specific commit id ?

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2011-05-20 17:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201105191526.31904.toralf.foerster@gmx.de>
2011-05-19 17:00 ` kernel 2.6.39 (user mode linux) crashes (2.6.38 works fine) richard -rw- weinberger
2011-05-19 17:20   ` Toralf Förster
2011-05-19 17:25     ` richard -rw- weinberger
2011-05-19 20:18   ` Toralf Förster
2011-05-19 20:43     ` Steven Rostedt
2011-05-20  7:37       ` Toralf Förster
2011-05-20  7:56         ` richard -rw- weinberger
2011-05-20  8:39           ` richard -rw- weinberger
2011-05-20  8:58             ` Toralf Förster
2011-05-20  9:02               ` richard -rw- weinberger
2011-05-20  9:19                 ` Toralf Förster
2011-05-20  8:42           ` Toralf Förster
2011-05-20 16:24             ` richard -rw- weinberger
2011-05-20 17:19               ` Steven Rostedt
2011-05-20 15:55           ` Darren Hart
2011-05-20 16:04             ` Steven Rostedt
2011-05-20 16:11               ` Steven Rostedt
2011-05-20 17:10                 ` Toralf Förster [this message]
2011-05-20 17:44                   ` Steven Rostedt
2011-05-20 17:46                   ` Steven Rostedt
2011-05-20 22:53                 ` Toralf Förster
2011-05-21  8:53                   ` Toralf Förster
2011-05-23 19:17                     ` richard -rw- weinberger
2011-05-23 19:48                       ` Toralf Förster
2011-05-21 10:12                   ` richard -rw- weinberger
2011-05-21 22:37                     ` Peter Zijlstra
2011-05-21 23:06                       ` richard -rw- weinberger
2011-05-20 17:35               ` Darren Hart
2011-05-20 17:41                 ` Steven Rostedt
     [not found] ` <201105191834.56577.toralf.foerster@gmx.de>
2011-05-20  6:44   ` richard -rw- weinberger
2011-05-20  7:43     ` Toralf Förster

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=201105201910.13095.toralf.foerster@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=dvhart@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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