All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm <kvm@vger.kernel.org>
Subject: Re: Frame buffer corruptions with KVM >= 2.6.36
Date: Thu, 14 Oct 2010 14:13:26 +0200	[thread overview]
Message-ID: <4CB6F3E6.9000407@siemens.com> (raw)
In-Reply-To: <4CB6F35F.1030504@redhat.com>

Am 14.10.2010 14:11, Avi Kivity wrote:
>  On 10/14/2010 02:04 PM, Avi Kivity wrote:
>>  On 10/14/2010 09:27 AM, Jan Kiszka wrote:
>>> Hi,
>>>
>>> I'm seeing quite frequent corruptions of the VESA frame buffer with
>>> Linux guests (vga=0x317) that are starting with KVM kernel modules of
>>> upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
>>> downgrading to kvm-kmod-2.6.35.6. Will see if I can bisect later, but
>>> maybe someone already has an idea or wants to reproduce (just run
>>> something like "find /" on one text console and witch to another one -
>>> text fragments will remain on the screen on every few switches).
>>>
>>
>> Reproduces on kvm.git.  I wonder what's going on.
>>
>> Looks like vesafb uses the bios to switch the display start, so I
>> expect a problem in qemu reacting to this.
>>
> 
> Hm, you said it is a kernel regression.  Maybe it's an issue with dirty
> bit tracking.
> 

Ah, cross-posting...

It need not be a kernel thing, see my other mail.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-10-14 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  7:27 Frame buffer corruptions with KVM >= 2.6.36 Jan Kiszka
2010-10-14 12:04 ` Avi Kivity
2010-10-14 12:11   ` Avi Kivity
2010-10-14 12:13     ` Jan Kiszka [this message]
2010-10-14 12:10 ` Jan Kiszka
2010-10-14 12:13   ` Avi Kivity
2010-10-14 12:31     ` Avi Kivity
2010-10-14 12:36     ` Jan Kiszka
2010-10-14 12:38       ` Avi Kivity
2010-10-15  6:41         ` Takuya Yoshikawa
2010-10-18 12:14           ` Takuya Yoshikawa
2010-10-18 12:17             ` Jan Kiszka

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=4CB6F3E6.9000407@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.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.