From: Kevin Winchester <kjwinchester@gmail.com>
To: torvalds@linux-foundation.org
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.sf.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Radeon KMS regression still present in 2.6.33-rc6
Date: Sat, 30 Jan 2010 13:18:19 -0400 [thread overview]
Message-ID: <1264871899.1533.6.camel@localhost.localdomain> (raw)
I'm not quite sure if this can be called a regression, since radeon KMS
is still in staging as far as I know, but it was working quite well for
me up until about -rc3, and now it causes a panic on every boot. If I
pass radeon.modeset=0 on the command line, everything works.
I took a picture of the crash details:
http://picasaweb.google.ca/kjwinchester/LinuxKernelPanic#5432580230065271634
I was hoping that the last pull of DRM fixes would correct the issue,
but unfortunately they had no effect.
In case it helps, here is the gdb listing for the problem address:
(gdb) l *(radeon_agp_init+0x1d)
0xffffffff811c1592 is in radeon_agp_init (drivers/gpu/drm/radeon/radeon_agp.c:136).
131 uint32_t agp_status;
132 int default_mode;
133 bool is_v3;
134 int ret;
135
136 if (rdev->ddev->agp->agp_info.aper_size < 32) {
137 dev_warn(rdev->dev, "AGP aperture to small (%dM) "
138 "need at least 32M, disabling AGP\n",
139 rdev->ddev->agp->agp_info.aper_size);
140 return -EINVAL;
Is there any other info I can provide?
Thanks,
--
Kevin Winchester
next reply other threads:[~2010-01-30 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 17:18 Kevin Winchester [this message]
2010-01-30 17:43 ` Linus Torvalds
2010-01-30 19:50 ` Johannes Hirte
2010-01-30 19:54 ` Linus Torvalds
2010-01-30 20:49 ` John Kacur
2010-01-31 0:29 ` Kevin Winchester
2010-02-01 18:56 ` Linus Torvalds
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=1264871899.1533.6.camel@localhost.localdomain \
--to=kjwinchester@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®