dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31732] X crashes with "X: radeon_texture.c:682: radeon_store_teximage: Assertion `0' failed."
Date: Fri, 19 Nov 2010 11:44:04 -0800 (PST)	[thread overview]
Message-ID: <20101119194404.4476613004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31732-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=31732

--- Comment #8 from Alex Schuster <wonko@wonkology.org> 2010-11-19 11:44:02 PST ---
Okay, so I compiled kernel 2.6.36-tuxonice-r1 with KMS enabled. During boot,
very soon after I entered my LUKS passphrae, the screen blanks. It comes back
when X has started. X and direct rendering sort of work, but syslog shows some
kernel nullpointer dereferences, I get only 50 frames with glxgears - quake3 is
not playable at all.

When I activated gallium again and restarted X, I I got a blank screen only. I
deactivated gallium and restarted X (I had entered a command that would do this
automatically after 2 minutes), and I got the KDM login screen, but no mouse or
keyboard.

BTW, with and without KVM, with and without gallium, I cannot switch to a text
console most of the time. Surprisingly, at this moment it just works, no idea
why.

I will avoid KVM for a while, and try newer X.org versions again. Or the fglrx
driver, but that did not seem to work either when I tried it some days ago. But
I did not reboot, I only unloaded the radeon module, maybe that was the
problem. I had fglrx running before I switched to radeon 2 months ago (as I
never had any success with the radeon driver before), but that seems to have
some memory leak, and my system was very slow. So I was happy when radeon
finally seemed to work. I had many artifacts when scrolling, especially when
KDE4's desktop effects were enabled, that went away with my the latest update
of X.org. But from then on I had the random crashes, today I had two already.

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

  parent reply	other threads:[~2010-11-19 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31732-502@http.bugs.freedesktop.org/>
2010-11-18 18:19 ` [Bug 31732] X crashes with "X: radeon_texture.c:682: radeon_store_teximage: Assertion `0' failed." bugzilla-daemon
2010-11-18 23:11 ` bugzilla-daemon
2010-11-18 23:37 ` bugzilla-daemon
2010-11-19  0:42 ` bugzilla-daemon
2010-11-19 11:59 ` bugzilla-daemon
2010-11-19 16:02 ` bugzilla-daemon
2010-11-19 19:44 ` bugzilla-daemon [this message]
2011-02-09 16:01 ` [Bug 31732] [RADEON:KMS:RS780:R600C-R600G] " bugzilla-daemon
2011-02-10  1:19 ` bugzilla-daemon
2012-02-22 18:03 ` 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=20101119194404.4476613004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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