From: Avi Kivity <avi@redhat.com>
To: nicolas prochazka <prochazka.nicolas@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [ kernel 3.5 ] Kernel bug when using kvm
Date: Mon, 16 Jul 2012 17:40:53 +0300 [thread overview]
Message-ID: <500427F5.80709@redhat.com> (raw)
In-Reply-To: <CADdae-jrhsuRvG-+rTWGActWtaLiQUzzothdcfq3hHp5OOKYUQ@mail.gmail.com>
On 07/16/2012 05:37 PM, nicolas prochazka wrote:
> No, It is not 100% reproductible, I'm trying to find the case, but :
> Now when i start a qemu-kvm ,
> there is a kvm-pit/xxxx which takes a lot of cpu time ( ~ 20 %) , (
> not with kernel 3.3.8 )
>
> for the complete stack trace, which kernel options should i set,
> i've already kernel debug .
Should be following the BUG message. Is what you posted everything you got?
>
> Regards,
> Nicolas Prochazka.
>
> 2012/7/16 Avi Kivity <avi@redhat.com>:
>> On 07/16/2012 02:06 PM, nicolas prochazka wrote:
>>> Hello,
>>> with linux kernel 3.5rc6 and 3.5rc7
>>> I do not test with other kernel 3.5.
>>> On linux kernel 3.3.8 , threre is no problem.
>>>
>>> If I start qemu-kvm process, system is overload and
>>> dmesg :
>>>
>>> BUG: unable to handle kernel paging request at 000000010000003b
>>> IP: [<ffffffff8119f694>] tid_fd_revalidate+0x84/0x1a0
>>> PGD 66989a067 PUD 0
>>> Oops: 0000 [#1] SMP
>>> CPU 3
>>> Modules linked in: [last unloaded: kvm]
>>
>> Is this repeatable?
>>
>> Please post a complete stack trace.
>>
>>
>>
>>
>> --
>> error compiling committee.c: too many arguments to function
>>
>>
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-16 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 11:06 [ kernel 3.5 ] Kernel bug when using kvm nicolas prochazka
2012-07-16 11:25 ` Avi Kivity
2012-07-16 14:37 ` nicolas prochazka
2012-07-16 14:40 ` Avi Kivity [this message]
2012-07-16 14:46 ` nicolas prochazka
2012-07-16 14:56 ` Oops in proc_fd_instantiate (was: Re: [ kernel 3.5 ] Kernel bug when using kvm) Avi Kivity
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=500427F5.80709@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=prochazka.nicolas@gmail.com \
/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