All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26199] New: kernel oops in 2.6.33 rc5 when dri is set to off in xorg.conf
Date: Sun, 24 Jan 2010 12:17:00 -0800 (PST)	[thread overview]
Message-ID: <bug-26199-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26199

           Summary: kernel oops in 2.6.33 rc5 when dri is set to off in
                    xorg.conf
           Product: DRI
           Version: XOrg CVS
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: phercek@gmail.com


Created an attachment (id=32797)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=32797)
dmesg with dri off and booting to X

If option dri is set to off and I'm booting to X then I get the oops. When it
is set to on (or I boot only to console) I do not get the oops. Still the
acceleration is not working when dri is set to on. It complains about dri
version mismatch which is strange since I compiled libdrm with
--enable-radeon-experimental-api and I recompiled xf86-video-ati and mesa only
after the new libdrm was installed. But this is probably a separate issue.
Anyway looks to me it should not be possible to make kernel oops so here is the
report. Ach, and it is an agp system but I never had any stability problems
with it on windows (also worked very well with 2.6.30 and agd5f's r6xx-r7xx-3d
drm module with agp 8x and even the fast writes).

I'll attach dmesg with the oops and also without it (a boot to console).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
--

             reply	other threads:[~2010-01-24 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 20:17 bugzilla-daemon [this message]
2010-01-24 20:18 ` [Bug 26199] kernel oops in 2.6.33 rc5 when dri is set to off in xorg.conf bugzilla-daemon
2010-01-25 16:00 ` bugzilla-daemon
2010-01-25 21:41 ` bugzilla-daemon
2010-01-25 21:42 ` bugzilla-daemon
2010-01-25 21:43 ` bugzilla-daemon
2010-01-25 21:47 ` bugzilla-daemon
2010-01-26 10:02 ` bugzilla-daemon
2010-01-26 11:35 ` bugzilla-daemon
2010-01-26 14:44 ` bugzilla-daemon
2010-01-30 14:24 ` bugzilla-daemon

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=bug-26199-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.