From: Borislav Petkov <petkov@uni-muenster.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Dave Airlie <airlied@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc2-mm4 drm and XFree oopses
Date: Wed, 29 Sep 2004 23:18:41 +0200 [thread overview]
Message-ID: <200409292318.41640.petkov@uni-muenster.de> (raw)
In-Reply-To: <1096484185.1600.50.camel@krustophenia.net>
On Wednesday 29 September 2004 20:56, Lee Revell wrote:
> On Wed, 2004-09-29 at 14:43, Denis Vlasenko wrote:
> > On Wednesday 29 September 2004 15:28, Dave Airlie wrote:
> > > It might help if you enabled AGP for your chipset, you have no agp
> > > compiled in for your Intel motherboard, you need intel agp chipset
> > > support..
> >
> > However kernel shouldn't use using smp_processor_id() in preemptible
> > regions, with or without Intel AGP support compuled in.
> >
I wonder _who_ is the user of smp_processor_id() in this case?
> > > > Sep 29 12:03:07 zmei kernel: [drm:radeon_cp_init] *ERROR*
> > > > radeon_cp_init called without lock held Sep 29 12:03:07 zmei kernel:
> > > > [drm:radeon_unlock] *ERROR* Process 2807 using kernel context 0 Sep
> > > > 29 12:03:07 zmei kernel: using smp_processor_id() in preemptible
> > > > code: XFree86/2807
>
> It looks like that code that uses smp_processor_id assumes that it has
> the DRM lock, but for whatever reason you don't have it.
>
> Lee
However, the above error concerning drm disappears after compiling in AGP.
What remains is the oops...
Regards,
Boris.
prev parent reply other threads:[~2004-09-29 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 10:28 Borislav Petkov
2004-09-29 12:28 ` Dave Airlie
2004-09-29 13:17 ` Borislav Petkov
2004-09-29 13:49 ` Dave Airlie
2004-09-29 14:43 ` Borislav Petkov
2004-09-29 14:57 ` Borislav Petkov
2004-09-29 18:43 ` Denis Vlasenko
2004-09-29 18:56 ` Lee Revell
2004-09-29 21:18 ` Borislav Petkov [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=200409292318.41640.petkov@uni-muenster.de \
--to=petkov@uni-muenster.de \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®