Bug 73297 - Xorg crashes with kernel 3.13-rc7
Summary: Xorg crashes with kernel 3.13-rc7
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-05 11:04 UTC by Anton Sudak
Modified: 2019-11-19 08:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kern.log (85.39 KB, text/plain)
2014-01-05 11:04 UTC, Anton Sudak
no flags Details

Description Anton Sudak 2014-01-05 11:04:46 UTC
Created attachment 91514 [details]
kern.log

With kernel 3.13-rc7 xorg crashes after few seconds after start.

My configuration
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks [Radeon HD 7650A/7670A]

Ubuntu 13.10, kernel 3.13-rc7, Mesa 10.0, libdrm and Xorg radeon driver from git.
Comment 1 Michel Dänzer 2014-01-06 03:47:12 UTC
Assuming this is a regression, can you bisect?
Comment 2 Alex Deucher 2014-01-06 15:12:29 UTC
Probably a duplicate of bug 70687.
Comment 3 Anton Sudak 2014-01-07 22:43:43 UTC
(In reply to comment #2)
> Probably a duplicate of bug 70687.

Looks like my issue is really duplicate. Logs are similar and workaround from comment #13 worked for me.

*** This bug has been marked as a duplicate of bug 70687 ***
Comment 4 Anton Sudak 2014-01-11 11:26:54 UTC
Reopen this bug. My problem wasn't resolved by commit from bug 70687.

I tried to do bisect, but some kernels stucks on load, so I was unable to get logs and find if error replicated on this kernel.

As I said in previous comment workaround with disabling CONFIG_HOTPLUG_PCI_ACPI works for me. Also, I can say that this bug doesn't present in 3.12 branch, but kernels starting from 3.13-rc1 are affected.
Comment 5 Anton Sudak 2014-01-21 09:13:22 UTC
Cannot replicate on 3.13 release, closing.
Comment 6 Anton Sudak 2014-02-11 21:05:40 UTC
Still suffering from this bug. My fault, I forgot, that I added radeon.runpm=1 option to kernel. This option cause X to start normally, but without radeon videocard. I desribed this in bug 74211. I can mark that bug as duplicate of this one, if needed.
I can replicate this bug on 3.14-rc2.
Comment 7 Alex Deucher 2014-02-12 03:44:25 UTC
(In reply to comment #6)
> Still suffering from this bug. My fault, I forgot, that I added
> radeon.runpm=1 option to kernel. This option cause X to start normally, but
> without radeon videocard. I desribed this in bug 74211. I can mark that bug
> as duplicate of this one, if needed.
> I can replicate this bug on 3.14-rc2.

You may be seeing this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=69901
Try the patch on that bug.
Comment 8 Anton Sudak 2014-02-12 14:32:16 UTC
Alex,

I tried to compile lastest kernel from git which contains that patch. But result is same - gdm appears for few seconds and than Xorg crashes. I can provide logs with 3.14 kernel little later.
Comment 9 Alex Deucher 2014-02-12 14:52:50 UTC
It's not clear to me how this bug is related or not related to bug 74211.  What do you do differently to get those symptoms vs. these symptoms?
Comment 10 Anton Sudak 2014-02-12 16:55:02 UTC
I belive that this two bugs are related and possibly bug 74211 is duplicate. If you look at logs you can see that there are same traces (search for drm_mm_takedown+0x2f/0x40). I can be wrong, but I think that the same problem occurs in different time.

In this bug radeon module crashes when xorg tries to use it and this cause Xorg to crash too. I closed this bug mistakenly, I added radeon.runpm=1 flag and forgot about this. This flag cause radeon module to crash before Xorg start so I thinked that my bug was resolved.
In bug 74211 I runned kernel with radeon.runpm=1 and radeon module crashes before Xorg start, so X finds only one working module - i915 and that's why it starts normally and I don't see my Radeon videocard.
Comment 11 Martin Peres 2019-11-19 08:41:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/422.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.