On Mon, Apr 12, 2010 at 11:34:16AM +0200, Daniel Lezcano wrote:
> At the first glance I would say it is related to the FAIR_SCHEDULER.
Here is the full stack trace:
http://img-fotki.yandex.ru/get/4210/wrar.4a/0_3a641_f9a80e04_XL
> Does sysrq + t show something ? Or the host is definitively stuck
On Mon, Apr 12, 2010 at 11:34:16AM +0200, Daniel Lezcano wrote:
> At the first glance I would say it is related to the FAIR_SCHEDULER.
CONFIG_FAIR_GROUP_SCHED=y
> After having multiple Oops on my host, I decided to disable this option
> in the kernel.
I will try it.
> Does sysrq + t show somet
Andrey Rahmatullin wrote:
> Hello.
> When I run lxc-stop for my Debian container, my system OOPSes. This is not
> 100% reproducible, though. I could catch only a part of the OOPS report
> using netconsole:
>
>
> [ 9243.740626] Oops: [#1] PREEMPT
> [ 9243.740648] last sysfs file: /sys/devices/p
Hello.
When I run lxc-stop for my Debian container, my system OOPSes. This is not
100% reproducible, though. I could catch only a part of the OOPS report
using netconsole:
[ 9243.740626] Oops: [#1] PREEMPT
[ 9243.740648] last sysfs file: /sys/devices/platform/w83627hf.656/fan1_input
[ 9243.7
