* K.R. Foley <kr@xxxxxxxxxx> wrote:This was on my SMP system. I can try the maxcpus=1. However, the trouble may be reproducing the oops. This happened at ~5:35 this morning (~9 hrs. ago). Hadn't happened again as of an hour ago when I booted S2. I will give it a try though.
Ingo Molnar wrote:
i've released the -S1 VP patch:
http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.9-rc2-mm1-S1
Two separate oopses this morning running that above patch. One appears
to happen in locks_delete_lock. [...]
i too got this one today. Seems to be related to the BKL changes -
locks.c is a heavy user of the BKL. You have an SMP system, right? Does
the oops happen if you boot with maxcpus=1?
Ingo