From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: module param for CPU_NOTIFIER_ERROR_INJECT
Date: Mon, 22 Aug 2011 21:17:44 -0700 [thread overview]
Message-ID: <4E5329E8.7060608@gmail.com> (raw)
In-Reply-To: <CAKFRV=PSQT7Wt01gxirnkJEJv2GvQ7ELkd8QvxhT6BjXnBgQsw@mail.gmail.com>
On 08/22/2011 09:41 AM, Justin Mattock wrote:
> Cool.. I will retry on this and let you know.
>
> On Aug 22, 2011 5:48 AM, "Akinobu Mita" <akinobu.mita@gmail.com
> <mailto:akinobu.mita@gmail.com>> wrote:
> > 2011/8/22 Justin P. Mattock <justinmattock@gmail.com
> <mailto:justinmattock@gmail.com>>:
> >
> >> example 2
> >> # modprobe cpu-notifier-error-inject cpu_up_prepare_error=-2
> >> # echo 1 > /sys/devices/system/cpu/cpu1/online
> >> bash: echo: write error: No such file or directory
> >>
> >> is not working for me, or atleast is not showing me any info that it is
> >> working.
> >
> > I suspect that cpu-notifier-error-inject module is already loaded and
> > the module parameter is just ignored when you run above commands.
> >
> > Please retry it after rmmod or change that parameter through
> > /sys/module/cpu-error-inject/parameters/cpu_up_prepare_error.
>
cool, Thanks for the help.. not sure if this is correct, but I had to
shutdown one of the cores, then execute the cammand to get any response..:
echo 0 > /sys/devices/system/cpu/cpu1/online
modprobe cpu-notifier-error-inject cpu_up_prepare_error=-2
echo 1 > /sys/devices/system/cpu/cpu1/online
[ 4205.955592] Injecting error (-2) at cpu notifier
[ 4205.955601] _cpu_up: attempt to bring up CPU 1 failed
so it is working!
Justin P. Mattock
prev parent reply other threads:[~2011-08-23 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 18:52 module param for CPU_NOTIFIER_ERROR_INJECT Justin P. Mattock
2011-08-22 12:48 ` Akinobu Mita
[not found] ` <CAKFRV=PSQT7Wt01gxirnkJEJv2GvQ7ELkd8QvxhT6BjXnBgQsw@mail.gmail.com>
2011-08-23 4:17 ` Justin P. Mattock [this message]
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=4E5329E8.7060608@gmail.com \
--to=justinmattock@gmail.com \
--cc=akinobu.mita@gmail.com \
--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.