public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Borislav Petkov <petkov@uni-muenster.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm4 drm and XFree oopses
Date: Wed, 29 Sep 2004 22:28:35 +1000	[thread overview]
Message-ID: <21d7e99704092905284f48af35@mail.gmail.com> (raw)
In-Reply-To: <20040929102840.GA11325@none>

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

Dave.


On Wed, 29 Sep 2004 12:28:40 +0200, Borislav Petkov
<petkov@uni-muenster.de> wrote:
> Hi there people,
>    here are some fine, unresolved mutual exclusion issues. Sysinfo
>    attached.
> 
>    Regards,
>    Boris.
> 
> 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
> Sep 29 12:03:07 zmei kernel:  [dump_stack+23/27] dump_stack+0x17/0x1b
> Sep 29 12:03:07 zmei kernel:  [smp_processor_id+146/152] smp_processor_id+0x92/0x98
> Sep 29 12:03:07 zmei kernel:  [add_timer_randomness+274/313] add_timer_randomness+0x112/0x139
> Sep 29 12:03:07 zmei kernel:  [input_event+72/940] input_event+0x48/0x3ac
> Sep 29 12:03:07 zmei kernel:  [kbd_rate+76/156] kbd_rate+0x4c/0x9c
> Sep 29 12:03:07 zmei kernel:  [vt_ioctl+3430/6535] vt_ioctl+0xd66/0x1987
> Sep 29 12:03:07 zmei kernel:  [tty_ioctl+874/1075] tty_ioctl+0x36a/0x433
> Sep 29 12:03:07 zmei kernel:  [sys_ioctl+196/511] sys_ioctl+0xc4/0x1ff
> Sep 29 12:03:07 zmei kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
> Sep 29 12:03:07 zmei kernel: using smp_processor_id() in preemptible code: XFree86/2807
> Sep 29 12:03:07 zmei kernel:  [dump_stack+23/27] dump_stack+0x17/0x1b
> Sep 29 12:03:07 zmei kernel:  [smp_processor_id+146/152] smp_processor_id+0x92/0x98
> Sep 29 12:03:07 zmei kernel:  [add_timer_randomness+274/313] add_timer_randomness+0x112/0x139
> Sep 29 12:03:07 zmei kernel:  [input_event+72/940] input_event+0x48/0x3ac
> Sep 29 12:03:07 zmei kernel:  [kbd_rate+103/156] kbd_rate+0x67/0x9c
> Sep 29 12:03:07 zmei kernel:  [vt_ioctl+3430/6535] vt_ioctl+0xd66/0x1987
> Sep 29 12:03:07 zmei kernel:  [tty_ioctl+874/1075] tty_ioctl+0x36a/0x433
> Sep 29 12:03:07 zmei kernel:  [sys_ioctl+196/511] sys_ioctl+0xc4/0x1ff
> Sep 29 12:03:07 zmei kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
> 
> 
> 
>

  reply	other threads:[~2004-09-29 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 10:28 2.6.9-rc2-mm4 drm and XFree oopses Borislav Petkov
2004-09-29 12:28 ` Dave Airlie [this message]
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

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=21d7e99704092905284f48af35@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petkov@uni-muenster.de \
    /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