From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
mattia.bonomi@studenti.unitn.it
Subject: Re: [ftrace] kernel panics during my attempt to use ftrace
Date: Fri, 24 Jun 2016 10:08:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.20.1606241004120.16561@localhost.localdomain> (raw)
In-Reply-To: <20160622111025.03e738ba@gandalf.local.home>
Hi Steven.
Thank you for your very very kind response.
I can build a stock kernel (I usually did for my real hw): and I don't see problems on this.
The problem is the bitness. My only KVM-enabled machine, as far as I can tell, has a 32-bit CPU.
So This would be a different problem.
I'll let you know when I can continue: right now I am a little bit in trouble with my exams: but I hope I will be able to eventually cme back and test.
Below my cpuinfo just for the record.
Thank you very much,
Enrico
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU Z520 @ 1.33GHz
stepping : 2
microcode : 0x211
cpu MHz : 1333.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
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 pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 xtpr pdcm movbe lahf_lm tpr_shadow vnmi flexpriority dtherm
bugs :
bogomips : 2662.89
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU Z520 @ 1.33GHz
stepping : 2
microcode : 0x211
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 1
initial apicid : 1
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 pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 xtpr pdcm movbe lahf_lm tpr_shadow vnmi flexpriority dtherm
bugs :
bogomips : 2662.42
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual
power management:
next prev parent reply other threads:[~2016-06-24 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 12:53 Enrico Mioso
2016-06-22 15:10 ` Steven Rostedt
2016-06-24 8:08 ` Enrico Mioso [this message]
2016-06-28 3:45 ` Namhyung Kim
2016-06-28 7:16 ` Enrico Mioso
2016-07-17 23:59 ` Enrico Mioso
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=alpine.LNX.2.20.1606241004120.16561@localhost.localdomain \
--to=mrkiko.rs@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattia.bonomi@studenti.unitn.it \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®