From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 17201] Kernel NULL pointer dereference in r600_ioctl_wait_idle
Date: Wed, 8 Sep 2010 07:30:56 GMT [thread overview]
Message-ID: <201009080730.o887Uuxf024057@demeter1.kernel.org> (raw)
In-Reply-To: <bug-17201-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=17201
--- Comment #7 from Duncan <1i5t5.duncan@cox.net> 2010-09-08 07:30:47 ---
[I filed #17702, the dup.]
There's apparently something else happening, too. Because with the patch,
2.6.36-rc3 gets farther than it did before, X starts, but it consistently
freezes (hard kernel freeze, Magic-SRQ fails, hard-reset time) before I hit the
desktop, while without the patch, it soft-freezes (X has gobbled the keyboard
and VT-switching is dead, but I can Magic-SRQ-R, then C-A-Del to reboot) while
it's still black-screened, before the KDE splash.
Meanwhile, reverting the original commit
(4437579efca258e3c4a09f59838c8f933611990 as mentioned in bug #17702),
everything works fine, just as it did with earlier kernels. So there's
obviously something still wrong with the code-path after the patch, or it
wouldn't be hard-freezing the kernel.
Also, as with the original bug after the commit, if I set disable dri in
xorg.conf.d, everything works, but of course without accelerated 3D.
Unfortunately, while I could get a log after the soft freeze, that's not
possible now, as it's a hard freeze. But we know the commit that does it, and
the patch above does at least allow X to start; it just hard-kernel freezes
before it hits the full kde (4.5.0, I've not upgraded to 4.5.1 yet)
plasma-desktop.
So either this bug needs reopened, or I can reopen mine or file a new one.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
--
next prev parent reply other threads:[~2010-09-08 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 19:50 [Bug 17201] New: Kernel NULL pointer dereference in r600_ioctl_wait_idle bugzilla-daemon
2010-08-28 19:53 ` [Bug 17201] " bugzilla-daemon
2010-08-29 0:22 ` bugzilla-daemon
2010-08-29 12:43 ` bugzilla-daemon
2010-09-02 21:44 ` bugzilla-daemon
2010-09-05 22:09 ` bugzilla-daemon
2010-09-05 22:09 ` bugzilla-daemon
2010-09-05 22:10 ` bugzilla-daemon
2010-09-08 7:30 ` bugzilla-daemon [this message]
2010-09-12 19:05 ` 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=201009080730.o887Uuxf024057@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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.