All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Luis Henriques <henrix@sapo.pt>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348
Date: Sun, 30 Nov 2008 22:20:45 +0200	[thread overview]
Message-ID: <4932F59D.2060002@redhat.com> (raw)
In-Reply-To: <20081130193401.GA7690@hades>

Luis Henriques wrote:
> Hi,
>
> Maybe this is duplicated bug report, but since I was not able to find any
> reference to it, I am reporting it anyway.
>
> I am running 2.6.28-rc6-00007-ged31348 on x86_64.
>
> I just tried to start kvm and got the following:
>
> [  883.483978] ------------[ cut here ]------------
> [  883.483995] kernel BUG at /home/miguel/projects/linux/trees/linux-2.6/arch/x86/kvm/../../../virt/kvm/kvm_main.c:1824!
> [  883.484006] invalid opcode: 0000 [#1] PREEMPT SMP 
> [  883.484021] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
> [  883.484031] Dumping ftrace buffer:
> [  883.484038]    (ftrace buffer empty)
> [  883.484044] CPU 1 
> [  883.484052] Modules linked in: kqemu loop aes_x86_64 aes_generic af_packet binfmt_misc bridge stp llc rfcomm bnep sco l2cap bluetooth vboxdrv kvm_amd kvm 
> parport_pc ppdev parport ipv6 powernow_k8 cpufreq_userspace cpufreq_powersave cpufreq_stats cpufreq_ondemand freq_table cpufreq_conservative container sbs wm
> i sbshc iptable_filter ip_tables x_tables sbp2 arc4 snd_hda_intel ecb snd_pcm snd_page_alloc snd_hwdep ath5k snd_seq snd_timer snd_seq_device mac80211 led_cl
> ass uvcvideo i2c_piix4 snd compat_ioctl32 videodev v4l1_compat cfg80211 i2c_core k8temp psmouse rfkill video output battery soundcore ac input_polldev button
>  evdev ext3 jbd mbcache sr_mod cdrom ata_generic pata_acpi sg sd_mod pata_atiixp ahci ide_pci_generic ohci1394 ieee1394 ide_core ehci_hcd ohci_hcd libata usb
>  core scsi_mod r8169 mii thermal processor fan fuse
>  [  883.484270] Pid: 10886, comm: kvm Tainted: G        W  2.6.28-rc6-00007-ged31348 #1
>  [  883.484270] RIP: 0010:[<ffffffffa04b8262>]  [<ffffffffa04b8262>] kvm_handle_fault_on_reboot+0x12/0x20 [kvm]
>   

Is it repeatable? Does it happen if you prefix the qemu command with 
'taskset 1'?



-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2008-11-30 20:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 19:34 [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348 Luis Henriques
2008-11-30 20:20 ` Avi Kivity [this message]
2008-11-30 20:38   ` Luis Henriques
2008-11-30 20:44     ` Avi Kivity
2008-11-30 21:04       ` Luis Henriques
2008-12-02 12:23         ` Avi Kivity
2008-12-02 12:25           ` Avi Kivity
2008-12-02 12:31             ` Avi Kivity
2008-12-02 19:09           ` Luis Henriques
2008-12-02 19:27             ` Avi Kivity
2008-12-02 19:30             ` Avi Kivity
2008-12-02 19:46             ` Luis Henriques
2008-12-02 20:25               ` Steven Rostedt
2008-12-02 20:38                 ` Avi Kivity
2008-12-02 20:48                   ` Steven Rostedt
2008-12-02 20:56                     ` Avi Kivity
2008-12-04 15:36                   ` Avi Kivity
2008-12-04 22:05                     ` Luis Henriques
2008-12-02 20:46                 ` Luis Henriques
2008-12-02 21:16                   ` Steven Rostedt

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=4932F59D.2060002@redhat.com \
    --to=avi@redhat.com \
    --cc=henrix@sapo.pt \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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.