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: Tue, 24 Oct 2006 14:14:23 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0610241408000.1852@pcgl.dsa-ac.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0610241003280.1852@pcgl.dsa-ac.de>

On Tue, 24 Oct 2006, Guennadi Liakhovetski wrote:

> On Tue, 24 Oct 2006, Guennadi Liakhovetski wrote:
>
>> [22644.590000] BUG: scheduling with irqs disabled: 
>> posix_cpu_timer/0x00000001/2
>> [22644.590000] caller is schedule+0x10/0x118
> [...]
>
> Hm, got the same BUG with the patch from the previous email. Looking further, 
> unless somebody has an idea?

Could the reason have been that I in my (pxa) timer ISR had 
irq_enter()/_exit around the call to handle_event, as suggested in 
i386/kernel/apic.c:

 	/*
 	 * update_process_times() expects us to have done irq_enter().
 	 * Besides, if we don't timer interrupts ignore the global
 	 * interrupt lock, which is the WrongThing (tm) to do.
 	 */
 	irq_enter();
 	/*
 	 * If the task is currently running in user mode, don't
 	 * detect soft lockups.  If CONFIG_DETECT_SOFTLOCKUP is not
 	 * configured, this should be optimized out.
 	 */
 	if (user_mode(regs))
 		touch_softlockup_watchdog();

 	evt->event_handler(regs);
 	irq_exit();

? Anyway, I cannot SEEM to reproduce it anymore now I've removed those 
calls. Will test further.

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

  reply	other threads:[~2006-10-24 12:14 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 [this message]
2006-10-24 13:14     ` Guennadi Liakhovetski
2006-10-25 11:09       ` Guennadi Liakhovetski

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.0610241408000.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®