public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sasa Ostrouska <casaxa@gmail.com>,
	linux-kernel@vger.kernel.org,
	KVM <kvm-devel@lists.sourceforge.net>
Subject: Re: KVM-AMD OOPS
Date: Mon, 09 Jul 2007 10:08:19 +0300	[thread overview]
Message-ID: <4691DEE3.5050305@argo.co.il> (raw)
In-Reply-To: <4691BF62.2060207@goop.org>

Jeremy Fitzhardinge wrote:
> Sasa Ostrouska wrote:
>> root@rcserver:~# modprobe kvm-amd
>> int3: 0000 [1] PREEMPT SMP
>> CPU 1
>> Modules linked in: kvm_amd snd_seq_dummy snd_seq_oss
>> snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss
>> nls_iso8859_1 ntfs nls_base usb_storage libusual capability commoncap
>> lp psmouse snd_hda_intel snd_hda_codec snd_pcm snd_timer ohci_hcd
>> ehci_hcd 8139too rtc_cmos snd soundcore snd_page_alloc usbcore k8temp
>> mii rtc_core rtc_lib i2c_nforce2 parport_pc parport
>> Pid: 2898, comm: modprobe Tainted: P       2.6.21.5 #1
>> RIP: 0010:[<ffffffff80572364>]  [<ffffffff80572364>]
>> register_cpu_notifier+0x1/0x31
>> RSP: 0000:ffff81006e34df40  EFLAGS: 00000246
>> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000c0010117
>> RDX: 000000000000ffff RSI: ffff81006e219640 RDI: ffffffff80536510
>> RBP: ffffffff880d8840 R08: 0000000000000000 R09: 000000000006b5f4
>> R10: 0000000000000000 R11: 0000000000000000 R12: 00000000005296b0
>> R13: 00007fff51fe55c0 R14: 0000000000000000 R15: 0000000000000000
>> FS:  00002b4e58e18b00(0000) GS:ffff810002e794c0(0000)
>> knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> CR2: 000000000050df64 CR3: 000000007a0f3000 CR4: 00000000000006e0
>> Process modprobe (pid: 2898, threadinfo ffff81006e34c000, task
>> ffff81007bc48400)
>> Stack:  ffffffff8039e024 ffff81006e34c000 ffffffff880d8840
>> 0000000000005e19
>> ffffffff8024537c 0000000000000000 00007fff51fe50c0 00000000004142d0
>> ffffffff8020967e 0000000000000206 00000000005230e0 000000000052f4c9
>> Call Trace:
>> [<ffffffff8039e024>] kvm_init_arch+0x90/0x145
>> [<ffffffff8024537c>] sys_init_module+0xad/0x168
>> [<ffffffff8020967e>] system_call+0x7e/0x83
>>
>>
>> Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
>
> This is the init section poison pattern.  Looks like an init function
> was used after the code was freed.

Indeed, the function is register_cpu_notifier which is declared
__cpuinit, which, without hotplug compiled in, is simply __init.

I'll prepare a patch for this.  Meanwhile, you can work around it by
enabling CONFIG_HOTPLUG_CPU.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2007-07-09  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 16:15 KVM-AMD OOPS Sasa Ostrouska
2007-07-08 17:41 ` Michal Piotrowski
     [not found]   ` <dcf706c60707081051r2ff03a7bi35307536755b42f6@mail.gmail.com>
2007-07-08 18:11     ` Sasa Ostrouska
2007-07-09  4:53 ` Jeremy Fitzhardinge
2007-07-09  7:08   ` Avi Kivity [this message]
2007-07-09 12:02     ` Avi Kivity
2007-07-09 12:12       ` Sasa Ostrouska
     [not found]       ` <dcf706c60707090510w4a1293cbw69c8e0d47640f77d@mail.gmail.com>
2007-07-09 12:14         ` Avi Kivity
2007-07-09  7:15   ` Jiri Slaby
2007-07-09 12:58     ` 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=4691DEE3.5050305@argo.co.il \
    --to=avi@argo.co.il \
    --cc=casaxa@gmail.com \
    --cc=jeremy@goop.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox