public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net, Greg KH <gregkh@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oliver@neukum.org>,
	Tino Keitel <tino.keitel@gmx.de>,
	linux-alpha@vger.kernel.org, Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Oliver Falk <oliver@linux-kernel.at>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [4/4] 2.6.23-rc3: known regressions v3
Date: Fri, 24 Aug 2007 12:30:22 -0700	[thread overview]
Message-ID: <46CF31CE.306@vmware.com> (raw)
In-Reply-To: <82e4877d0708241231j76474326ufdd19ec5448537b9@mail.gmail.com>

Parag Warudkar wrote:
> On 8/24/07, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>   
>
>> Virtualization
>>
>> Subject         : CONFIG_VMI broken
>> References      : http://lkml.org/lkml/2007/8/14/203
>> Last known good : ?
>> Submitter       : Parag Warudkar <parag.warudkar@gmail.com>
>> Caused-By       : ?
>> Handled-By      : Zachary Amsden <zach@vmware.com>
>> Status          : problem is being debugged
>>     
>
> Zach seemed to think that this is already fixed - I am not in a
> position to test it immediately so if we know what fixed this - can be
> closed. I'll report back once I get a chance to test latest git.
>   

Parag, thanks.  I reproduced this bug with your kernel config on 
2.6.23-rc3 and verified it does not happen on latest git.  I inspected 
memory after the crash and determined the problem was patching of 
instructions went awry.  Chris in the meantime fixed a bug with patching 
instructions, and the change from 100% apocalyptic failure to 100% 
unequivocal success has convinced me that was the same bug.

Zach

  reply	other threads:[~2007-08-24 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46CF0DEF.5040107@googlemail.com>
2007-08-24 17:38 ` [2/4] 2.6.23-rc3: known regressions v3 Michal Piotrowski
2007-08-24 17:38 ` [3/4] " Michal Piotrowski
2007-08-24 17:46   ` Stephen Hemminger
2007-08-28 23:05     ` Michal Piotrowski
2007-08-24 17:38 ` [4/4] " Michal Piotrowski
2007-08-24 17:56   ` Greg KH
2007-08-24 18:01     ` Tino Keitel
2007-08-24 18:08       ` Greg KH
2007-08-24 18:25         ` [linux-usb-devel] " David Brownell
2007-08-24 19:31   ` Parag Warudkar
2007-08-24 19:30     ` Zachary Amsden [this message]
2007-08-26  4:15   ` Satyam Sharma

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=46CF31CE.306@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=oliver@linux-kernel.at \
    --cc=oliver@neukum.org \
    --cc=parag.warudkar@gmail.com \
    --cc=rth@twiddle.net \
    --cc=stern@rowland.harvard.edu \
    --cc=tino.keitel@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox