https://bugzilla.kernel.org/show_bug.cgi?id=115911
--- Comment #4 from Jan Prunk ---
I am not in a position to help you with my own custom kernel compiling
however...
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=115911
Jan Prunk changed:
What|Removed |Added
CC||janprunk at gmail.com
--- Comment #5 from Ja
https://bugzilla.kernel.org/show_bug.cgi?id=116101
Bug ID: 116101
Summary: "Userspace still has active objects" and "trying to
unbind memory from uninitialized GART !" when
unbinding from radeon
Product: Drivers
V
https://bugzilla.kernel.org/show_bug.cgi?id=116101
Joe P. changed:
What|Removed |Added
Summary|"Userspace still has active |"RIP
|objects" and "trying to
https://bugzilla.kernel.org/show_bug.cgi?id=116101
Christian König changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Commen
https://bugzilla.kernel.org/show_bug.cgi?id=116101
--- Comment #2 from Joe P. ---
Right now the radeon card isn't being used for anything. I am using my Intel
iGPU as my output but using PRIME offloading to play games via the 290 (which
works fine). Sorry, I should have specified that in the orig
https://bugzilla.kernel.org/show_bug.cgi?id=116101
--- Comment #3 from Joe P. ---
(In reply to Christian König from comment #1)
> Well as the error message already suggests "Userspace still has active
> objects !" you have an application which is still using the hardware.
>
> So unbinding and r
https://bugzilla.kernel.org/show_bug.cgi?id=116101
--- Comment #4 from Christian König ---
It doesn't matter what OpenGL driver you currently use for the desktop. The
hardware is in use by something so unbinding can't work correctly.
Try "sudo lsof /dev/dri/card1" (or whatever number your Radeo
https://bugzilla.kernel.org/show_bug.cgi?id=67681
--- Comment #41 from KernelBug <3fdd1e5d at opayq.com> ---
Can someone PLEASE be kind enough to tell me if the kernel now has the support
for these functions for this laptop?
thank you
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=116101
Joe P. changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=116101
--- Comment #6 from Michel Dänzer ---
There's still a bug though â if unbinding can't work, it should be refused
upfront, not attempted anyway, breaking things.
--
You are receiving this mail because:
You are watching the assignee of the bug
https://bugzilla.kernel.org/show_bug.cgi?id=89661
Bernd Steinhauser changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=116251
Bug ID: 116251
Summary: radeon 5a427809cd9143bef89ee3110f45e84f37484218
"drm/radeon: disable runtime pm on PX laptop" makes
dGPU never stop
Product: Drivers
Versi
https://bugzilla.kernel.org/show_bug.cgi?id=116251
Eugene Shalygin changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=116251
--- Comment #1 from Michel Dänzer ---
Duplicate of bug 115321.
(In reply to Eugene Shalygin from comment #0)
> With kernel 4.5.1 the Radeon card is always on. Reverting
> 5a427809cd9143bef89ee3110f45e84f37484218 fixes the problem.
I did warn G
https://bugzilla.kernel.org/show_bug.cgi?id=116251
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 f
https://bugzilla.kernel.org/show_bug.cgi?id=115321
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 f
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #2 from Alex Deucher ---
Created attachment 212681
--> https://bugzilla.kernel.org/attachment.cgi?id=212681&action=edit
possible fix 2/2
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=116251
--- Comment #3 from Eugene Shalygin ---
Created attachment 212691
--> https://bugzilla.kernel.org/attachment.cgi?id=212691&action=edit
dmesg
dmesg with the commit reverted
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #3 from Christoph Haag ---
It does work for my laptop, so thanks for that. I guess if it was possible to
test at runtime for it you'd have done it, so we can only hope that there are
no other laptops with this problem..
--
You are r
https://bugzilla.kernel.org/show_bug.cgi?id=116251
--- Comment #4 from Alex Deucher ---
Created attachment 212711
--> https://bugzilla.kernel.org/attachment.cgi?id=212711&action=edit
possible fix
Please apply this patch on top of the patches from bug 115321.
--
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=116251
--- Comment #5 from Eugene Shalygin ---
With the quirk it works, thank you.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=103271
Amarildo changed:
What|Removed |Added
CC||amarildosjr at riseup.net
--- Comment #22 fro
https://bugzilla.kernel.org/show_bug.cgi?id=115251
--- Comment #3 from Bernd Steinhauser ---
Ping.
Was this forgotten? Afaics, it's still not applied to 4.5 stable (in 4.5.2).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=115251
--- Comment #4 from Alex Deucher ---
Greg still hasn't applied it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=114991
--- Comment #3 from M G Berberich ---
Created attachment 213751
--> https://bugzilla.kernel.org/attachment.cgi?id=213751&action=edit
crash with linux-4.5.2
crash with linux-4.5.2
journalctl --boot -1 _TRANSPORT=kernel
--
You are receiving th
https://bugzilla.kernel.org/show_bug.cgi?id=114991
--- Comment #4 from M G Berberich ---
Created attachment 213761
--> https://bugzilla.kernel.org/attachment.cgi?id=213761&action=edit
Xorg.log
The Xorg.log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=114991
--- Comment #5 from M G Berberich ---
I had another crash with oops in the logs with 4.5.2 stock kernel.
I attached the full output from
journalctl --boot -1 _TRANSPORT=kernel
and Xorg.log.old as requested.
--
You are receiving this mail bec
https://bugzilla.kernel.org/show_bug.cgi?id=117111
Bug ID: 117111
Summary: Quitting X with xrandr rotation enabled freezes vt
Product: Drivers
Version: 2.5
Kernel Version: 4.4.8
Hardware: x86-64
OS: Linux
Tree
https://bugzilla.kernel.org/show_bug.cgi?id=117131
Bug ID: 117131
Summary: vga_switcheroo does not switch IGP -> DIS ( IGP ==
i915 , DIS == radeon )
Product: Drivers
Version: 2.5
Kernel Version: 4.5.0
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #1 from Jason Vas Dias ---
Next steps: hacking X-Server & kernel drm & dri code to emit more debug log
messages .
Any suggestions as to how to bring up an X-Server on Radeon 8970M card when
Intel i915 IGP is active under Linux 4.5+ ?
https://bugzilla.kernel.org/show_bug.cgi?id=117131
3pb33h+1ymmkx54pslys at sharklasers.com changed:
What|Removed |Added
CC||3pb33h+1ymmkx54p
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #3 from Jason Vas Dias ---
(In reply to 3pb33h+1ymmkx54pslys from comment #2)
> Check this bug https://bugs.freedesktop.org/show_bug.cgi?id=95078
> Does it work if you revert that commit?
Thanks for the info ! But 'git revert e64c952
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #4 from Jason Vas Dias ---
Aha, so this ACPI call failure looks very fatal to any vga_switcheroo :
/**
* radeon_atpx_switch_start - notify the sbios of a GPU switch
*
* @atpx: atpx info struct
* @mux_id: mux state (0 = integrated
https://bugzilla.kernel.org/show_bug.cgi?id=117131
--- Comment #5 from Jason Vas Dias ---
OK, I tried adding 'radeon.dpm=1' to kernel command line:
fbcon=map:01 radeon.modeset=1 radeon.dpm=1 video=radeon:1920x1080 at 60e \
drm_kms_helper.edid_firmware=edid/1920x1080.bin
(I have copied a valid
https://bugzilla.kernel.org/show_bug.cgi?id=117151
Bug ID: 117151
Summary: amdgpu: Fails to initialize R7 260x (Bonaire)
Product: Drivers
Version: 2.5
Kernel Version: 4.6
Hardware: x86-64
OS: Linux
Tree: Mainl
https://bugzilla.kernel.org/show_bug.cgi?id=50091
Tom Wijsman changed:
What|Removed |Added
CC||kernel at gentoo.org
--- Comment #32 from T
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #7 from nucrap at hotmail.com ---
I have taken the time, read some how-to's and bisected the kernel. I have
managed narrow down the number responsible commits to 8.
Unfortunately out of some reason Xorg sincerely broke on my system (wi
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #8 from Alex Deucher ---
Created attachment 107198
--> https://bugzilla.kernel.org/attachment.cgi?id=107198&action=edit
possible fix
This patch should fix it.
--
You are receiving this mail because:
You are watching the assignee o
https://bugzilla.kernel.org/show_bug.cgi?id=60741
Bug ID: 60741
Summary: When using the 3.10 kernel, System boot is blocked on
the udev stage because of loading the radeon DRM
module
Product: Drivers
Version: 2.5
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #1 from Eastern Heart ---
3.8 is ok.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60741
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 fr
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #3 from Eastern Heart ---
(In reply to Alex Deucher from comment #2)
> I'm guessing you are getting a stall due to waiting for the firmware fetch
> to time out. Make sure your initrd contains the firmware if you are using
> one or if
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #4 from Alex Deucher ---
Might be a duplicate of bug 60674. Can you try the patch on that bug? If that
doesn't help, can you bisect?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #5 from Eastern Heart ---
(In reply to Alex Deucher from comment #4)
> Might be a duplicate of bug 60674. Can you try the patch on that bug? If
> that doesn't help, can you bisect?
I cannot try now... And I cannot even boot, not inc
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #6 from Alex Deucher ---
(In reply to Eastern Heart from comment #5)
> I cannot try now... And I cannot even boot, not incorrect display!
> I said, my boot paused when start the kernel radeon module.
> Sorry.
The patch is still be rel
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #7 from Eastern Heart ---
(In reply to Alex Deucher from comment #6)
> (In reply to Eastern Heart from comment #5)
> > I cannot try now... And I cannot even boot, not incorrect display!
> > I said, my boot paused when start the kernel
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #8 from Alex Deucher ---
(In reply to Eastern Heart from comment #7)
>
> Although I haven't apply this patch, can I ask: will this patch be merged to
> linux-3.10.7?
It should make it's way to 3.10 eventually. I'm not sure which 3.1
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #9 from Yves G. (theYinYeti) ---
Sorry for the long time without an answer; I was on holidays. Just to be clear:
the kernel (and associated packages for my setup) is the only component that
changes; here?s the exact list: linux, linux-
https://bugzilla.kernel.org/show_bug.cgi?id=60523
Tobias Droste changed:
What|Removed |Added
Kernel Version|drm-fixes-3.11 |drm-next-3.12-wip
Summary|Lock
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #17 from Alex Deucher ---
Does this patch help?
diff --git a/drivers/gpu/drm/radeon/cypress_dpm.c
b/drivers/gpu/drm/radeon/cypress_dpm.c
index 95a66db..a1d2503 100644
--- a/drivers/gpu/drm/radeon/cypress_dpm.c
+++ b/drivers/gpu/drm/ra
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #10 from nucrap at hotmail.com ---
Hey Alex, I was able to resolve my Xorg issue (it was due to no disk space
being left on the partition :s) and could fully test your patch.
I can gladly confirm that it fully fixes the issue!
Thanks f
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #18 from Tobias Droste ---
Doesn't help here.
But I can confirm that it works as soon as dpms is active and dpm switches to
power level 0. It stays at power level 0 after the monitors are active again
and I can echo things to power_dp
https://bugzilla.kernel.org/show_bug.cgi?id=60687
--- Comment #12 from Rafa? Mi?ecki ---
Fix posted:
[FIX][PATCH] drm/radeon: fix WREG32_OR macro setting bits in a register
http://lists.freedesktop.org/archives/dri-devel/2013-August/043835.html
--
You are receiving this mail because:
You are wa
https://bugzilla.kernel.org/show_bug.cgi?id=60709
--- Comment #18 from Rafa? Mi?ecki ---
Fix posted:
[FIX][PATCH] drm/radeon: fix WREG32_OR macro setting bits in a register
http://lists.freedesktop.org/archives/dri-devel/2013-August/043835.html
--
You are receiving this mail because:
You are wa
https://bugzilla.kernel.org/show_bug.cgi?id=60709
--- Comment #19 from Rafa? Mi?ecki ---
This is a duplicate of #60687 (I'm afraid I don't have privileges to close
this)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #19 from Christian Birchinger ---
Just to be totaly clear. In my case i only have one monitor in use. I don't use
any multi-head setup at the moment.
The rest is identical. dpms standby puts it to level 0, when it wakes up it's
also l
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #20 from Alex Deucher ---
Christian, Can you try this patch:
http://lists.freedesktop.org/archives/dri-devel/2013-August/043464.html
I the vblank period on your monitor is short enough that it's causing the
driver to select the multi-
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #21 from Christian Birchinger ---
No change here at all with those 2 patches. I'm attaching my boot dmesg just in
case my maybe weird setup (CRT monitor) does not cause anything special.
--
You are receiving this mail because:
You ar
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #22 from Christian Birchinger ---
Created attachment 107211
--> https://bugzilla.kernel.org/attachment.cgi?id=107211&action=edit
drm/radeon boot output
The relevant radeon and drm boot message output
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #23 from Alex Deucher ---
Ah, you have a system with gddr5 memory. The blanking period is probably too
short on your monitor to support mclk switching. Something like this will tell
you for sure:
diff --git a/drivers/gpu/drm/radeon/
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #24 from Christian Birchinger ---
Created attachment 107212
--> https://bugzilla.kernel.org/attachment.cgi?id=107212&action=edit
debug drm output
Yes, i get lots of output. Log is attached
--
You are receiving this mail because:
Y
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #25 from Christian Birchinger ---
So with the problem being the vblank i switched the resolutions using xrandr.
Using lower resolution modes makes it start switching.
~ $ xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximu
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #26 from Alex Deucher ---
In order to switch the mclk, the hw needs at least 450us. The vblank period of
the 1600x1200 mode is 396us, so it's not long enough to switch. The switch has
to happen during vblank to avoid seeing a flicker
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #27 from Tobias Droste ---
Isn't this the reason why there is a multi-monitor power state? same mclk but
different sclk for each power level? So switching between them should be no
problem because there's no memory reclocking happening
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #28 from Christian Birchinger ---
Ok thanks.
I was just in the middle of posting this:
With 1280x1024 it switched to power level 0 but without "single_disp".
With the really low 640x400 mode it did also use "single_disp".
But i now
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #29 from Alex Deucher ---
Correct. I'm not sure why that state sees to get stuck in the highest
performance level on your cards though.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #30 from Christian Birchinger ---
Maybe the same reason why Tobias is stuck at level 2.
Since i'm no longer able to use tools like xvidtune and the online modeline
calculator tells me 1600x1200 85hz requires >300Mhz pixel clock, so i'
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #31 from Alex Deucher ---
(In reply to Christian Birchinger from comment #30)
> Maybe the same reason why Tobias is stuck at level 2.
>
Right you both seem to be afflicted but the same issue.
> Since i'm no longer able to use tools
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #32 from Christian Birchinger ---
Yes, i did this:
xrandr --newmode "1600x1200_test" 229.5 1600 1664 1856 2160 1200 1201 1204
1250 +hsync +vsync
Puts my state to this:
uvdvclk: 0 dclk: 0
power level 0sclk: 15700 mclk: 3000
https://bugzilla.kernel.org/show_bug.cgi?id=60674
Ond?ej Svoboda changed:
What|Removed |Added
CC||ondrej at svobodasoft.cz
--- Comment #11
https://bugzilla.kernel.org/show_bug.cgi?id=60687
--- Comment #13 from Gabor Hasenfrasz ---
@Rafa?: I've tested the patch and solves the problem in my case. Thank you!
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60523
queryv+fd at gmail.com changed:
What|Removed |Added
CC||queryv+fd at gmail.com
--- Commen
https://bugzilla.kernel.org/show_bug.cgi?id=60674
Dave changed:
What|Removed |Added
CC||systemdkiosk at yopmail.com
--- Comment #12 from D
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #34 from queryv+fd at gmail.com ---
Created attachment 107241
--> https://bugzilla.kernel.org/attachment.cgi?id=107241&action=edit
full dmesg (HD6870)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60709
Torsten Krah changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=60687
Torsten Krah changed:
What|Removed |Added
CC||krah.tm at gmail.com
--- Comment #14 from
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #13 from Michel D?nzer ---
(In reply to Dave from comment #12)
> RV350 (Shivah) on AGP bus
[...]
> For us, switching the xorg.conf AccelMethod from EXA to glamor caused the
> mess. No problems occur under EXA.
I doubt an RV350 can han
https://bugzilla.kernel.org/show_bug.cgi?id=60687
--- Comment #15 from Rafa? Mi?ecki ---
Fix is in Linus's tree:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d43a93c8d9bc4e0dc0293b6458c077c3c797594f
Resolved, code fix?
--
You are receiving this mail because:
You ar
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #35 from pitamm at gmail.com ---
I have the same problem with HD5700. Since the others have attached dmesg
reports already, I am not including mine.
Unlike droste, when I do:
# echo high > power_dpm_force_performance_level
OR
# echo
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #36 from Tobias Droste ---
Hm I'm pretty sure the "stuck" power level is the same problem as the "write
error: Invalid argument" problem.
Are you sure you're in the correct directory before executing the command?
If you're not in '/s
https://bugzilla.kernel.org/show_bug.cgi?id=60687
Gabor Hasenfrasz changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=60687
--- Comment #16 from Gabor Hasenfrasz ---
@Rafa?: I've changed it to resolved, code fix. Sorry.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #14 from Dave ---
(In reply to Michel D?nzer from comment #13)
Michel you could well be 100% right. I'll simply add,
RV350 failures should emit X log outputs, not X crashes or worse,
hardware/driver/kernel crashes. Code should fail g
https://bugzilla.kernel.org/show_bug.cgi?id=60231
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
https://bugzilla.kernel.org/show_bug.cgi?id=60674
--- Comment #15 from Alex Deucher ---
(In reply to Dave from comment #14)
> (In reply to Michel D?nzer from comment #13)
>
> Michel you could well be 100% right.
While the symptoms may be similar, your issue is completely different, and not
kern
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #37 from Alex Deucher ---
I was finally able to reproduce this, but only with gcc 4.8. Older versions of
gcc work fine. Looks like the gcc bug has struck again. See:
https://bugs.freedesktop.org/show_bug.cgi?id=66932
Now to find wha
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #38 from Tobias Droste ---
I don't want to say that it's not a gcc bug, but I'm using gcc 4.7:
gcc version 4.7.2 20130108 [gcc-4_7-branch revision 195012] (SUSE Linux)
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #39 from Alex Deucher ---
Created attachment 107254
--> https://bugzilla.kernel.org/attachment.cgi?id=107254&action=edit
fix for 3.11
The attached patch seems to fix it for me.
--
You are receiving this mail because:
You are watch
https://bugzilla.kernel.org/show_bug.cgi?id=60775
Bug ID: 60775
Summary: Installing NVIDIA proprietary drivers on kernel
3.10.7-100.fc18.x86_64 errors out . . . can't find
kernel source files
Product: Drivers
Vers
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #40 from queryv+fd at gmail.com ---
(In reply to Alex Deucher from comment #39)
> Created attachment 107254 [details]
> fix for 3.11
>
> The attached patch seems to fix it for me.
That doesn't seem to fix it for me (6870). I first tri
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #41 from Alex Deucher ---
Well, it helps a little, but I'm still able to reproduce it eventually even
with the patch. The same kernel source is working fine on a fedora 16 system
and now exhibits this problem on Fedora 19. So maybe i
https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #42 from Alex Deucher ---
I can reproduce it in Fedora 17 as well (gcc 4.7). So it seems to be something
about Fedora 16 (gcc 4.6).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60775
--- Comment #1 from Ryan Letourneau ---
Just tried solution here
http://ewaldertl.blogspot.ca/2013/02/update-fedora-18-to-kernel-376-let-fail.html
but did not resolve issue
--
You are receiving this mail because:
You are watching the assignee o
https://bugzilla.kernel.org/show_bug.cgi?id=60231
prettyvanilla at posteo.at changed:
What|Removed |Added
Attachment #106381|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=60231
--- Comment #3 from prettyvanilla at posteo.at ---
Created attachment 107259
--> https://bugzilla.kernel.org/attachment.cgi?id=107259&action=edit
xrandr --verbose
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60231
--- Comment #4 from prettyvanilla at posteo.at ---
Created attachment 107260
--> https://bugzilla.kernel.org/attachment.cgi?id=107260&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=60231
--- Comment #5 from prettyvanilla at posteo.at ---
I am running a current mainline kernel until dpm stabilises, so I am on 3.11rc6
currently, which has the patch mentioned already applied. Sadly, no change in
behaviour.
I updated the dmesg output a
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #9 from Eastern Heart ---
(In reply to Alex Deucher from comment #8)
> (In reply to Eastern Heart from comment #7)
> >
> > Although I haven't apply this patch, can I ask: will this patch be merged to
> > linux-3.10.7?
>
> It should m
https://bugzilla.kernel.org/show_bug.cgi?id=60741
--- Comment #10 from Alex Deucher ---
Glad it's working. Please mark this bug as a duplicate of bug 60674.
--
You are receiving this mail because:
You are watching the assignee of the bug.
1301 - 1400 of 5870 matches
Mail list logo
