Bug 36783 - Radeon {M} and VGASWITCHEROO deadly mix
Summary: Radeon {M} and VGASWITCHEROO deadly mix
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-02 13:40 UTC by Cedric Sodhi
Modified: 2014-01-10 14:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (51.44 KB, patch)
2011-05-02 13:43 UTC, Cedric Sodhi
no flags Details | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Sodhi 2011-05-02 13:40:44 UTC
I can't tell much more than that.

WITH or WITHOUT "Cedar" firmware compiled into the kernel, the combination VGASWITCHEROO && Radeon (+KMS) {M} && i915 (+KMS) {M} && AGP {M} && <other relevant items as {M}> causes problems, log attached, I think it speaks for itsself.

Readeon and Intel being {M} is enough for this to happen.
Comment 1 Cedric Sodhi 2011-05-02 13:43:48 UTC
Created attachment 46262 [details] [review]
dmesg
Comment 2 Nikolay Antonov 2011-05-03 10:56:29 UTC
(In reply to comment #0)
> I can't tell much more than that.
> 
> WITH or WITHOUT "Cedar" firmware compiled into the kernel, the combination
> VGASWITCHEROO && Radeon (+KMS) {M} && i915 (+KMS) {M} && AGP {M} && <other
> relevant items as {M}> causes problems, log attached, I think it speaks for
> itsself.
> 
> Readeon and Intel being {M} is enough for this to happen.

Same problem affects me: https://bugzilla.kernel.org/show_bug.cgi?id=30052
Comment 3 Alex Deucher 2011-10-05 06:23:11 UTC
Is this still an issue with kernel 3.1?
Comment 4 Alex Deucher 2014-01-09 20:48:20 UTC
Is this still an issue with a newer kernel?
Comment 5 Cedric Sodhi 2014-01-10 08:26:18 UTC
Can't tell, as I don't possess the h/w any more. Feel free to close.


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.