From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15969] New: radeon regression couldn't schedule IB on resume with 2.6.34-rc7
Date: Thu, 13 May 2010 19:06:41 GMT [thread overview]
Message-ID: <bug-15969-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=15969
Summary: radeon regression couldn't schedule IB on resume with
2.6.34-rc7
Product: Drivers
Version: 2.5
Kernel Version: 2.6.34-rc7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: cedric@belbone.be
Regression: Yes
Created an attachment (id=26367)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26367)
kernel config
Hello,
When resuming my laptop from a -rc7, my X session reacted weirdly.
Reading the dmesg log, I had :
May 12 21:58:03 enea kernel: [ 122.627332] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(0).
May 12 21:58:03 enea kernel: [ 122.627342] [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
May 12 21:58:03 enea kernel: [ 123.251198] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(1).
May 12 21:58:03 enea kernel: [ 123.251207] [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
May 12 21:58:04 enea kernel: [ 123.626341] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(2).
May 12 21:58:04 enea kernel: [ 123.626351] [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
May 12 21:58:04 enea kernel: [ 124.256505] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(3).
May 12 21:58:04 enea kernel: [ 124.256514] [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
May 12 21:58:05 enea kernel: [ 124.626191] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(4).
May 12 21:58:05 enea kernel: [ 124.626200] [drm:radeon_cs_ioctl] *ERROR* Faild
to schedule IB !
May 12 21:58:05 enea kernel: [ 125.059095] [drm:radeon_ib_schedule] *ERROR*
radeon: couldn't schedule IB(5).
And so on until IB(15)
This was not the case with a -rc5 kernel nor with a kernel without KMS
(radeon.modeset=0).
Bisection gives me (on drivers/gpu):
# bad: [b57f95a38233a2e73b679bea4a5453a1cc2a1cc9] Linux 2.6.34-rc7
# good: [01bf0b64579ead8a82e7cfc32ae44bc667e7ad0f] Linux 2.6.34-rc5
git bisect start 'v2.6.34-rc7' 'v2.6.34-rc5' '--' 'drivers/gpu/'
# bad: [3515387ba90ef2c38602f4d52c4d5ec5fc95ae5c] drm/radeon/kms: fix panel
scaling adjusted mode setup
git bisect bad 3515387ba90ef2c38602f4d52c4d5ec5fc95ae5c
# good: [88b045077a1462a47503137fd4ca0c31772819ca] drm/radeon: Fix sparc
regression in r300_scratch()
git bisect good 88b045077a1462a47503137fd4ca0c31772819ca
# bad: [404b017d00a9f472bdf725a06892d42f1cba5ed8] drivers/gpu/drm/drm_memory.c:
fix check for end of loop
git bisect bad 404b017d00a9f472bdf725a06892d42f1cba5ed8
# bad: [ccb2ad579f910e6146adf4eb3aa50325253ee8c9] drm/radeon/kms/agp The wrong
AGP chipset can cause a NULL pointer dereference
git bisect bad ccb2ad579f910e6146adf4eb3aa50325253ee8c9
with 797fd5b9dad12a100c81b5782573a41259728cb1 being the culprit
commit 797fd5b9dad12a100c81b5782573a41259728cb1
Author: Marek Olšák <maraeo@gmail.com>
Date: Tue Apr 13 02:33:36 2010 +0200
drm/radeon/kms: r300 fix CS checker to allow zbuffer-only fastfill
Signed-off-by: Marek Olšák <maraeo@gmail.com>
--
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.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2010-05-13 19:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 19:06 bugzilla-daemon [this message]
2010-05-13 19:08 ` [Bug 15969] radeon regression couldn't schedule IB on resume with 2.6.34-rc7 bugzilla-daemon
2010-05-13 20:30 ` bugzilla-daemon
2010-05-13 20:32 ` bugzilla-daemon
2010-05-13 21:01 ` bugzilla-daemon
2010-05-14 8:58 ` bugzilla-daemon
2010-05-14 9:27 ` bugzilla-daemon
2010-05-14 16:47 ` bugzilla-daemon
2010-05-16 10:44 ` bugzilla-daemon
2010-05-16 12:10 ` bugzilla-daemon
2010-05-17 9:53 ` bugzilla-daemon
2010-05-19 12:21 ` bugzilla-daemon
2010-05-19 12:24 ` bugzilla-daemon
2010-05-19 13:55 ` bugzilla-daemon
2010-05-19 13:56 ` bugzilla-daemon
2010-05-21 12:21 ` bugzilla-daemon
2010-05-21 14:03 ` bugzilla-daemon
2010-05-27 22:08 ` bugzilla-daemon
2010-05-27 22:16 ` bugzilla-daemon
2010-05-28 20:09 ` bugzilla-daemon
2010-05-31 13:42 ` bugzilla-daemon
2010-05-31 13:54 ` bugzilla-daemon
2010-05-31 14:44 ` bugzilla-daemon
2010-06-13 11:54 ` bugzilla-daemon
2010-06-13 11:54 ` 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-15969-2300@https.bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox