https://bugzilla.kernel.org/show_bug.cgi?id=211189
Dominik Mierzejewski (domi...@greysector.net) changed:
What|Removed |Added
Tree|Mainline|Fedora
--
https://bugzilla.kernel.org/show_bug.cgi?id=211263
Bug ID: 211263
Summary: amdgpu: navi (RX 5500 XT) high power consumption while
idling on 75Hz display
Product: Drivers
Version: 2.5
Kernel Version: 5.10.7
Hardware: x86
https://bugzilla.kernel.org/show_bug.cgi?id=211263
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=211263
Paulo Marcos de Souza Arruda do Nascimento (contato-mygh...@protonmail.com)
changed:
What|Removed |Added
Status|NEW
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Bug ID: 211277
Summary: sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu,
drm, commit_tail, amdgpu_dm_atomic_commit_tail
Product: Drivers
Version: 2.5
Kernel Version: 5.10.4
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #1 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 294747
--> https://bugzilla.kernel.org/attachment.cgi?id=294747&action=edit
kern.log
--
You may reply to this email to add a comment.
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #2 from kolAflash (kolafl...@kolahilft.de) ---
Created attachment 294749
--> https://bugzilla.kernel.org/attachment.cgi?id=294749&action=edit
BIOS update history (just in case someone has a clue if something looks
suspicios and this
https://bugzilla.kernel.org/show_bug.cgi?id=211219
Aleksandr Makarov (aleksandr.o.maka...@gmail.com) changed:
What|Removed |Added
CC||dri-de
https://bugzilla.kernel.org/show_bug.cgi?id=211161
Benji Wiebe (benjiwieb...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
R
https://bugzilla.kernel.org/show_bug.cgi?id=210321
--- Comment #3 from Florian Evers (florian-ev...@gmx.de) ---
Hi,
new info: this "crash" can be reproduced very easily here on my system. It is
enough to switch the screen off and on again to find the dump in the dmesg log.
I did not test yet whet
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #8 from Oliver Reeh (oli...@diereehs.de) ---
It's fixed in kernel 5.10.9 with Mesa 20.3.3.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #3 from kolAflash (kolafl...@kolahilft.de) ---
I searched through my journalctl log.
I set up the whole system in May 2020 with Linux-5.6.7.
(journalctl has everything back to that date)
The bug appeared as following since October
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #9 from Klaus Mueller (kmuel...@justmail.de) ---
no - same behavior as before with 5.10.9 and Mesa 20.3.3
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #10 from Klaus Mueller (kmuel...@justmail.de) ---
Uups, it's the other crash now:
2021-01-23T18:45:31.955962+01:00 localhost kernel: [23110.401847]
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR*
[CRTC:62:crtc-0] fl
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #20 from Jay Tuckey (jay@tuckey.email) ---
Hi, I'm also running into this issue, using an RX Vega 64 with an Asus ROG
display. Let me know if there's any logs or testing that I can do to assist.
--
You may reply to this email to add
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #11 from Oliver Reeh (oli...@diereehs.de) ---
The problem is back with kernel 5.10.10.
[ 89.664494] WARNING: CPU: 6 PID: 4323 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_link_encoder.c:483
dcn10_get_dig_frontend+0x94/0xc
https://bugzilla.kernel.org/show_bug.cgi?id=211277
Jerome C (m...@jeromec.com) changed:
What|Removed |Added
CC||m...@jeromec.com
--- Commen
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #39 from Randune (randyk...@gmail.com) ---
There doesn't appear to be any progress on this bug, does anyone have any
suggestions with regards on how to fix this issue?
--
You may reply to this email to add a comment.
You are receivi
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #40 from j.cordoba (j.cord...@gmx.net) ---
(In reply to Randune from comment #39)
> There doesn't appear to be any progress on this bug, does anyone have any
> suggestions with regards on how to fix this issue?
Try to add iommu=pt as
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #41 from Panagiotis Polychronis (panospolychro...@gmail.com) ---
(In reply to j.cordoba from comment #40)
> (In reply to Randune from comment #39)
> > There doesn't appear to be any progress on this bug, does anyone have any
> > sugges
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #42 from MajorGonzo (majorgo...@juno.com) ---
I made a change a while back. I added:
amdgpu.gpu_recovery=1
as a grub parameter. I have no other (of the many suggested) parameters set:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #21 from Sebastien Bernard (sbern...@nerim.net) ---
The more I think about it,
the more it seems to be related only to this monitor.
I think the 4.19 kernel closed a bug and is rejectiting the EDID reported by
this screen.
If someone
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #22 from Jay Tuckey (jay@tuckey.email) ---
@Sebastien that could well be the case. The screen works fine under windows,
but it could be that they are working around bad EDID data?
Is there any way I can validate if the EDID is bad?
-
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #43 from Randune (randyk...@gmail.com) ---
(In reply to Panagiotis Polychronis from comment #41)
> (In reply to j.cordoba from comment #40)
> > (In reply to Randune from comment #39)
> > > There doesn't appear to be any progress on thi
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #44 from MajorGonzo (majorgo...@juno.com) ---
Here's another thing I tried which also may have made a difference. Gonna
sound weird, but worth a try. I had a 675VA UPS that my system was plugged
into. One time, it started shrieking
https://bugzilla.kernel.org/show_bug.cgi?id=211349
Bug ID: 211349
Summary: IB test failed on sdma0 ! AMDGPU driver for Raven APU
(ryzen 2400G) hangs!
Product: Drivers
Version: 2.5
Kernel Version: 5.10.9
Hardware: i386
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #1 from bola...@163.com ---
Created attachment 294855
--> https://bugzilla.kernel.org/attachment.cgi?id=294855&action=edit
Main Error
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are wa
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #2 from bola...@163.com ---
Created attachment 294857
--> https://bugzilla.kernel.org/attachment.cgi?id=294857&action=edit
Kernel log without kfd fd kfd: added device 1002:15dd and amdgpu: Topology:
Add APU node [0x0:0x0]
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #3 from bola...@163.com ---
Created attachment 294859
--> https://bugzilla.kernel.org/attachment.cgi?id=294859&action=edit
Kernel config file
--
You may reply to this email to add a comment.
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #4 from bola...@163.com ---
Created attachment 294861
--> https://bugzilla.kernel.org/attachment.cgi?id=294861&action=edit
GCC version
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are w
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #5 from bola...@163.com ---
I have tested with many kernels and firmwares but failed ! To compare with
Ubuntu 20.4 LTS kern log,my kern log lack of "kfd: added device" and "amdgpu
:06:00.0: amdgpu: Topology: Add APU node [0x0
https://bugzilla.kernel.org/show_bug.cgi?id=211349
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #7 from bola...@163.com ---
Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only worked
on X86_64 ? The radeon drivers worked well on 32bit kernel. I have Caicos and
Oland chipset radeon graphic cards,all be drived
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #8 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to bolando from comment #7)
> Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only
> worked on X86_64 ? The radeon drivers worked well on 32bit kernel. I ha
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #9 from bola...@163.com ---
(In reply to Alex Deucher from comment #8)
> (In reply to bolando from comment #7)
> > Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only
> > worked on X86_64 ? The radeon drivers worke
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #10 from Alex Deucher (alexdeuc...@gmail.com) ---
does setting CONFIG_HSA_AMD=n fix it?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #11 from bola...@163.com ---
No HSA_AMD option, it's only for 64bit kernel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=211033
Shawn Anastasio (sh...@anastas.io) changed:
What|Removed |Added
CC||sh...@anastas.io
---
https://bugzilla.kernel.org/show_bug.cgi?id=211033
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #5 from Jerome C (m...@jeromec.com) ---
Created attachment 294879
--> https://bugzilla.kernel.org/attachment.cgi?id=294879&action=edit
Kernel log
Unfortunately it crashed again although I've noticed it's been crashing a lot
less (4-
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Bug ID: 211425
Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for
more than 20secs aborting
Product: Drivers
Version: 2.5
Kernel Version: 5.10.10
Hardware:
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #12 from Michel Dänzer (mic...@daenzer.net) ---
I'd recommend running a 64-bit kernel, even if all user-space is 32-bit.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assi
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Severity|high|normal
--
You may reply
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #13 from bola...@163.com ---
(In reply to Michel Dänzer from comment #12)
> I'd recommend running a 64-bit kernel, even if all user-space is 32-bit.
I just have finished LFS-10.0 in several weeks,it's a very hard work. If enable
64bit
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #14 from Michel Dänzer (mic...@daenzer.net) ---
> If enable 64bit kernel support,I need to recompile everything on LFS10.0 in
> next weeks.
You shouldn't. 32-bit user-space works fine with a 64-bit kernel.
--
You may reply to this e
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #15 from bola...@163.com ---
(In reply to Michel Dänzer from comment #14)
> > If enable 64bit kernel support,I need to recompile everything on LFS10.0 in
> > next weeks.
>
> You shouldn't. 32-bit user-space works fine with a 64-bit ke
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #16 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to bolando from comment #15)
> (In reply to Michel Dänzer from comment #14)
> > > If enable 64bit kernel support,I need to recompile everything on LFS10.0
> in
> > > next week
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #17 from bola...@163.com ---
(In reply to Alex Deucher from comment #16)
> (In reply to bolando from comment #15)
> > (In reply to Michel Dänzer from comment #14)
> > > > If enable 64bit kernel support,I need to recompile everything on
https://bugzilla.kernel.org/show_bug.cgi?id=211425
--- Comment #1 from Andreas (icedragon...@web.de) ---
Kernel 5.10.11 (mainline) issues still persist:
[ 181.977478] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
20secs aborting
[ 181.977546] [drm:amdgpu_atom_execute_table_loc
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.10.10 |5.10.11
--
You may reply
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #18 from bola...@163.com ---
I have compiled x64 kernel for my LFS10.0.Booting with the X64 kernel,when load
the amdgpu driver,screen frozen again. check the kern log ,everything seems OK
but no amdgpudrmfb .I try to start X11,but fail
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #19 from Alex Deucher (alexdeuc...@gmail.com) ---
Please attach your xorg log and dmesg output. Note that if you want an fbdev
interface for the console, you need to enable CONFIG_DRM_FBDEV_EMULATION=y in
your config.
--
You may rep
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #20 from bola...@163.com ---
Everything is OK!I recompiled the 5.10.8 X64 kernel,AMDGPU is successful load
!It seems the 32bit kernel is not supported now .I think the AMDGPU drivers
need IOMMU and HSPA support,the 32bit kernel haven
https://bugzilla.kernel.org/show_bug.cgi?id=211349
bola...@163.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #21 from bola...@163.com ---
(In reply to Michel Dänzer from comment #14)
> > If enable 64bit kernel support,I need to recompile everything on LFS10.0 in
> > next weeks.
>
> You shouldn't. 32-bit user-space works fine with a 64-bit ke
https://bugzilla.kernel.org/show_bug.cgi?id=210123
--- Comment #7 from Stefan Mayr (stefan+ker...@mayr-stefan.de) ---
Same issue with Kernel 5.10.9
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #6 from kolAflash (kolafl...@kolahilft.de) ---
(In reply to Jerome C from comment #4)
> [...]
> Do you have kernel parameter set "init_on_free=1" or in your kernel config
> "CONFIG_INIT_ON_FREE_DEFAULT_ON=y", [...]
I'm using the Debia
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #7 from Jerome C (m...@jeromec.com) ---
ok, you have it turned off already
Weird thing happened this morning... I woke my laptop up and it was slow screen
updates... I just closed my laptop lid, frustrated... I noticed it suspended
ag
https://bugzilla.kernel.org/show_bug.cgi?id=209713
Frank Kruger (fkrue...@mailbox.org) changed:
What|Removed |Added
CC||fkrue...@mailbox.org
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #13 from Frank Kruger (fkrue...@mailbox.org) ---
The only change regarding "DCN" from 5.10.9 to 5.10.10 is
commit 99ea120383b19feb1737c787dc1c8b35ce630fc5
Author: Alex Deucher
Date: Mon Jan 4 11:24:20 2021 -0500
drm/amdgpu/dis
https://bugzilla.kernel.org/show_bug.cgi?id=209713
--- Comment #14 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Frank Kruger from comment #12)
> I am seeing the aforementioned warning at boot for kernel >= 5.10.10, with
> kernel-firmware-amdgpu-20210119 (AMD Ryzen 7 PRO 4750U). Kernel
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #8 from Jerome C (m...@jeromec.com) ---
I've tried kernel 5.11-rc5 and same issue occurs there.
For now I've downgraded kernel to 5.9.14 ( will update it to 5.9.16 ) until
this issue is fixed
What I've mentioned in comment 4 isn't re
https://bugzilla.kernel.org/show_bug.cgi?id=211501
Bug ID: 211501
Summary: Kernel freeze when waking monitor from blanking / DPMS
(AMDGPU / DC)
Product: Drivers
Version: 2.5
Kernel Version: 5.10.11
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=211501
--- Comment #1 from Jasen Borisov (borisovja...@protonmail.com) ---
Created attachment 295023
--> https://bugzilla.kernel.org/attachment.cgi?id=295023&action=edit
dmesg output from the system booting (for extra info)
--
You may reply to this e
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #1 from ninel...@protonmail.com ---
Can confirm this with a Ryzen 7 4800H. Any news on this?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=203905
Antony J.R (antonyjr...@gmail.com) changed:
What|Removed |Added
CC||antonyjr...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=207833
Antony J.R (antonyjr...@gmail.com) changed:
What|Removed |Added
CC||antonyjr...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.10.11 |5.10.12
--- Comment #2 fr
https://bugzilla.kernel.org/show_bug.cgi?id=211501
--- Comment #2 from Jasen Borisov (borisovja...@protonmail.com) ---
OK, it just happened again. More info:
The secondary monitor lights up, but just shows a black screen with the mouse
cursor, but the primary monitor does not. This makes me suspe
https://bugzilla.kernel.org/show_bug.cgi?id=211033
--- Comment #16 from Shawn Anastasio (sh...@anastas.io) ---
Created attachment 295063
--> https://bugzilla.kernel.org/attachment.cgi?id=295063&action=edit
kernel log
I have encountered the same issue on 5.10.10 which contains the revert.
Attach
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #10 from JerryD (jvdeli...@charter.net) ---
This bug has basically disabled two different machines I have that use AMD
graphics cards. One, a work station running Fedora 33 will lose the display if
I do not log on right away after a p
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.10.12 |5.10.13
--- Comment #3 fr
https://bugzilla.kernel.org/show_bug.cgi?id=210849
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #12 from JerryD (jvdeli...@charter.net) ---
I have done some bisection with the kernel by uninstalling packages and rolling
back. I tried this with my best guess of which packages to roll back using
package manager (dnf here). In the
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #13 from Alex Deucher (alexdeuc...@gmail.com) ---
most likely kernel.
https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #14 from JerryD (jvdeli...@charter.net) ---
(In reply to Alex Deucher from comment #13)
> most likely kernel.
>
> https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
OK, I have done the kernel builds before no problems
https://bugzilla.kernel.org/show_bug.cgi?id=201539
--- Comment #75 from michael (lkb...@deegan.id.au) ---
An update. Now on 5.10.0-2-amd64.
Fresh boot, with amdgpu.dc=1, everything is mostly fine. pwm1_enable=2. Except
that after resuming from suspend, pwm1_enable=1 and pwm1=255, resulting in
max
https://bugzilla.kernel.org/show_bug.cgi?id=207763
--- Comment #7 from Mohammad Naeim (xunilar...@gmail.com) ---
(In reply to Alex Deucher from comment #5)
> Does it work correctly with 5.9-rc1 or newer?
I tested with 5.10 and the problem still exists.
--
You may reply to this email to add a co
https://bugzilla.kernel.org/show_bug.cgi?id=207763
--- Comment #8 from Mohammad Naeim (xunilar...@gmail.com) ---
(In reply to Alex Deucher from comment #6)
> Another thing to try, does setting radeon.agpmode=-1 fix the issue?
I add it to grub but the issue still exists.
--
You may reply to this
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #15 from JerryD (jvdeli...@charter.net) ---
Dropped back to kernel-5.7.0 and everything works fine on laptop with lid close
suspend / returns from suspend with no errors on my laptop. I made no other
changes so this confirms the kerne
https://bugzilla.kernel.org/show_bug.cgi?id=203905
Paulo Nascimento (paulo.ul...@googlemail.com) changed:
What|Removed |Added
CC||paulo.ul..
https://bugzilla.kernel.org/show_bug.cgi?id=202043
Bruno Jacquet (maxi...@free.fr) changed:
What|Removed |Added
CC||maxi...@free.fr
--- Com
https://bugzilla.kernel.org/show_bug.cgi?id=203905
--- Comment #22 from Antony J.R (antonyjr...@gmail.com) ---
A workaround for this is done by the OpenSUSE folks, Please see
https://bugzilla.opensuse.org/show_bug.cgi?id=1180749
The only distro which fixes this is OpenSUSE. This is because there
https://bugzilla.kernel.org/show_bug.cgi?id=204241
a.g...@libero.it changed:
What|Removed |Added
CC||a.g...@libero.it
--- Comment #75 from
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #76 from Robert M. Muncrief (rmuncr...@humanavance.com) ---
I also continue to have this problem on Arch with kernel 5.10.14.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #77 from Alex Deucher (alexdeuc...@gmail.com) ---
Please open a new ticket this issue was fixed.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #16 from JerryD (jvdeli...@charter.net) ---
kernel-5.8.1-301.fc33 amdgpu_dm_backlight_update_status+0xb4/0xc0 [amdgpu]
kernel-5.8.0-1.fc33 amdgpu_dm_backlight_update_status+0xb4/0xc0 [amdgpu]
* breakage somewhere between th
https://bugzilla.kernel.org/show_bug.cgi?id=211649
Bug ID: 211649
Summary: "drm/amd/display: reuse current context instead of
recreating one" cause hdmi hotplug blackscreen on
amdgpu
Product: Drivers
Version: 2.5
https://bugzilla.kernel.org/show_bug.cgi?id=211651
Bug ID: 211651
Summary: Dual screen not working with Nvidia GTX 1050ti in a
notebook
Product: Drivers
Version: 2.5
Kernel Version: 5.8.0.43
Hardware: Intel
https://bugzilla.kernel.org/show_bug.cgi?id=211651
--- Comment #1 from fily1212 (ker...@fily.com.de) ---
Created attachment 295143
--> https://bugzilla.kernel.org/attachment.cgi?id=295143&action=edit
screenshoot of screen setting during not working kernel
--
You may reply to this email to add
https://bugzilla.kernel.org/show_bug.cgi?id=211651
--- Comment #2 from fily1212 (ker...@fily.com.de) ---
Created attachment 295145
--> https://bugzilla.kernel.org/attachment.cgi?id=295145&action=edit
screenshoot of screen setting during working kernel
--
You may reply to this email to add a co
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.10.13 |5.10.14
--- Comment #4 fr
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=211425
--- Comment #6 from Andreas (icedragon...@web.de) ---
(In reply to Alex Deucher from comment #5)
> If this is a regression can you bisect?
I can try to bisect at next weekend.
--
You may reply to this email to add a comment.
You are receiving t
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #2 from ninel...@protonmail.com ---
I just found out that this Issue does NOT occur when you additionally add the
fbcon=nodefer kernel parameter.
--
You may reply to this email to add a comment.
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=211649
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=211649
Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) changed:
What|Removed |Added
CC||nichol
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #3 from Fabian (plusf...@gmail.com) ---
(In reply to ninelore from comment #2)
> I just found out that this Issue does NOT occur when you additionally add
> the fbcon=nodefer kernel parameter.
This workaround works for me too.
--
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #3 from youling...@gmail.com ---
replug hdmi, [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:67:crtc-0] flip_done timed out
[ 252.377374] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR*
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #4 from youling...@gmail.com ---
Created attachment 295189
--> https://bugzilla.kernel.org/attachment.cgi?id=295189&action=edit
dmesg.txt
echo 6 > /sys/module/drm/parameters/debug
replug hdmi dmesg.
--
You may reply to this email
201 - 300 of 44705 matches
Mail list logo
