https://bugzilla.kernel.org/show_bug.cgi?id=121021
--- Comment #3 from zhiquan.lee at gmail.com ---
I've added debug kernel command line parameters: drm.debug=0xf when captured
the log.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121021
zhiquan.lee at gmail.com changed:
What|Removed |Added
Component|Video(DRI - non Intel) |Video(Other)
Hardwar
https://bugzilla.kernel.org/show_bug.cgi?id=119831
Zhang Rui changed:
What|Removed |Added
Component|Other |Video(DRI - non Intel)
Assignee|ru
https://bugzilla.kernel.org/show_bug.cgi?id=119831
--- Comment #10 from Jani Nikula ---
[ 14.841410] nouveau :01:00.0: DRM: evicting buffers...
[ 14.841411] nouveau :01:00.0: DRM: waiting for kernel channels to go
idle...
[ 14.841425] nouveau :01:00.0: DRM: suspending client obj
https://bugzilla.kernel.org/show_bug.cgi?id=119831
Zhang Rui changed:
What|Removed |Added
CC|lenb at kernel.org,|
|rui.zhang at intel.co
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #5 from Michel Dänzer ---
Please attach the Xorg log file and the output of xrandr when the problem
occurs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #6 from Fred Santos ---
Created attachment 200361
--> https://bugzilla.kernel.org/attachment.cgi?id=200361&action=edit
Log: 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=108221
--- Comment #7 from Fred Santos ---
And here is the output of xrandr (the problem *always* and *constantly*
occurs):
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DP-1 disconnected (normal left inverted right x axis y a
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #8 from Michel Dänzer ---
Looks like xf86-video-amdgpu wasn't installed correctly, so Xorg can't find it
and uses the generic modesetting driver instead. Does the problem persist if
you actually use xf86-video-amdgpu (preferably a ne
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #9 from Fred Santos ---
Thanks for your answer.
Yes, the log is quite strange about that, since xf86-video-amdgpu is indeed
installed, but doesn't seem to be found... (Is there a way to 'force' the use
of amdgpu?)
Btw, the problem o
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #10 from Michel Dänzer ---
(In reply to Fred Santos from comment #9)
> Yes, the log is quite strange about that, since xf86-video-amdgpu is indeed
> installed, but doesn't seem to be found...
Maybe 10-amdgpu.conf isn't installed in
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #11 from OndÅej Súkup ---
Created attachment 200391
--> https://bugzilla.kernel.org/attachment.cgi?id=200391&action=edit
xorg.log on r9-380
with Xorg autodetection...
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #12 from OndÅej Súkup ---
Created attachment 200401
--> https://bugzilla.kernel.org/attachment.cgi?id=200401&action=edit
xorg log r9-380
with /etc/X11/xorg.conf.d/10-amdgpu.conf
--
You are receiving this mail because:
You are w
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #13 from Michel Dänzer ---
(In reply to Fred Santos from comment #0)
> The problem is present only since an update to the kernel 4.3.0-3, the first
> versions of 4.3.x were OK for me.
Can you find out what changed in 4.3.0-3 compare
https://bugzilla.kernel.org/show_bug.cgi?id=88861
--- Comment #9 from Lukas Wunner ---
Hi Jani,
Paul Hordiienko, the reporter of this bug, successfully tested an earlier
version (v2) of the patch set, see the Tested-by: tags on these patches:
http://lists.freedesktop.org/archives/dri-devel/2015-
https://bugzilla.kernel.org/show_bug.cgi?id=88861
--- Comment #10 from Paul Hordiienko ---
Hi Lukas and Jani,
I have tested v5 and confirm that it works on my MBP 6,2 2010 without any
issues.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #14 from Fred Santos ---
(In reply to Michel Dänzer from comment #10)
> (In reply to Fred Santos from comment #9)
> > (Is there a way to 'force' the use of amdgpu?)
>
> Yes, you can force it in Section "Device" in /etc/X11/xorg.conf
https://bugzilla.kernel.org/show_bug.cgi?id=108561
--- Comment #8 from Elmar Stellnberger ---
... and now the external monitor stays black all the time no matter what I do
with xrandr/nouveau while the proprietary driver does happily continue to work.
It is a shame that nobody seems to care about
https://bugzilla.kernel.org/show_bug.cgi?id=108561
--- Comment #9 from Elmar Stellnberger ---
... gonna try it with kernel 4.4 now as I heard that there were certain
improvements ...
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=108561
Ilia Mirkin changed:
What|Removed |Added
CC||imirkin at alum.mit.edu
--- Comment #10 fr
https://bugzilla.kernel.org/show_bug.cgi?id=60523
Mathias Anselmann changed:
What|Removed |Added
CC||mathias.anselmann at gmail.com
--- Co
https://bugzilla.kernel.org/show_bug.cgi?id=105041
Aaron Lu changed:
What|Removed |Added
Status|NEEDINFO|ASSIGNED
Component|Hibernation/Suspe
https://bugzilla.kernel.org/show_bug.cgi?id=111271
Bug ID: 111271
Summary: Black stripe on screen with MGAG200 (PowerEdge R320)
and modesetting
Product: Drivers
Version: 2.5
Kernel Version: 4.4
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=111271
--- Comment #1 from Jean-Yves Faye ---
Created attachment 201401
--> https://bugzilla.kernel.org/attachment.cgi?id=201401&action=edit
Xorg.0.log (4.4 kernel, disregard kernel command line)
--
You are receiving this mail because:
You are watch
https://bugzilla.kernel.org/show_bug.cgi?id=111271
--- Comment #2 from Jean-Yves Faye ---
Created attachment 201411
--> https://bugzilla.kernel.org/attachment.cgi?id=201411&action=edit
kernel config for our Dell R320 (no module)
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=111271
--- Comment #3 from Jean-Yves Faye ---
Created attachment 201421
--> https://bugzilla.kernel.org/attachment.cgi?id=201421&action=edit
bisect log
I've ran bisect between 3.10.40 and 3.18, but still present on 4.4
Linux localhost.adm 4.4.0 #21
https://bugzilla.kernel.org/show_bug.cgi?id=111271
Ville Syrjala changed:
What|Removed |Added
CC||ville.syrjala at linux.intel.c
https://bugzilla.kernel.org/show_bug.cgi?id=111271
--- Comment #5 from Jean-Yves Faye ---
Created attachment 201431
--> https://bugzilla.kernel.org/attachment.cgi?id=201431&action=edit
Picture of screen
This was caught on a CRT monitor and is quite visible. The strip follow the
mouse cursor on
https://bugzilla.kernel.org/show_bug.cgi?id=111271
Jean-Yves Faye changed:
What|Removed |Added
Attachment #201421|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=111271
--- Comment #7 from Jean-Yves Faye ---
Created attachment 202021
--> https://bugzilla.kernel.org/attachment.cgi?id=202021&action=edit
dumb patch
Some experimentation lead me to this patch, this seems to resolve the problem,
but I have no idead
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #15 from Michel Dänzer ---
(In reply to Fred Santos from comment #14)
> 2. We found (Comment #10) that amdgpu was not found/activated during boot:
> when 'forcing' its use by creating this /etc/X11/xorg.conf file, everything
> is OK,
https://bugzilla.kernel.org/show_bug.cgi?id=108561
Elmar Stellnberger changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=78111
Alex changed:
What|Removed |Added
CC||mad_sam at bk.ru
--- Comment #10 from Alex ---
AM
https://bugzilla.kernel.org/show_bug.cgi?id=78111
--- Comment #11 from Alex ---
(In reply to Alex from comment #10)
> AMD A8-5557M (Richland). APU turbo core boost still is not working.
>
> With radeon.dpm=1
>
> boost state support:
> Supported: yes
> Active: no
> Boost States: 3
https://bugzilla.kernel.org/show_bug.cgi?id=78111
--- Comment #12 from Alex Deucher ---
Setting radeon.bapm=1 will enable it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=78111
--- Comment #13 from Alex ---
(In reply to Alex Deucher from comment #12)
> Setting radeon.bapm=1 will enable it.
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=86351
--- Comment #20 from Christian Birchinger ---
The kernel documentation for CONFIG_SND_HDA_PREALLOC_SIZE has this:
Note that the pre-allocation size can be change dynamically via a proc file
(/proc/asound/card*/pcm*/sub*/prealloc), too.
I don't h
https://bugzilla.kernel.org/show_bug.cgi?id=75241
Benjamin Herrenschmidt changed:
What|Removed |Added
CC||benh at kernel.crashing.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #31 from Benjamin Herrenschmidt ---
Note: It's an LCD :-) It's one of those fixed-mode panels Apple has always been
fond of, one of the very first 1920x1200 out there.
--
You are receiving this mail because:
You are watching the assi
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #32 from Benjamin Herrenschmidt ---
Note 2: Catalyst and the Windows driver both work fine. Any way to know what
formula these 2 use (I assume it's the same code) ?
--
You are receiving this mail because:
You are watching the assigne
https://bugzilla.kernel.org/show_bug.cgi?id=119631
Thorsten Leemhuis changed:
What|Removed |Added
CC||regressions at leemhuis.info
--- Com
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #33 from Christian König ---
(In reply to Benjamin Herrenschmidt from comment #30)
> The combo is Radeon R9 290 (from Sapphire) and good old Apple Cinema Display
> 23" (1920x1200x60 fixed resolution display) on DVI.
Well this bug rep
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #34 from Benjamin Herrenschmidt ---
Well, the Apple Cinema Display is nearly 10 years old too :-) But at least it's
an LCD... I will open a new bug on FDO.
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=119631
--- Comment #16 from Michel Dänzer ---
(In reply to Thorsten Leemhuis from comment #15)
> What's the status of this issue? Just wondering, as this issue is listed
> in my regression reports for 4.7 [...]
This isn't a kernel regression. It's a W
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #35 from Benjamin Herrenschmidt ---
https://bugs.freedesktop.org/show_bug.cgi?id=96789
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Bug ID: 121481
Summary: No video output after loading nouveau module
Product: Drivers
Version: 2.5
Kernel Version: 4.7-rc6
Hardware: x86-64
OS: Linux
Tree: Ma
https://bugzilla.kernel.org/show_bug.cgi?id=121481
Dmitrii Tcvetkov changed:
What|Removed |Added
CC||demfloro at demfloro.ru
--- Comment #
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
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 #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
Ilia Mirkin changed:
What|Removed |Added
CC||imirkin at alum.mit.edu
--- Comment #5 fro
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
--- 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
--- 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
Dmitrii Tcvetkov changed:
What|Removed |Added
Resolution|CODE_FIX|PATCH_ALREADY_AVAILABLE
--- Comment #
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
Status|RESOLVED|CLOSED
--- Comment #10 from Dmitrii T
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=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=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=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=119831
Pierre Moreau changed:
What|Removed |Added
CC||pierre.morrow at free.fr
--- Comment #12
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=115011
Hans de Goede changed:
What|Removed |Added
CC||jwrdegoede at fedoraproject.or
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=115321
Peter Wu changed:
What|Removed |Added
CC||peter at lekensteyn.nl
--- Comment #4 from Pe
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
--- 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 #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 #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 #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 #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 #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 #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 #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 #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=113891
Jean Delvare changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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=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
--- 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=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=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
--- 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 #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 #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 #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 #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
Michael Schenaerts changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail
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=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=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 #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 #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=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=141741
Christian König changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Commen
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
Vedran MiletiÄ changed:
What|Removed |Added
CC||vedran at miletic.net
--- Comment #11
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=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=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
601 - 700 of 5870 matches
Mail list logo
