[Bug 2055973] Re: Firefox trunk Gah. Your tab just crashed.
After update to kernel 6.8.0-11 all firefox tabs crash. Using 6.6.0.14 does not cause any problems. My dmesg has the same info on libxul.so crashing as the reporter's: [ 4270.862686] Sandbox Forked[18464]: segfault at 0 ip 717f2d94172e sp 717f21abd520 error 6 in libxul.so[717f2d84d000+61a3000] likely on CPU ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055973 Title: Firefox trunk Gah. Your tab just crashed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2055973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055973] Re: Firefox trunk Gah. Your tab just crashed.
BTW it affects both my PCs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055973 Title: Firefox trunk Gah. Your tab just crashed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2055973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055445] [NEW] configmanager fails to import libnetplan
Public bug reported: Executing `python3 /usr/share/netplan/netplan/configmanager.py` causes: ``` File "/usr/share/netplan/netplan/configmanager.py", line 28, in from netplan import libnetplan ModuleNotFoundError: No module named 'netplan' ``` As the `libnetplan` module is in the same directory it's possible to fix the error by changing `from netplan import libnetplan` to `import libnetplan` ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055445 Title: configmanager fails to import libnetplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2055445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
I have following kernels installed: - 5.13.0-35-generic - 5.14.0-1024-oem - 5.14.0-1027-oem Kernel 5.13 does not work. The other two do work. I see the problem on Lenovo Ideapad 320. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
Right now I'm using OEM kernel and everything works well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
My screen looks like this: https://postimg.cc/Tp2LJB4N The right side of the screen changes very quickly. Sometimes it is black and sometimes it looks like the rest of the screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] Re: [amdgpu] Static-noise-like effect
Attached journal.txt. ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+attachment/5562797/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
That didn't fix the bug in my case. Should I create new bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I made a experiment and I can confirm static noise after waking from suspend. @jamesf My device model is Lenovo Ideapad 320. You can update your post. I will copy my other post since we are tracking this bug here: When your computer boots press escape (UEFI boot) or shift (BIOS boot). You may have to try several times to press it in right time. A menu should appear. Choose option 'Advanced options for Ubuntu'. Then choose 'Ubuntu, with Linux 5.11.0-46-generic'. Then you can follow instructions in post #15 to boot with Linux 5.11.0 by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958412] Re: [amdgpu] Flickering/noise on screen started in kernel 5.13
In my case the problem is severe. I can see login screen, but when I log in I see a white noise screen. It renders my computer unusable. That is unless I use older kernel. There is how to do it: When your computer boots press escape (UEFI boot) or shift (BIOS boot). You may have to try several times to press it in right time. A menu should appear. Choose option 'Advanced options for Ubuntu'. Then choose 'Ubuntu, with Linux 5.11.0-46-generic'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] Flickering/noise on screen started in kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958523] [NEW] Static-noise-like effect
Public bug reported: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "version+lspci.log" https://bugs.launchpad.net/bugs/1958523/+attachment/805/+files/version+lspci.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: Static-noise-like effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890248] Re: SRU of mdadm to Focal
Hello, mdadm supports set of different metadata. Intel metadata is a part of it (called IMSM). We (as Intel) are submitted a lot of fixes and features, all are validated and tested. Beside upstream testing, we have our internal test scope, focused on IMSM aspects. I can say with certainty that upstream test form IMSM are working and are used daily. But there are more metadata types. They are not maintained as IMSM is. There was recent topic on mailing list about problem with tests: https://lore.kernel.org/linux-raid/2022030635.1...@linux.intel.com/T/#t Seems that some tests could be invalid. New test are not added frequently. I'm not aware of CI testing done by the maintainer. For that reason, I have to say that mdadm meet SRU criteria. So, according to your questions: 1 - there are some test added a lot time ago and they are not updated frequently. They covers usecases mainly. New test are added rarely. 2- I don't know, but I think that it doesn't matter since it is tending to be rejected. 3- We (and community) submitted many bugfixes for many different problems. There are small improvements, there are fixes for potential DC too. Unfortunately, maintainer doesn't list features in announce file: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/tree/ANNOUNCE-4.2?id=e30ca260741d727e6f444e8f2ce25fe7a5a26567 4- We submitted many fixes and features for IMSM, all are validated, but as I wrote below- we are only a part of product. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890248 Title: SRU of mdadm to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868708] Re: mdmon: device descriptor is not closed
yes, it is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868708 Title: mdmon: device descriptor is not closed To manage notifications about this bug go to: https://bugs.launchpad.net/mdadm/+bug/1868708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
yes, it is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
John - thanks for finding ==> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081 There is a great testing work done there. For this thread I have been running kernel 4.15.0-144-generic for the last 3 weeks and haven't seen the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hey, We experienced the performance issue on different hardware servers: LENOVO System x3650 M5 Lenovo ThinkSystem SR650 with the following kernels: 4.15.0-137-generic: disk performance issue 4.15.0-139-generic: disk performance issue 4.15.0-140-generic: disk performance issue 4.15.0-142-generic: disk performance issue I haven't seen this issue on virtual machines (VMware VMs Ubuntu 18/20). At the moment, I'm testing "4.15.0-144-generic". To early to say it is free of the bug - I will come back in a week. Thanks Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi Khaled, I have finished testing the kernels - it took more time than I expected but the results are: 4.15.0-136-generic: no issues 4.15.0-137-generic: disk performance issue 4.15.0-139-generic: disk performance issue 4.15.0-140-generic: disk performance issue 4.15.0-142-generic: disk performance issue Each kernel was running for minimum 7 days. Those which have disk performance issue start to break after few days of normal workload. Here is an example of "iotop -a", when our disk operations are throttled: Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND 10908 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=XX replication=~o-password --directory=/data/barman/X/streaming --slot=barman 9494 be/4 barman0.00 B144.00 K 0.00 % 99.99 % rsync --server -logDtpre.iLsfxC . /data/barman/XX/incoming/0001318300ED 10907 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=XX replication~-password --directory=/data/barman/XXX/streaming --slot=barman 7148 be/4 barman0.00 B144.00 K 0.00 % 99.99 % rsync --server -logDtpre.iLsfxC . /data/barman/XX/incoming/0001D2E90043 11144 be/4 barman0.00 B144.00 K 0.00 % 99.99 % pg_receivewal --dbname=dbname=replication host=X replication=~o-password --directory=/data/barman/X/streaming --slot=barman 17724 be/3 root 0.00 B 8.00 K 0.00 % 99.99 % auditd 11217 be/4 root 0.00 B 8.00 K 0.00 % 99.99 % syslog-ng -F 10003 be/4 barman0.00 B 96.00 K 0.00 % 99.99 % gpg -e -r BarmanBackup 10219 be/4 barman0.00 B 96.00 K 0.00 % 99.99 % gpg -e -r BarmanBackup 9247 be/4 barman0.00 B140.00 K 0.00 % 98.62 % rsync --server -logDtpre.iLsfxC . /data/barman/mel-attn-hostdb/incoming/00014CE00083 11391 be/4 barman0.00 B140.00 K 0.00 % 98.60 % pg_receivewal --dbname=dbname=replication host=XXX replication=~o-password --directory=/data/barmanXXX/streaming --slot=barman 9556 be/4 barman0.00 B 92.00 K 0.00 % 98.53 % gpg -e -r BarmanBackup 4381 be/4 root 0.00 B 8.00 K 0.00 % 57.53 % sadc -F -L -S DISK 60 /var/log/sysstat 10959 be/4 root 0.00 B 4.00 K 0.00 % 26.29 % sadc -F -L -S DISK 60 /var/log/sysstat 15626 be/4 root 0.00 B 4.00 K 0.00 % 8.22 % sadc -F -L -S DISK 60 /var/log/sysstat So, I think it is ok to say that the problem was introduced with 4.15.0-137-generic. We will try to see the latest kernel in our next patching window. However, based on the fact that kernels 137,139,140,142 are not working correctly, could this be related to some tuning changes? In our case, we haven't done any changes to e.g. sysctl after patching. Many thanks for your help so far! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi, I have done longer testing of kernel 140 and it has performance degradation issue as well. It took a couple of days to fully max out disk IOs on that kernel with the same load. Therefore, I came back to testing the other kernels in longer time-window. At the moment, I'm running kernel 4.15.0-137-generic. Will leave it running for the next few days to see if there is any difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi, In the last 3 days, I have been testing the other kernels. The steps which I took: 1. Boot to kernel-4.15.0-136. 2. Install kernel X, where X = 136,137,139,140: sudo apt-get install linux-image-4.15.0-X-generic linux-headers-4.15.0-X-generic linux-modules-4.15.0-X-generic linux-modules-extra-4.15.0-X-generic 3. Boot to kernel X. 4. Manually run: sudo depmod 5. Reboot. 4. Run the server's normal workload and see how it was performing. I haven't seen disk performance issues with those kernels. But there is one difference, which I don't know how to explain. Before I raised this bug, we had the same disk performance issues on kernel-4.15.0-140. I collected the list of kernel modules running on that kernel at that time: Module Size Used by joydev 24576 0 input_leds 16384 0 hid_generic16384 0 usbhid 49152 0 hid 122880 2 usbhid,hid_generic ip6_tables 28672 0 iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 40960 3 iptable_filter,ip6_tables,ip_tables tcp_diag 16384 0 udp_diag 16384 0 inet_diag 24576 2 tcp_diag,udp_diag cpuid 16384 0 btrfs1155072 0 zstd_compress 163840 1 btrfs xor24576 1 btrfs raid6_pq 114688 1 btrfs ufs77824 0 qnx4 16384 0 minix 32768 0 ntfs 102400 0 msdos 20480 0 jfs 188416 0 xfs 1204224 0 libcrc32c 16384 1 xfs intel_rapl 20480 0 sb_edac24576 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm_intel 217088 0 kvm 614400 1 kvm_intel ipmi_ssif 32768 0 irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 pcbc 16384 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel cdc_ether 16384 0 usbnet 45056 1 cdc_ether mii16384 1 usbnet crypto_simd16384 1 aesni_intel glue_helper16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel intel_cstate 20480 0 intel_rapl_perf16384 0 ipmi_si57344 0 ipmi_devintf 20480 0 ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif shpchp 36864 0 mei_me 40960 0 mei94208 1 mei_me lpc_ich24576 0 acpi_power_meter 20480 0 acpi_pad 180224 0 mac_hid16384 0 bonding 163840 0 lp 20480 0 parport49152 1 lp autofs440960 2 mgag20045056 1 i2c_algo_bit 16384 1 mgag200 ttm 106496 1 mgag200 drm_kms_helper172032 1 mgag200 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper tg3 167936 0 sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper ptp20480 1 tg3 drm 401408 4 drm_kms_helper,mgag200,ttm pps_core 20480 1 ptp megaraid_sas 143360 12 mxm_wmi16384 0 wmi24576 1 mxm_wmi Now, after the testing we are running on kernel-4.15.0-140 (again) and this time I don't see the issue. But the list of kernel module is different: lsmod Module Size Used by intel_rapl 20480 0 sb_edac24576 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm_intel 217088 0 ipmi_ssif 32768 0 kvm 614400 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 pcbc 16384 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel crypto_simd16384 1 aesni_intel glue_helper16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel intel_cstate 20480 0 cdc_ether 16384 0 usbnet 45056 1 cdc_ether input_leds 16384 0 joydev 24576 0 mii16384 1 usbnet intel_rapl_perf16384 0 ipmi_si57344 0 ipmi_devintf 20480 0 ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif mei_me 40960 0 mei94208 1 mei_me lpc_ich
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Cool cool, I will try to do what you have suggested - that make sense. Will get back once I have some details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi, I have done another test and compared the same server running on 4.15.0-136-generic and kernel 4.15.0-142-generic. Collected zabbix CPU utilization graph which is showing the problem from the performance point of view. On 4.15.0-136-generic, the server works normal and there are no processes stuck on 99% iowait. On 4.15.0-142-generic it is not working at all and rsync, pg_receivewal or dd processes are hanging with iowait 99%. I attached the zabbix graph to this bug. ** Attachment added: "kernel_issue.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+attachment/5498858/+files/kernel_issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Unable to run apport-collect 1928744 command. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Thanks a lot for coming back to me. I couldn't run apport-collect as we don't have python-launchpadlib installed. I did check (apt install python3-launchpadlib) and in my case it would install quite a lot of dependent packages - we would like to avoid that due to the nature of our server. But I did collect a bug report with "ubuntu-bug linux-image-generic" and attached to this case. Hope this will be helpful. ** Attachment added: "apport.linux-image-generic.zrvzpzar.apport" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1928744/+attachment/5498602/+files/apport.linux-image-generic.zrvzpzar.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
** Package changed: ubuntu => linux-signed-hwe (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] [NEW] Disk IO very slow on kernel 4.15.0-142-generic
Public bug reported:
After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
4.15.0-142-generic disk IOs (writes) are suffering from terrible delay.
Time required to write 1GB of data to the dist is ~12 minutes.
1GB in 12 minutes:
strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero
of=/data/disk_test/dd_test
Before the upgrade, it took seconds to complete.
The only change which was done on the system was security upgrade done with
unattended-upgrade utility and main repositories for bionic and bionic-security.
This is physical server LENOVO System x3650 M5, with Symbios Logic
MegaRAID SAS-3 3108 disk controller.
The only difference which I see is that there are more modules loaded by
the latest kernel.
I would expect that the performance would be the same. There were no
changes to the physical server and the disks are reported as online and
healthy. No only dd is affected but also all disk-based operation by
barman (we are using postgres steaming backup along with rsync/ssh
archiving).
I think this could be a kernel bug. I would be happy to provide other
information which would help in fixing this problem.
=
Details:
lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
lsmod
Module Size Used by
ip6_tables 28672 0
iptable_filter 16384 0
ip_tables 28672 1 iptable_filter
x_tables 40960 3 iptable_filter,ip6_tables,ip_tables
tcp_diag 16384 0
udp_diag 16384 0
raw_diag 16384 0
inet_diag 24576 3 tcp_diag,raw_diag,udp_diag
unix_diag 16384 0
binfmt_misc20480 1
ipmi_ssif 32768 0
kvm_intel 217088 0
kvm 614400 1 kvm_intel
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel16384 0
pcbc 16384 0
aesni_intel 188416 0
aes_x86_64 20480 1 aesni_intel
crypto_simd16384 1 aesni_intel
glue_helper16384 1 aesni_intel
cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel
ipmi_si57344 0
ipmi_devintf 20480 0
ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif
acpi_pad 180224 0
bonding 163840 0
lp 20480 0
parport49152 1 lp
autofs440960 2
mgag20045056 1
i2c_algo_bit 16384 1 mgag200
ttm 106496 1 mgag200
drm_kms_helper172032 1 mgag200
syscopyarea16384 1 drm_kms_helper
tg3 167936 0
sysfillrect16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops16384 1 drm_kms_helper
ptp20480 1 tg3
drm 401408 4 drm_kms_helper,mgag200,ttm
pps_core 20480 1 ptp
megaraid_sas 143360 12
lspci -vnn -s 0b:00.0
0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19
Capabilities: [1c0] Power Budgeting
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas
Strace example for 10MB:
strace -ttvvff -o mel.strace dd bs=1024k count=10 if=/dev/zero
of=/data/disk_test/dd_test
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 6.73972 s, 1.6 MB/s
14:59:19.145037 execve("/bin/dd", ["dd", "bs=1024k", "count=10",
"if=/dev/zero", "of=/data/disk_test/dd_test"],
["LS_COLORS=rs=0:di=01;34:ln=01;36"..., "LESSCLOSE=/usr/bin/lesspipe %s %"...,
"LANG=en_AU.UTF-8", "SUDO_GID=4118", "USERNAME=root", "SUDO_COMMAND=/bin/bash",
"S_COLORS=auto", "USER=root", "PWD=/data/disk_test", "HOME=/root",
"SUDO_USER=mariusz.boruc", "SUDO_UID=4118", "MAIL=/var/mail/root",
"SHELL=/bin/bash", "TERM=xterm-256color", "SHLVL=1", "LANGUAGE=en_AU:",
"LOGNAME=root", "PATH=/usr/local/sbin:/usr/local/"..., "LESSOPEN=|
/usr/bin/lesspipe %s", "_=/usr/bin/strace", "OLDPWD=/data"]) = 0
14:59:19.145685
[Bug 1928236] [NEW] update mdadm for Hirsute
Public bug reported: Please update mdadm package for Hirsuteto latest upstream release. mdadm-4.2-rc1 was released for this moment. mdadm-4.2 on track. I will notify if mdadm 4.2 will become available. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928236 Title: update mdadm for Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1928236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890248] Re: update mdadm for focal
mdadm-4.2-rc-1 has been released officially. Could you update the mdadm version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890248 Title: update mdadm for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917049] [NEW] GRUB has installed on another drive
Public bug reported: Hi! I was installing Ubuntu and create /boot partition on sda6 (HDD). I picked this partition to install boot program. But in BIOS it shows that GRUB has been installed on another drive (SSD) - my main drive with Windows. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917049 Title: GRUB has installed on another drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1917049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911892] [NEW] package virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego
Public bug reported: Hallo, I installed Virtualbox from Ubuntu Software. I got a reply that Ubuntu has an error and cannot install Virtualbox. But Virtualbox was installed and it works. Some programs installed by Ubuntu Software also got not installed due to Virtualbox bug. But they did install. Unfortunately, I have no idea how to remove this error from the system. Yours sincerely, Mariusz. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 11:05:21 2021 ErrorMessage: problemy z zależnościami - pozostawianie nieskonfigurowanego InstallationDate: Installed on 2021-01-12 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: virtualbox Title: package virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.virtualbox: [deleted] modified.conffile..etc.init.d.virtualbox: [deleted] ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911892 Title: package virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1911892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758282] Re: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
Hello, fix for second problem has been accepted upstream: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=a64f1263a56bd8653267c1a9800daa0bc993a743 Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758282 Title: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1758282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890162] Re: Update mdadm for bionic
mdadm-4.2 not yet released. Feel free to close it if not applicable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890162 Title: Update mdadm for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890248] Re: update mdadm for focal
mdadm-4.2 not released yet. Feel free to close it if not applicable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890248 Title: update mdadm for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
Hi, Patch has been accepted upstream: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887143] Re: mdmonitor closes mdstat fd if is empty
Hi, sorry copy-paste mistake, here the correct ones: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=007087d0898a045901e4e120296e6d9b845b20a6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887143 Title: mdmonitor closes mdstat fd if is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887143] Re: mdmonitor closes mdstat fd if is empty
Hi, Patches have been accepted upstream: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887143 Title: mdmonitor closes mdstat fd if is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885191] Re: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885191 Title: [Focal] Installation Fails with "Invalid dep_id" when using Intel VROC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1885191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891151] Re: md: improve IO accounting
For 5.8 this is a simple backport with one conflict caused by function
md_make_request() renamed to md_submit_bio(). Then it can be easily
cherry picked to 5.4 but will need a change to use
generic_{start,end}_io_acct() instead of disk_{start,end}_io_acct(). I
can send you the backported patches if you wish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891151
Title:
md: improve IO accounting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891151] Re: md: improve IO accounting
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891151 Title: md: improve IO accounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893480] Re: undefined symbols
Renaming or deleting the offending .so files makes GIMP start. Ugly but effective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893480 Title: undefined symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1893480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893480] Re: undefined symbols
Me too (as of 2020-09-05): mariusz:~> gimp GEGL-Message: 22:03:19.420: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: /usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so: undefined symbol: _ZN7Imf_2_36HeaderC1EiifRKN9Imath_2_34Vec2IfEEfNS_9LineOrderENS_11CompressionE GEGL-Message: 22:03:19.851: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: /usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so: undefined symbol: _ZN7Imf_2_314ChromaticitiesC1ERKN9Imath_2_34Vec2IfEES5_S5_S5_ Gtk-Message: 22:03:20.360: Failed to load module "atk-bridge" (gimp:3451): Gtk-WARNING **: 22:03:23.947: Unable to locate theme engine in module_path: "adwaita", thread panicked while processing panic. aborting. Illegal instruction (core dumped) gegl amd64 0.4.24-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893480 Title: undefined symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1893480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758282] Re: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758282 Title: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1758282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887143] Re: mdmonitor closes mdstat fd if is empty
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887143 Title: mdmonitor closes mdstat fd if is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868708] Re: mdmon: device descriptor is not closed
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868708 Title: mdmon: device descriptor is not closed To manage notifications about this bug go to: https://bugs.launchpad.net/mdadm/+bug/1868708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811228] Re: Mdadm allows to change the name of the volume to empty and not trim whitespaces.
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811228 Title: Mdadm allows to change the name of the volume to empty and not trim whitespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1811228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890162] Re: Update mdadm for bionic
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890162 Title: Update mdadm for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890248] Re: update mdadm for focal
** Tags added: vrco ** Tags removed: vrco ** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890248 Title: update mdadm for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887372] Re: Cannot create lvm upon IMSM raid array
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887640] Re: IMSM: finish recovery when drive with rebuild fails
** Tags added: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887640 Title: IMSM: finish recovery when drive with rebuild fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891151] [NEW] md: improve IO accounting
Public bug reported: Currently reported IO stats may be incorrect or missing. This adds correct statistics about in-flight IOs and IO processing time, interpreted e.g. in iostat as await, svctm, aqu-sz and %util. Commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891151 Title: md: improve IO accounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1891151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890248] [NEW] update mdadm for focal
Public bug reported: Please update mdadm package for focal to latest upstream. mdadm-4.2 in on way but no release date was committed yet. Upstream contains a lot of various fixes for problems with specific hardware or system configuration. Also there are some fixes for sporadic bugs related with metadata updater (mdmon). I will notify if mdadm 4.2 will become available. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890248 Title: update mdadm for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890162] Re: Update mdadm for bionic
** Description changed: Mdadm version available in bionic was released in march 2018. Since it many various fixes has been added. The most common and important of them (from IMSM site) are already reported: https://bugs.launchpad.net/oem-priority/+bug/1868708 https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887640 However there is also many other bugs. Some of them are connected with specific hardware or system configuration, others are sporadic ones which occurs in certain conditions. Here the most important fixes, but not reported: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=9f4218274cd4a1e1f356a1617f9a1d09960cf255 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=69d084784de196acec8ab703cd1b379af211d624 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=d2e11da4b7fd0453e942f43e4196dc63b3dbd708 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=2b57e4fe041d52ae29866c93a878a11c07223cff https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=05501181f18cdccdb0b3cec1d8cf59f0995504d7 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=4ec389e3f0c1233f5aa2d5b4e63d96e33d2a37f0 There are also a lot of minor bugs and some features. Maintainer is working on releasing version 4.2, but it is still in progress. Please update mdadm to latest upstream for bionic. - I will notify if mdadm.4-2 becomes available. + I will notify if mdadm-4.2 becomes available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890162 Title: Update mdadm for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890162] [NEW] Update mdadm for bionic
Public bug reported: Mdadm version available in bionic was released in march 2018. Since it many various fixes has been added. The most common and important of them (from IMSM site) are already reported: https://bugs.launchpad.net/oem-priority/+bug/1868708 https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887640 However there is also many other bugs. Some of them are connected with specific hardware or system configuration, others are sporadic ones which occurs in certain conditions. Here the most important fixes, but not reported: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=9f4218274cd4a1e1f356a1617f9a1d09960cf255 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=69d084784de196acec8ab703cd1b379af211d624 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=d2e11da4b7fd0453e942f43e4196dc63b3dbd708 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=2b57e4fe041d52ae29866c93a878a11c07223cff https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=05501181f18cdccdb0b3cec1d8cf59f0995504d7 https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=4ec389e3f0c1233f5aa2d5b4e63d96e33d2a37f0 There are also a lot of minor bugs and some features. Maintainer is working on releasing version 4.2, but it is still in progress. Please update mdadm to latest upstream for bionic. I will notify if mdadm.4-2 becomes available. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890162 Title: Update mdadm for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1890162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
** Description changed: mdmonitor reacts on md events, it pools on /proc/mdstat file. Those events are generated if a change on any mddevice is observed in kernel. This is done asynchronously and can be caused by user space process (mdadm called by udev or user), or by kernel itself (drive is removed - because it have to much errors). + because it has to many errors). The problem here is that mdmonitor isn't dealing with user space or udev. When drive with metadata is inserted, mdadm adds it to mddevice (it is done by udev). Md Event is generated then and mdmonitor may try to move drive to other mddevice if needed. It relies on by-path links, but this link to newly appeared device is not created yet, udev is still working on. As a result recovery doesn't start immediately. Observed on Ubuntu 20.04. Steps to reproduce: 1. Create RAID volume: # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme1n1 /dev/nvme7n1 /dev/nvme3n1 --run - # mdadm --create /dev/md/r10d4s64-20_A --level=10 --chunk 64 --raid-devices=4 /dev/nvme6n1 /dev/nvme1n1 /dev/nvme7n1 /dev/nvme3n1 --run + # mdadm --create /dev/md/r10d4s64-20_A --level=10 --chunk 64 --raid-devices=4 /dev/nvme6n1 /dev/nvme1n1 /dev/nvme7n1 /dev/nvme3n1 --run 2. Add spare to container: # mdadm --add /dev/md/imsm0 /dev/nvme0n1 3. Create appropriate policy line in /etc/mdadm/mdadm.conf. POLICY domain=RAID_DOMAIN_1 path=* action=spare-same-slot - 4. Disconnect spare from container. 5. Start mdadm monitor with big delay (ex. 10 minutes): # mdadm --monitor --delay 6000 --scan --mail=root@localhost --daemonize --syslog 6. Hot remove disk from array (physical disconnect). 7. Connect previously prepared spare. - + Expected results: Rebuild should start. Actual results: Rebuild does not start, added spare is in separate container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
Hi, mdmonitor needs to deal with other tasks, issue still in development. Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] [NEW] mdmonitor doesn't start recovery immediately
Public bug reported: mdmonitor reacts on md events, it pools on /proc/mdstat file. Those events are generated if a change on any mddevice is observed in kernel. This is done asynchronously and can be caused by user space process (mdadm called by udev or user), or by kernel itself (drive is removed because it have to much errors). The problem here is that mdmonitor isn't dealing with user space or udev. When drive with metadata is inserted, mdadm adds it to mddevice (it is done by udev). Md Event is generated then and mdmonitor may try to move drive to other mddevice if needed. It relies on by-path links, but this link to newly appeared device is not created yet, udev is still working on. As a result recovery doesn't start immediately. Observed on Ubuntu 20.04. Steps to reproduce: 1. Create RAID volume: # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme1n1 /dev/nvme7n1 /dev/nvme3n1 --run # mdadm --create /dev/md/r10d4s64-20_A --level=10 --chunk 64 --raid-devices=4 /dev/nvme6n1 /dev/nvme1n1 /dev/nvme7n1 /dev/nvme3n1 --run 2. Add spare to container: # mdadm --add /dev/md/imsm0 /dev/nvme0n1 3. Create appropriate policy line in /etc/mdadm/mdadm.conf. POLICY domain=RAID_DOMAIN_1 path=* action=spare-same-slot 4. Disconnect spare from container. 5. Start mdadm monitor with big delay (ex. 10 minutes): # mdadm --monitor --delay 6000 --scan --mail=root@localhost --daemonize --syslog 6. Hot remove disk from array (physical disconnect). 7. Connect previously prepared spare. Expected results: Rebuild should start. Actual results: Rebuild does not start, added spare is in separate container. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887640] [NEW] IMSM: finish recovery when drive with rebuild fails
Public bug reported: Current version of mdadm doesn't have second fix for raid10. Mdmon is not able do handle end recovery if drive was disconnected while rebuild. Steps to reproduce: 1. Create RAID10 and wait for resync. #mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/sda /dev/sdb /dev/sde /dev/sdf –run #mdadm --create /dev/md/r10d4s64_A --level=10 --chunk 64 --raid-devices=4 /dev/sda /dev/sdb /dev/sde /dev/sdf –run 2. Degrade RAID 10 volume by disconnecting 2 drives. #mdadm -If sdb #mdadm -If sdf 3. Add spare drive. #mdadm --add /dev/md/imsm0 /dev/sdg 4. Wait for recovery start. 5. While rebuild, disconnect recovered member drive (spare added in step 4). 6. Add another spare drive. #mdadm --add /dev/md/imsm0 /dev/sdh 7. Wait for recovery start. Expected result: Recovery starts automatically. Actual result: Recovery does not start. Following fix resolves the issue: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=a4e96fd8f3f0b5416783237c1cb6ee87e7eff23d ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887640 Title: IMSM: finish recovery when drive with rebuild fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887372] Re: Cannot create lvm upon IMSM raid array
** Summary changed: - Cannot create lvm opon IMSM raid array + Cannot create lvm upon IMSM raid array -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887372] [NEW] Cannot create lvm opon IMSM raid array
Public bug reported: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm opon IMSM raid array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887143] Re: mdmonitor closes mdstat fd if is empty
Hello, The main issue is in development, we need to deal with module reload and descriptor handling. The second one can be easily workaround by using systemctl service (systemctl mdmonitor restart) instead of command line. Here error handling is needed instead of quiet fail. I will notify if any fix will become available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887143 Title: mdmonitor closes mdstat fd if is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887143] [NEW] mdmonitor closes mdstat fd if is empty
Public bug reported: There was a change in mdadm to fix issue when md_mod is reloaded (not a case for ubuntu because md_mod is build-in). Commit: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=52209d6ee1183581e148791cf6ee4d60a0193b1d The fix prevents mdmonitor from occupying mdstat file descriptor in there is no any mddevice available. As a side effect mdmonitor cannot react on md events because it is waiting in undefined resource (probably 1 which in demonize mode case is /dev/null). When mdmonitor is started form command line and there was one mdmonitor already active, error message also is omitted, because error is thrown after forking. As a result, unexpectedly we may got same same issue after array creation. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887143 Title: mdmonitor closes mdstat fd if is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1887143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868708] Re: mdmon: device descriptor is not closed
Hi, issue is fixed by: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=91c97c5432028875db5f8abeddb5cb5f31902001 Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868708 Title: mdmon: device descriptor is not closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1868708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868708] [NEW] mdmon: device descriptor is not closed
Public bug reported: When device disappears from the system "mdadm -If" is triggered by udev and drive is removed from the corresponding array and container. The missing close() in metadata manager (mdmon) causes that userspace handler to the device is still opened (can be tracked by lsof -p ). For nvme drives it causes weird namespace number after hot-plug (e.g. will appear nvme1n2). The issue affects only IMSM metadata format. Reproducible on Focal with latest mdadm 4.1-5ubuntu1. Steps: 1. Create IMSM container: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 2. Create IMSM array: #mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 3. remove via sysfs drive: #echo 1 > /sys/block/nvme0n1/device/device/remove 4. restore the same drive: #echo 1 > /sys/bus/pci/rescan 5. see mdstat and lsblk: # cat /proc/mdstat Result: /dev/nvme0n2 appears in system. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868708 Title: mdmon: device descriptor is not closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1868708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758282] Re: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
Hi, We have two issues here: 1. mdraid stuff is always included in initrd even system isn't on raid( ubuntu specific). 2. grow continue service is not restarted after switch root( to be fixed in upstream) First one should be detected and managed in ubuntu installer. This is how it is done in other distributions. It will hide second problem when system is not on raid. Initial ram disk should be minimal as possible, in this case md stuff is unnecessary. As Pawel wrote reshape is managed by mdadm-grow-continue@.service or fork which is started by mdadm (if needed) as a last step of raid assembly. If it is started in initrd then it is not restarted after switch root because raid assemblation is already done. No fix for today- work in progress. Please look into first one. I think that it is not a mdadm defect now, new launchpad is needed? I will notify this lp when fix for second defect appears. Thanks Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758282 Title: [INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1758282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
Please note that on a Dell laptop everything works as expected. The difference most probably is caused by hardware in the laptop. Two different modems do not work with Toshiba and both of them work with Dell. The same up-to-date "focal fossa" system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
Make the comment on Kubuntu irrelevant. I have launched Kubuntu Live CD daily and the same behavior can be observed. The laptop is Toshiba Satellite L755. Let me know if I can provide any further useful information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
On Kubuntu @ Dell with the same modem: cat /var/log/usb_modeswitch.log USB_ModeSwitch log from Thu Mar 12 20:09:49 2020 Use global config file: /etc/usb_modeswitch.conf Adjust delay for USB storage devices ... Error: could not access delay_use attribute: No such file or directory Raw args from udev: 3-4 Bus ID for device not given by udev. Trying to determine it from kernel name (3-4) ... Use top device dir /sys/bus/usb/devices/3-4 USB dir exists: /sys/bus/usb/devices/3-4 SCSI dir exists: /sys/bus/usb/devices/3-4 Warning: SCSI attribute "vendor" not readable. Warning: SCSI attribute "model" not readable. Warning: SCSI attribute "rev" not readable. Use interface /sys/bus/usb/devices/3-4/3-4:1.0 USB values from sysfs: idVendor 2001 idProduct a706 manufacturer D-Link,Inc product D-Link DWM-156 serial536591500189710 bNumConfigurations3 bConfigurationValue 1 devnum3 busnum3 Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz Searching entries named: /usr/share/usb_modeswitch/2001:a706* Searching overriding entries named: /etc/usb_modeswitch.d/2001:a706* SCSI attributes not needed, move on. Extract config 2001:a706 from collection /usr/share/usb_modeswitch/configPack.tar.gz config: TargetVendor set to 2001 config: TargetProduct set to 7d01 Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1 ! matched, now switching Device may have an MBIM configuration, check driver ... no MBIM driver found, switch to legacy modem mode Unbinding driver Command to be run: /usr/sbin/usb_modeswitch -W -D -s 20 -c /run/usb_modeswitch/current_cfg -b 3 -g 3 -v 2001 -p a706 2>&1 Verbose debug output of usb_modeswitch and libusb follows (Note that some USB errors are expected in the process) Read config file: /run/usb_modeswitch/current_cfg * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x2001 DefaultProduct= 0xa706 TargetVendor= 0x2001 TargetProduct= 0x7d01 StandardEject=1 Success check enabled, max. wait time 20 seconds System integration mode enabled Use given bus/device number: 003/003 ... Look for default devices ... bus/device number matched found USB ID 2001:a706 vendor ID matched product ID matched Found devices in default mode (1) Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: D-Link,Inc Product: D-Link DWM-156 Serial No.: 536591500189710 - Sending standard EJECT sequence Looking for active drivers ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Read the response to message 1 (CSW) ... Response successfully read (13 bytes), status 0 Trying to send message 2 to endpoint 0x01 ... OK, message successfully sent Read the response to message 2 (CSW) ... Response successfully read (13 bytes), status 0 Trying to send message 3 to endpoint 0x01 ... OK, message successfully sent Read the response to message 3 (CSW) ... Device seems to have vanished after reading. Good. Device is gone, skip any further commands ok:busdev (end of usb_modeswitch output) Check success of mode switch for max. 20 seconds ... Read attributes ... USB dir exists: /sys/bus/usb/devices/3-4 Warning: USB attribute "serial" not readable. All attributes matched Mode switching was successful, found 2001:7d01 (D-Link,Inc: D-Link DWM-156)Now check for bound driver ... no driver has bound to interface 0 yet Device not in "bind_list" yet, bind it now Module loader is /sbin/modprobe Module is active already Try to add ID to driver "option" ID added to driver; check for new devices in /dev driver binding failed Check for AVOID_RESET_QUIRK kernel attribute AVOID_RESET_QUIRK activated All done, exit mariusz:~> lsusb Bus 002 Device 004: ID 0cf3:e004 Qualcomm Atheros Communications Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0c45:648b Microdia Integrated Webcam Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 2001:7d01 D-Link Corp. D-Link DWM-156 Bus 003 Device 002: ID 24ae:2003 RAPOO RAPOO 5G Wireless Device
[Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
064/cgroup/anon_vma_chain(1373:usb_modeswitch@2-1.2.service) (cgroup) KERNEL[2854.728674] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0 (scsi) KERNEL[2854.728808] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0 (scsi) UDEV [2854.735181] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0 (scsi) UDEV [2854.740568] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0 (scsi) KERNEL[2854.759608] add /devices/virtual/bdi/11:1 (bdi) KERNEL[2854.759686] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr1 (block) KERNEL[2854.759958] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0 (scsi) KERNEL[2854.759996] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device) KERNEL[2854.760115] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[2854.760232] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg) UDEV [2854.761707] add /devices/virtual/bdi/11:1 (bdi) KERNEL[2854.764840] change /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr1 (block) UDEV [2854.897603] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr1 (block) UDEV [2854.904413] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0 (scsi) UDEV [2854.908717] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/scsi_device/6:0:0:0 (scsi_device) UDEV [2854.909051] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [2854.909843] add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/bsg/6:0:0:0 (bsg) UDEV [2854.992291] change /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host6/target6:0:0/6:0:0:0/block/sr1 (block) KERNEL[2855.103425] remove /dentry(1359:media-mariusz-D\x2dLink\x20Modem.mount) (cgroup) UDEV [2855.104678] remove /dentry(1359:media-mariusz-D\x2dLink\x20Modem.mount) (cgroup) Manual execution of usb_modeswitch: $ sudo usb_modeswitch -v 0x2001 -p 0xa706 -c /etc/usb_modeswitch.d/2001:a706 Look for target devices ... No devices in target mode or class found Look for default devices ... Found devices in default mode (1) Access device 017 on bus 002 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) Looking for active drivers ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Read the response to message 1 (CSW) ... Response successfully read (13 bytes), status 0 Reset response endpoint 0x81 Reset message endpoint 0x01 -> Run lsusb to note any changes. Bye! mariusz@Tosia:/usr/share/usb_modeswitch$ lsusb Bus 002 Device 004: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller Bus 002 Device 018: ID 2001:7d01 D-Link Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b289 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 24ae:2003 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub As mentioned before same up-to-date Kubuntu works like a charm. Another thing I noticed is that the Mobile Broadband no longer has a menu item in the upper-right menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
** Package changed: ubuntu => usb-modeswitch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866926] [NEW] usb_modeswitch does not switch modems (remain visible as mass storage)
Public bug reported: After upgrading to Ubuntu focal fossa development branch the usb_modeswitch does not seem to work any more on a Toshiba laptop. Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from the terminal. I have a strong feeling that it may either be related to Gnome or hardware. On another Dell laptop with Kubuntu focal fossa development, both modems connect automatically. /var/log/usb_modeswitch.log ends with: Warning: SCSI attribute "ref" not readable. Check class of first interface ... Device is in istall mode. No access to interface 8. Exit Up until and including the "ref" not readable is exactly the same as on Kubuntu @ Dell. Yet on Kubuntu I get plenty of successful config logs after that and on Ubuntu @ Toshiba I don't. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1866926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792085] Re: Regression: MTP not working/very slow
I have just tried installing libmtp-1.1.17-2 on 18.04 from here: https://launchpad.net/ubuntu/+source/libmtp/1.1.17-2/+build/18694144 files: libmtp-common_1.1.17-2_all.deb libmtp-runtime_1.1.17-2_amd64.deb libmtp9_1.1.17-2_amd64.deb (disconnect phone and after installation log out and log in back to the system or reboot for new libraries to be loaded) Now listing files is quick and I can actually transfer files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855254] Re: Update ledmon to 0.94 to include NPEM support
Hi, New version of ledmon has been released. https://github.com/intel/ledmon/releases/tag/0.94 Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855254 Title: Update ledmon to 0.94 to include NPEM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1855254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855254] [NEW] Update ledmon to latest upstream version
Private bug reported: New version of ledmon (v0.94) may contain following features: - NPEM support Ledmon’s extension including feature above is in active development. Final version will be included in GitHub repository: https://github.com/intel/ledmon Pull request will be triggered on this Bugzilla. Intel can come back with specific commit requests if needed. ** Affects: ledmon (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855254 Title: Update ledmon to latest upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1855254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821638] Re: xfwm4-settings assert failure: xfwm4-settings: ../../../../src/cairo-surface.c:1734: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed.
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821638 Title: xfwm4-settings assert failure: xfwm4-settings: ../../../../src/cairo- surface.c:1734: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1821638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811228] Re: Mdadm allows to change the name of the volume to empty and not trim whitespaces.
Hi, the issue is fixed in bionic-proposed. Thanks Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811228 Title: Mdadm allows to change the name of the volume to empty and not trim whitespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1811228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811795] Re: Mdadm: external metadata arrays and containers are removed incorrectly
Hi, the issue is fixed in bionic-proposed. Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811795 Title: Mdadm: external metadata arrays and containers are removed incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1811795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] Re: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811228] Re: Mdadm allows to change the name of the volume to empty and not trim whitespaces.
Hi, The issue is fixed in PPA. Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811228 Title: Mdadm allows to change the name of the volume to empty and not trim whitespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1811228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811795] Re: Mdadm: external metadata arrays and containers are removed incorrectly
Hi, Here test steps: 1. Create IMSM Container: mdadm -CR imsm0 -e imsm -n 2 /dev/sd[bc] 2. Create IMSM level 0 Array: mdadm -CR vol0 -l 0 -n 2 /dev/sd[bc] 3. Wait for resync to complete mdadm --wait /dev/md/vol0 4. Read /proc/mdstat and check /dev/md/ directory cat /proc/mdstat ls /dev/md/ 5. Fail one disk incrementaly (simulate device disappearing from system) mdadm -If sdc 6. Check mdstat file and /dev/md/ cat /proc/mdstat ls /dev/md/ Result: After disk fail [5] raid 0 array should disappear from mdstat, link /dev/md/imsm0 should exist. The issue is fixed in PPA. Thanks, Mariusz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811795 Title: Mdadm: external metadata arrays and containers are removed incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1811795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
In general nvidia-drm.modeset=1 is required to have Nvidia PRIME enabled, which reduces (or even removes) tearing of moving images on Optimus setups. KMS - kernel mode settings, allows kernel to control video card and in Optimus setups, among other features, this allows to synchronize graphics buffers by both graphics cards - so there are no artifacts/tearing/etc, because before displaying anything on monitor buffers are fully copied from one card to another. When modeset is disabled for Nvidia driver - buffers of both graphics cards cannot be synchronized properly so sometimes images that are displayed are only partially updated and this is visible as taring or other similar artifacts (part of the screen is filled with current frame and part of the screen is filled with previous frame). The problem is that for some reason when KMS is enabled for Nvidia driver - vulkan requires root privileges to be initialized properly. After initialization for the first time (as root), it can be used with normal user privileges. The bug is still there on Ubuntu 18.04 with newer drivers and kernel: nvidia-driver-418 linux-image-4.18.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
The bug is still there on Ubuntu 18.04 with newer drivers and kernel: nvidia-driver-418 linux-image-4.18.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143]
I'm on Xubuntu 19.04 Disco Dingo now and I still have this issue with Window Manager settings window. It doesn't always crash, but the issue with disappearing buttons when changing the layout is all the time, easy to reproduce. xfwm4 4.13.1-3~19.04, VirtualBox VM Bug reports from Launchpad related to this issue: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1821638 https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1821517 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] Re: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
I have the same issue on Xubuntu 19.04 Disco Dingo with some development PPAs. xfce4-settings: Installed: 4.13.4-1ubuntu2 ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821638] [NEW] xfwm4-settings assert failure: xfwm4-settings: ../../../../src/cairo-surface.c:1734: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed
Public bug reported: I opened Window Manager settings from the main Settings Manager, then I tried to change button layout. The Window Manager window closed and I was back in the main Settings Manager window. After some time I saw a crash report window. Sometimes it works fine (I can change the layout without a crash), but I still have this bug: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1821517 It seems related to this bug also: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143 Tested in VirtualBox VM, with additional Xubuntu Development PPAs 4.13.1-3~19.04 ** Affects: xfwm4 (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Attachment added: "_usr_bin_xfwm4-settings.1000.crash" https://bugs.launchpad.net/bugs/1821638/+attachment/5249254/+files/_usr_bin_xfwm4-settings.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821638 Title: xfwm4-settings assert failure: xfwm4-settings: ../../../../src/cairo- surface.c:1734: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1821638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815255] [NEW] ubuntu 18.04 freezes randomly
Public bug reported: unable to do anything, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: godzill22 1619 F pulseaudio /dev/snd/controlC0: godzill22 1619 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 8 23:28:34 2019 InstallationDate: Installed on 2018-12-22 (48 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_K505ZA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=45dac615-9bbf-4809-8615-e47376e42226 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505ZA.305:bd06/01/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_K505ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUS Laptop X505ZA_K505ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815255 Title: ubuntu 18.04 freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811795] [NEW] Mdadm: external metadata arrays and containers are removed incorrectly
Private bug reported: Steps to reproduce: 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks Expected result: R0 Array should disappear form /proc/mdstat. Actual result: R0 array is visible in mdstat, link to container in /dev/md/ is removed. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811795 Title: Mdadm: external metadata arrays and containers are removed incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1811795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808339] Re: partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem - wrong swap partition size
** Description changed:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
d-i partman-auto/expert_recipe string \
boot-root ::\
40 512 512 ext4 \
$primary{ } $bootable{ }\
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
mountpoint{ /boot } \
. \
2048 1 10 ext4 \
$lvmok{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
mountpoint{ / } \
. \
1024 2000 100% linux-swap \
$lvmok{ } \
method{ swap } format{ }\
.
Below is the correct operation (from an older server)
Disk /dev/sda: 999.0 GB, 998999326720 bytes
255 heads, 63 sectors/track, 121454 cylinders, total 1951170560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b7b5d
Device Boot Start End Blocks Id System
/dev/sda1 *2048 391167 194560 83 Linux
/dev/sda2 393214 1951168511 9753876495 Extended
/dev/sda5 393216 1884870655 942238720 83 Linux
/dev/sda6 1884872704 195116851133147904 82 Linux swap / Solaris
Below from the new installation
Disk /dev/sda: 931.5 GiB, 1000171331584 bytes, 1953459632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: dos
Disk identifier: 0x8a964ccf
Device Boot StartEndSectors Size Id Type
/dev/sda1 * 2048 999423 997376 487M 83 Linux
/dev/sda2 1001470 1953458175 1952456706 931G 5 Extended
/dev/sda5 1001472 1951459327 1950457856 930.1G 83 Linux
/dev/sda6 1951461376 19534581751996800 975M 82 Linux swap /
Solaris
Partition 2 does not start on physical sector boundary.
Both servers have 32GB RAM (identical machines). As you can see in the
new installation, the swap partition is created in the smallest size.
For the test I reinstalled one of the servers from 16/04 to 16/04 and
after the reinstallation the situation is the same.
I found information about the bug -
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299 -
maybe something similar?
What other information can I provide?
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
+
+
+ For me it is a huge problem. I have a machine with 128GB ram and more. Huge
disks ... every server after installation I have to run the server from
sysrecuecd and move the partitions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808339
Title:
partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem -
wrong swap partition size
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1808339/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808339] Re: partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem - wrong swap partition size
** Description changed:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
d-i partman-auto/expert_recipe string \
- boot-root ::\
- 40 512 512 ext4 \
- $primary{ } $bootable{ }\
- method{ format } format{ } \
- use_filesystem{ } filesystem{ ext4 }\
- mountpoint{ /boot } \
- . \
- 2048 1 10 ext4 \
- $lvmok{ } \
- method{ format } format{ } \
- use_filesystem{ } filesystem{ ext4 }\
- mountpoint{ / } \
- . \
- 1024 2000 100% linux-swap \
- $lvmok{ } \
- method{ swap } format{ }\
- .
+ boot-root ::\
+ 40 512 512 ext4 \
+ $primary{ } $bootable{ }\
+ method{ format } format{ } \
+ use_filesystem{ } filesystem{ ext4 }\
+ mountpoint{ /boot } \
+ . \
+ 2048 1 10 ext4 \
+ $lvmok{ } \
+ method{ format } format{ } \
+ use_filesystem{ } filesystem{ ext4 }\
+ mountpoint{ / } \
+ . \
+ 1024 2000 100% linux-swap \
+ $lvmok{ } \
+ method{ swap } format{ }\
+ .
Below is the correct operation (from an older server)
Disk /dev/sda: 999.0 GB, 998999326720 bytes
255 heads, 63 sectors/track, 121454 cylinders, total 1951170560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b7b5d
-Device Boot Start End Blocks Id System
+ Device Boot Start End Blocks Id System
/dev/sda1 *2048 391167 194560 83 Linux
/dev/sda2 393214 1951168511 9753876495 Extended
/dev/sda5 393216 1884870655 942238720 83 Linux
/dev/sda6 1884872704 195116851133147904 82 Linux swap / Solaris
-
Below from the new installation
Disk /dev/sda: 931.5 GiB, 1000171331584 bytes, 1953459632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: dos
Disk identifier: 0x8a964ccf
Device Boot StartEndSectors Size Id Type
/dev/sda1 * 2048 999423 997376 487M 83 Linux
/dev/sda2 1001470 1953458175 1952456706 931G 5 Extended
/dev/sda5 1001472 1951459327 1950457856 930.1G 83 Linux
/dev/sda6 1951461376 19534581751996800 975M 82 Linux swap /
Solaris
Partition 2 does not start on physical sector boundary.
- Both servers have 32GB RAM. As you can see in the new installation, the
- swap partition is created in the smallest size.
+ Both servers have 32GB RAM (identical machines). As you can see in the
+ new installation, the swap partition is created in the smallest size.
For the test I reinstalled one of the servers from 16/04 to 16/04 and
after the reinstallation the situation is the same.
I found information about the bug -
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299 -
maybe something similar?
What other information can I provide?
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808339
Title:
partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem -
wrong swap partition size
To manage notifications about this bug go to:
[Bug 1808339] [NEW] partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem - wrong swap partition size
Public bug reported:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
d-i partman-auto/expert_recipe string \
boot-root ::\
40 512 512 ext4 \
$primary{ } $bootable{ }\
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
mountpoint{ /boot } \
. \
2048 1 10 ext4 \
$lvmok{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 }\
mountpoint{ / } \
. \
1024 2000 100% linux-swap \
$lvmok{ } \
method{ swap } format{ }\
.
Below is the correct operation (from an older server)
Disk /dev/sda: 999.0 GB, 998999326720 bytes
255 heads, 63 sectors/track, 121454 cylinders, total 1951170560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b7b5d
Device Boot Start End Blocks Id System
/dev/sda1 *2048 391167 194560 83 Linux
/dev/sda2 393214 1951168511 9753876495 Extended
/dev/sda5 393216 1884870655 942238720 83 Linux
/dev/sda6 1884872704 195116851133147904 82 Linux swap / Solaris
Below from the new installation
Disk /dev/sda: 931.5 GiB, 1000171331584 bytes, 1953459632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: dos
Disk identifier: 0x8a964ccf
Device Boot StartEndSectors Size Id Type
/dev/sda1 * 2048 999423 997376 487M 83 Linux
/dev/sda2 1001470 1953458175 1952456706 931G 5 Extended
/dev/sda5 1001472 1951459327 1950457856 930.1G 83 Linux
/dev/sda6 1951461376 19534581751996800 975M 82 Linux swap / Solaris
Partition 2 does not start on physical sector boundary.
Both servers have 32GB RAM. As you can see in the new installation, the
swap partition is created in the smallest size.
For the test I reinstalled one of the servers from 16/04 to 16/04 and
after the reinstallation the situation is the same.
I found information about the bug -
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299 -
maybe something similar?
What other information can I provide?
lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
** Affects: partman-auto (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808339
Title:
partman-auto netboot kickstart preseed 18.04 16.04 14.04 problem -
wrong swap partition size
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1808339/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
As a workaround one needs to run (after each reboot): sudo vulkaninfo and then all vulkan apps start to work properly until system is shut down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
This helped to solve the problem. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
Hello, Attached you will find file. I have reinstalled the drivers since reporting the message, but the sound does not come back and I need to restart it in the terminal. it only helps "alsa force-reload". ** Attachment added: "all.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+attachment/5207164/+files/all.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800272] [NEW] [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: After update to 18.10 no sound in internal speakers and jackport. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 11:10:22 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (820 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-10-21 (6 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.00 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.3E dmi.chassis.asset.tag: CNU14045VQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.00:bd02/14/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.3E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6460b dmi.product.sku: LG643EA#AKD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
I can confirm this is still an issue. My setup is: Ubuntu 18.04 MSI GE60 Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel HD 4600 + GeForce GTX 760M nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA) nvidia-prime for switching cards With nvidia-drm.modeset=1 until some vulkan app is run as root the vulkaninfo crashes like this: == VULKANINFO == Vulkan Instance Version: 1.1.82 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 INTEL-MESA: warning: Haswell Vulkan support is incomplete INTEL-MESA: warning: ../../../src/intel/vulkan/anv_device.c:1150: FINISHME: Implement pop-free point clipping Instance Extensions: Instance Extensions count = 17 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 9 VK_EXT_debug_utils : extension revision 1 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_KHR_device_group_creation: extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities: extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2: extension revision 1 VK_KHR_get_surface_capabilities2: extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 Layers: count = 3 === VK_LAYER_LUNARG_standard_validation (LunarG Standard Validation Layer) Vulkan version 1.0.82, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 VK_LAYER_VALVE_steam_overlay_32 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 VK_LAYER_VALVE_steam_overlay_64 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1 Layer Extensionscount = 0 Devices count = 2 GPU id : 0 (Intel(R) Haswell Mobile) Layer-Device Extensions count = 0 GPU id : 1 (GeForce GTX 760M) Layer-Device Extensions count = 0 Presentable Surfaces: = GPU id : 0 (Intel(R) Haswell Mobile) Surface type : VK_KHR_xcb_surface Formats:count = 2 B8G8R8A8_SRGB B8G8R8A8_UNORM Present Modes: count = 3 IMMEDIATE_KHR MAILBOX_KHR FIFO_KHR VkSurfaceCapabilitiesKHR: = minImageCount = 2 maxImageCount = 0 currentExtent: width = 256 height = 256 minImageExtent: width = 256 height = 256 maxImageExtent: width = 256 height = 256 maxImageArrayLayers = 1 supportedTransform: VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR currentTransform: VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR supportedCompositeAlpha: VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR supportedUsageFlags: VK_IMAGE_USAGE_TRANSFER_SRC_BIT VK_IMAGE_USAGE_TRANSFER_DST_BIT VK_IMAGE_USAGE_SAMPLED_BIT VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT VkSurfaceCapabilities2EXT: == supportedSurfaceCounters: None GPU id : 1 (GeForce GTX 760M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-WIuZIg/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Aborted (core dumped) I have added some logs to vulkaninfo to check what is the value of vkGetPhysicalDeviceSurfaceFormatsKHR function that leads to abort and it is: -3 (VK_ERROR_INITIALIZATION_FAILED)
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Submitted: https://bugs.freedesktop.org/show_bug.cgi?id=106529 ** Bug watch added: freedesktop.org Bugzilla #106529 https://bugs.freedesktop.org/show_bug.cgi?id=106529 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Just checked and nothing changes – monitors in standby get treated as hotplugged. So unless someone can get upstream interested, multi monitor on amd stays kind of broken for who knows how long. I really should've bought an nvidia card. :/ ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
Looks like I'm not the only one: https://bugs.freedesktop.org/show_bug.cgi?id=104300. And, interestingly enough, running 4.15 with amdgpu.dc=0 makes this issue happen, but not 100% of the time (had it work correctly when waking computer from sleep, but have a problem when only the monitors went to sleep and the computer was on). So whatever amdgpu changes were made between 4.14 and 4.15, introduce this issue a bit even on the non- DC code path. ** Bug watch added: freedesktop.org Bugzilla #104300 https://bugs.freedesktop.org/show_bug.cgi?id=104300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work, using 4.4.15 (and 4.15 with amdgpu.dc=0): https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work, using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. When waking the displays from sleep with 4.15 any display not yet fully woken up seem to be reported as disconnected. This happens both when waking the whole computer from sleep (systemctl suspend) or just the displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work, using 4.4.15 (and 4.15 with amdgpu.dc=0): https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmazur 2270 F pulseaudio /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770836] Re: amdgpu+xorg possibly marks displays as off while they wake from sleep
** Description changed: Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE. - When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display - not yet fully woken up seem to be reported as disconnected. This happens - both when waking the whole computer from sleep (systemctl suspend) or - just the displays themselves (due to me not touching mouse+keyboard for - a while). + When waking the displays from sleep with 4.15 any display not yet fully + woken up seem to be reported as disconnected. This happens both when + waking the whole computer from sleep (systemctl suspend) or just the + displays themselves (due to me not touching mouse+keyboard for a while). Setup: Radeon RX 560 Primary display: bottom right, displayport, on Secondary display 1: left, hdmi, on Secondary display 2: top right, dvi, off - Video of how it should work using 4.4.15 and amdgpu.dc=0: https://www.youtube.com/watch?v=h7nMYbm5ZxU + Video of how it should work using 4.4.15: https://www.youtube.com/watch?v=h7nMYbm5ZxU Note how even though the left (secondary) display wakes up first, both instantly display their proper desktops. Video of how it works with the current default kernel (and 4.16.7 from kernel-ppa/mainline): https://www.youtube.com/watch?v=VdVFNXPszSI Note how when the left (secondary) display wakes up first, KDE decides that this is probably the only display available, so tries to switch the primary desktop to it, then a split second later the bottom right wakes up and KDE knows *that* should be the primary according to the config, so it switches back. My interpretation is that KDE thinks the bottom right display slowly waking up is actually off, so it does the reasonable thing and uses the other available one as primary. - One way or the other, that's not how it used to work in older kernels (which defaulted to amdgpu.dc=0), so as far as I'm concerned it's a regression. - --- + One way or the other, that's not how it used to work in older kernels, so as far as I'm concerned it's a regression. + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mmazur 2270 F pulseaudio - /dev/snd/controlC1: mmazur 2270 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mmazur 2270 F pulseaudio + /dev/snd/controlC1: mmazur 2270 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d170afa1-e8de-4480-a0d7-4a4e8e304caf ro amdgpu.dc_log=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: - linux-restricted-modules-4.15.0-20-generic N/A - linux-backports-modules-4.15.0-20-generic N/A - linux-firmware 1.173 + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 RfKill: - 1: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 1: hci0: Bluetooth + Soft blocked: no + Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bacula cdrom dip docker libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97E-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/29/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97E-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770836 Title: amdgpu+xorg possibly marks displays as off while they wake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
