From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
carsteno@de.ibm.com, Mike Lampard <mike@secnet.net.au>,
Linux-kernel@vger.kernel.org,
Aurelien Jarno <aurelien@aurel32.net>,
kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] severe bug in 2.6.23+ kvm.git
Date: Fri, 19 Oct 2007 17:23:48 +0200 [thread overview]
Message-ID: <200710191723.48104.borntraeger@de.ibm.com> (raw)
In-Reply-To: <4718C5E0.9000204@bull.net>
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
> linux-2.6.23.1.tar.bz2 ?
>
> 2.6.23.1 corrects nothing except sata_mv...
Yes I know. The question we tried to answer was: is the bug in 2.6.23 or was
it introduced after 2.6.23, as kvm.git already contains lots of post 2. 6.23
stuff.
Current state is:
kvm.git with tag 2.6.23-rc6 works for days without a problem.
2.6.23.1 vanilla has survived and is currently still under test.
kvm.git tag master killed our filesystem at least three times.since monday.
I will continue to bang on 2.6.23.1 to see if its really fine. After that,
maybe I will try to bisect on kvm.git, but this will take quite a long time,
given that we had to reinstall the system due to this error.
Christian
next prev parent reply other threads:[~2007-10-19 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 11:22 severe bug in 2.6.23+ kvm.git Carsten Otte
2007-10-19 11:31 ` [kvm-devel] " Aurelien Jarno
2007-10-19 11:37 ` Carsten Otte
[not found] ` <47189706.1040809-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 11:42 ` Laurent Vivier
[not found] ` <4718982D.4020500-6ktuUTfB/bM@public.gmane.org>
2007-10-19 11:49 ` Carsten Otte
[not found] ` <471899CA.8060206-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 11:53 ` Laurent Vivier
[not found] ` <47189AD3.8010301-6ktuUTfB/bM@public.gmane.org>
2007-10-19 11:58 ` Christian Borntraeger
2007-10-19 11:57 ` Mike Lampard
[not found] ` <200710192127.17584.mike-pBbpZId3k0Zx3z9c7Zyw2w@public.gmane.org>
2007-10-19 12:21 ` Carsten Otte
[not found] ` <4718A14B.4060008-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 13:44 ` Carsten Otte
[not found] ` <4718B4DB.1000202-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 14:18 ` Jan Engelhardt
[not found] ` <Pine.LNX.4.64.0710191618450.1997-vVwEwcwQeYFPkBl3ERsXe1l1cybopEuJUBSOeVevoDU@public.gmane.org>
2007-10-19 14:48 ` Christian Borntraeger
2007-10-19 14:57 ` [kvm-devel] " Laurent Vivier
2007-10-19 15:23 ` Christian Borntraeger [this message]
[not found] ` <200710191723.48104.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 15:43 ` Luca Tettamanti
2007-10-19 18:49 ` [kvm-devel] " Christian Borntraeger
[not found] ` <47189371.7080104-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-19 11:55 ` Carsten Otte
2007-10-19 15:13 ` [kvm-devel] " Avi Kivity
[not found] ` <4718C9A1.3010703-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 10:57 ` Carsten Otte
2007-10-22 11:48 ` [kvm-devel] " Avi Kivity
[not found] ` <471C8E28.9020707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 13:14 ` Carsten Otte
2007-10-22 14:00 ` Carsten Otte
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=200710191723.48104.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=Laurent.Vivier@bull.net \
--cc=Linux-kernel@vger.kernel.org \
--cc=aurelien@aurel32.net \
--cc=carsteno@de.ibm.com \
--cc=jengelh@computergmbh.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mike@secnet.net.au \
/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