From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75211] Division error in radeon_compute_pll_avivo (X hang)
Date: Thu, 01 May 2014 16:30:41 +0000 [thread overview]
Message-ID: <bug-75211-2300-zenVNPekSg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75211-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #5 from Christian König <deathsimple@vodafone.de> ---
(In reply to Darren Salt from comment #4)
> It appears that you do actually need mismatched builds of xserver git and
> xf86-video-ati git, the latter built against (ideally) 1.15.99.902, to
> trigger this kernel bug... I wonder why it's gone apparently unnoticed until
> now. ☺
I've reworked that function for 3.15. It's likely that with mismatched DDX and
X you pass some parameters as zero into the kernel and so trigger a divide by
zero error.
Allready digging into this, just give me a day or two to catch up with the
bugs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-01 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 1:45 [Bug 75211] New: Division error in radeon_compute_pll_avivo (X hang) bugzilla-daemon
2014-05-01 9:55 ` [Bug 75211] " bugzilla-daemon
2014-05-01 9:57 ` bugzilla-daemon
2014-05-01 14:16 ` bugzilla-daemon
2014-05-01 15:16 ` bugzilla-daemon
2014-05-01 16:30 ` bugzilla-daemon [this message]
2014-05-01 17:08 ` bugzilla-daemon
2014-05-01 20:33 ` bugzilla-daemon
2014-05-02 12:29 ` bugzilla-daemon
2014-05-02 15:49 ` bugzilla-daemon
2014-05-03 15: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-75211-2300-zenVNPekSg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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