From: Joshua Kwan <joshk@mspencer.net>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [OOPS] 2.4.20-rc4-ac1 (also occurs 2.4.20-rc2-ac3) in radeon DRI for XFree86
Date: Wed, 27 Nov 2002 02:57:52 -0800 [thread overview]
Message-ID: <20021127025752.7c44482b.joshk@mspencer.net> (raw)
In-Reply-To: <200211270939.38410.m.c.p@wolk-project.de>
Not good! Not good!
Booted fine with no oops or DRI init errors while starting X.
and the quake3 test, alas:
- went into 640x480 correctly but would not display the opening movie;
- keyboard stopped responding and I had to hard-shutdown.
- i was wearing headphones too and I got some big static from my sound card :X
Looked okay, but it seems to not work all the way.
Compiling the driver gave me lots of warnings which I am not entirely sure appear in the kernels before those affected:
In file included from radeon_drv.c:35:
radeon_drv.h:846:2: warning: #warning PCI posting bug
In file included from drm_dma.h:33,
from radeon_drv.c:42:
drm_os_linux.h:16:2: warning: #warning the author of this code needs to read up on list_entry
In file included from radeon_cp.c:35:
radeon_drv.h:846:2: warning: #warning PCI posting bug
In file included from radeon_cp.c:36:
drm_os_linux.h:16:2: warning: #warning the author of this code needs to read up on list_entry
In file included from radeon_state.c:35:
radeon_drv.h:846:2: warning: #warning PCI posting bug
In file included from radeon_state.c:36:
drm_os_linux.h:16:2: warning: #warning the author of this code needs to read up on list_entry
In file included from radeon_mem.c:36:
radeon_drv.h:846:2: warning: #warning PCI posting bug
In file included from radeon_mem.c:37:
drm_os_linux.h:16:2: warning: #warning the author of this code needs to read up on list_entry
radeon_mem.c:135: warning: `print_heap' defined but not used
In file included from radeon_irq.c:37:
radeon_drv.h:846:2: warning: #warning PCI posting bug
In file included from radeon_irq.c:38:
drm_os_linux.h:16:2: warning: #warning the author of this code needs to read up on list_entry
this may or may not have caused the problem. bummer. I'm back on 2.4.20-rc2-ac2 right now, old reliable... and boy i need bed...3am where I am. i still have the diff lying around for reference.
night all -- josh
Rabid cheeseburgers forced Marc-Christian Petersen <m.c.p@wolk-project.de> to write this on Wed, 27 Nov 2002 09:39:38 +0100:
> Hi Joshua,
>
> > Ksymoops output follows.
> > I compiled Radeon DRM stuff into the kernel -- i845 agp support from
> > agapgart. I am using gcc-3.2 to compile. 100% reproducible (okay, i've been
> > spending too much time on bugzillas...) Feel the power of the oops.
>
> I've posted a similar oops with latest rc2 -AC kernel. I have an ATI Rage128
> card and also got those oops if using DRI.
>
> I hope Arjan may find the bug :)
>
> ciao, Marc
next prev parent reply other threads:[~2002-11-27 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 8:39 Marc-Christian Petersen
2002-11-27 9:39 ` Joshua Kwan
2002-11-27 9:58 ` Marc-Christian Petersen
2002-11-27 10:57 ` Joshua Kwan [this message]
2002-11-27 12:26 ` Marc-Christian Petersen
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 3:52 Joshua Kwan
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=20021127025752.7c44482b.joshk@mspencer.net \
--to=joshk@mspencer.net \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.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
all inboxes | Powered by JetHome®