[Bug 28342] New: When cold-booting gfx is messed up with latest drm-radeon-testing kernel
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Summary: When cold-booting gfx is messed up with latest drm-radeon-testing kernel Product: DRI Version: DRI CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: magnus@jensenligan.se
This only occurs when computer has been of for a long time (e.g over night) Does not work either when booting into gdm, or booting into console and loading radeon module manually. If i first boot an vanilla kernel and go into X then warm-boot into d-r-t kernel it will not show up anymore until next time i cold-boot. It seems like the drm is having troubles initializing my gfx output.
My gfx card is an agp hd3650 (rv635)
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Marc marvin24@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |marvin24@gmx.de
--- Comment #1 from Marc marvin24@gmx.de 2010-06-01 08:23:53 PDT --- me too! But I wouldn't say "cold boot". Here, just booting the disto kernel once and then booting the testing kernel also works. Chip is rs780.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #2 from Alex Deucher agd5f@yahoo.com 2010-06-01 08:56:15 PDT --- Can you bisect what change caused the problem?
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #3 from Magnus Jensen magnus@jensenligan.se 2010-06-01 11:32:23 PDT --- Marc, do you also have patched mesa and ddx? (Add r6xx/r7xx tiling support to mesa Alex Deucher ; Add r6xx/r7xx tiling support to the ddx Alex Deucher)
When replacing the packages individually with unpatched versions i still have error, i have to remove patches from both mesa and ddx, then i don't have this error. Tried with latest drm-radeon-testing from git.
At least this is the situation for me. I came to the conclusion by resetting using REISUB when trash output appears then reinstalling first ddx using no patches, then tried with unpatched mesa and patched ddx, then unpatched mesa & ddx and it worked!
So i am not 100% sure i will test some more with this.
(b.t.w i removed the whole patch set since it seemed a bad idea to run a half-patched driver but i can try with individual patches also if u think i should)
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #4 from Marc marvin24@gmx.de 2010-06-02 02:26:30 PDT --- Magnus: yes, I have the tiling patches applied to userspace and I think this is a tiling related bug, but I will check this later.
Alex: I guess the tiling patches are not bisectable enough to get a usefull result. Any suggestions?
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #5 from Marc marvin24@gmx.de 2010-06-02 10:04:19 PDT --- I donno how many times I rebooted my machine, but now it definitely will die earlier...
here my findings: I kept the userspace patches and tried kernel with and without tiling patches - no change, still crashes. Then I installed a newer distro kernel (maverick backport of 2.6.34, running Ubuntu lucid) -> works.
To make the long story short, crash or not to crash depends on whether plymouth is started or not. Uh! I normaly boot my self compiled kernels with "verbose", while the distro kernels boot with "quiet splash".
I guess plymouth initializes something the ddx doesn't.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #6 from Alex Deucher agd5f@yahoo.com 2010-06-02 10:07:43 PDT --- (In reply to comment #5)
I guess plymouth initializes something the ddx doesn't.
With kms, neither one touches the hw. It all goes through the drm.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #7 from Marc marvin24@gmx.de 2010-06-02 10:16:05 PDT --- so it must be something else - I'll take a look at plymouth source.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #8 from Magnus Jensen magnus@jensenligan.se 2010-06-02 10:52:21 PDT --- I use gdm, so maybe it's something gnome related? Isn't plymouth some continuation off gdm? It doesn't help when starting X straight into gnome with startx either, I think i even tried with twm but i guess the gnome stuff could be started anyway somehow. I haven't had any time today really to do any more testing, but i hope i can test some things later.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #9 from Alex Deucher agd5f@yahoo.com 2010-06-02 10:55:55 PDT --- Neither gdm nor plymouth touches the hw. Perhaps this is a dupe of bug 28327. Does the patch I posted there help?
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #10 from Magnus Jensen magnus@jensenligan.se 2010-06-02 14:17:52 PDT --- Created an attachment (id=36021) --> (https://bugs.freedesktop.org/attachment.cgi?id=36021) dmesg-lockups
After the patch the card gets inited, at least but i get gpu crashes when running gdm and firefox here's the dmesg utput when gdm and firefox crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #11 from Magnus Jensen magnus@jensenligan.se 2010-06-02 14:19:34 PDT --- sorry, to be clearer: the programs doesn't crash the gpu just crashes and recover with trashed image as result
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #12 from Marc marvin24@gmx.de 2010-06-02 14:28:00 PDT --- here it crashes hard as soon as X starts, no dmesg available. plymouth renders something to the framebuffer during boot process. Not all distros are using this (I know of Ubuntu and Fedora).
Magnus: can you try with tiling patches in kernel + mesa, but without patched ddx?
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #13 from Magnus Jensen magnus@jensenligan.se 2010-06-02 15:29:23 PDT --- Marc: I did what you suggested and now everything works fine (inited ok, no gpu lockups) I also updated xorg server to 1.8.1.901 (from 1.8.1) This is with the patch Alex suggested
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #14 from Magnus Jensen magnus@jensenligan.se 2010-06-02 15:46:52 PDT --- I decided to do one final test an found it works with just setting "ColorTiling" "off" in xorg.conf and all patches in both userspace and kernelspace intact.
Much easier than recompiling/switching packages over and over if u just want to workaround the problem for now.
(Haven't tried to do an cold boot to see if init works yet but i'll try it right away.)
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #15 from Alex Deucher agd5f@yahoo.com 2010-06-02 16:14:22 PDT --- (In reply to comment #14)
I decided to do one final test an found it works with just setting "ColorTiling" "off" in xorg.conf and all patches in both userspace and kernelspace intact.
colortiling is off by default and is automatically disabled if your kernel is not new enough. Lets try and clarify what the problem is. Try the following configurations (start each one from with a cold boot):
1. drm-radeon-testing + the patch from bug 28327. No patches to ddx or mesa. No tiling options in your config
2. drm-radeon-testing + the patch from bug 28327. ddx and mesa patch with tiling patches. no tiling options in your config.
And report back what happens.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #16 from Marc marvin24@gmx.de 2010-06-03 02:52:38 PDT --- Magnus: disabling tiling is not a real solution.
Alex: case 1: stable case 2: crash
I'm still wondering why running plymouth before seems to cure the problem.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #17 from Magnus Jensen magnus@jensenligan.se 2010-06-03 03:14:59 PDT --- Marc: Well that's my bad, it's not a solution. But it seems the problem is there even if tiling is turned off.
Alex:
Same results as Marc. stable in case 1, in case 2 not.
When it crashes the output on half the screen looks like the dmesg output just before fbcon starts, the boot messages that's lost because of loading radeon module. Then the screen goes black and there's just the pointer on screen.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #18 from Magnus Jensen magnus@jensenligan.se 2010-06-03 07:22:27 PDT --- I tried using built-in solution for kernel, and now it's a bit different in case 2 It just crashes once on starting X then seems to work fine for the rest of the session and looks to be stable after an warm boot (so far, so good).
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #19 from Alex Deucher agd5f@yahoo.com 2010-06-03 08:29:38 PDT --- In the case 2 crash, does the system hang or do you get a kernel oops? Can you still access the machine over the network? Is there any chance you could boot up without loading the radeon kernel module then load it manually after you've booted? Also, is there any chance you can get the xorg log and dmesg from case 2?
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #20 from Magnus Jensen magnus@jensenligan.se 2010-06-03 13:43:17 PDT --- (In reply to comment #19)
In the case 2 crash, does the system hang or do you get a kernel oops? Can you still access the machine over the network? Is there any chance you could boot up without loading the radeon kernel module then load it manually after you've booted? Also, is there any chance you can get the xorg log and dmesg from case 2?
OK, i compiled radeon as module (still have the patch from bug #28327) in kernelso i can blacklist it and load it from console before starting. All patches are in userspace, so this is case 2 test again. It does not hang it crashes randomly giving gpu lockup messages in dmesg. And it really crashes RANDOMLY sometimes when starting X it crashes over and over making X unusuble, sometimes just 1 time at x startup then seems stable after that. very strange. I think using built in radeon in kernel seems to give much less crashes. I attach what u wanted from this test.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #21 from Magnus Jensen magnus@jensenligan.se 2010-06-03 13:43:49 PDT --- Created an attachment (id=36037) --> (https://bugs.freedesktop.org/attachment.cgi?id=36037) /var/log/dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #22 from Magnus Jensen magnus@jensenligan.se 2010-06-03 13:44:16 PDT --- Created an attachment (id=36038) --> (https://bugs.freedesktop.org/attachment.cgi?id=36038) output from dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #23 from Magnus Jensen magnus@jensenligan.se 2010-06-03 13:44:47 PDT --- Created an attachment (id=36039) --> (https://bugs.freedesktop.org/attachment.cgi?id=36039) /var/log//Xorg.0.log
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #24 from Alex Deucher agd5f@yahoo.com 2010-06-03 13:55:55 PDT --- Created an attachment (id=36040) View: https://bugs.freedesktop.org/attachment.cgi?id=36040 Review: https://bugs.freedesktop.org/review?bug=28342&attachment=36040
diable createpixmap2
Does this ddx patch help? try case 2 with this patch applied to the ddx on top of the tiling patches.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #25 from Magnus Jensen magnus@jensenligan.se 2010-06-03 14:52:26 PDT --- Created an attachment (id=36042) --> (https://bugs.freedesktop.org/attachment.cgi?id=36042) dmesg after patch
This is after patch, still crashes
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #26 from Magnus Jensen magnus@jensenligan.se 2010-06-03 14:52:59 PDT --- Created an attachment (id=36043) --> (https://bugs.freedesktop.org/attachment.cgi?id=36043) Xorg.0.log after patch
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Magnus Jensen magnus@jensenligan.se changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #36042|0 |1 is obsolete| |
--- Comment #27 from Magnus Jensen magnus@jensenligan.se 2010-06-03 14:54:47 PDT --- Created an attachment (id=36044) --> (https://bugs.freedesktop.org/attachment.cgi?id=36044) dmesg before was wrong this is with right kernel
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #36040|0 |1 is obsolete| |
--- Comment #28 from Alex Deucher agd5f@yahoo.com 2010-06-03 15:34:00 PDT --- Created an attachment (id=36045) View: https://bugs.freedesktop.org/attachment.cgi?id=36045 Review: https://bugs.freedesktop.org/review?bug=28342&attachment=36045
emit DB_DEPTH_INFO
Try this ddx patch in case 2 instead of the last patch I attached.
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #29 from Magnus Jensen magnus@jensenligan.se 2010-06-03 23:43:31 PDT --- (In reply to comment #28)
Created an attachment (id=36045)
View: https://bugs.freedesktop.org/attachment.cgi?id=36045 Review: https://bugs.freedesktop.org/review?bug=28342&attachment=36045
emit DB_DEPTH_INFO
Try this ddx patch in case 2 instead of the last patch I attached.
Yes, that fixes it for me!
Thanks!
https://bugs.freedesktop.org/show_bug.cgi?id=28342
--- Comment #30 from Marc marvin24@gmx.de 2010-06-06 09:00:05 PDT --- last patch also fixes X startup here, but now I'm hit by
https://bugs.freedesktop.org/show_bug.cgi?id=28381
https://bugs.freedesktop.org/show_bug.cgi?id=28342
Fabio Pedretti fabio.ped@libero.it changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #31 from Fabio Pedretti fabio.ped@libero.it 2010-11-05 07:03:37 PDT --- The patch was merged to ddx.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org