mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: RT and pci_lock while reading or writing pci bus configuration.
Date: Mon, 20 Feb 2006 20:45:06 +0100	[thread overview]
Message-ID: <1140464706.2480.762.camel@localhost.localdomain> (raw)
In-Reply-To: <200602201542.19857.Serge.Noiraud@bull.net>

On Mon, 2006-02-20 at 15:42 +0100, Serge Noiraud wrote:
> Hi,
> I have one question :
> In drivers/pci/access.c we have a global lock for pci configuration access.
> In pci_bus_read_config_* or pci_bus_write_config_* functions, we acquire a lock.
> When we call spin_lock_irqsave, we obtain the following message :
> BUG: scheduling while atomic: IRQ 137/0x00000001/6431
> caller is schedule+0x43/0x120
>  [<c01050ec>] dump_stack+0x1c/0x20 (20)
>  [<c03e7144>] __schedule+0xf44/0x1240 (236)
>  [<c03e7483>] schedule+0x43/0x120 (12)
>  [<c03e855b>] __down_mutex+0x2bb/0x5f0 (112)
>  [<c03ea08c>] _spin_lock_irqsave+0x1c/0x40 (24)
>  [<c023670d>] pci_bus_read_config_word+0x2d/0x70 (24)
>  
> Do I miss something or is it a BUG ?

Yeah, you missed to paste the full backtrace :)

Preempt count is 1, so you are calling pci_bus_read_config_word() from a
non preemptible context.

	tglx



  reply	other threads:[~2006-02-20 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 14:42 Serge Noiraud
2006-02-20 19:45 ` Thomas Gleixner [this message]
2006-02-22  9:16   ` Serge Noiraud
2006-02-22 13:51     ` Christoph Hellwig

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=1140464706.2480.762.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=serge.noiraud@bull.net \
    /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®