[Bug 1195142] New: kernel 5.3.18-150300.59.43-default: radeon: RIP: 0010:rb_first_postorder+0xb/0x30
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 Bug ID: 1195142 Summary: kernel 5.3.18-150300.59.43-default: radeon: RIP: 0010:rb_first_postorder+0xb/0x30 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: manfred99@gmx.ch QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I upgraded my Leap15.3 box from 5.3.18-59.40-default to 5.3.18-59.43-default today. Monitor stayed black, but box was booting fine after some delay. Via ssh, I could access the logs. The only irregular messages I could find were from a crash of the radeon driver: 2022-01-26T12:14:39.732506+00:00 localhost kernel: [ 3.168424] radeon 0000:09:00.0: still active bo inside vm 2022-01-26T12:14:39.732508+00:00 localhost kernel: [ 3.168433] general protection fault: 0000 [#1] SMP NOPTI 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168435] CPU: 10 PID: 357 Comm: systemd-udevd Not tainted 5.3.18-150300.59.43-default #1 SLE15-SP3 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168437] Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F42e 10/18/2019 2022-01-26T12:14:39.732509+00:00 localhost kernel: [ 3.168443] RIP: 0010:rb_first_postorder+0xb/0x30 2022-01-26T12:14:39.732510+00:00 localhost kernel: [ 3.168445] Code: d2 74 f5 48 89 d0 48 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 0f 1f 44 00 00 48 8b 17 48 85 d2 74 17 48 89 d0 <48> 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 31 c0 2022-01-26T12:14:39.732510+00:00 localhost kernel: [ 3.168448] RSP: 0018:ffffb579007c7910 EFLAGS: 00010286 2022-01-26T12:14:39.732512+00:00 localhost kernel: [ 3.168450] RAX: 8948530000441f0f RBX: ffff8c958756b800 RCX: 0000000000000007 2022-01-26T12:14:39.732512+00:00 localhost kernel: [ 3.168451] RDX: 8948530000441f0f RSI: 0000000000000092 RDI: ffff8c958756b820 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168452] RBP: 0000000000000001 R08: 00000000000003a8 R09: 000000000000003d 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168454] R10: 0000000000000263 R11: ffffb579007c7668 R12: ffff8c9c726a8000 2022-01-26T12:14:39.732513+00:00 localhost kernel: [ 3.168456] R13: ffff8c9c726a8000 R14: ffff8c958756b820 R15: ffff8c958756b800 2022-01-26T12:14:39.732514+00:00 localhost kernel: [ 3.168457] FS: 00007fcde7096980(0000) GS:ffff8c9c7e880000(0000) knlGS:0000000000000000 2022-01-26T12:14:39.732515+00:00 localhost kernel: [ 3.168459] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-01-26T12:14:39.732516+00:00 localhost kernel: [ 3.168460] CR2: 0000562eff0496b8 CR3: 00000007f5882000 CR4: 00000000003506e0 2022-01-26T12:14:39.732516+00:00 localhost kernel: [ 3.168462] Call Trace: 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168486] radeon_vm_fini+0x2e/0x220 [radeon] 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168505] radeon_driver_open_kms+0x56/0x1c0 [radeon] 2022-01-26T12:14:39.732517+00:00 localhost kernel: [ 3.168517] drm_file_alloc+0x1a1/0x240 [drm] 2022-01-26T12:14:39.732518+00:00 localhost kernel: [ 3.168528] drm_client_init+0xb1/0x140 [drm] 2022-01-26T12:14:39.732519+00:00 localhost kernel: [ 3.168537] drm_fb_helper_init+0x37/0x40 [drm_kms_helper] 2022-01-26T12:14:39.732520+00:00 localhost kernel: [ 3.168556] radeon_fbdev_init+0x8e/0x130 [radeon] 2022-01-26T12:14:39.732520+00:00 localhost kernel: [ 3.168575] radeon_modeset_init+0x46c/0x9e0 [radeon] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168591] radeon_driver_load_kms+0x8a/0x250 [radeon] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168601] drm_dev_register+0x150/0x1e0 [drm] 2022-01-26T12:14:39.732521+00:00 localhost kernel: [ 3.168618] radeon_pci_probe+0x130/0x1e0 [radeon] 2022-01-26T12:14:39.732523+00:00 localhost kernel: [ 3.168621] ? __pm_runtime_resume+0x54/0x80 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168625] local_pci_probe+0x42/0x90 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168628] ? pci_assign_irq+0x27/0x130 2022-01-26T12:14:39.732524+00:00 localhost kernel: [ 3.168630] pci_device_probe+0x10b/0x1c0 2022-01-26T12:14:39.732525+00:00 localhost kernel: [ 3.168633] really_probe+0xef/0x430 2022-01-26T12:14:39.732525+00:00 localhost kernel: [ 3.168635] driver_probe_device+0x110/0x120 2022-01-26T12:14:39.732527+00:00 localhost kernel: [ 3.168637] device_driver_attach+0x4f/0x60 2022-01-26T12:14:39.732527+00:00 localhost kernel: [ 3.168639] __driver_attach+0x51/0x130 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168641] ? device_driver_attach+0x60/0x60 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168643] bus_for_each_dev+0x76/0xc0 2022-01-26T12:14:39.732528+00:00 localhost kernel: [ 3.168645] bus_add_driver+0x144/0x220 2022-01-26T12:14:39.732529+00:00 localhost kernel: [ 3.168647] ? 0xffffffffc06f4000 2022-01-26T12:14:39.732529+00:00 localhost kernel: [ 3.168649] driver_register+0x5b/0xf0 2022-01-26T12:14:39.732531+00:00 localhost kernel: [ 3.168651] ? 0xffffffffc06f4000 2022-01-26T12:14:39.732531+00:00 localhost kernel: [ 3.168654] do_one_initcall+0x46/0x1f4 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168656] ? kmem_cache_alloc_trace+0x18f/0x270 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168659] ? do_init_module+0x22/0x22f 2022-01-26T12:14:39.732532+00:00 localhost kernel: [ 3.168662] ? __vunmap+0x1b5/0x210 2022-01-26T12:14:39.732533+00:00 localhost kernel: [ 3.168664] do_init_module+0x5b/0x22f 2022-01-26T12:14:39.732534+00:00 localhost kernel: [ 3.168666] load_module+0x1d81/0x2320 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168669] ? __do_sys_init_module+0x160/0x190 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168671] ? _cond_resched+0x15/0x40 2022-01-26T12:14:39.732535+00:00 localhost kernel: [ 3.168673] __do_sys_init_module+0x160/0x190 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168676] do_syscall_64+0x5b/0x1e0 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168678] entry_SYSCALL_64_after_hwframe+0x44/0xa9 2022-01-26T12:14:39.732536+00:00 localhost kernel: [ 3.168680] RIP: 0033:0x7fcde5e916da 2022-01-26T12:14:39.732539+00:00 localhost kernel: [ 3.168682] Code: 48 8b 0d b9 c7 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 86 c7 2c 00 f7 d8 64 89 01 48 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168685] RSP: 002b:00007ffcf45aa2e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168687] RAX: ffffffffffffffda RBX: 0000562eff039820 RCX: 00007fcde5e916da 2022-01-26T12:14:39.732540+00:00 localhost kernel: [ 3.168689] RDX: 00007fcde67f179d RSI: 00000000002bcf00 RDI: 0000562eff4ade70 2022-01-26T12:14:39.732541+00:00 localhost kernel: [ 3.168690] RBP: 00007fcde67f179d R08: 0000000000000002 R09: 0000000000000000 2022-01-26T12:14:39.732541+00:00 localhost kernel: [ 3.168692] R10: 0000000000000003 R11: 0000000000000246 R12: 0000562eff4ade70 2022-01-26T12:14:39.732543+00:00 localhost kernel: [ 3.168693] R13: 0000562eff035f70 R14: 0000562eff00be10 R15: 0000562eff037af0 2022-01-26T12:14:39.732543+00:00 localhost kernel: [ 3.168695] Modules linked in: hid_generic usbhid sd_mod t10_pi radeon(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core ttm xhci_pci xhci_hcd drm ahci libahci libata usbcore crc32c_intel wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168705] Supported: Yes 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168707] ---[ end trace b2aadc042ce7a558 ]--- 2022-01-26T12:14:39.732544+00:00 localhost kernel: [ 3.168709] RIP: 0010:rb_first_postorder+0xb/0x30 2022-01-26T12:14:39.732545+00:00 localhost kernel: [ 3.168711] Code: d2 74 f5 48 89 d0 48 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 0f 1f 44 00 00 48 8b 17 48 85 d2 74 17 48 89 d0 <48> 8b 52 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb f3 c3 31 c0 2022-01-26T12:14:39.732547+00:00 localhost kernel: [ 3.168714] RSP: 0018:ffffb579007c7910 EFLAGS: 00010286 2022-01-26T12:14:39.732547+00:00 localhost kernel: [ 3.168716] RAX: 8948530000441f0f RBX: ffff8c958756b800 RCX: 0000000000000007 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168717] RDX: 8948530000441f0f RSI: 0000000000000092 RDI: ffff8c958756b820 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168719] RBP: 0000000000000001 R08: 00000000000003a8 R09: 000000000000003d 2022-01-26T12:14:39.732548+00:00 localhost kernel: [ 3.168720] R10: 0000000000000263 R11: ffffb579007c7668 R12: ffff8c9c726a8000 2022-01-26T12:14:39.732549+00:00 localhost kernel: [ 3.168722] R13: ffff8c9c726a8000 R14: ffff8c958756b820 R15: ffff8c958756b800 2022-01-26T12:14:39.732550+00:00 localhost kernel: [ 3.168724] FS: 00007fcde7096980(0000) GS:ffff8c9c7e880000(0000) knlGS:0000000000000000 2022-01-26T12:14:39.732551+00:00 localhost kernel: [ 3.168725] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-01-26T12:14:39.732551+00:00 localhost kernel: [ 3.168727] CR2: 0000562eff0496b8 CR3: 00000007f5882000 CR4: 00000000003506e0 This crash is new, introduced by the latest update, and repeatable. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manfred99@gmx.ch, | |tiwai@suse.com Flags| |needinfo?(manfred99@gmx.ch) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you try the latest kernel in OBS Kernel:SLE15-SP3 repo? http://download.opensuse.org/repositories/Kernel:/SLE15-SP3/pool/ -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c2 Manfred Schwarb <manfred99@gmx.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(manfred99@gmx.ch) | --- Comment #2 from Manfred Schwarb <manfred99@gmx.ch> --- Boots flawless, radeon survives. Thanks a lot! Do you need any details? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Thanks for quick testing. Then this must be the regression by the upstream backport (commit ab50cb9df889) that was fixed later by the commit bc2af58685c7. The latter fix was merged recently and missing in the last MU, unfortunately. -- You are receiving this mail because: You are the assignee for the bug.
Stakanov Schufter <stakanov@disroot.org> has asked openSUSE Kernel Bugs <kernel-bugs@opensuse.org> for needinfo: Bug 1195142: kernel 5.3.18-150300.59.43-default: radeon: RIP: 0010:rb_first_postorder+0xb/0x30 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 --- Comment #8 from Stakanov Schufter <stakanov@disroot.org> --- (In reply to Takashi Iwai from comment #6)
*** Bug 1195168 has been marked as a duplicate of this bug. ***
I have this too as a problem on a machine with an R600. Now, has this been closed for having been fixed or has this been closed for erroneously? What Kernel version was then the fix then applied? And in what repo?
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c8 Stakanov Schufter <stakanov@disroot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-bugs@opensuse.org, | |stakanov@disroot.org Flags| |needinfo?(kernel-bugs@opens | |use.org) --- Comment #8 from Stakanov Schufter <stakanov@disroot.org> --- (In reply to Takashi Iwai from comment #6)
*** Bug 1195168 has been marked as a duplicate of this bug. ***
I have this too as a problem on a machine with an R600. Now, has this been closed for having been fixed or has this been closed for erroneously? What Kernel version was then the fix then applied? And in what repo? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c9 Andreas Vetter <vetter@physik.uni-wuerzburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vetter@physik.uni-wuerzburg | |.de --- Comment #9 from Andreas Vetter <vetter@physik.uni-wuerzburg.de> --- (In reply to Martin Schr�der from comment #7)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
Excuse me? This leaves any headless server with Radeon (e.g. HP MicroServer) in a frozen state. I had to dig out a monitor and a keyboard for mine.
Same problem here. I reverted to 5.3.18-59.40.1 on my Microserver. On my desktop with graphics card, I found out "nomodeset" helps, but on a desktop I need working graphics. So I revrted, too. Maybe "nomodeset" is a workaround for the Microserver. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c10 --- Comment #10 from Andreas Vetter <vetter@physik.uni-wuerzburg.de> --- (In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230] -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c11 Andreas Klein <asklein@physik.uni-wuerzburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asklein@physik.uni-wuerzbur | |g.de --- Comment #11 from Andreas Klein <asklein@physik.uni-wuerzburg.de> --- Same problem on HP Proliant DL385 G7. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c13 --- Comment #13 from Stakanov Schufter <stakanov@disroot.org> --- (In reply to Andreas Vetter from comment #10)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230]
That worked for me as well with the Radeon R600 card (with KDE plasma BTW). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c14 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #14 from Takashi Iwai <tiwai@suse.com> --- *** Bug 1195284 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c15 --- Comment #15 from Andreas Vetter <vetter@physik.uni-wuerzburg.de> --- (In reply to Stakanov Schufter from comment #13)
(In reply to Andreas Vetter from comment #10)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230]
That worked for me as well with the Radeon R600 card (with KDE plasma BTW).
Works also on the HP Microserver G7: [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c16 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |obel1x@web.de --- Comment #16 from Takashi Iwai <tiwai@suse.com> --- *** Bug 1195301 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c17 Martin Schr�der <martin@oneiros.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #17 from Martin Schr�der <martin@oneiros.de> --- Reopening as a fix has not been released. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c18 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kernel-bugs@opens | |use.org) | --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- Resolving the bug as FIXED after the fix gets merged into the git branch is the standard procedure especially for kernel bugs. It's the intended action. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c19 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None --- Comment #19 from Takashi Iwai <tiwai@suse.com> --- Also, please don't touch Priority field of Bugzilla. It's the field only the developer side adjusts. You are free to adjust Severity field, but not Priority. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c20 --- Comment #20 from Stakanov Schufter <stakanov@disroot.org> --- (In reply to Takashi Iwai from comment #18)
Resolving the bug as FIXED after the fix gets merged into the git branch is the standard procedure especially for kernel bugs. It's the intended action.
This was actually asked with the doubt that putting it as "fixed" while it will not appear for some week in the repo may be origin of a lot of duplicates. Rational for my remark is that the default filter for the users are set to show only open bugs, while AFAIK the resolved ones do not appear. But thank you for answering the question, you contributed to my knowledge, very appreciated. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c21 Helmut Walle <helmut.walle@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helmut.walle@gmail.com --- Comment #21 from Helmut Walle <helmut.walle@gmail.com> --- Same issue here with [AMD/ATI] RV710 [Radeon HD 4550]. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c22 --- Comment #22 from Helmut Walle <helmut.walle@gmail.com> --- (In reply to Andreas Vetter from comment #15)
(In reply to Stakanov Schufter from comment #13)
(In reply to Andreas Vetter from comment #10)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230]
That worked for me as well with the Radeon R600 card (with KDE plasma BTW).
Works also on the HP Microserver G7: [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250]
It also works for my system with [AMD/ATI] RV710 [Radeon HD 4550]. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c23 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |faconle@gmail.com --- Comment #23 from Felix Miata <mrmazda@earthlink.net> --- *** Bug 1195270 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c26 HJF Boschker <henk@boschker.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |henk@boschker.net --- Comment #26 from HJF Boschker <henk@boschker.net> --- (In reply to Andreas Vetter from comment #10)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 23
Also in my case this worked perfect. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c27 Carlos Sancho <carlossancho@icabjerez.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlossancho@icabjerez.es --- Comment #27 from Carlos Sancho <carlossancho@icabjerez.es> --- (In reply to Andreas Vetter from comment #10)
(In reply to Takashi Iwai from comment #5)
I guess not, unless there is another urgent security fix coming up.
As a workaround, you can simply copy the old radeon module file from 5.3.18-59.40 to *-43, e.g. # mkdir /lib/modules/5.3.18-*.43-default/updates # cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/ # depmod 5.3.18-150300.59.43-default # mkinitrd
This workaround works for my [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230]
That worked for me. I was doing a new clean installation and it failed to boot. But since I had a backup of my old root partition I could boot up from that backup, copy radeon module from the old kernel to the new one and then chroot on the new system to do depmod and mkinitrd. Thank you. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c32 Bernhard Reiter <bernhard@intevation.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhard@intevation.de --- Comment #32 from Bernhard Reiter <bernhard@intevation.de> --- On the machine here, the defect show like RIP: 00010:radeon_vm_fini+0x15/0x220 [radeon] (there is no full trace I could see on the console and there is also nothing written to a log) What works for me as a workaround is adding radeon.modeset=0 to GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub because this machine has two graphic cards, the build in intel and the radeon. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c33 --- Comment #33 from al conle <faconle@gmail.com> --- For the non-expert some clarification of how to get into the 15.3 system would be useful. i.e.: is ssh the only way in, or is there some way from the DVD "Rescue System" to get in to copy the old radeon.ko file to the suggested location ? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c34 --- Comment #34 from Carlos Sancho <carlossancho@icabjerez.es> --- (In reply to al conle from comment #33)
For the non-expert some clarification of how to get into the 15.3 system would be useful. i.e.: is ssh the only way in, or is there some way from the DVD "Rescue System" to get in to copy the old radeon.ko file to the suggested location ?
You can use the method explained here to mount the failed system and copy the radeon module into it: https://doc.opensuse.org/documentation/leap/archive/42.1/startup/html/book.o... Then, after doing chroot as explained there, you can do depmod and mkinitrd as described before. I did it that way and it worked. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c35 --- Comment #35 from al conle <faconle@gmail.com> --- (In reply to Carlos Sancho from comment #34)
(In reply to al conle from comment #33)
For the non-expert some clarification of how to get into the 15.3 system would be useful. i.e.: is ssh the only way in, or is there some way from the DVD "Rescue System" to get in to copy the old radeon.ko file to the suggested location ?
You can use the method explained here to mount the failed system and copy the radeon module into it: https://doc.opensuse.org/documentation/leap/archive/42.1/startup/html/book. opensuse.startup/cha.trouble.html#sec.trouble.data.recover.rescue.access
Then, after doing chroot as explained there, you can do depmod and mkinitrd as described before.
I did it that way and it worked.
Thanks !! I will try that. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c38 --- Comment #38 from al conle <faconle@gmail.com> --- (In reply to al conle from comment #35)
(In reply to Carlos Sancho from comment #34)
(In reply to al conle from comment #33)
For the non-expert some clarification of how to get into the 15.3 system would be useful. i.e.: is ssh the only way in, or is there some way from the DVD "Rescue System" to get in to copy the old radeon.ko file to the suggested location ?
You can use the method explained here to mount the failed system and copy the radeon module into it: https://doc.opensuse.org/documentation/leap/archive/42.1/startup/html/book. opensuse.startup/cha.trouble.html#sec.trouble.data.recover.rescue.access
Then, after doing chroot as explained there, you can do depmod and mkinitrd as described before.
I did it that way and it worked.
Thanks !! I will try that.
Worked ok with some minor hiccups at the end with umount -a Boots now, but I seem to be unable to change the monitor resolution which is stuck at 1400s x something with no other options in the dropdown, thus I will go back to the 15.2 snapshot for awhile. Will play with it some more later. Thanks for the help. Al -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c39 --- Comment #39 from Felix Miata <mrmazda@earthlink.net> --- (In reply to al conle from comment #38)
I seem to be unable to change the monitor resolution which is stuck at 1400s x something with no other options in the dropdown
Are you using nomodeset? That might explain it, as it's troubleshooting workaround, not a fix: https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Installation_Obstacles https://forums.opensuse.org/showthread.php/562680-AMD-Intel-amp-NVidia-X-gra... -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c42 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rene.geile@mailbox.org --- Comment #42 from Takashi Iwai <tiwai@suse.com> --- *** Bug 1195569 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c43 --- Comment #43 from al conle <faconle@gmail.com> --- (In reply to Felix Miata from comment #39)
(In reply to al conle from comment #38)
I seem to be unable to change the monitor resolution which is stuck at 1400s x something with no other options in the dropdown
Are you using nomodeset? That might explain it, as it's troubleshooting workaround, not a fix: https://en.opensuse.org/SDB:Nomodeset: _Work_Around_Graphic_Upgrade_&_Installation_Obstacles https://forums.opensuse.org/showthread.php/562680-AMD-Intel-amp-NVidia-X- graphics-driver-primer-third-edition
Thanks for your suggestions. I seem not to be using nomodeset but am not sure. While running 15.3 grub file shows: # /boot/grub2/grub.cfg. # Uncomment to set your own custom distributor. If you leave it unset or empty, the default # policy is to determine the value from /etc/os-release GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=8 GRUB_CMDLINE_LINUX_DEFAULT="splash=verbose resume=/dev/sdb1 showopts splash=silent resume=/dev/disk/by-uuid/101f9b45-6c23-4f05-a460-59279dba839f mitigations=auto quiet" GRUB_CMDLINE_LINUX="" -------------------------------end of copy----- Meanwhile in 15.3 the Application menu -Settings- System Settings -Display and Monitor window appears to be stuck at resolution 1400 x 1050 and 77hz i.e. Drop-down has no other options Although not extensively explored everything seems to be ok except for the monitor display settings. One thing I noticed is that there appear to be two radeon.ko files in the 15.2 snapshot: -------------
locate radeon.ko /lib/modules/5.3.18-lp152.102-default/kernel/drivers/gpu/drm/radeon/radeon.ko /lib/modules/5.3.18-lp152.106-default/kernel/drivers/gpu/drm/radeon/radeon.ko Software/OpenSuse> ls -l /lib/modules/5.3.18-lp152.102-default/kernel/drivers/gpu/drm/radeon/radeon.ko -rw-r--r-- 1 root root 2895291 Nov 11 11:19 /lib/modules/5.3.18-lp152.102-default/kernel/drivers/gpu/drm/radeon/radeon.ko Software/OpenSuse> ls -l /lib/modules/5.3.18-lp152.106-default/kernel/drivers/gpu/drm/radeon/radeon.ko -rw-r--r-- 1 root root 2894811 Nov 23 05:24 /lib/modules/5.3.18-lp152.106-default/kernel/drivers/gpu/drm/radeon/radeon.ko
While solving the previous black screen (15.3) problem I copied the newer radion.ko file. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c44 --- Comment #44 from Felix Miata <mrmazda@earthlink.net> --- (In reply to al conle from comment #43)
One thing I noticed is that there appear to be two radeon.ko files in the 15.2 snapshot: -------------
locate radeon.ko /lib/modules/5.3.18-lp152.102-default/kernel/drivers/gpu/drm/radeon/radeon.ko /lib/modules/5.3.18-lp152.106-default/kernel/drivers/gpu/drm/radeon/radeon.ko
Right, one for the .102 kernel and one for the .106. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c45 Matthias Bach <marix@marix.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marix@marix.org --- Comment #45 from Matthias Bach <marix@marix.org> --- With today's update openSUSE-SLE-15.3-2022-340 to 5.3.18-150300.59.46 I can boot my system without the "nomodeset" workaround again. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c46 --- Comment #46 from Andreas Vetter <vetter@physik.uni-wuerzburg.de> --- (In reply to Matthias Bach from comment #45)
With today's update openSUSE-SLE-15.3-2022-340 to 5.3.18-150300.59.46 I can boot my system without the "nomodeset" workaround again.
Works on the HP Microserver, too. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c47 Johan Dot <jonte1@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonte1@gmail.com --- Comment #47 from Johan Dot <jonte1@gmail.com> --- Loking forward to test, Dl rigth now. Was it 12 days..? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c50 Felix Brenk <fbrenk@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |fbrenk@gmx.net Resolution|--- |FIXED --- Comment #50 from Felix Brenk <fbrenk@gmx.net> --- Update is working fine on my Fujitsu. Thank you very much! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195142 http://bugzilla.opensuse.org/show_bug.cgi?id=1195142#c53 --- Comment #53 from al conle <faconle@gmail.com> --- (In reply to Felix Miata from comment #44)
(In reply to al conle from comment #43)
One thing I noticed is that there appear to be two radeon.ko files in the 15.2 snapshot: -------------
locate radeon.ko /lib/modules/5.3.18-lp152.102-default/kernel/drivers/gpu/drm/radeon/radeon.ko /lib/modules/5.3.18-lp152.106-default/kernel/drivers/gpu/drm/radeon/radeon.ko
Right, one for the .102 kernel and one for the .106.
Latest kernel update solves my graphics display problem. Many thanks !! Al -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com