On 2010-03-22, at 05:06, Gregory Matthews wrote:
after running racer over the weekend on some test clients I see a
lot of these, is this lustre or cat? There are lustre functions
listed in the stack trace.
It definitely wouldn't have anything to do with cat itself.
Unfortunately, I
if it helps, I have longer stack traces...
Mar 21 05:31:42 dec055 kernel: BUG: scheduling while atomic:
cat/4439/0x0002
Mar 21 05:31:42 dec055 kernel: Modules linked in:3BUG: scheduling
while atomic: cat/4508/0x0002
Mar 21 05:31:42 dec055 kernel: mgc lustre lov mdc lquotaModules linked
Andreas...
Andreas Dilger wrote:
On 2010-03-17, at 02:59, Gregory Matthews wrote:
Gregory Matthews wrote:
BUG: using smp_processor_id() in preemptible [] code:
modprobe/6024
caller is set_ptldebug_header+0x41/0xa0 [libcfs]
Pid: 6024, comm: modprobe Not tainted 2.6.27.39-default #2
On 2010-03-18, at 03:44, Gregory Matthews wrote:
thanks for the advice. I've compiled new lustre packages with the
suggested fix and am currently running racer. So far, the above bug
has
not reappeared... In the meantime, lustre just got
more compatible with the preempt kernel. Will this
Well, I'm no expert at reading the the kernel bugzilla but...
Gregory Matthews wrote:
BUG: using smp_processor_id() in preemptible [] code: modprobe/6024
caller is set_ptldebug_header+0x41/0xa0 [libcfs]
Pid: 6024, comm: modprobe Not tainted 2.6.27.39-default #2
Call Trace:
On 2010-03-17, at 02:59, Gregory Matthews wrote:
Well, I'm no expert at reading the the kernel bugzilla but...
Gregory Matthews wrote:
BUG: using smp_processor_id() in preemptible [] code:
modprobe/6024
caller is set_ptldebug_header+0x41/0xa0 [libcfs]
Pid: 6024, comm: modprobe Not
I get lots of these errors when using Lustre with a preempt kernel.
Earlier discussions on this list suggested that preempt should work even
tho it used to be blocked during the build process.
This is with freshly compiled 1.8.2 patchless clients, vanilla 2.6.27.39
kernel on OpenSuse 10.3. The
