From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: carsteno@de.ibm.com, Mike Lampard <mike@secnet.net.au>,
kvm-devel@lists.sourceforge.net,
Aurelien Jarno <aurelien@aurel32.net>,
Linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] severe bug in 2.6.23+ kvm.git
Date: Fri, 19 Oct 2007 16:48:32 +0200 [thread overview]
Message-ID: <200710191648.32157.borntraeger@de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710191618450.1997@fbirervta.pbzchgretzou.qr>
Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
>
> On Oct 19 2007 15:44, Carsten Otte wrote:
> > Carsten Otte wrote:
> >> First thing we do, is figure whether or not 2.6.23.1 as released breaks our
> >> system too. This way, we can either focus on differences between Linus and
> >> Avi, or turn on the big red warning sign saying "regression".
> >
> > Looks like 2.6.23.1 works fine on that box. We'll leave it running over
> > the weekend with "while true; do make; make clean; done".
>
> Well, do you happen to use sata_mv?
no, we have nvidia, so its sata_nv.
next prev parent reply other threads:[~2007-10-19 14:49 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
2007-10-19 11:42 ` Laurent Vivier
2007-10-19 11:49 ` Carsten Otte
2007-10-19 11:53 ` Laurent Vivier
2007-10-19 11:58 ` Christian Borntraeger
2007-10-19 11:57 ` Mike Lampard
2007-10-19 12:21 ` Carsten Otte
2007-10-19 13:44 ` Carsten Otte
2007-10-19 14:18 ` Jan Engelhardt
2007-10-19 14:48 ` Christian Borntraeger [this message]
2007-10-19 14:57 ` Laurent Vivier
2007-10-19 15:23 ` Christian Borntraeger
2007-10-19 15:43 ` Luca Tettamanti
2007-10-19 18:49 ` Christian Borntraeger
2007-10-19 11:55 ` Carsten Otte
2007-10-19 15:13 ` [kvm-devel] " Avi Kivity
2007-10-22 10:57 ` Carsten Otte
2007-10-22 11:48 ` Avi Kivity
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=200710191648.32157.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--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