All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: lguest: unhandled trap 13 in current -rc
Date: Fri, 06 Mar 2009 12:17:21 +0100	[thread overview]
Message-ID: <49B10641.9070908@trash.net> (raw)
In-Reply-To: <200903061726.04101.rusty@rustcorp.com.au>

Rusty Russell wrote:
> On Thursday 05 March 2009 00:42:39 Patrick McHardy wrote:
>> Patrick McHardy wrote:
>>> When trying to run lguest in the current -rc, I get an "unhandled
>>> trap 13" and it stops. The address resolves to the rdmsr intruction
>>> in native_read_msr_safe(). -rc2 works fine, but I couldn't find
>>> any changes that looks related.
>>>
>>> .config is attached, more information available on request.
>> For the record, this is still broken in -rc7.
> 
> (Sorry, I missed the first mail to lkml).
> 
> Reproduced on one of my test machines (kvm doesn't show the problem here).
> 
> Subject: lguest: fix crash 'unhandled trap 13 at <native_read_msr_safe>'


Thanks Rusty, this fixed the problem for me.

There's a second problem, outgoing network performance using a routed
tap-interface is in the area of 20-30 kbit/second. I noticed this
previously (which is why I wanted to test the latest version), in
-rc2 what still worked was turning TSO/GSO etc. off, this seems to
be without effect in -rc7. I'll have a look at this myself tommorrow
unless someone beats me to it :)

      reply	other threads:[~2009-03-06 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  7:16 lguest: unhandled trap 13 in current -rc Patrick McHardy
2009-03-04 14:12 ` Patrick McHardy
2009-03-06  6:56   ` Rusty Russell
2009-03-06 11:17     ` Patrick McHardy [this message]

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=49B10641.9070908@trash.net \
    --to=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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.