From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46161] divide error on radeon modprobe
Date: Mon, 3 Sep 2012 14:04:11 +0000 (UTC) [thread overview]
Message-ID: <20120903140411.CC9EB11FC25@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-46161-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=46161
--- Comment #1 from Michel Dänzer <michel@daenzer.net> 2012-09-03 14:04:11 ---
(In reply to comment #0)
> This started happening in 3.6-rc1 and is still in rc2. It does happen on 3.5.1
> and 3.5.2 if the radeon module is manually loaded a second time after boot.
So, do I understand this correctly: With 3.5.x it only happens after the radeon
kernel module was loaded a second time, but with 3.6-rc* it even happens after
it was loaded for the first time? If so, can you bisect what introduced the
change in behaviour for 3.6-rc*?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- 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:[~2012-09-03 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-46161-2300@https.bugzilla.kernel.org/>
2012-08-30 17:00 ` [Bug 46161] divide error on radeon modprobe bugzilla-daemon
2012-09-03 14:04 ` bugzilla-daemon [this message]
2012-09-03 19:37 ` bugzilla-daemon
2012-09-03 21:58 ` bugzilla-daemon
2012-09-03 22:26 ` bugzilla-daemon
2013-11-19 23:31 ` [Bug 46161] [BISECTED]divide " bugzilla-daemon
2013-11-20 14:24 ` bugzilla-daemon
2013-11-20 14:28 ` bugzilla-daemon
2013-11-20 16:13 ` bugzilla-daemon
2013-11-20 16:13 ` 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=20120903140411.CC9EB11FC25@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