From: "Sasa Ostrouska" <casaxa@gmail.com>
To: linux-kernel@vger.kernel.org, michal.k.k.piotrowski@gmail.com
Subject: Re: KVM-AMD OOPS
Date: Sun, 8 Jul 2007 20:11:34 +0200 [thread overview]
Message-ID: <dcf706c60707081111yd4240ftf612ddc8695325f4@mail.gmail.com> (raw)
In-Reply-To: <dcf706c60707081051r2ff03a7bi35307536755b42f6@mail.gmail.com>
Ok, here is the output without nvidia driver installed.
Jul 9 00:02:38 rcserver kernel: int3: 0000 [1] PREEMPT SMP
Jul 9 00:02:38 rcserver kernel: CPU 1
Jul 9 00:02:38 rcserver kernel: 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 snd 8139too mii k8temp soundcore snd_page_alloc
ehci_hcd ohci_hcd rtc_cmos i2c_nforce2 usbcore rtc_core rtc_lib
parport_pc parport
Jul 9 00:02:38 rcserver kernel: Pid: 2898, comm: modprobe Not tainted
2.6.21.5 #1
Jul 9 00:02:38 rcserver kernel: RIP: 0010:[<ffffffff80572364>]
[<ffffffff80572364>] register_cpu_notifier+0x1/0x31
Jul 9 00:02:38 rcserver kernel: RSP: 0018:ffff81006f117f40 EFLAGS: 00000246
Jul 9 00:02:38 rcserver kernel: RAX: 0000000000000000 RBX:
0000000000000000 RCX: 00000000c0010117
Jul 9 00:02:38 rcserver kernel: RDX: 000000000000ffff RSI:
ffff81007b7d6cc0 RDI: ffffffff80536510
Jul 9 00:02:38 rcserver kernel: RBP: ffffffff8816e840 R08:
0000000000000000 R09: 000000000006c112
Jul 9 00:02:38 rcserver kernel: R10: 0000000000000000 R11:
0000000000000000 R12: 00000000005296b0
Jul 9 00:02:38 rcserver kernel: R13: 00007fffa75ddbb0 R14:
0000000000000000 R15: 0000000000000000
Jul 9 00:02:38 rcserver kernel: FS: 00002af70381fb00(0000)
GS:ffff810002e794c0(0000) knlGS:0000000000000000
Jul 9 00:02:38 rcserver kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Jul 9 00:02:38 rcserver kernel: CR2: 0000000000508a68 CR3:
000000007a299000 CR4: 00000000000006e0
Jul 9 00:02:38 rcserver kernel: Process modprobe (pid: 2898,
threadinfo ffff81006f116000, task ffff81007bd62340)
Jul 9 00:02:38 rcserver kernel: Stack: ffffffff8039e024
ffff81006f116000 ffffffff8816e840 0000000000005e19
Jul 9 00:02:38 rcserver kernel: ffffffff8024537c 0000000000000000
00007fffa75dd6b0 00000000004142d0
Jul 9 00:02:38 rcserver kernel: ffffffff8020967e 0000000000000206
00000000005230e0 000000000052f4c9
Jul 9 00:02:38 rcserver kernel: Call Trace:
Jul 9 00:02:38 rcserver kernel: [<ffffffff8039e024>] kvm_init_arch+0x90/0x145
Jul 9 00:02:38 rcserver kernel: [<ffffffff8024537c>]
sys_init_module+0xad/0x168
Jul 9 00:02:38 rcserver kernel: [<ffffffff8020967e>] system_call+0x7e/0x83
Jul 9 00:02:38 rcserver kernel:
Jul 9 00:02:38 rcserver kernel:
Jul 9 00:02:38 rcserver kernel: Code: cc cc cc cc cc cc cc cc cc cc
cc cc cc cc cc cc cc cc cc cc
Jul 9 00:02:38 rcserver kernel: RIP [<ffffffff80572364>]
register_cpu_notifier+0x1/0x31
Jul 9 00:02:38 rcserver kernel: RSP <ffff81006f117f40>
Jul 9 00:02:38 rcserver kernel: BUG: scheduling while atomic:
modprobe/0x10000001/2898
Jul 9 00:02:38 rcserver kernel:
Jul 9 00:02:38 rcserver kernel: Call Trace:
Jul 9 00:02:38 rcserver kernel: <#DB> [<ffffffff80445740>]
__sched_text_start+0x60/0x80f
Jul 9 00:02:38 rcserver kernel: [<ffffffff804451f9>] __down_trylock+0x44/0x4f
Jul 9 00:02:38 rcserver kernel: [<ffffffff804477fb>]
__down_failed_trylock+0x35/0x3a
Jul 9 00:02:38 rcserver kernel: [<ffffffff80225517>] __cond_resched+0x1c/0x44
Jul 9 00:02:38 rcserver kernel: [<ffffffff80446818>] cond_resched+0x2e/0x39
Jul 9 00:02:38 rcserver kernel: [<ffffffff802586c5>] unmap_vmas+0x6a5/0x73d
Jul 9 00:02:38 rcserver kernel: [<ffffffff8025dabb>] exit_mmap+0x7f/0x11b
Jul 9 00:02:38 rcserver kernel: [<ffffffff80227449>] mmput+0x29/0x9a
Jul 9 00:02:38 rcserver kernel: [<ffffffff8022c2f9>] do_exit+0x216/0x823
Jul 9 00:02:38 rcserver kernel: [<ffffffff80447b38>]
__lock_text_start+0x8/0x30
Jul 9 00:02:38 rcserver kernel: [<ffffffff8020b044>] die_nmi+0x0/0x75
Jul 9 00:02:38 rcserver kernel: [<ffffffff8020bb3a>] do_int3+0x81/0xa1
Jul 9 00:02:38 rcserver kernel: [<ffffffff804485d3>] int3+0x93/0xb0
Jul 9 00:02:38 rcserver kernel: [<ffffffff80572364>]
register_cpu_notifier+0x1/0x31
Jul 9 00:02:38 rcserver kernel: <<EOE>> [<ffffffff8039e024>]
kvm_init_arch+0x90/0x145
Jul 9 00:02:38 rcserver kernel: [<ffffffff8024537c>]
sys_init_module+0xad/0x168
Jul 9 00:02:38 rcserver kernel: [<ffffffff8020967e>] system_call+0x7e/0x83
Jul 9 00:02:38 rcserver kernel:
Rgds
Saxa
next prev parent reply other threads:[~2007-07-08 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 16:15 Sasa Ostrouska
2007-07-08 17:41 ` Michal Piotrowski
[not found] ` <dcf706c60707081051r2ff03a7bi35307536755b42f6@mail.gmail.com>
2007-07-08 18:11 ` Sasa Ostrouska [this message]
2007-07-09 4:53 ` Jeremy Fitzhardinge
2007-07-09 7:08 ` Avi Kivity
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=dcf706c60707081111yd4240ftf612ddc8695325f4@mail.gmail.com \
--to=casaxa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@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
Powered by JetHome