public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cliff white <cliffw@osdl.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: drm bugs hopefully fixed but there might still be one..
Date: Thu, 24 Mar 2005 13:58:51 -0800	[thread overview]
Message-ID: <20050324135851.388d1b4e@es175> (raw)
In-Reply-To: <Pine.LNX.4.58.0503241015190.7647@skynet>

On Thu, 24 Mar 2005 10:33:02 +0000 (GMT)
Dave Airlie <airlied@linux.ie> wrote:

> 
> Hi Andrew, Dave,
> 
> I've put a couple of patches into my drm-2.6 tree that hopefully fix up
> the multi-bridge on i915 and the XFree86 4.3 issue.. Andrew can you drop
> the two patches in your tree.. the one from Brice and the one I attached
> to the bug? you'll get conflicts anyway I'm sure. I had to modify Brices
> one as it didn't look safe to me in all cases..
> 
> I think their might be one left, but I think it only seems to be on
> non-intel AGP system, as in my system works fine for a combination of
> cards and X releases ... anyone with a VIA chipset and Radeon graphics
> card or r128 card.. testing the next -mm would help me a lot..

Okay, i have a iBook G4, with radeon, with 2.6.12-rc1-mm2, i'm getting the following OOPS
on boot. I'm hand-copying this stuff, please let me know if you need any more info, .config, etc
------------[drm] Initalized drm 1.0.0 20040925
floating point used in kernel (task=effc1770, pc=c03bd040)
Oops: kernel access of nad area, sig:11 [#1]
PREEMPT
NIP: C03BD040 LR: C01, cliffw80540 SP:
...
TASK = effc1770[1] 'swapper' THREAD: effc2000


LRL [c0180540] drm_agp_init+0x48/0xdc
Call trace:
 [c017e74c] drm_fill_in_dev+0xdc/0x180
 [c017eb44] drm_get_dev+0x78
 [c...] radeon_init
 [c...] do_initcalls
 [c..] init
 [c..] kernel_thread
---------------
cliffw

> 
> Dave.
> 
> -- 
> David Airlie, Software Engineer
> http://www.skynet.ie/~airlied / airlied at skynet.ie
> Linux kernel - DRI, VAX / pam_smb / ILUG
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
"Ive always gone through periods where I bolt upright at four in the morning; 
now at least theres a reason." -Michael Feldman

  parent reply	other threads:[~2005-03-24 21:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 10:33 drm bugs hopefully fixed but there might still be one Dave Airlie
2005-03-24 11:04 ` Andrew Morton
2005-03-24 17:02 ` Jesse Barnes
2005-03-24 18:18   ` Dave Jones
2005-03-24 18:35     ` Jesse Barnes
2005-03-24 21:58 ` cliff white [this message]
2005-03-24 22:21   ` Andrew Morton
2005-03-24 23:04     ` cliff white
2005-03-24 23:12       ` Andrew Morton
     [not found] <3LxV3-5Is-25@gated-at.bofh.it>
     [not found] ` <3LE0y-2Kn-55@gated-at.bofh.it>
     [not found]   ` <3LFg5-3MJ-37@gated-at.bofh.it>
     [not found]     ` <3LFzj-40t-15@gated-at.bofh.it>
2005-03-24 20:09       ` Jean Delvare

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=20050324135851.388d1b4e@es175 \
    --to=cliffw@osdl.org \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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