Re: module param for CPU_NOTIFIER_ERROR_INJECT

[Justin P. Mattock]

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@xxxxxxxxx
> <mailto:akinobu.mita@xxxxxxxxx>> wrote:
>  > 2011/8/22 Justin P. Mattock <justinmattock@xxxxxxxxx
> <mailto:justinmattock@xxxxxxxxx>>:
>  >
>  >> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/