https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #15 from Stas Sergeev ---
> I should mention, my pwm1_min is 0 and pwm1_max is 255.
Same here.
IMHO pwm1_min should contain the value that
keeps the fan rotating at a minimal safe speed.
Putting 0 there makes it entirely useless.
--
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #14 from Jimi ---
I should mention, my pwm1_min is 0 and pwm1_max is 255.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #13 from Jimi ---
That's interesting. My pwm1_enable returns 1, and trying to change it to 0 or 2
does nothing, but my pwm1 value does indeed change on its own, and I've never
seen it be 0. It sounds like I don't have this bug but do
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #5 from Andre ---
eh, do what? ..may if you give complete howto for my sabayon/gentoo system?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #4 from Alex Deucher ---
(In reply to Andre from comment #3)
> I'm using mesa 12.0.1
> The only thing that works is downgrading kernel to 4.5
Can you bisect?
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #3 from Andre ---
I'm using mesa 12.0.1
The only thing that works is downgrading kernel to 4.5
had the Problem with kernel 4.6.2 too
I'm on Sabayon
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #12 from Stas Sergeev ---
Created attachment 228121
--> https://bugzilla.kernel.org/attachment.cgi?id=228121&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #11 from Stas Sergeev ---
Created attachment 228111
--> https://bugzilla.kernel.org/attachment.cgi?id=228111&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #10 from Alex Deucher ---
Please attach your dmesg output and xorg log (if running X).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #9 from Stas Sergeev ---
(In reply to Alex Deucher from comment #8)
> By default the hw controls the fan based on temperature, etc.
For me not.
> Not all cards have a fan control. If you do, then the following standard
> HWMON
> pwm
https://bugzilla.kernel.org/show_bug.cgi?id=119211
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #8 f
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #7 from Jimi ---
I do not have fancontrol set up or running (it's inactive on my system). I
don't know anything about fancontrol at all. I'm running Arch Linux, so I
pretty much only am running services that I know about.
I tried wri
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #6 from Stas Sergeev ---
> Is this bug still happening?
For me it is happening as a hell.
And because fancontrol service also doesn't
work on my PC (I've filled another reports
about it), the problems are very real.
> I managed to c
https://bugzilla.kernel.org/show_bug.cgi?id=151831
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 f
https://bugzilla.kernel.org/show_bug.cgi?id=151831
--- Comment #1 from Andre ---
Created attachment 228061
--> https://bugzilla.kernel.org/attachment.cgi?id=228061&action=edit
glxinfo
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151831
Bug ID: 151831
Summary: Video freezes mouse moveable, video graphical errors
like black strips an screen goes black sometimes,
system almost unresponsive.
Product: Drivers
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #5 from Jimi ---
I managed to check the fans while pwm1 was giving values like 68, 61, and 56,
and they were not turned on. I don't know if that means anything, because the
card was still <40 degrees and definitely not too hot to touc
https://bugzilla.kernel.org/show_bug.cgi?id=119211
--- Comment #4 from Jimi ---
Is this bug still happening? With my R9 Fury on amdgpu, cat
/sys/class/hwmon/hwmon0/pwm1 (well, in my case, it's hwmon2 because I have
another card), returns 35 on idle, not 0, but the fans are not running. Even
when
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #3 from Jimi ---
I've now confirmed this issue on Fiji (R9 Fury) as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=100871
--- Comment #10 from Charles R. Anderson ---
Problem still exists in Linux 4.6.4 in Fedora 24
(kernel-4.6.4-301.fc24.x86_64).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=118701
Stuart Foster changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|CODE_FIX
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #6 from yshuiv7 at gmail.com ---
Created attachment 227901
--> https://bugzilla.kernel.org/attachment.cgi?id=227901&action=edit
Kernel Oops when resetting the GPU
--
You are receiving this mail because:
You are watching the assigne
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #5 from yshuiv7 at gmail.com ---
I tried to reset the gpu by using /sys/kernel/debug/dri/0/amdgpu_gpu_reset, and
the result is a NULL pointer dereference in the kernel.
dmesg attached
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #4 from yshuiv7 at gmail.com ---
Previous dmesg is from 4.7.0, the attached one is from git HEAD.
Using the _k_ firmware seems to make this happen much less frequently.
--
You are receiving this mail because:
You are watching the as
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #3 from yshuiv7 at gmail.com ---
Created attachment 227871
--> https://bugzilla.kernel.org/attachment.cgi?id=227871&action=edit
Xorg.log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151341
--- Comment #2 from yshuiv7 at gmail.com ---
Created attachment 227861
--> https://bugzilla.kernel.org/attachment.cgi?id=227861&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #18 from Christian Casteyde ---
See comment #3, #4 and #5.
I think i'm using radeon driver with kms since the only graphic chip I have on
my laptop is a Radeon 6650M (no intel graphic in CPU, has been deactivated by
vendor).
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #17 from bastienphilbert at gmail.com ---
Can you find out what drm driver you are currently using as all of them link to
the core function that is leaking memory and knowing which drive is doing it
would be very helpful.
--
You are r
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #6 from Dainius Masiliūnas ---
Created attachment 227741
--> https://bugzilla.kernel.org/attachment.cgi?id=227741&action=edit
4.7.0-next-20160803 dmesg
No. I tried the linux-next tree and it gave me the same errors even during boo
https://bugzilla.kernel.org/show_bug.cgi?id=84431
--- Comment #10 from JoaquÃn AramendÃa ---
> JoaquÃn, how does 97d30fa35 break nouveau vga-switcheroo? If you load
> nouveau with runpm=0, then you can write OFF to debugfs' vga_switcheroo.
> However runpm=1 (or -1 for Optimus systems) is reco
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #5 from Alex Deucher ---
Does it work any better with kernel 4.8?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #4 from Dainius Masiliūnas ---
Yes, it does. With that setting, there are no errors either, and lspci runs
quickly.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #3 from Alex Deucher ---
On the kernel command line in grub.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 f
https://bugzilla.kernel.org/show_bug.cgi?id=118611
K. Paden changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=151541
--- Comment #1 from Dainius Masiliūnas ---
Using radeon.dpm=0 doesn't change anything, only the "*ERROR* radeon: dpm
resume failed" line is not there in that case.
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Dainius Masiliūnas changed:
What|Removed |Added
Attachment #227711|text/x-log |text/plain
mime type|
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Bug ID: 151541
Summary: AMD hybrid graphics: [drm:evergreen_resume [radeon]]
*ERROR* evergreen startup failed on resume
Product: Drivers
Version: 2.5
Kernel Version: 4.7.0
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #16 from Christian Casteyde ---
No, I still have this:
[ 1215.037018] WARNING: kmemcheck: Caught 16-bit read from uninitialized memory
(8801c307d020)
[ 1215.037029] 2e032b012206070e0307373e033534262327353721171507111e031514062322
[
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #15 from bastienphilbert at gmail.com ---
Created attachment 227551
--> https://bugzilla.kernel.org/attachment.cgi?id=227551&action=edit
Cmap Fix
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=36522
bastienphilbert at gmail.com changed:
What|Removed |Added
CC||bastienphilbert at gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=151341
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 f
https://bugzilla.kernel.org/show_bug.cgi?id=151341
Bug ID: 151341
Summary: AMDGPU Hawaii: screen freeze, Xorg blocked in
fence_default_wait
Product: Drivers
Version: 2.5
Kernel Version: 4.7.0
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=96721
--- Comment #2 from Michel Dänzer ---
It's not clear that those are both one and the same bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #13 from Michael Schenaerts ---
I did the bisect with no luck. Evrything was running fine
I built the 4.6 and even the 4.7 with the config files from the 4.5 I set the
other options to default and... it works.
I'll try to build them
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #2 from Jimi ---
Another clarification: the behavior is the same if I don't bind the card to
amdgpu myself and let it be bound to amdgpu on boot, automatically, which is
how I usually test it.
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=150731
--- Comment #1 from Jimi ---
Clarification: If I bind the card to amdgpu, X doesn't crash when I actually
bind it to amdgpu. I never actually get to bind it to amdgpu. X crashes when I
rescan PCI devices (after unbinding the card from whatever it
https://bugzilla.kernel.org/show_bug.cgi?id=150731
Bug ID: 150731
Summary: amdgpu: segfault on unbind in sysfs; card becomes
nonresponsive
Product: Drivers
Version: 2.5
Kernel Version: 4.6.4
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=96721
--- Comment #1 from Christoph Haag ---
Created attachment 226841
--> https://bugzilla.kernel.org/attachment.cgi?id=226841&action=edit
dmesg with stacktrace used for getting line numbers
With 4.7 it's still happening. I finally built a kernel wi
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #12 from Michael Schenaerts ---
Thx, I'll try right away
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
Vedran MiletiÄ changed:
What|Removed |Added
CC||vedran at miletic.net
--- Comment #11
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #10 from Michael Schenaerts ---
I'll be glad to help but I don't know where to start.
Do you have some documentation ?
Thanks
Michaël
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
Christian König changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Commen
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #8 from Michael Schenaerts ---
??
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=117931
--- Comment #6 from Eugene A. Shatokhin ---
Created attachment 225781
--> https://bugzilla.kernel.org/attachment.cgi?id=225781&action=edit
lspci -vnn (kernel 4.7)
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=117931
--- Comment #5 from Eugene A. Shatokhin ---
Created attachment 225771
--> https://bugzilla.kernel.org/attachment.cgi?id=225771&action=edit
Xorg.0.log after resume (kernel 4.7)
--
You are receiving this mail because:
You are watching the assig
https://bugzilla.kernel.org/show_bug.cgi?id=117931
--- Comment #4 from Eugene A. Shatokhin ---
Created attachment 225761
--> https://bugzilla.kernel.org/attachment.cgi?id=225761&action=edit
System log after resume (kernel 4.7)
--
You are receiving this mail because:
You are watching the assig
https://bugzilla.kernel.org/show_bug.cgi?id=117931
--- Comment #3 from Eugene A. Shatokhin ---
Re-checked on Fedora 23 x64 with the mainline kernel 4.7-rc7, git rev
68093c43f352, with no additional patches.
Resume from hibernation is not fully working yet but the problem looks
different this tim
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #7 from Michel Dänzer ---
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=141741
Michael Schenaerts changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #6 from Michael Schenaerts ---
Created attachment 225721
--> https://bugzilla.kernel.org/attachment.cgi?id=225721&action=edit
XRANDR 4.6.4
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #5 from Michael Schenaerts ---
Created attachment 225711
--> https://bugzilla.kernel.org/attachment.cgi?id=225711&action=edit
XRANDR 4.5.5
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #4 from Michael Schenaerts ---
Created attachment 225701
--> https://bugzilla.kernel.org/attachment.cgi?id=225701&action=edit
LSPCI on 4.6.4
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #3 from Michael Schenaerts ---
Created attachment 225691
--> https://bugzilla.kernel.org/attachment.cgi?id=225691&action=edit
LSPCI on 4.5.5
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #2 from Michael Schenaerts ---
Created attachment 225681
--> https://bugzilla.kernel.org/attachment.cgi?id=225681&action=edit
DMESG on 4.6.4
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
--- Comment #1 from Michael Schenaerts ---
Created attachment 225671
--> https://bugzilla.kernel.org/attachment.cgi?id=225671&action=edit
DMESG on 4.5.5
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=141741
Bug ID: 141741
Summary: drm:radeon_get_bios [radeon]] *ERROR* Unable to locate
a BIOS ROM
Product: Drivers
Version: 2.5
Kernel Version: 4.6.4
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=117591
--- Comment #12 from Thomas J. Moore ---
(In reply to Michel Dänzer from comment #11)
> Thomas, since your symptoms are different from Jani's, please file your own
> report, preferably at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&
https://bugzilla.kernel.org/show_bug.cgi?id=117591
--- Comment #11 from Michel Dänzer ---
Thomas, since your symptoms are different from Jani's, please file your own
report, preferably at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/AMDgpu .
--
You are receiving this ma
https://bugzilla.kernel.org/show_bug.cgi?id=117591
Thomas J. Moore changed:
What|Removed |Added
CC||darktjm at gmail.com
--- Comment #10 f
https://bugzilla.kernel.org/show_bug.cgi?id=113891
Jean Delvare changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #14 from Peter Wu ---
Ah... vga_switcheroo_ready() actually checks for clients.. makes sense.
As documented[1], the init handler is called when there is a dependence on
vga[_switcheroo] clients. Radeon however does not seem to need t
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #13 from Christoph Haag ---
This seems like a circular dependency.
if ((rdev->flags & RADEON_IS_PX) && radeon_has_atpx_dgpu_power_cntl())
runtime = true;
vga_switcheroo_register_client(rdev->pdev, &radeon_switcheroo_
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #12 from Christoph Haag ---
First is the one radeon_atpx_init(); call that I added manually to
radeon_device_init in order to make it work:
[6.083965] CPU: 5 PID: 295 Comm: systemd-udevd Not tainted 4.6.0-mainline
#1
[6.083966
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #11 from Peter Wu ---
Can you put a dump_stack() in the atpx_init function and
radeon_has_atpx_dgpu_power_cntl functions such that we can see how it is
called?
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #10 from Christoph Haag ---
Well, it does not help. I wanted to get you some more info, so I inserted some
printks:
in radeon_atpx_handler.c
static void radeon_atpx_parse_functions(struct radeon_atpx_functions *f, u32
mask)
{
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #9 from Peter Wu ---
For that to work on stable v4.6 you have to revert dfc4f59d901b and
bfaddd9fc8ac. My .config and compiler generates the same (inlined) code for
both sources:
// (radeon.ko) mask & (1 << 1) => (mask >> 1) & 1
e
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #8 from Peter Wu ---
Created attachment 224001
--> https://bugzilla.kernel.org/attachment.cgi?id=224001&action=edit
possible patch (force integers into bools)
Yay, I found documentation for the SGMD (SG Mode) field:
0 - None
1 - Sw
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #7 from Christoph Haag ---
No, the stock BIOS of the Clevo P170EM has *very* limited settings and I
believe the radeon GPU has no physical connectors connected at all.
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #6 from Peter Wu ---
Yes, that is what I was looking for.
[3.278214] ACPI Error: Field [TMPB] at 294912 exceeds Buffer [ROM1] size
262144 (bits) (20160108/dsopcode-236)
[3.278218] ACPI Error: Method parse/execution failed [\_
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #5 from Christoph Haag ---
Created attachment 223931
--> https://bugzilla.kernel.org/attachment.cgi?id=223931&action=edit
acpidump
This?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=115321
Peter Wu changed:
What|Removed |Added
CC||peter at lekensteyn.nl
--- Comment #4 from Pe
https://bugzilla.kernel.org/show_bug.cgi?id=84431
Peter Wu changed:
What|Removed |Added
CC||peter at lekensteyn.nl
--- Comment #9 from Pet
https://bugzilla.kernel.org/show_bug.cgi?id=115011
Hans de Goede changed:
What|Removed |Added
CC||jwrdegoede at fedoraproject.or
https://bugzilla.kernel.org/show_bug.cgi?id=119831
Sam changed:
What|Removed |Added
Attachment #220781|0 |1
is obsolete||
https://bugzilla.kernel.org/show_bug.cgi?id=119831
Pierre Moreau changed:
What|Removed |Added
CC||pierre.morrow at free.fr
--- Comment #12
https://bugzilla.kernel.org/show_bug.cgi?id=119831
--- Comment #11 from Sam ---
Created attachment 222951
--> https://bugzilla.kernel.org/attachment.cgi?id=222951&action=edit
kern.log from 4.7-rc7 kernel no-option and nomodeset option
Hi,
I try latest kernel (4.7-rc7) and :
- in a normal boot,
https://bugzilla.kernel.org/show_bug.cgi?id=121831
--- Comment #1 from Michel Dänzer ---
Shouldn't drivers/dma-buf/fence.c:fence_init() fully initialize the struct
fence passed in? If not, using kzalloc instead of kmalloc in radeon_fence_emit
should probably fix this.
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=121831
Bug ID: 121831
Summary: Several kmemcheck: Caught 64-bit read from
uninitialized memory in radeo
Product: Drivers
Version: 2.5
Kernel Version: 4.7-rc6
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=36522
--- Comment #13 from Christian Casteyde ---
Update:
Still present in 4.7-rc6
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Dmitrii Tcvetkov changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #10 from Dmitrii T
https://bugzilla.kernel.org/show_bug.cgi?id=117861
--- Comment #3 from Alex Deucher ---
fixed in:
https://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-next&id=bd6e2732f0e2894ce792f344c41fc32591436fe3
drm/prime: fix error path deadlock fail
There were a couple messed up things about this fai
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Dmitrii Tcvetkov changed:
What|Removed |Added
Resolution|CODE_FIX|PATCH_ALREADY_AVAILABLE
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=121481
--- Comment #8 from Ilia Mirkin ---
Ben has a better fix here:
https://github.com/skeggsb/linux/commit/217215041b9285af2193a755b56a8f3ed408bfe2
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121481
--- Comment #7 from Dmitrii Tcvetkov ---
Created attachment 222141
--> https://bugzilla.kernel.org/attachment.cgi?id=222141&action=edit
dmesg with reverted 6th patch from a8953c52b95167b5d21a66f0859751570271d834
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Dmitrii Tcvetkov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Ilia Mirkin changed:
What|Removed |Added
CC||imirkin at alum.mit.edu
--- Comment #5 fro
https://bugzilla.kernel.org/show_bug.cgi?id=121481
--- Comment #4 from Dmitrii Tcvetkov ---
Created attachment 222131
--> https://bugzilla.kernel.org/attachment.cgi?id=222131&action=edit
lspci
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121481
--- Comment #3 from Dmitrii Tcvetkov ---
Created attachment 222121
--> https://bugzilla.kernel.org/attachment.cgi?id=222121&action=edit
Xorg.0.log for modprobe nouveau debug=trace
--
You are receiving this mail because:
You are watching the a
https://bugzilla.kernel.org/show_bug.cgi?id=121481
--- Comment #2 from Dmitrii Tcvetkov ---
Created attachment 222111
--> https://bugzilla.kernel.org/attachment.cgi?id=222111&action=edit
dmesg for modprobe nouveau debug=trace
--
You are receiving this mail because:
You are watching the assign
301 - 400 of 5870 matches
Mail list logo
