mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <gl@dsa-ac.de>
To: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.18-rt6] BUG / typo
Date: Wed, 25 Oct 2006 13:09:37 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0610251247460.1852@pcgl.dsa-ac.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0610241512500.1852@pcgl.dsa-ac.de>

Hi again

Just a bit more detail to the way the bug occurs: you just need

CONFIG_LATENCY_TIMING=y

and in my case I had 2 consoles: tty1 and ttyS0. tty1 is a framebuffer. I 
don't know where irqs get disabled (the original BUG was

BUG: scheduling with irqs disabled: posix_cpu_timer/0x00000001/2
caller is rt_spin_lock_slowlock+0xd8/0x1c8

but is it at all ok to schedule in kmalloc(GFP_ATOMIC)? Which is exactly 
what happens here as kmalloc tries to acquire the per-cpu "spinlock" / 
mutex slab_irq_locks and is forced into the slow path.

The bug often triggers when I reset /proc/sys/kernel/preempt_max_latency 
with 0 and if I have high enough console logging level in 
/proc/sys/kernel/printk.

Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany

      reply	other threads:[~2006-10-25 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24  8:00 Guennadi Liakhovetski
2006-10-24  8:17 ` Guennadi Liakhovetski
2006-10-24 12:14   ` Guennadi Liakhovetski
2006-10-24 13:14     ` Guennadi Liakhovetski
2006-10-25 11:09       ` Guennadi Liakhovetski [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=Pine.LNX.4.63.0610251247460.1852@pcgl.dsa-ac.de \
    --to=gl@dsa-ac.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®