* kernel 3.10.1 - "NMI received for unknown reason"
@ 2013-07-26 18:25 Stefan Pietsch
2013-07-26 18:39 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-07-26 18:25 UTC (permalink / raw)
To: kvm
Hi all,
starting a virtual machine (Debian sid) with KVM on my host running
kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
[ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
[ 765.522927] Do you have a strange power saving mode enabled?
[ 765.522930] Dazed and confused, but trying to continue
[ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
[ 770.487740] Do you have a strange power saving mode enabled?
[ 770.487742] Dazed and confused, but trying to continue
[ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
[ 846.340973] Do you have a strange power saving mode enabled?
[ 846.340976] Dazed and confused, but trying to continue
[ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
[ 847.563029] Do you have a strange power saving mode enabled?
[ 847.563032] Dazed and confused, but trying to continue
I can disable the messages (echo 0 > /proc/sys/kernel/nmi_watchdog) and
the host and the virtual machine are running as usual.
Host CPU: Intel(R) Core(TM) Duo CPU L2400
Regards,
Stefan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-26 18:25 kernel 3.10.1 - "NMI received for unknown reason" Stefan Pietsch
@ 2013-07-26 18:39 ` Gleb Natapov
2013-07-29 9:09 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-07-26 18:39 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
> Hi all,
>
> starting a virtual machine (Debian sid) with KVM on my host running
> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
>
Are those messages printed by a host or a guest?
> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> [ 765.522927] Do you have a strange power saving mode enabled?
> [ 765.522930] Dazed and confused, but trying to continue
> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
> [ 770.487740] Do you have a strange power saving mode enabled?
> [ 770.487742] Dazed and confused, but trying to continue
> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
> [ 846.340973] Do you have a strange power saving mode enabled?
> [ 846.340976] Dazed and confused, but trying to continue
> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> [ 847.563029] Do you have a strange power saving mode enabled?
> [ 847.563032] Dazed and confused, but trying to continue
>
> I can disable the messages (echo 0 > /proc/sys/kernel/nmi_watchdog) and
> the host and the virtual machine are running as usual.
>
>
> Host CPU: Intel(R) Core(TM) Duo CPU L2400
>
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-26 18:39 ` Gleb Natapov
@ 2013-07-29 9:09 ` Stefan Pietsch
2013-07-29 9:16 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-07-29 9:09 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 26.07.2013 20:39, Gleb Natapov wrote:
> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
>> Hi all,
>>
>> starting a virtual machine (Debian sid) with KVM on my host running
>> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
>>
> Are those messages printed by a host or a guest?
The host shows the messages.
>> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
>> [ 765.522927] Do you have a strange power saving mode enabled?
>> [ 765.522930] Dazed and confused, but trying to continue
>> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
>> [ 770.487740] Do you have a strange power saving mode enabled?
>> [ 770.487742] Dazed and confused, but trying to continue
>> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
>> [ 846.340973] Do you have a strange power saving mode enabled?
>> [ 846.340976] Dazed and confused, but trying to continue
>> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
>> [ 847.563029] Do you have a strange power saving mode enabled?
>> [ 847.563032] Dazed and confused, but trying to continue
Is it safe to ignore them?
Regards,
Stefan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-29 9:09 ` Stefan Pietsch
@ 2013-07-29 9:16 ` Gleb Natapov
2013-07-29 20:50 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-07-29 9:16 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote:
> On 26.07.2013 20:39, Gleb Natapov wrote:
> > On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
> >> Hi all,
> >>
> >> starting a virtual machine (Debian sid) with KVM on my host running
> >> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
> >>
> > Are those messages printed by a host or a guest?
>
> The host shows the messages.
>
> >> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >> [ 765.522927] Do you have a strange power saving mode enabled?
> >> [ 765.522930] Dazed and confused, but trying to continue
> >> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
> >> [ 770.487740] Do you have a strange power saving mode enabled?
> >> [ 770.487742] Dazed and confused, but trying to continue
> >> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
> >> [ 846.340973] Do you have a strange power saving mode enabled?
> >> [ 846.340976] Dazed and confused, but trying to continue
> >> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >> [ 847.563029] Do you have a strange power saving mode enabled?
> >> [ 847.563032] Dazed and confused, but trying to continue
>
> Is it safe to ignore them?
>
They should not happen. What is the last kernel version you tried that
does not produce them? Can you verify that they do not happen without
guest running? What is the qemu command line you are using to start the
guest and what "cat /proc/cpuinfo" looks like in the guest?
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-29 9:16 ` Gleb Natapov
@ 2013-07-29 20:50 ` Stefan Pietsch
2013-07-30 5:31 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-07-29 20:50 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 29.07.2013 11:16, Gleb Natapov wrote:
> On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote:
>> On 26.07.2013 20:39, Gleb Natapov wrote:
>>> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
>>>> Hi all,
>>>>
>>>> starting a virtual machine (Debian sid) with KVM on my host running
>>>> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
>>>>
>>> Are those messages printed by a host or a guest?
>>
>> The host shows the messages.
>>
>>>> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
>>>> [ 765.522927] Do you have a strange power saving mode enabled?
>>>> [ 765.522930] Dazed and confused, but trying to continue
>>>> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
>>>> [ 770.487740] Do you have a strange power saving mode enabled?
>>>> [ 770.487742] Dazed and confused, but trying to continue
>>>> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
>>>> [ 846.340973] Do you have a strange power saving mode enabled?
>>>> [ 846.340976] Dazed and confused, but trying to continue
>>>> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
>>>> [ 847.563029] Do you have a strange power saving mode enabled?
>>>> [ 847.563032] Dazed and confused, but trying to continue
>>
>> Is it safe to ignore them?
>>
> They should not happen. What is the last kernel version you tried that
> does not produce them? Can you verify that they do not happen without
> guest running? What is the qemu command line you are using to start the
> guest and what "cat /proc/cpuinfo" looks like in the guest?
The Debian wheezy kernel (3.2.46) does not show this behaviour.
It is directly related to KVM and I found out that replacing the option
"-cpu coreduo" with "-cpu kvm32" does not generate the NMI messages.
"coreduo" /proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2600 @ 2.16GHz
stepping : 8
microcode : 0x1
cpu MHz : 1662.559
cache size : 4096 KB
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
clflush mmx fxsr sse sse2 ss nx constant_tsc arch_perfmon pni hypervisor
bogomips : 3325.11
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 0 bits virtual
power management:
"kvm32" /proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Common 32-bit KVM processor
stepping : 1
microcode : 0x1
cpu MHz : 1662.559
cache size : 4096 KB
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
clflush mmx fxsr sse sse2 constant_tsc pni hypervisor
bogomips : 3325.11
clflush size : 64
cache_alignment : 128
address sizes : 32 bits physical, 0 bits virtual
power management:
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-29 20:50 ` Stefan Pietsch
@ 2013-07-30 5:31 ` Gleb Natapov
2013-07-31 9:10 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-07-30 5:31 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Mon, Jul 29, 2013 at 10:50:00PM +0200, Stefan Pietsch wrote:
> On 29.07.2013 11:16, Gleb Natapov wrote:
> > On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote:
> >> On 26.07.2013 20:39, Gleb Natapov wrote:
> >>> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
> >>>> Hi all,
> >>>>
> >>>> starting a virtual machine (Debian sid) with KVM on my host running
> >>>> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
> >>>>
> >>> Are those messages printed by a host or a guest?
> >>
> >> The host shows the messages.
> >>
> >>>> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >>>> [ 765.522927] Do you have a strange power saving mode enabled?
> >>>> [ 765.522930] Dazed and confused, but trying to continue
> >>>> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0.
> >>>> [ 770.487740] Do you have a strange power saving mode enabled?
> >>>> [ 770.487742] Dazed and confused, but trying to continue
> >>>> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1.
> >>>> [ 846.340973] Do you have a strange power saving mode enabled?
> >>>> [ 846.340976] Dazed and confused, but trying to continue
> >>>> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0.
> >>>> [ 847.563029] Do you have a strange power saving mode enabled?
> >>>> [ 847.563032] Dazed and confused, but trying to continue
> >>
> >> Is it safe to ignore them?
> >>
> > They should not happen. What is the last kernel version you tried that
> > does not produce them? Can you verify that they do not happen without
> > guest running? What is the qemu command line you are using to start the
> > guest and what "cat /proc/cpuinfo" looks like in the guest?
>
> The Debian wheezy kernel (3.2.46) does not show this behaviour.
> It is directly related to KVM and I found out that replacing the option
> "-cpu coreduo" with "-cpu kvm32" does not generate the NMI messages.
>
What happen if you run perf on your host (perf record -a)?
Do you see same NMI messages?
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-30 5:31 ` Gleb Natapov
@ 2013-07-31 9:10 ` Stefan Pietsch
2013-07-31 9:20 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-07-31 9:10 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 30.07.2013 07:31, Gleb Natapov wrote:
> What happen if you run perf on your host (perf record -a)?
> Do you see same NMI messages?
It seems that "perf record -a" triggers some delayed NMI messages.
They appear about 20 or 30 minutes after the command. This seems strange.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-31 9:10 ` Stefan Pietsch
@ 2013-07-31 9:20 ` Gleb Natapov
2013-08-02 6:24 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-07-31 9:20 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
> On 30.07.2013 07:31, Gleb Natapov wrote:
>
> > What happen if you run perf on your host (perf record -a)?
> > Do you see same NMI messages?
>
> It seems that "perf record -a" triggers some delayed NMI messages.
> They appear about 20 or 30 minutes after the command. This seems strange.
Definitely strange. KVM guest is not running in parallel, correct? 20, 30
minutes after perf stopped running or it is running all of the time?
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-07-31 9:20 ` Gleb Natapov
@ 2013-08-02 6:24 ` Stefan Pietsch
2013-08-04 12:44 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-08-02 6:24 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 31.07.2013 11:20, Gleb Natapov wrote:
> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
>> On 30.07.2013 07:31, Gleb Natapov wrote:
>>
>>> What happen if you run perf on your host (perf record -a)?
>>> Do you see same NMI messages?
>>
>> It seems that "perf record -a" triggers some delayed NMI messages.
>> They appear about 20 or 30 minutes after the command. This seems strange.
> Definitely strange. KVM guest is not running in parallel, correct? 20, 30
> minutes after perf stopped running or it is running all of the time?
No, the KVM guest ist not running in parallel. But I'm not able to
clearly reproduce the NMI messages with "perf record".
I start "perf record -a" and after some minutes I stop the recording.
After that it seems NMI messages appear within a random period of time.
So, I cannot tell what triggers the messages.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-08-02 6:24 ` Stefan Pietsch
@ 2013-08-04 12:44 ` Gleb Natapov
2013-08-09 19:14 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-08-04 12:44 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
> On 31.07.2013 11:20, Gleb Natapov wrote:
> > On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
> >> On 30.07.2013 07:31, Gleb Natapov wrote:
> >>
> >>> What happen if you run perf on your host (perf record -a)?
> >>> Do you see same NMI messages?
> >>
> >> It seems that "perf record -a" triggers some delayed NMI messages.
> >> They appear about 20 or 30 minutes after the command. This seems strange.
> > Definitely strange. KVM guest is not running in parallel, correct? 20, 30
> > minutes after perf stopped running or it is running all of the time?
>
> No, the KVM guest ist not running in parallel. But I'm not able to
> clearly reproduce the NMI messages with "perf record".
> I start "perf record -a" and after some minutes I stop the recording.
>
> After that it seems NMI messages appear within a random period of time.
> So, I cannot tell what triggers the messages.
When you run KVM with coreduo cpu model it emulates PMU which basically
make is perf front end. If you can reproduce the messages with perf too
it probably means that the problem is not in the KVM itself. If you
disabled NMI watchdog in the guest the messages may go away.
Can you send your guest's dmesg when you boot it with coreduo mode?
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-08-04 12:44 ` Gleb Natapov
@ 2013-08-09 19:14 ` Stefan Pietsch
2013-08-25 11:45 ` Gleb Natapov
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Pietsch @ 2013-08-09 19:14 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 04.08.2013 14:44, Gleb Natapov wrote:
> On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
>> On 31.07.2013 11:20, Gleb Natapov wrote:
>>> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
>>>> On 30.07.2013 07:31, Gleb Natapov wrote:
>>>>
>>>>> What happen if you run perf on your host (perf record -a)?
>>>>> Do you see same NMI messages?
>>>>
>>>> It seems that "perf record -a" triggers some delayed NMI messages.
>>>> They appear about 20 or 30 minutes after the command. This seems strange.
>>> Definitely strange. KVM guest is not running in parallel, correct? 20, 30
>>> minutes after perf stopped running or it is running all of the time?
>>
>> No, the KVM guest ist not running in parallel. But I'm not able to
>> clearly reproduce the NMI messages with "perf record".
>> I start "perf record -a" and after some minutes I stop the recording.
>>
>> After that it seems NMI messages appear within a random period of time.
>> So, I cannot tell what triggers the messages.
> When you run KVM with coreduo cpu model it emulates PMU which basically
> make is perf front end. If you can reproduce the messages with perf too
> it probably means that the problem is not in the KVM itself. If you
> disabled NMI watchdog in the guest the messages may go away.
> Can you send your guest's dmesg when you boot it with coreduo mode?
The NMI messages appear in the host only. The guest runs as usual.
This is the guest dmesg with "-cpu coreduo":
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10-2-686-pae
(debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) )
#1 SMP Debian 3.10.5-1 (2013-08-07)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000fffdfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000fffe000-0x000000000fffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff]
reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: Bochs Bochs, BIOS Bochs 01/01/2011
[ 0.000000] Hypervisor detected: KVM
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0xfffe max_arch_pfn = 0x1000000
[ 0.000000] MTRR default type: write-back
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 080000000 mask 080000000 uncachable
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] PAT not supported by CPU.
[ 0.000000] found SMP MP-table at [mem 0x000f1840-0x000f184f] mapped
at [c00f1840]
[ 0.000000] initial memory mapped: [mem 0x00000000-0x019fffff]
[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x0fc00000-0x0fdfffff]
[ 0.000000] [mem 0x0fc00000-0x0fdfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x0c000000-0x0fbfffff]
[ 0.000000] [mem 0x0c000000-0x0fbfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x0bffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x0bffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x0fe00000-0x0fffdfff]
[ 0.000000] [mem 0x0fe00000-0x0fffdfff] page 4k
[ 0.000000] BRK [0x0159c000, 0x0159cfff] PGTABLE
[ 0.000000] BRK [0x0159d000, 0x0159efff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x0eaac000-0x0f715fff]
[ 0.000000] ACPI: RSDP 000f16e0 00014 (v00 BOCHS )
[ 0.000000] ACPI: RSDT 0fffe450 00034 (v01 BOCHS BXPCRSDT 00000001
BXPC 00000001)
[ 0.000000] ACPI: FACP 0fffff80 00074 (v01 BOCHS BXPCFACP 00000001
BXPC 00000001)
[ 0.000000] ACPI: DSDT 0fffe490 01137 (v01 BXPC BXDSDT 00000001
INTL 20100528)
[ 0.000000] ACPI: FACS 0fffff40 00040
[ 0.000000] ACPI: SSDT 0ffff700 00838 (v01 BOCHS BXPCSSDT 00000001
BXPC 00000001)
[ 0.000000] ACPI: APIC 0ffff610 00078 (v01 BOCHS BXPCAPIC 00000001
BXPC 00000001)
[ 0.000000] ACPI: HPET 0ffff5d0 00038 (v01 BOCHS BXPCHPET 00000001
BXPC 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 255MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 0fffe000
[ 0.000000] low ram: 0 - 0fffe000
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[ 0.000000] kvm-clock: cpu 0, msr 0:fffd001, boot clock
[ 0.000000] BRK [0x0159f000, 0x0159ffff] PGTABLE
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] Normal [mem 0x01000000-0x0fffdfff]
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009efff]
[ 0.000000] node 0: [mem 0x00100000-0x0fffdfff]
[ 0.000000] On node 0 totalpages: 65436
[ 0.000000] free_area_init_node: node 0, pgdat c1483180, node_mem_map
cfdfd020
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3998 pages, LIFO batch:0
[ 0.000000] Normal zone: 480 pages used for memmap
[ 0.000000] Normal zone: 61438 pages, LIFO batch:15
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0xb008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ5 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ10 used by override.
[ 0.000000] ACPI: IRQ11 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009f000 -
00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 -
0000000000100000
[ 0.000000] e820: [mem 0x10000000-0xfeffbfff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on KVM
[ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1
nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @cfdeb000 s34560 r0 d22784
u57344
[ 0.000000] pcpu-alloc: s34560 r0 d22784 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] kvm-clock: cpu 0, msr 0:fffd001, primary cpu clock
[ 0.000000] KVM setup async PF for cpu 0
[ 0.000000] kvm-stealtime: cpu 0, msr fdee100
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 64924
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10-2-686-pae
root=/dev/mapper/debiansid-root ro quiet
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072
bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 240876k/262136k available (3083k kernel code,
20868k reserved, 1574k data, 460k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xffd34000 - 0xfffff000 (2860 kB)
[ 0.000000] pkmap : 0xffa00000 - 0xffc00000 (2048 kB)
[ 0.000000] vmalloc : 0xd07fe000 - 0xff9fe000 ( 754 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcfffe000 ( 255 MB)
[ 0.000000] .init : 0xc148d000 - 0xc1500000 ( 460 kB)
[ 0.000000] .data : 0xc1302dbc - 0xc148c800 (1574 kB)
[ 0.000000] .text : 0xc1000000 - 0xc1302dbc (3083 kB)
[ 0.000000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:2304 nr_irqs:256 16
[ 0.000000] CPU 0 irqstacks, hard=cf806000 soft=cf808000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Detected 1662.524 MHz processor
[ 0.008000] Calibrating delay loop (skipped) preset value.. 3325.04
BogoMIPS (lpj=6650096)
[ 0.008000] pid_max: default: 32768 minimum: 301
[ 0.008000] Security Framework initialized
[ 0.008000] AppArmor: AppArmor disabled by boot time parameter
[ 0.008000] Yama: disabled by default; enable with sysctl kernel.yama.*
[ 0.008000] Mount-cache hash table entries: 512
[ 0.008000] Initializing cgroup subsys memory
[ 0.008000] Initializing cgroup subsys devices
[ 0.008000] Initializing cgroup subsys freezer
[ 0.008000] Initializing cgroup subsys net_cls
[ 0.008000] Initializing cgroup subsys blkio
[ 0.008000] Initializing cgroup subsys perf_event
[ 0.008000] mce: CPU supports 10 MCE banks
[ 0.008000] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[ 0.008000] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0
[ 0.008000] tlb_flushall_shift: 6
[ 0.112848] Freeing SMP alternatives: 12k freed
[ 0.116231] ACPI: Core revision 20130328
[ 0.117832] ACPI: All ACPI Tables successfully acquired
[ 0.118210] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.122025] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.122029] smpboot: CPU0: Genuine Intel(R) CPU T2600 @
2.16GHz (fam: 06, model: 0e, stepping: 08)
[ 0.124000] Performance Events: Core events, core PMU driver.
[ 0.124000] ... version: 1
[ 0.124000] ... bit width: 40
[ 0.124000] ... generic registers: 2
[ 0.124000] ... value mask: 000000ffffffffff
[ 0.124000] ... max period: 000000007fffffff
[ 0.124000] ... fixed-purpose events: 0
[ 0.124000] ... event mask: 0000000000000003
[ 0.124000] Brought up 1 CPUs
[ 0.124000] smpboot: Total of 1 processors activated (3325.04 BogoMIPS)
[ 0.124000] NMI watchdog: enabled on all CPUs, permanently consumes
one hw-PMU counter.
[ 0.124000] devtmpfs: initialized
[ 0.124000] regulator-dummy: no parameters
[ 0.124000] NET: Registered protocol family 16
[ 0.124000] ACPI: bus type PCI registered
[ 0.124000] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.124000] PCI : PCI BIOS area is rw and x. Use pci=nobios if you
want it NX.
[ 0.124000] PCI: PCI BIOS revision 2.10 entry at 0xfd4e3, last bus=0
[ 0.124000] PCI: Using configuration type 1 for base access
[ 0.124931] bio: create slab <bio-0> at 0
[ 0.125153] ACPI: Added _OSI(Module Device)
[ 0.125157] ACPI: Added _OSI(Processor Device)
[ 0.125160] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.125163] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.126444] ACPI: EC: Look up EC in DSDT
[ 0.129279] ACPI: Interpreter enabled
[ 0.129291] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep
State [\_S1_] (20130328/hwxface-568)
[ 0.129298] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep
State [\_S2_] (20130328/hwxface-568)
[ 0.129317] ACPI: (supports S0 S3 S4 S5)
[ 0.129320] ACPI: Using IOAPIC for interrupt routing
[ 0.129341] PCI: Using host bridge windows from ACPI; if necessary,
use "pci=nocrs" and report a bug
[ 0.129923] ACPI: No dock devices found.
[ 0.136086] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.136233] acpi PNP0A03:00: fail to add MMCONFIG information, can't
access extended PCI configuration space under this bridge.
[ 0.136726] acpiphp: Slot [3] registered
[ 0.136783] acpiphp: Slot [4] registered
[ 0.136846] acpiphp: Slot [5] registered
[ 0.136899] acpiphp: Slot [6] registered
[ 0.136950] acpiphp: Slot [7] registered
[ 0.137011] acpiphp: Slot [8] registered
[ 0.137063] acpiphp: Slot [9] registered
[ 0.137113] acpiphp: Slot [10] registered
[ 0.137164] acpiphp: Slot [11] registered
[ 0.137215] acpiphp: Slot [12] registered
[ 0.137265] acpiphp: Slot [13] registered
[ 0.137316] acpiphp: Slot [14] registered
[ 0.137366] acpiphp: Slot [15] registered
[ 0.137460] acpiphp: Slot [16] registered
[ 0.137512] acpiphp: Slot [17] registered
[ 0.137573] acpiphp: Slot [18] registered
[ 0.137625] acpiphp: Slot [19] registered
[ 0.137686] acpiphp: Slot [20] registered
[ 0.137737] acpiphp: Slot [21] registered
[ 0.137788] acpiphp: Slot [22] registered
[ 0.137839] acpiphp: Slot [23] registered
[ 0.137889] acpiphp: Slot [24] registered
[ 0.137940] acpiphp: Slot [25] registered
[ 0.137991] acpiphp: Slot [26] registered
[ 0.138052] acpiphp: Slot [27] registered
[ 0.138103] acpiphp: Slot [28] registered
[ 0.138154] acpiphp: Slot [29] registered
[ 0.138205] acpiphp: Slot [30] registered
[ 0.138256] acpiphp: Slot [31] registered
[ 0.138287] PCI host bridge to bus 0000:00
[ 0.138293] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.138297] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.138301] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.138305] pci_bus 0000:00: root bus resource [mem
0x000a0000-0x000bffff]
[ 0.138310] pci_bus 0000:00: root bus resource [mem
0x80000000-0xfebfffff]
[ 0.138425] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
[ 0.139464] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
[ 0.140856] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
[ 0.149841] pci 0000:00:01.1: reg 20: [io 0xc180-0xc18f]
[ 0.153394] pci 0000:00:01.2: [8086:7020] type 00 class 0x0c0300
[ 0.162771] pci 0000:00:01.2: reg 20: [io 0xc160-0xc17f]
[ 0.167173] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
[ 0.168481] pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] claimed by
PIIX4 ACPI
[ 0.168511] pci 0000:00:01.3: quirk: [io 0xb100-0xb10f] claimed by
PIIX4 SMB
[ 0.169015] pci 0000:00:02.0: [1234:1111] type 00 class 0x030000
[ 0.172047] pci 0000:00:02.0: reg 10: [mem 0xfd000000-0xfdffffff pref]
[ 0.180035] pci 0000:00:02.0: reg 18: [mem 0xfebf2000-0xfebf2fff]
[ 0.196036] pci 0000:00:02.0: reg 30: [mem 0xfebe0000-0xfebeffff pref]
[ 0.196642] pci 0000:00:03.0: [1274:5000] type 00 class 0x040100
[ 0.198532] pci 0000:00:03.0: reg 10: [io 0xc000-0xc0ff]
[ 0.210301] pci 0000:00:04.0: [1af4:1000] type 00 class 0x020000
[ 0.213745] pci 0000:00:04.0: reg 10: [io 0xc140-0xc15f]
[ 0.217721] pci 0000:00:04.0: reg 14: [mem 0xfebf1000-0xfebf1fff]
[ 0.233762] pci 0000:00:04.0: reg 30: [mem 0xfebd0000-0xfebdffff pref]
[ 0.234626] pci 0000:00:05.0: [1af4:1001] type 00 class 0x010000
[ 0.237735] pci 0000:00:05.0: reg 10: [io 0xc100-0xc13f]
[ 0.241751] pci 0000:00:05.0: reg 14: [mem 0xfebf0000-0xfebf0fff]
[ 0.261087] pci_bus 0000:00: on NUMA node 0
[ 0.261106] acpi PNP0A03:00: ACPI _OSC support notification failed,
disabling PCIe ASPM
[ 0.261111] acpi PNP0A03:00: Unable to request _OSC control (_OSC
support mask: 0x08)
[ 0.261814] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.262040] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.262258] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.262474] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.262587] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
[ 0.263359] ACPI: Enabled 16 GPEs in block 00 to 0F
[ 0.263369] acpi root: \_SB_.PCI0 notify handler is installed
[ 0.263402] Found 1 acpi root devices
[ 0.263855] vgaarb: device added:
PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.263859] vgaarb: loaded
[ 0.263861] vgaarb: bridge control possible 0000:00:02.0
[ 0.263949] PCI: Using ACPI for IRQ routing
[ 0.263953] PCI: pci_cache_line_size set to 64 bytes
[ 0.264421] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[ 0.264437] e820: reserve RAM buffer [mem 0x0fffe000-0x0fffffff]
[ 0.264703] HPET: 3 timers in total, 0 timers will be used for
per-cpu timer
[ 0.264767] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.264773] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ 0.269262] Switching to clocksource kvm-clock
[ 0.271646] pnp: PnP ACPI init
[ 0.271665] ACPI: bus type PNP registered
[ 0.271828] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.271828] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.271828] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
[ 0.271828] pnp 00:03: [dma 2]
[ 0.271828] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
[ 0.271828] pnp 00:04: Plug and Play ACPI device, IDs PNP0400 (active)
[ 0.271828] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.271828] pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active)
[ 0.271828] pnp: PnP ACPI: found 7 devices
[ 0.271830] ACPI: bus type PNP unregistered
[ 0.271857] PnPBIOS: Disabled
[ 0.309684] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.309690] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.309694] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.309698] pci_bus 0000:00: resource 7 [mem 0x80000000-0xfebfffff]
[ 0.309774] NET: Registered protocol family 2
[ 0.310021] TCP established hash table entries: 2048 (order: 2, 16384
bytes)
[ 0.310064] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.310102] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.310173] TCP: reno registered
[ 0.310177] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.310185] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.310296] NET: Registered protocol family 1
[ 0.310321] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 0.310359] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[ 0.310412] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 0.311075] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[ 0.312440] pci 0000:00:02.0: Boot video device
[ 0.312540] PCI: CLS 0 bytes, default 64
[ 0.312596] Unpacking initramfs...
[ 0.801940] Freeing initrd memory: 12712k freed
[ 0.810143] audit: initializing netlink socket (disabled)
[ 0.810167] type=2000 audit(1376074310.808:1): initialized
[ 0.836745] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.836855] VFS: Disk quotas dquot_6.5.2
[ 0.836887] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.837014] msgmni has been set to 495
[ 0.837284] alg: No test for stdrng (krng)
[ 0.837307] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 252)
[ 0.837344] io scheduler noop registered
[ 0.837346] io scheduler deadline registered
[ 0.837354] io scheduler cfq registered (default)
[ 0.837457] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.837482] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.837582] intel_idle: does not run on family 6 model 14
[ 0.837621] GHES: HEST is not enabled!
[ 0.837659] isapnp: Scanning for PnP cards...
[ 1.210391] isapnp: No Plug & Play device found
[ 1.210513] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.239247] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 1.239936] Linux agpgart interface v0.103
[ 1.240302] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at
0x60,0x64 irq 1,12
[ 1.242006] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.242017] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.242171] mousedev: PS/2 mouse device common for all mice
[ 1.242894] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 1.243348] rtc_cmos 00:00: RTC can wake from S4
[ 1.244187] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[ 1.244569] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram,
hpet irqs
[ 1.244587] cpuidle: using governor ladder
[ 1.244589] cpuidle: using governor menu
[ 1.244613] drop_monitor: Initializing network drop monitor service
[ 1.244730] TCP: cubic registered
[ 1.244746] NET: Registered protocol family 10
[ 1.245020] mip6: Mobile IPv6
[ 1.245024] NET: Registered protocol family 17
[ 1.245178] Using IPI No-Shortcut mode
[ 1.245281] PM: Hibernation image not present or could not be loaded.
[ 1.245292] registered taskstats version 1
[ 1.246066] rtc_cmos 00:00: setting system clock to 2013-08-09
18:51:50 UTC (1376074310)
[ 1.246546] Freeing unused kernel memory: 460k freed
[ 1.246969] Write protecting the kernel text: 3084k
[ 1.247146] Write protecting the kernel read-only data: 1240k
[ 1.247150] NX-protecting the kernel data: 3060k
[ 1.381314] udevd[53]: starting version 175
[ 1.584281] SCSI subsystem initialized
[ 1.616907] ACPI: bus type USB registered
[ 1.616971] usbcore: registered new interface driver usbfs
[ 1.616991] usbcore: registered new interface driver hub
[ 1.629748] virtio-pci 0000:00:04.0: setting latency timer to 64
[ 1.629950] usbcore: registered new device driver usb
[ 1.636609] ACPI: bus type ATA registered
[ 1.638952] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
[ 1.640435] virtio-pci 0000:00:05.0: setting latency timer to 64
[ 1.646688] libata version 3.00 loaded.
[ 1.652101] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.654360] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.670328] ata_piix 0000:00:01.1: version 2.13
[ 1.672135] ata_piix 0000:00:01.1: setting latency timer to 64
[ 1.679121] scsi0 : ata_piix
[ 1.684132] scsi1 : ata_piix
[ 1.684216] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc180 irq 14
[ 1.684220] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc188 irq 15
[ 1.686648] uhci_hcd 0000:00:01.2: setting latency timer to 64
[ 1.686677] uhci_hcd 0000:00:01.2: UHCI Host Controller
[ 1.686696] uhci_hcd 0000:00:01.2: new USB bus registered, assigned
bus number 1
[ 1.686977] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c160
[ 1.687162] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.687167] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.687171] usb usb1: Product: UHCI Host Controller
[ 1.687174] usb usb1: Manufacturer: Linux 3.10-2-686-pae uhci_hcd
[ 1.687178] usb usb1: SerialNumber: 0000:00:01.2
[ 1.688237] hub 1-0:1.0: USB hub found
[ 1.688245] hub 1-0:1.0: 2 ports detected
[ 1.808138] tsc: Refined TSC clocksource calibration: 1662.524 MHz
[ 1.844611] Floppy drive(s): fd0 is 1.44M
[ 1.853089] ata2.01: NODEV after polling detection
[ 1.853655] ata2.00: ATAPI: QEMU DVD-ROM, 1.5.1, max UDMA/100
[ 1.854761] ata2.00: configured for MWDMA2
[ 1.855949] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM
1.5. PQ: 0 ANSI: 5
[ 1.861374] FDC 0 is a S82078B
[ 1.924854] virtio-pci 0000:00:05.0: irq 40 for MSI/MSI-X
[ 1.924912] virtio-pci 0000:00:05.0: irq 41 for MSI/MSI-X
[ 1.926649] virtio-pci 0000:00:04.0: irq 42 for MSI/MSI-X
[ 1.926706] virtio-pci 0000:00:04.0: irq 43 for MSI/MSI-X
[ 1.926761] virtio-pci 0000:00:04.0: irq 44 for MSI/MSI-X
[ 1.936701] vda: vda1 vda2 < vda5 >
[ 1.939711] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 1.939718] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.940297] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 1.958544] sr 1:0:0:0: Attached scsi generic sg0 type 5
[ 2.000119] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[ 2.161424] usb 1-1: New USB device found, idVendor=0627, idProduct=0001
[ 2.161434] usb 1-1: New USB device strings: Mfr=1, Product=3,
SerialNumber=5
[ 2.161442] usb 1-1: Product: QEMU USB Tablet
[ 2.161447] usb 1-1: Manufacturer: QEMU
[ 2.161453] usb 1-1: SerialNumber: 42
[ 2.187753] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.197893] usbcore: registered new interface driver usbhid
[ 2.197898] usbhid: USB HID core driver
[ 2.208601] input: QEMU QEMU USB Tablet as
/devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/input/input1
[ 2.208864] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID
v0.01 Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
[ 2.255431] device-mapper: uevent: version 1.0.3
[ 2.256404] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15)
initialised: dm-devel@redhat.com
[ 2.330286] bio: create slab <bio-1> at 1
[ 2.536086] raid6: mmxx1 1637 MB/s
[ 2.604072] raid6: mmxx2 1747 MB/s
[ 2.672047] raid6: sse1x1 1197 MB/s
[ 2.740063] raid6: sse1x2 1613 MB/s
[ 2.808070] raid6: sse2x1 1903 MB/s
[ 2.876048] raid6: sse2x2 2021 MB/s
[ 2.876052] raid6: using algorithm sse2x2 (2021 MB/s)
[ 2.876055] raid6: using intx1 recovery algorithm
[ 2.879238] xor: measuring software checksum speed
[ 2.916039] pIII_sse : 3932.000 MB/sec
[ 2.956066] prefetch64-sse: 4365.000 MB/sec
[ 2.956069] xor: using function: prefetch64-sse (4365.000 MB/sec)
[ 2.982035] bio: create slab <bio-2> at 2
[ 2.982948] Btrfs loaded
[ 3.039019] kjournald starting. Commit interval 5 seconds
[ 3.039048] EXT3-fs (dm-0): mounted filesystem with ordered data mode
[ 4.341551] udevd[328]: starting version 175
[ 4.603537] WARNING! power/level is deprecated; use power/control instead
[ 4.782734] piix4_smbus 0000:00:01.3: SMBus Host Controller at
0xb100, revision 0
[ 4.801175] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 4.801187] ACPI: Power Button [PWRF]
[ 5.032431] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 5.034554] snd_ens1370 0000:00:03.0: setting latency timer to 64
[ 6.243366] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 6.278638] parport_pc 00:04: reported by Plug and Play ACPI
[ 6.279018] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 6.291654] Error: Driver 'pcspkr' is already registered, aborting...
[ 6.301792] microcode: CPU0 sig=0x6e8, pf=0x1, revision=0x1
[ 6.481324] platform microcode: firmware: agent aborted loading
intel-ucode/06-0e-08 (not found?)
[ 6.482603] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 7.158416] input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input/input4
[ 7.931043] EXT3-fs (dm-0): using internal journal
[ 9.216927] fuse init (API version 7.22)
[ 9.280443] loop: module loaded
[ 9.870640] Adding 401404k swap on /dev/mapper/debiansid-swap_1.
Priority:-1 extents:1 across:401404k
[ 12.772839] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 12.816962] nf_conntrack version 0.5.0 (3969 buckets, 15876 max)
[ 12.915796] ip6_tables: (C) 2000-2006 Netfilter Core Team
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-08-09 19:14 ` Stefan Pietsch
@ 2013-08-25 11:45 ` Gleb Natapov
2013-08-26 21:48 ` Stefan Pietsch
0 siblings, 1 reply; 13+ messages in thread
From: Gleb Natapov @ 2013-08-25 11:45 UTC (permalink / raw)
To: Stefan Pietsch; +Cc: kvm
On Fri, Aug 09, 2013 at 09:14:13PM +0200, Stefan Pietsch wrote:
> On 04.08.2013 14:44, Gleb Natapov wrote:
> > On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
> >> On 31.07.2013 11:20, Gleb Natapov wrote:
> >>> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
> >>>> On 30.07.2013 07:31, Gleb Natapov wrote:
> >>>>
> >>>>> What happen if you run perf on your host (perf record -a)?
> >>>>> Do you see same NMI messages?
> >>>>
> >>>> It seems that "perf record -a" triggers some delayed NMI messages.
> >>>> They appear about 20 or 30 minutes after the command. This seems strange.
> >>> Definitely strange. KVM guest is not running in parallel, correct? 20, 30
> >>> minutes after perf stopped running or it is running all of the time?
> >>
> >> No, the KVM guest ist not running in parallel. But I'm not able to
> >> clearly reproduce the NMI messages with "perf record".
> >> I start "perf record -a" and after some minutes I stop the recording.
> >>
> >> After that it seems NMI messages appear within a random period of time.
> >> So, I cannot tell what triggers the messages.
> > When you run KVM with coreduo cpu model it emulates PMU which basically
> > make is perf front end. If you can reproduce the messages with perf too
> > it probably means that the problem is not in the KVM itself. If you
> > disabled NMI watchdog in the guest the messages may go away.
> > Can you send your guest's dmesg when you boot it with coreduo mode?
>
>
> The NMI messages appear in the host only. The guest runs as usual.
>
>
I understand that. But enabling guest nmi watchdog is what makes KVM to
use perf subsystem and likely causes this host messages. Try do disable
nmi watchdog in a guest and see what happens.
--
Gleb.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: kernel 3.10.1 - "NMI received for unknown reason"
2013-08-25 11:45 ` Gleb Natapov
@ 2013-08-26 21:48 ` Stefan Pietsch
0 siblings, 0 replies; 13+ messages in thread
From: Stefan Pietsch @ 2013-08-26 21:48 UTC (permalink / raw)
To: Gleb Natapov; +Cc: kvm
On 25.08.2013 13:45, Gleb Natapov wrote:
> On Fri, Aug 09, 2013 at 09:14:13PM +0200, Stefan Pietsch wrote:
>> On 04.08.2013 14:44, Gleb Natapov wrote:
>>> On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
>>>> On 31.07.2013 11:20, Gleb Natapov wrote:
>>>>> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
>>>>>> On 30.07.2013 07:31, Gleb Natapov wrote:
>>>>>>
>>>>>>> What happen if you run perf on your host (perf record -a)?
>>>>>>> Do you see same NMI messages?
>>>>>>
>>>>>> It seems that "perf record -a" triggers some delayed NMI messages.
>>>>>> They appear about 20 or 30 minutes after the command. This seems strange.
>>>>> Definitely strange. KVM guest is not running in parallel, correct? 20, 30
>>>>> minutes after perf stopped running or it is running all of the time?
>>>>
>>>> No, the KVM guest ist not running in parallel. But I'm not able to
>>>> clearly reproduce the NMI messages with "perf record".
>>>> I start "perf record -a" and after some minutes I stop the recording.
>>>>
>>>> After that it seems NMI messages appear within a random period of time.
>>>> So, I cannot tell what triggers the messages.
>>> When you run KVM with coreduo cpu model it emulates PMU which basically
>>> make is perf front end. If you can reproduce the messages with perf too
>>> it probably means that the problem is not in the KVM itself. If you
>>> disabled NMI watchdog in the guest the messages may go away.
>>> Can you send your guest's dmesg when you boot it with coreduo mode?
>>
>>
>> The NMI messages appear in the host only. The guest runs as usual.
>>
>>
> I understand that. But enabling guest nmi watchdog is what makes KVM to
> use perf subsystem and likely causes this host messages. Try do disable
> nmi watchdog in a guest and see what happens.
I disabled the watchdog in the guest by booting the kernel with
"nmi_watchdog=0". This does not produce any NMI errors.
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2013-08-26 21:48 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-26 18:25 kernel 3.10.1 - "NMI received for unknown reason" Stefan Pietsch
2013-07-26 18:39 ` Gleb Natapov
2013-07-29 9:09 ` Stefan Pietsch
2013-07-29 9:16 ` Gleb Natapov
2013-07-29 20:50 ` Stefan Pietsch
2013-07-30 5:31 ` Gleb Natapov
2013-07-31 9:10 ` Stefan Pietsch
2013-07-31 9:20 ` Gleb Natapov
2013-08-02 6:24 ` Stefan Pietsch
2013-08-04 12:44 ` Gleb Natapov
2013-08-09 19:14 ` Stefan Pietsch
2013-08-25 11:45 ` Gleb Natapov
2013-08-26 21:48 ` Stefan Pietsch
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.