Created attachment 1522599 [details] Boot log Description of problem: Xorg crashes when the kernel is updated to 4.20 and using a Vega integrated GPU (Ryzen 2400) on HP Envy x360. Version-Release number of selected component (if applicable): 4.20-3 Steps to Reproduce: 1. Update kernel to 4.20 2. Reboot your system Actual results: The system becomes unresponsive and shows an orange dotted line (perhaps some random framebuffer data?) on the bottom of the screen Expected results: The system boots fine and plymouth shows the fedora logo filling up Additional info: I'm writing from this same machine booted using kernel 4.19 System info: https://paste.fedoraproject.org/paste/4XCVpn8FE2FwTKbf49iG8w Complete boot log as an attachment. If booting with plymouth disabled i can see the screen hangs at "fb0: switching to amdgpudrmfb from EFI VGA".
Same issue happening with me. I'm on HP Envy x360 with Ryzen 5 2500U APU. Booting into 4.19.14-300.fc29.x86_64 works fine.
Issue is still happening on kernel-4.20.4-200.fc29.x86_64. These errors show up in journalctl: Jan 29 04:53:22 infinity.localdomain kernel: [drm:psp_cmd_submit_buf [amdgpu]] *ERROR* failed loading with status (-65530) and ucode id (19) Jan 29 04:53:22 infinity.localdomain kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Jan 29 04:53:22 infinity.localdomain kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 Jan 29 04:53:22 infinity.localdomain kernel: amdgpu 0000:04:00.0: amdgpu_device_ip_init failed Jan 29 04:53:22 infinity.localdomain kernel: amdgpu 0000:04:00.0: Fatal error during GPU init
Still happening on kernel 4.20.6-200.fc29.x86_64 journalctl output with more details:: Feb 05 11:26:14 infinity.localdomain kernel: [drm:psp_cmd_submit_buf [amdgpu]] *ERROR* failed loading with status (-65530) and ucode id (19) Feb 05 11:26:14 infinity.localdomain kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Feb 05 11:26:14 infinity.localdomain kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 Feb 05 11:26:14 infinity.localdomain kernel: amdgpu 0000:04:00.0: amdgpu_device_ip_init failed Feb 05 11:26:14 infinity.localdomain kernel: amdgpu 0000:04:00.0: Fatal error during GPU init Feb 05 11:26:14 infinity.localdomain kernel: [drm] amdgpu: finishing device. Feb 05 11:26:14 infinity.localdomain kernel: amdgpu 0000:04:00.0: 0000000061cc5e37 unpin not necessary Feb 05 11:26:14 infinity.localdomain kernel: ------------[ cut here ]------------ Feb 05 11:26:14 infinity.localdomain kernel: Memory manager not clean during takedown. Feb 05 11:26:14 infinity.localdomain kernel: WARNING: CPU: 4 PID: 420 at drivers/gpu/drm/drm_mm.c:950 drm_mm_takedown+0x1f/0x30 [drm] Feb 05 11:26:14 infinity.localdomain kernel: Modules linked in: hid_sensor_hub amdgpu(+) rtsx_pci_sdmmc mmc_core hid_multitouch chash i2c_algo_bit amd_iommu_v2 gpu_sched drm_kms_helper ttm crc32c_intel drm serio_raw rtsx_pci nvme nvme_c> Feb 05 11:26:14 infinity.localdomain kernel: CPU: 4 PID: 420 Comm: systemd-udevd Not tainted 4.20.6-200.fc29.x86_64 #1 Feb 05 11:26:14 infinity.localdomain kernel: Hardware name: HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.20 12/25/2018 Feb 05 11:26:14 infinity.localdomain kernel: RIP: 0010:drm_mm_takedown+0x1f/0x30 [drm] Feb 05 11:26:14 infinity.localdomain kernel: Code: f6 c3 48 8d 41 c0 eb bb 0f 1f 00 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 c7 75 01 c3 48 c7 c7 d0 a9 33 c0 e8 ab 37 db fa <0f> 0b c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f > Feb 05 11:26:14 infinity.localdomain kernel: RSP: 0018:ffff9f01c1fcb9e0 EFLAGS: 00010282 Feb 05 11:26:14 infinity.localdomain kernel: RAX: 0000000000000000 RBX: ffff8e5806c84200 RCX: 0000000000000006 Feb 05 11:26:14 infinity.localdomain kernel: RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff8e580f1168c0 Feb 05 11:26:14 infinity.localdomain kernel: RBP: ffff8e58047529e8 R08: 000000000000003c R09: 0000000000000003 Feb 05 11:26:14 infinity.localdomain kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8e58047529c8 Feb 05 11:26:14 infinity.localdomain kernel: R13: 0000000000000000 R14: 0000000000000170 R15: ffff8e5804594790 Feb 05 11:26:14 infinity.localdomain kernel: FS: 00007f6c6184f940(0000) GS:ffff8e580f100000(0000) knlGS:0000000000000000 Feb 05 11:26:14 infinity.localdomain kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 05 11:26:14 infinity.localdomain kernel: CR2: 000055a1a7194108 CR3: 0000000405662000 CR4: 00000000003406e0 Feb 05 11:26:14 infinity.localdomain kernel: Call Trace: Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_vram_mgr_fini+0x22/0x40 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: ttm_bo_clean_mm+0xa2/0xb0 [ttm] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_ttm_fini+0x71/0xe0 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_bo_fini+0xe/0x30 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: gmc_v9_0_sw_fini+0x3c/0x50 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_device_fini+0x23a/0x3f5 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_driver_unload_kms+0xb2/0x150 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_driver_load_kms+0x1a4/0x340 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: drm_dev_register+0x113/0x150 [drm] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_pci_probe+0xbd/0x120 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: local_pci_probe+0x41/0x90 Feb 05 11:26:14 infinity.localdomain kernel: pci_device_probe+0x188/0x1a0 Feb 05 11:26:14 infinity.localdomain kernel: really_probe+0xf8/0x3b0 Feb 05 11:26:14 infinity.localdomain kernel: driver_probe_device+0xb3/0xf0 Feb 05 11:26:14 infinity.localdomain kernel: __driver_attach+0xdd/0x110 Feb 05 11:26:14 infinity.localdomain kernel: ? driver_probe_device+0xf0/0xf0 Feb 05 11:26:14 infinity.localdomain kernel: bus_for_each_dev+0x76/0xc0 Feb 05 11:26:14 infinity.localdomain kernel: ? klist_add_tail+0x3b/0x60 Feb 05 11:26:14 infinity.localdomain kernel: bus_add_driver+0x152/0x230 Feb 05 11:26:14 infinity.localdomain kernel: ? 0xffffffffc0794000 Feb 05 11:26:14 infinity.localdomain kernel: driver_register+0x6b/0xb0 Feb 05 11:26:14 infinity.localdomain kernel: ? 0xffffffffc0794000 Feb 05 11:26:14 infinity.localdomain kernel: do_one_initcall+0x46/0x1c3 Feb 05 11:26:14 infinity.localdomain kernel: ? _cond_resched+0x15/0x30 Feb 05 11:26:14 infinity.localdomain kernel: ? kmem_cache_alloc_trace+0x15f/0x1e0 Feb 05 11:26:14 infinity.localdomain kernel: do_init_module+0x5a/0x210 Feb 05 11:26:14 infinity.localdomain kernel: load_module+0x208c/0x22f0 Feb 05 11:26:14 infinity.localdomain kernel: ? __do_sys_init_module+0x13d/0x180 Feb 05 11:26:14 infinity.localdomain kernel: __do_sys_init_module+0x13d/0x180 Feb 05 11:26:14 infinity.localdomain kernel: do_syscall_64+0x5b/0x160 Feb 05 11:26:14 infinity.localdomain kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Feb 05 11:26:14 infinity.localdomain kernel: RIP: 0033:0x7f6c6250c0ee Feb 05 11:26:14 infinity.localdomain kernel: Code: 48 8b 0d 9d 1d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 1d 0c 00 f7 d8 64 > Feb 05 11:26:14 infinity.localdomain kernel: RSP: 002b:00007ffcc54e9568 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Feb 05 11:26:14 infinity.localdomain kernel: RAX: ffffffffffffffda RBX: 00005642c5350350 RCX: 00007f6c6250c0ee Feb 05 11:26:14 infinity.localdomain kernel: RDX: 00007f6c6268284d RSI: 00000000006acdfe RDI: 00005642c5ce7660 Feb 05 11:26:14 infinity.localdomain kernel: RBP: 00007f6c6268284d R08: 00005642c534d2d0 R09: 0000000000000006 Feb 05 11:26:14 infinity.localdomain kernel: R10: 0000000000000007 R11: 0000000000000246 R12: 00005642c5ce7660 Feb 05 11:26:14 infinity.localdomain kernel: R13: 00005642c534e8d0 R14: 0000000000020000 R15: 0000000000000000 Feb 05 11:26:14 infinity.localdomain kernel: ---[ end trace b67661fa98bd295d ]--- Feb 05 11:26:14 infinity.localdomain kernel: ------------[ cut here ]------------ Feb 05 11:26:14 infinity.localdomain kernel: Memory manager not clean during takedown. Feb 05 11:26:14 infinity.localdomain kernel: WARNING: CPU: 4 PID: 420 at drivers/gpu/drm/drm_mm.c:950 drm_mm_takedown+0x1f/0x30 [drm] Feb 05 11:26:14 infinity.localdomain kernel: Modules linked in: hid_sensor_hub amdgpu(+) rtsx_pci_sdmmc mmc_core hid_multitouch chash i2c_algo_bit amd_iommu_v2 gpu_sched drm_kms_helper ttm crc32c_intel drm serio_raw rtsx_pci nvme nvme_c> Feb 05 11:26:14 infinity.localdomain kernel: CPU: 4 PID: 420 Comm: systemd-udevd Tainted: G W 4.20.6-200.fc29.x86_64 #1 Feb 05 11:26:14 infinity.localdomain kernel: Hardware name: HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.20 12/25/2018 Feb 05 11:26:14 infinity.localdomain kernel: RIP: 0010:drm_mm_takedown+0x1f/0x30 [drm] Feb 05 11:26:14 infinity.localdomain kernel: Code: f6 c3 48 8d 41 c0 eb bb 0f 1f 00 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 c7 75 01 c3 48 c7 c7 d0 a9 33 c0 e8 ab 37 db fa <0f> 0b c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 1f > Feb 05 11:26:14 infinity.localdomain kernel: RSP: 0018:ffff9f01c1fcb9e0 EFLAGS: 00010282 Feb 05 11:26:14 infinity.localdomain kernel: RAX: 0000000000000000 RBX: ffff8e5806c84100 RCX: 0000000000000006 Feb 05 11:26:14 infinity.localdomain kernel: RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff8e580f1168c0 Feb 05 11:26:14 infinity.localdomain kernel: RBP: ffff8e5804752930 R08: 000000000000003c R09: 0000000000000003 Feb 05 11:26:14 infinity.localdomain kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8e5804752910 Feb 05 11:26:14 infinity.localdomain kernel: R13: 0000000000000000 R14: 00000000000000b8 R15: ffff8e5804594790 Feb 05 11:26:14 infinity.localdomain kernel: FS: 00007f6c6184f940(0000) GS:ffff8e580f100000(0000) knlGS:0000000000000000 Feb 05 11:26:14 infinity.localdomain kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 05 11:26:14 infinity.localdomain kernel: CR2: 000055a1a7194108 CR3: 0000000405662000 CR4: 00000000003406e0 Feb 05 11:26:14 infinity.localdomain kernel: Call Trace: Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_gtt_mgr_fini+0x22/0x40 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: ttm_bo_clean_mm+0xa2/0xb0 [ttm] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_ttm_fini+0x7e/0xe0 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_bo_fini+0xe/0x30 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: gmc_v9_0_sw_fini+0x3c/0x50 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_device_fini+0x23a/0x3f5 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_driver_unload_kms+0xb2/0x150 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_driver_load_kms+0x1a4/0x340 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: drm_dev_register+0x113/0x150 [drm] Feb 05 11:26:14 infinity.localdomain kernel: amdgpu_pci_probe+0xbd/0x120 [amdgpu] Feb 05 11:26:14 infinity.localdomain kernel: local_pci_probe+0x41/0x90 Feb 05 11:26:14 infinity.localdomain kernel: pci_device_probe+0x188/0x1a0 Feb 05 11:26:14 infinity.localdomain kernel: really_probe+0xf8/0x3b0 Feb 05 11:26:14 infinity.localdomain kernel: driver_probe_device+0xb3/0xf0 Feb 05 11:26:14 infinity.localdomain kernel: __driver_attach+0xdd/0x110 Feb 05 11:26:14 infinity.localdomain kernel: ? driver_probe_device+0xf0/0xf0 Feb 05 11:26:14 infinity.localdomain kernel: bus_for_each_dev+0x76/0xc0 Feb 05 11:26:14 infinity.localdomain kernel: ? klist_add_tail+0x3b/0x60 Feb 05 11:26:14 infinity.localdomain kernel: bus_add_driver+0x152/0x230 Feb 05 11:26:14 infinity.localdomain kernel: ? 0xffffffffc0794000 Feb 05 11:26:14 infinity.localdomain kernel: driver_register+0x6b/0xb0 Feb 05 11:26:14 infinity.localdomain kernel: ? 0xffffffffc0794000 Feb 05 11:26:14 infinity.localdomain kernel: do_one_initcall+0x46/0x1c3 Feb 05 11:26:14 infinity.localdomain kernel: ? _cond_resched+0x15/0x30 Feb 05 11:26:14 infinity.localdomain kernel: ? kmem_cache_alloc_trace+0x15f/0x1e0 Feb 05 11:26:14 infinity.localdomain kernel: do_init_module+0x5a/0x210 Feb 05 11:26:14 infinity.localdomain kernel: load_module+0x208c/0x22f0 Feb 05 11:26:14 infinity.localdomain kernel: ? __do_sys_init_module+0x13d/0x180 Feb 05 11:26:14 infinity.localdomain kernel: __do_sys_init_module+0x13d/0x180 Feb 05 11:26:14 infinity.localdomain kernel: do_syscall_64+0x5b/0x160 Feb 05 11:26:14 infinity.localdomain kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Feb 05 11:26:14 infinity.localdomain kernel: RIP: 0033:0x7f6c6250c0ee Feb 05 11:26:14 infinity.localdomain kernel: Code: 48 8b 0d 9d 1d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 1d 0c 00 f7 d8 64 > Feb 05 11:26:14 infinity.localdomain kernel: RSP: 002b:00007ffcc54e9568 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Feb 05 11:26:14 infinity.localdomain kernel: RAX: ffffffffffffffda RBX: 00005642c5350350 RCX: 00007f6c6250c0ee Feb 05 11:26:14 infinity.localdomain kernel: RDX: 00007f6c6268284d RSI: 00000000006acdfe RDI: 00005642c5ce7660 Feb 05 11:26:14 infinity.localdomain kernel: RBP: 00007f6c6268284d R08: 00005642c534d2d0 R09: 0000000000000006 Feb 05 11:26:14 infinity.localdomain kernel: R10: 0000000000000007 R11: 0000000000000246 R12: 00005642c5ce7660 Feb 05 11:26:14 infinity.localdomain kernel: R13: 00005642c534e8d0 R14: 0000000000020000 R15: 0000000000000000 Feb 05 11:26:14 infinity.localdomain kernel: ---[ end trace b67661fa98bd295e ]---
Issue still persists on kernel 4.20.6. However, seems to be fixed on kernel 5.0.0rc3
Issue still persists on 4.20.8. Ed, is the issue still fixed in the latest 5.0 rc?
Using 5.0.0-0.rc4.git3.1.fc30.x86_64 right now. Everything works, even though i get the "dotted line" at boot for a few seconds, and sometimes the boot takes a long time.
For long boot times, how long have you waited? Is this before or after you log in? For 4.20.8, I've waited a few minutes at the dotted line screen but there was no progress.
Still occurring on kernel 4.20.11-200.fc29.x86_64.
Created attachment 1539221 [details] Journalctl output for kernel 4.20.11-200.fc29.x86_64
Still occurring on kernel 4.20.12-200.fc29.x86_64.
Still occurring on kernel 4.20.15-200.fc29.x86_64.
Kernel 5.0 worked perfectly up to update to version 5.0.3-200, where I've found the issue happening again.
On my system the issue persists after upgrading my kernel from 4.20.x to 5.0.3. The last kernel where I didn't have this issue was on 4.19.x. I'm surprised that this isn't getting any more attention, as this is a critical issue.
Created attachment 1548627 [details] Journalctl output for kernel 5.0.3-200.fc29.x86_64 Here is the journalctl output
Still happening on kernel 5.0.4-200. I will attach the journalctl output
Created attachment 1549451 [details] Journalctl output for kernel 5.0.4-200.fc29.x86_64
This bug may be related: https://bugs.freedesktop.org/show_bug.cgi?id=109206
This happens on Kernel 5.0.5-200 as well. Also occurring on Fedora 30 Beta because that has kernel 5.0.0.
This seems to be the workaround as per https://bugs.freedesktop.org/show_bug.cgi?id=109206, and it worked for me and am able to boot into kernel 5.0.6-200.fc29.x86_64: 1. move/rename the /lib/firmware/amdgpu/raven_dcmu.bin file 2. run the following: dracut --kver 5.0.6-200.fc29.x86_64 --force This recreates the default 5.0.6-200.fc29.x86_64 initram fs image but without the raven_dcmu.bin file. After this completes, reboot and this time things should work.
(In reply to Talha Khan from comment #19) > This seems to be the workaround as per > https://bugs.freedesktop.org/show_bug.cgi?id=109206, and it worked for me > and am able to boot into kernel 5.0.6-200.fc29.x86_64: > > 1. move/rename the /lib/firmware/amdgpu/raven_dcmu.bin file > 2. run the following: > dracut --kver 5.0.6-200.fc29.x86_64 --force > > This recreates the default 5.0.6-200.fc29.x86_64 initram fs image but > without the raven_dcmu.bin file. > > After this completes, reboot and this time things should work. This is not a good workaround. While the laptop will boot, you have very limited usage of your GPU. For example, running any OpenGL application or even loading the Steam will crash the laptop requiring a hard power off, at least for me. The only real solution is a pre-4.19 kernel at this point.
Adrian, Not sure how your setup is like, but I am running Fedora 29 KDE. I have a KWin rule in place to disable compositing when running Steam. I am able to launch Steam just fine, and I was able to play Shadowrun Dragonfall Director's Cut with no issues. I'll attach the console output. As far as I can tell, nothing seems out of the ordinary.
Created attachment 1554864 [details] Console output when running Steam on kernel 5.0.6
(In reply to Talha Khan from comment #22) > Created attachment 1554864 [details] > Console output when running Steam on kernel 5.0.6 Interesting. Are you using any special boot options? The behavior I'm seeing is with none. Thanks!
Here's what grubby shows: # grubby --info /boot/vmlinuz-5.0.6-200.fc29.x86_64 index=1 kernel=/boot/vmlinuz-5.0.6-200.fc29.x86_64 args="ro rhgb quiet LANG=en_US.UTF-8" root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda initrd=/boot/initramfs-5.0.6-200.fc29.x86_64.img title=Fedora (5.0.6-200.fc29.x86_64) 29 (Twenty Nine)
The same workaround works for me on kernel 5.0.7-200.fc29.x86_64. The initramfs image had the raven_dmcu.bin file included.
(In reply to Talha Khan from comment #25) > The same workaround works for me on kernel 5.0.7-200.fc29.x86_64. The > initramfs image had the raven_dmcu.bin file included. I can confirm the same results. The newer 5.0.x kernels are fully usable if I remove the raven_dmcu.bin from initramfs and the firmware folder.
Issue still occurs and workaround still works on kernels 5.0.8 and 5.0.8.
Has anyone upgraded to Fedora 30? I assume the error still occurs since that is running on Kernel 5.0.x.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.