[Bug 2068061] [NEW] Since Ubuntu 23.10 driverless printing is broken using a HP Color LaserJet MFP 280nw
Public bug reported: The print hangs in the queue and wont get printed. It worked with 22.04 and I think 22.10. But since driverless 2.0.0 it didnt work anymore. The error is: cfFilterExternal (ipp): Backend (PID 537356) stopped with status 4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: cups 2.4.7-1.2ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [04/Jun/2024:07:23:28 +0200] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 E [04/Jun/2024:07:23:28 +0200] Missing value on line 440 of /var/cache/cups/job.cache. W [04/Jun/2024:09:11:26 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M280nw_83DB46-Gray..\' already exists W [04/Jun/2024:09:11:26 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M280nw_83DB46-DeviceN..\' already exists CurrentDesktop: KDE Date: Tue Jun 4 22:16:44 2024 InstallationDate: Installed on 2022-10-13 (600 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_ColorLaserJet_MFP_M278-M281: dnssd://HP%20Color%20LaserJet%20MFP%20M280nw%20(83DB46)._pdl-datastream._tcp.local/?uuid=564e424e-4d34-5638-4b32-9c7bef83db46 MachineType: ASUS System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: cups UpgradeStatus: Upgraded to noble on 2024-05-27 (9 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068061 Title: Since Ubuntu 23.10 driverless printing is broken using a HP Color LaserJet MFP 280nw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2068061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063995] [NEW] package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to install/upgrade: »neues pre-installation-Skript des Paketes thunderbird«-Unterprozess gab den Fehlerwert 1 zurück
Public bug reported: tried upgrade to Ubuntu 24.04 later upgrade failed completely ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rbur 2287 F wireplumber /dev/snd/controlC1: rbur 2287 F wireplumber /dev/snd/seq:rbur 2281 F pipewire BuildID: 20240417192958 CasperMD5CheckResult: pass Channel: Unavailable Date: Sun Apr 28 11:44:44 2024 ErrorMessage: »neues pre-installation-Skript des Paketes thunderbird«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False InstallationDate: Installed on 2024-01-15 (103 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.178.1 dev eno1 proto dhcp src 192.168.178.103 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.178.0/24 dev eno1 proto kernel scope link src 192.168.178.103 metric 100 MachineType: LENOVO 11TBS1UL00 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to install/upgrade: »neues pre-installation-Skript des Paketes thunderbird«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to noble on 2024-04-28 (0 days ago) dmi.bios.date: 10/31/2023 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: M41KT4BA dmi.board.name: 32CB dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN 3556131491778 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.53 dmi.modalias: dmi:bvnLENOVO:bvrM41KT4BA:bd10/31/2023:br1.75:efr1.53:svnLENOVO:pn11TBS1UL00:pvrThinkCentreM70sGen3:rvnLENOVO:rn32CB:rvrSDK0T76530WIN3556131491778:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_11TB_BU_Think_FM_ThinkCentreM70sGen3: dmi.product.family: ThinkCentre M70s Gen 3 dmi.product.name: 11TBS1UL00 dmi.product.sku: LENOVO_MT_11TB_BU_Think_FM_ThinkCentre M70s Gen 3 dmi.product.version: ThinkCentre M70s Gen 3 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063995 Title: package thunderbird 1:115.10.1+build1-0ubuntu0.23.10.1 failed to install/upgrade: »neues pre-installation-Skript des Paketes thunderbird«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2063995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058133] Re: [SRU] update-manager crashes when ua security-status response is an error
Hallo Andreas, also so ganz schlau bin ich aus dem Ganzen nicht geworden. Denn meine Aktualisierungsverwaltung hakt nach wie vor. Wenn ich hingegen den von Dir übermittelten Befehl eingebe im Terminal, aktualisiert das alles problemlos. mfG Rainer Bruns Am 11.04.24 um 21:08 schrieb Andreas Hasenack: > Focal still has an ubuntu-release-upgrader regression on armhf. I > triggered that one again. > > Jammy is ok. > > Bionic is ok, but can't be released before focal. > > The xenial upload is still in unapproved, probably because there is another > xenial SRU going on > in xenial-proposed: 1:16.04.21 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058133 Title: [SRU] update-manager crashes when ua security-status response is an error To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2058133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi Matthew, I think I will leave except you want to do some tests. I think you tested it with a latest NFS Server version and maybe the NFS Version on QNAP is too old and/or buggy. Best regards Rainer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Dear Matthew, I tried your commands with the following results: $ mount -vvv -o vers=4.2 /srv/www/nextcloud/data // this hangs? $ mount -vvv -o vers=4.1 /srv/www/nextcloud/data // this hang too? $ mount -vvv -o vers=4.0 /srv/www/nextcloud/data // this works In the attachment you can find the screenshot. Now I changed the value in /etc/fstab to nfsvers=4.0 and this works too. Best regards Rainer ** Attachment added: "mount results" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+attachment/5755330/+files/mount_results.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hey Matthew, I will try it today after the working hours. I have access to the QNAP but I can only activate 3.x and/or 4.x on the Webinterface (See here for an example: https://www.qnap.com/en/how-to/faq/article/how-to-access-files-on-nas-via-nfs-from-unixlinux-clients). I checked the supported versions via CLI on the QNAP via: [~] # cat /proc/fs/nfsd/versions +2 +3 +4 +4.1 +4.2 Therefore it should support 4.2 but maybe it is not implemented correctly. I will give you a feedback today evening. Best regards Rainer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
Hi, in the attachment you can find a screenshot about the /etc/fstab. Additionally you can find a screenshot about the mount result. The command hung. The timeout time was already reached but the command is running. This is the only output. The NFS Server should be version 4.x. QNap can run both 3 and 4 at the same time and I always used 4 (see /etc/fstab). If you need the exact version please let me know and I will check it. Best regards Rainer ** Attachment added: "/etc/fstab" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+attachment/5754913/+files/1.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
And here the mount command screenshot ** Attachment added: "mount" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+attachment/5754915/+files/2.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
I'm happy to report that in three working days the problem has not reoccurred. So the fix in kernel 6.5.0-21-generic #21~22.04.1 looks good to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1 now. I'll report if the problem occurs again (in my usage it happened every one or two days). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
Hi Roxana, I'm confused by your comment #11. You write about versions 6.5.0-21.21~22.04.1 and 6.5.0-25.25~22.04.1. Do both contain the fix? As of today, I can see neither of these versions, but only 6.5.0.21.21~22.04.11 (.11, not .1!). And that version has already been released as a regular (not proposed) update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966066] Re: audio from external sound card is distorted
For me too, I don't know why comment #52 by the kernel bot has appeared now. I'm going to set the "verification done" tag. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
In my case the host is not running any virtual machines. I have another similar HPE Gen9 server (without the HPE Smart HBA H240 SATA controller) that doesn't have the problem. So in my case I suspect the H240 controller is (at least part of) the problem. @phdonnelly, are you using VMs and/or do you have an H240 controller? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971505] Re: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set
This might be a duplicate of bug #1970453, which also occurs on HPE servers starting with Ubuntu 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971505 Title: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971093] Re: collectd missing in 22.04/jammy
As a workaround, the packages that were in the jammy proposed repository can be downloaded from https://launchpad.net/ubuntu/+source/collectd/5.12.0-9/+build/23189375. I only needed collectd_5.12.0-9_amd64.deb and collectd-core_5.12.0-9_amd64.deb. Installing them via apt install ./collectd_5.12.0-9_amd64.deb ./collectd-core_5.12.0-9_amd64.deb results in a working collectd on 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971093 Title: collectd missing in 22.04/jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971093] [NEW] collectd missing in 22.04/jammy
Public bug reported: collectd is missing in the 22.04/jammy repositories. collectd was available in the proposed repository at first, but has been removed on April 29. Why was it removed and when will collectd be available in 22.04? ** Affects: collectd (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971093 Title: collectd missing in 22.04/jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
If this question was meant for me: I cannot really say, in my case no VMs are involved at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
I tried the latest currently available 5.15 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15.36/amd64/, 5.15.36-051536-generic #202204271420 SMP Wed Apr 27 16:37:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). The problem still occurs there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970453] [NEW] DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
Public bug reported: I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA controller. Since Ubuntu 22.04, the kernel runs into trouble after a few hours of uptime. The problem starts with a few instances of a message such as this: Apr 26 12:03:37 kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set (to 7bf32003 not 24c563801) Apr 26 12:03:37 kernel: [ cut here ] Apr 26 12:03:37 kernel: WARNING: CPU: 1 PID: 10171 at drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Modules linked in: tls rpcsec_gss_krb5 binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi> Apr 26 12:03:37 kernel: drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa> Apr 26 12:03:37 kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not tainted 5.15.0-27-generic #28-Ubuntu Apr 26 12:03:37 kernel: Hardware name: HP ProLiant DL20 Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021 Apr 26 12:03:37 kernel: Workqueue: writeback wb_workfn (flush-253:2) Apr 26 12:03:37 kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 > Apr 26 12:03:37 kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202 Apr 26 12:03:37 kernel: RAX: 0004 RBX: 9f0042062990 RCX: Apr 26 12:03:37 kernel: RDX: RSI: 9f02b3d20980 RDI: 9f02b3d20980 Apr 26 12:03:37 kernel: RBP: c077826b2ff0 R08: 00024c563801 R09: 0024c563 Apr 26 12:03:37 kernel: R10: R11: c01550e0 R12: 000f Apr 26 12:03:37 kernel: R13: 0007bf32 R14: 9f00412f5800 R15: 9f0042062938 Apr 26 12:03:37 kernel: FS: () GS:9f02b3d0() knlGS: Apr 26 12:03:37 kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 26 12:03:37 kernel: CR2: 1530f676a01c CR3: 00029c210001 CR4: 002706e0 Apr 26 12:03:37 kernel: Call Trace: Apr 26 12:03:37 kernel: Apr 26 12:03:37 kernel: intel_iommu_map_pages+0xdc/0x120 Apr 26 12:03:37 kernel: ? __alloc_and_insert_iova_range+0x203/0x240 Apr 26 12:03:37 kernel: __iommu_map+0xda/0x270 Apr 26 12:03:37 kernel: __iommu_map_sg+0x8e/0x120 Apr 26 12:03:37 kernel: iommu_map_sg_atomic+0x14/0x20 Apr 26 12:03:37 kernel: iommu_dma_map_sg+0x345/0x4d0 Apr 26 12:03:37 kernel: __dma_map_sg_attrs+0x68/0x70 Apr 26 12:03:37 kernel: dma_map_sg_attrs+0xe/0x20 Apr 26 12:03:37 kernel: scsi_dma_map+0x39/0x50 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa] Apr 26 12:03:37 kernel: ? __blk_rq_map_sg+0x36/0x160 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel_queue_command+0x82/0xd0 [hpsa] Apr 26 12:03:37 kernel: hpsa_ioaccel_submit+0x174/0x190 [hpsa] Apr 26 12:03:37 kernel: hpsa_scsi_queue_command+0x19c/0x240 [hpsa] Apr 26 12:03:37 kernel: ? recalibrate_cpu_khz+0x10/0x10 Apr 26 12:03:37 kernel: scsi_dispatch_cmd+0x93/0x1f0 Apr 26 12:03:37 kernel: scsi_queue_rq+0x2d1/0x690 Apr 26 12:03:37 kernel: blk_mq_dispatch_rq_list+0x126/0x600 Apr 26 12:03:37 kernel: ? __sbitmap_queue_get+0x1/0x10 Apr 26 12:03:37 kernel: __blk_mq_do_dispatch_sched+0xba/0x2d0 Apr 26 12:03:37 kernel: __blk_mq_sched_dispatch_requests+0x104/0x150 Apr 26 12:03:37 kernel: blk_mq_sched_dispatch_requests+0x35/0x60 Apr 26 12:03:37 kernel: __blk_mq_run_hw_queue+0x34/0xb0 Apr 26 12:03:37 kernel: __blk_mq_delay_run_hw_queue+0x162/0x170 Apr 26 12:03:37 kernel: blk_mq_run_hw_queue+0x83/0x120 Apr 26 12:03:37 kernel: blk_mq_sched_insert_requests+0x69/0xf0 Apr 26 12:03:37 kernel: blk_mq_flush_plug_list+0x103/0x1c0 Apr 26 12:03:37 kernel: blk_flush_plug_list+0xdd/0x100 Apr 26 12:03:37 kernel: blk_mq_submit_bio+0x2bd/0x600 Apr 26 12:03:37 kernel: __submit_bio+0x1ea/0x220 Apr 26 12:03:37 kernel: ? mempool_alloc_slab+0x17/0x20 Apr 26 12:03:37 kernel: __submit_bio_noacct+0x85/0x1f0 Apr 26 12:03:37 kernel: submit_bio_noacct+0x4e/0x120 Apr 26 12:03:37 kernel: ? radix_tree_lookup+0xd/0x10 Apr 26 12:03:37 kernel: ? bio_associate_blkg_from_css+0x1b2/0x310 Apr 26 12:03:37 kernel: submit_bio+0x4a/0x130 Apr 26 12:03:37 kernel: ? wbc_account_cgroup_owner+0x2c/0x80 Apr 26 12:03:37 kernel: submit_bh_wbc+0x18d/0x1c0 Apr 26 12:03:37 kernel: __block_write_full_page+0x227/0x4a0 Apr 26 12:03:37 kernel: ? block_invalidatepage+0x150/0x150 Apr 26 12:03:37 kernel: ? blkdev_llseek+0x60/0x60 Apr 26 12:03:37 kernel: block_write_full_page+0x6f/0x90 Apr 26 12:03:37 kernel: blkdev_writepage+0x18/0x20 Apr 26 12:03:37 kernel: __writepage+0x1e/0x70 Apr 26
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
I can confirm as well, thanks Jeremy :)! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
While this bug is fixed for displaying emails in Evolution, the same problem still occurs when editing emails. I created bug #1969584 for this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
Versions: Evolution: 3.44.0-1 Mesa: 22.0.1-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] [NEW] Evolution does not allow editing email content on Wayland
Public bug reported: This is very similar to bug #1966418, but only concerns the email edit window. Before bug #1966418 was fixed, Evolution did not display email contents when running under Wayland. Starting Evolution with WEBKIT_DISABLE_COMPOSITING_MODE=1 worked around the issue. Now that #1966418 is fixed, displaying email contents works again even without the workaround. However, it's still not possible to write/edit an email. The message area is greyed out and unresponsive. When running under X or using the above workaround, editing emails works. So the issue seems to be the same as in #1966418, but for the edit window. ** Affects: evolution (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/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967679] Re: touchscreen
touchscreen does not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967679 Title: touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967679] [NEW] touchscreen
Public bug reported: touchscreen does not work at any time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 3 16:06:33 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Device [0501:02f3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1902:8301 Generic HD camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: THOMSON GEN360-4C128BK ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=461ced2f-89f8-4a9c-a1ec-fe9520b392d8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GP12_THOMSON_0_04 dmi.board.asset.tag: Default string dmi.board.name: GP12 dmi.board.vendor: MX dmi.board.version: V300 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGP12_THOMSON_0_04:bd09/06/2021:br5.13:svnTHOMSON:pnGEN360-4C128BK:pvrV300:rvnMX:rnGP12:rvrV300:cvnDefaultstring:ct3:cvrDefaultstring:skuGEN360-4C128BK: dmi.product.family: MIPI PC dmi.product.name: GEN360-4C128BK dmi.product.sku: GEN360-4C128BK dmi.product.version: V300 dmi.sys.vendor: THOMSON version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967679 Title: touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
I installed 22.04 today on a machine with an AMD GPU. I have libmutter-10-0 42.0-1ubuntu1 and I still encountered the problem. Setting MUTTER_DEBUG_USE_KMS_MODIFIERS=0 is still necessary in 42.0-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Updating NVIDIA driver from 460 to 470 messed up my system (even GRUB). Making an parallel install brought GRUB back to life, but I was not able to fix it. Even starting from pen drive only worked when using safe grafic after the NVIDIA update. System is working since years (16.04, 18.04, 20.04). So I decided to completely wipe the ssd and to reinstall. Then the installer ran into this error. I assume NVIDIA also touches the cards firmware when updating the driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
The same applies to Chromium, please set it to medium as well, Luka. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538621/+files/acpidump.txt ** 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/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538619/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538620/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538618/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538617/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538616/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538615/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538614/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538613/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538610/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538612/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538611/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538609/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Re: tg3 transmit timed out, resetting
apport information ** Tags added: apport-collected uec-images ** Description changed: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 29 13:56 seq + crw-rw 1 root audio 116, 33 Oct 29 13:56 timer + AplayDevices: aplay: device_list:276: no soundcards found... + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + ArecordDevices: arecord: device_list:276: no soundcards found... + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-26 (559 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: HP ProLiant MicroServer Gen8 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity + ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-38-generic N/A + linux-backports-modules-5.11.0-38-generic N/A + linux-firmware 1.187.20 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.11.0-38-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 04/04/2019 + dmi.bios.vendor: HP + dmi.bios.version: J06 + dmi.chassis.type: 7 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 2.78 + dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: + dmi.product.family: ProLiant + dmi.product.name: ProLiant MicroServer Gen8 + dmi.product.sku: 712317-421 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538608/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950046] Re: tg3 transmit timed out, resetting
Example 2: Nov 06 15:34:38 kernel: [ cut here ] Nov 06 15:34:38 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue 0 timed out Nov 06 15:34:38 kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 Nov 06 15:34:38 kernel: Modules linked in: rpcsec_gss_krb5 usblp binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm hpilo rapl intel_cstate acpi_ip> Nov 06 15:34:38 kernel: ghash_clmulni_intel cryptd drm psmouse libahci xhci_pci tg3 lpc_ich xhci_pci_renesas Nov 06 15:34:38 kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.11.0-38-generic #42~20.04.1-Ubuntu Nov 06 15:34:38 kernel: Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 Nov 06 15:34:38 kernel: RIP: 0010:dev_watchdog+0x24f/0x260 Nov 06 15:34:38 kernel: Code: 07 78 fd ff eb ab 4c 89 ff c6 05 33 22 ee 00 01 e8 26 3c fa ff 44 89 e9 4c 89 fe 48 c7 c7 f0 42 c9 8f 48 89 c2 e8 cf 5a 16 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 Nov 06 15:34:38 kernel: RSP: 0018:ad17002c4e88 EFLAGS: 00010282 Nov 06 15:34:38 kernel: RAX: RBX: 93cd93e7bd00 RCX: Nov 06 15:34:38 kernel: RDX: 93d07aa68a20 RSI: 93d07aa58ac0 RDI: 0300 Nov 06 15:34:38 kernel: RBP: ad17002c4eb8 R08: 93d07aa58ac0 R09: ad17002c4c48 Nov 06 15:34:38 kernel: R10: 00cb9cd0 R11: 00cb9db8 R12: 0005 Nov 06 15:34:38 kernel: R13: R14: 93cd94af04c0 R15: 93cd94af Nov 06 15:34:38 kernel: FS: () GS:93d07aa4() knlGS: Nov 06 15:34:38 kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 06 15:34:38 kernel: CR2: 7f41920eed38 CR3: be610001 CR4: 001706e0 Nov 06 15:34:38 kernel: Call Trace: Nov 06 15:34:38 kernel: Nov 06 15:34:38 kernel: ? pfifo_fast_enqueue+0x150/0x150 Nov 06 15:34:38 kernel: call_timer_fn+0x2e/0x100 Nov 06 15:34:38 kernel: __run_timers.part.0+0x1e0/0x250 Nov 06 15:34:38 kernel: ? lapic_next_deadline+0x2c/0x40 Nov 06 15:34:38 kernel: ? clockevents_program_event+0x8f/0xe0 Nov 06 15:34:38 kernel: run_timer_softirq+0x2a/0x50 Nov 06 15:34:38 kernel: __do_softirq+0xe0/0x29b Nov 06 15:34:38 kernel: asm_call_irq_on_stack+0x12/0x20 Nov 06 15:34:38 kernel: Nov 06 15:34:38 kernel: do_softirq_own_stack+0x3d/0x50 Nov 06 15:34:38 kernel: irq_exit_rcu+0xa4/0xb0 Nov 06 15:34:38 kernel: sysvec_apic_timer_interrupt+0x3d/0x90 Nov 06 15:34:38 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Nov 06 15:34:38 kernel: RIP: 0010:cpuidle_enter_state+0xdf/0x350 Nov 06 15:34:38 kernel: Code: ff e8 95 a8 77 ff 80 7d d7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 52 02 00 00 31 ff e8 c8 52 7e ff fb 66 0f 1f 44 00 00 <45> 85 ff 0f 88 e5 00 00 00 49 63 c7 4c 2b 75 c8 48 8d 14 40 48 8d Nov 06 15:34:38 kernel: RSP: 0018:ad1700097e48 EFLAGS: 0246 Nov 06 15:34:38 kernel: RAX: 93d07aa6c380 RBX: 0004 RCX: 001f Nov 06 15:34:38 kernel: RDX: RSI: 37c75227 RDI: Nov 06 15:34:38 kernel: RBP: ad1700097e80 R08: 00027d42516aa349 R09: 0e3b Nov 06 15:34:38 kernel: R10: 93d07aa6afa4 R11: 93d07aa6af84 R12: 93d07aa77600 Nov 06 15:34:38 kernel: R13: 9004d8e0 R14: 00027d42516aa349 R15: 0004 Nov 06 15:34:38 kernel: ? cpuidle_enter_state+0xbb/0x350 Nov 06 15:34:38 kernel: cpuidle_enter+0x2e/0x40 Nov 06 15:34:38 kernel: call_cpuidle+0x23/0x40 Nov 06 15:34:38 kernel: do_idle+0x1df/0x260 Nov 06 15:34:38 kernel: cpu_startup_entry+0x20/0x30 Nov 06 15:34:38 kernel: start_secondary+0x11f/0x160 Nov 06 15:34:38 kernel: secondary_startup_64_no_verify+0xc2/0xcb Nov 06 15:34:38 kernel: ---[ end trace 28a5883990ef746a ]--- Nov 06 15:34:38 kernel: tg3 :03:00.0 eno1: transmit timed out, resetting Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x: 0x165f14e4, 0x00100446, 0x0200, 0x00800010 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0010: 0xfabf000c, 0x, 0xfabe000c, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0020: 0xfabd000c, 0x, 0x, 0x2133103c Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0030: 0x, 0x0048, 0x, 0x010a Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0040: 0x, 0x1a00, 0xc8035001, 0x64002008 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0050: 0x5803, 0x, 0x0086a005, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0060: 0x, 0x, 0xf298, 0x00380081 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0070: 0x000710b0, 0xf50eacfb, 0x, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0080: 0x165f14e4, 0x80f8,
[Bug 1950046] Re: tg3 transmit timed out, resetting
Example 1: Nov 04 17:34:59 kernel: [ cut here ] Nov 04 17:34:59 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue 0 timed out Nov 04 17:34:59 kernel: WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 Nov 04 17:34:59 kernel: Modules linked in: rpcsec_gss_krb5 xt_nat veth xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_use> Nov 04 17:34:59 kernel: raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel m> Nov 04 17:34:59 kernel: CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.11.0-38-generic #42~20.04.1-Ubuntu Nov 04 17:34:59 kernel: Hardware name: HP ProLiant ML30 Gen9/ProLiant ML30 Gen9, BIOS U23 04/04/2019 Nov 04 17:34:59 kernel: RIP: 0010:dev_watchdog+0x24f/0x260 Nov 04 17:34:59 kernel: Code: 07 78 fd ff eb ab 4c 89 ff c6 05 33 22 ee 00 01 e8 26 3c fa ff 44 89 e9 4c 89 fe 48 c7 c7 f0 4> Nov 04 17:34:59 kernel: RSP: 0018:a82b80174e88 EFLAGS: 00010282 Nov 04 17:34:59 kernel: RAX: RBX: 94c7927c8500 RCX: 0027 Nov 04 17:34:59 kernel: RDX: 0027 RSI: 000100012071 RDI: 94cbebd98ac8 Nov 04 17:34:59 kernel: RBP: a82b80174eb8 R08: 94cbebd98ac0 R09: a82b80174c48 Nov 04 17:34:59 kernel: R10: 0113d6b0 R11: 0113d790 R12: 0005 Nov 04 17:34:59 kernel: R13: R14: 94c7931cc4c0 R15: 94c7931cc000 Nov 04 17:34:59 kernel: FS: () GS:94cbebd8() knlGS: Nov 04 17:34:59 kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 04 17:34:59 kernel: CR2: 56452bee1a38 CR3: 00052a610003 CR4: 003706e0 Nov 04 17:34:59 kernel: DR0: DR1: DR2: Nov 04 17:34:59 kernel: DR3: DR6: fffe0ff0 DR7: 0400 Nov 04 17:34:59 kernel: Call Trace: Nov 04 17:34:59 kernel: Nov 04 17:34:59 kernel: ? pfifo_fast_enqueue+0x150/0x150 Nov 04 17:34:59 kernel: call_timer_fn+0x2e/0x100 Nov 04 17:34:59 kernel: __run_timers.part.0+0x1e0/0x250 Nov 04 17:34:59 kernel: ? lapic_next_deadline+0x2c/0x40 Nov 04 17:34:59 kernel: ? clockevents_program_event+0x8f/0xe0 Nov 04 17:34:59 kernel: run_timer_softirq+0x2a/0x50 Nov 04 17:34:59 kernel: __do_softirq+0xe0/0x29b Nov 04 17:34:59 kernel: asm_call_irq_on_stack+0x12/0x20 Nov 04 17:34:59 kernel: Nov 04 17:34:59 kernel: do_softirq_own_stack+0x3d/0x50 Nov 04 17:34:59 kernel: irq_exit_rcu+0xa4/0xb0 Nov 04 17:34:59 kernel: sysvec_apic_timer_interrupt+0x3d/0x90 Nov 04 17:34:59 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Nov 04 17:34:59 kernel: RIP: 0010:cpuidle_enter_state+0xdf/0x350 Nov 04 17:34:59 kernel: Code: ff e8 95 a8 77 ff 80 7d d7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 52 02 00 00 31 ff e8 c> Nov 04 17:34:59 kernel: RSP: 0018:a82b800cfe48 EFLAGS: 0246 Nov 04 17:34:59 kernel: RAX: 94cbebdac380 RBX: 0006 RCX: 001f Nov 04 17:34:59 kernel: RDX: RSI: 2aaa530e RDI: Nov 04 17:34:59 kernel: RBP: a82b800cfe80 R08: 0001e6651774fce9 R09: 104c Nov 04 17:34:59 kernel: R10: 94cbebdaafa4 R11: 94cbebdaaf84 R12: 94cbebdb7a00 Nov 04 17:34:59 kernel: R13: b804d8e0 R14: 0001e6651774fce9 R15: 0006 Nov 04 17:34:59 kernel: ? cpuidle_enter_state+0xbb/0x350 Nov 04 17:34:59 kernel: cpuidle_enter+0x2e/0x40 Nov 04 17:34:59 kernel: call_cpuidle+0x23/0x40 Nov 04 17:34:59 kernel: do_idle+0x1df/0x260 Nov 04 17:34:59 kernel: cpu_startup_entry+0x20/0x30 Nov 04 17:34:59 kernel: start_secondary+0x11f/0x160 Nov 04 17:34:59 kernel: secondary_startup_64_no_verify+0xc2/0xcb Nov 04 17:34:59 kernel: ---[ end trace 7e2e93595130f070 ]--- Nov 04 17:34:59 kernel: tg3 :02:00.0 eno1: transmit timed out, resetting Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x: 0x165f14e4, 0x00100546, 0x0200, 0x00800010 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0010: 0x92b3000c, 0x, 0x92b4000c, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0020: 0x92b5000c, 0x, 0x, 0x22e8103c Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0030: 0x, 0x0048, 0x, 0x01ff Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0040: 0x, 0x7400, 0xc8035001, 0x64002008 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0050: 0x5803, 0x, 0x0086a005, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0060: 0x, 0x, 0xf298, 0x00380081 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0070: 0x000710b0, 0xf56dffdb, 0x, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0080: 0x165f14e4, 0x80f8, 0x, 0x089d Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0090: 0x, 0x, 0x,
[Bug 1950046] [NEW] tg3 transmit timed out, resetting
Public bug reported: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Maybe the information I collected here https://bugzilla.mozilla.org/show_bug.cgi?id=1734791 for the Firefox snap, which suffers from the same problem, is helpful in order to fix the problem for the Chromium snap as well. ** Bug watch added: Mozilla Bugzilla #1734791 https://bugzilla.mozilla.org/show_bug.cgi?id=1734791 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925303] Re: UDP networking is broken in 20.10.2-0ubuntu1~20.04.2
This does not seem to occur in 20.10.7-0ubuntu1~20.04.1 anymore. ** Changed in: docker.io (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925303 Title: UDP networking is broken in 20.10.2-0ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1925303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Similar to what Dan wrote in comment #10, my original test case of installing ubuntu-desktop now works even without enabling the proposed repository. So unfortunately I cannot verify the fix now since I cannot reproduce the original error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
I tested evolution-data-server version 3.40.0-1ubuntu1.1 from proposed in Hirsute. I can confirm that iCloud accounts can be accessed again. Thanks for your work, Brian, Sebastien and Iain! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933213] [NEW] package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: »installiertes grub-efi-amd64-signed-Skript des Paketes post-installation«-Unterprozess gab den Fe
Public bug reported: error when updating ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.7 AptOrdering: grub-efi-amd64-signed:amd64: Install grub-efi-amd64-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 18 06:30:12 2021 ErrorMessage: »installiertes grub-efi-amd64-signed-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: »installiertes grub-efi-amd64-signed-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933213 Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: »installiertes grub-efi-amd64-signed-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1933213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Thank you Brian for following up on this! Is there any news regarding the fix in Hirsute yet? Two months of not being able to access iCloud mails in a core component of the current supported Ubuntu release is a really long time ... :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Hi, when will this bug be fixed in 21.04/Hirsute? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924825] Re: After upgrading to 21.04, F12 no longer toggles Guake.
This affects me as well, and it's rather frustrating. I guess we will have to wait until there's a new Guake version out that will work with Wayland 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/1924825 Title: After upgrading to 21.04, F12 no longer toggles Guake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1924825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Manfred: Thanks! (Offtopic: I googled "apt phased 20%". The "20%" seems to throw Google off completely, it didn't show ANY results related to Linux. Leaving off the 20% yields much better results ;)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
A workaround is to manually force installation of the dependencies with the newer "phased" versions: apt install ubuntu-release-upgrader-core=1:21.04.11 python3-distupgrade=1:21.04.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925745] [NEW] Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Public bug reported: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 21.04 hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925303] [NEW] UDP networking is broken in 20.10.2-0ubuntu1~20.04.2
Public bug reported: I upgraded to docker.io 20.10.2-0ubuntu1~20.04.2 in 20.04/focal yesterday and restarted docker.service. I'm running InfluxDB (image influxdb:1.8.4-alpine) that has port UDP port 25826 exposed for receiving collectd traffic. Since installing the new version, InfluxDB does not receive any data anymore. No errors are visible in the docker or container log. (TCP traffic to a Grafana container on the same host still works.) Downgrading to the previous versions of the relevant packages restores UDP traffic: apt remove docker.io containerd runc apt install docker.io=19.03.8-0ubuntu1 containerd=1.3.3-0ubuntu2 runc=1.0.0~rc10-0ubuntu1 ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: focal regression ** Description changed: - I upgraded to docker.io 20.10.2-0ubuntu1~20.04.2 yesterday and restarted - docker.service. + I upgraded to docker.io 20.10.2-0ubuntu1~20.04.2 in 20.04/focal + yesterday and restarted docker.service. I'm running InfluxDB (image influxdb:1.8.4-alpine) that has port UDP port 25826 exposed for receiving collectd traffic. Since installing the new version, InfluxDB does not receive any data anymore. No errors are visible in the docker or container log. (TCP traffic to a Grafana container on the same host still works.) Downgrading to the previous versions of the relevant packages restores UDP traffic: apt remove docker.io containerd runc apt install docker.io=19.03.8-0ubuntu1 containerd=1.3.3-0ubuntu2 runc=1.0.0~rc10-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925303 Title: UDP networking is broken in 20.10.2-0ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1925303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920608] Re: egrub-efi.amd-64-signed fehlt ; booten nicht möglich
Was kann ich weiter tun? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920608 Title: egrub-efi.amd-64-signed fehlt ; booten nicht möglich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920608] [NEW] egrub-efi.amd-64-signed fehlt ; booten nicht möglich
Public bug reported: bei Neuinstallation Ubuntu 18.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Sat Mar 20 15:13:03 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920608 Title: egrub-efi.amd-64-signed fehlt ; booten nicht möglich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913414] [NEW] no system tray on this system
Public bug reported: HPLIP no system tray on this system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 11:22:49 2021 InstallationDate: Installed on 2019-12-22 (401 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-10-02 (116 days ago) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913414 Title: no system tray on this system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1913414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
Since Andreas Kübrich (akuebrich) has verified the fix I'll go ahead and set the verification-done-groovy tag. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884538] Re: Removing debian-installer from groovy
I now managed to get a working PXE setup for Groovy that runs the Subiquity installer with an autoinstall configuration. I documented my findings in detail at https://askubuntu.com/q/1292032. My solution can be used both for UEFI and BIOS systems and also mentions how to install a desktop system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884538 Title: Removing debian-installer from groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1884538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Hi, I can confirm that bind9 1:9.16.1-0ubuntu2.4 from proposed fixes the problem. I have the following messages in my log, and BIND did _not_ crash: Oct 24 13:16:01 named[1057]: timed out resolving 'www-cdn.icloud.com.akadns.net//IN': 2606:4700:4700::#53 Oct 24 13:16:01 named[1057]: timed out resolving 'd2xproa6koigec.cloudfront.net//IN': 2606:4700:4700::#53 Oct 24 13:16:03 named[1057]: resolver.c:5107: unexpected error: Oct 24 13:16:03 named[1057]: '_.akamaiedge.net/A' is not subdomain of 'dsce9.akamaiedge.net' Oct 24 13:16:03 named[1057]: resolver.c:5107: unexpected error: Oct 24 13:16:03 named[1057]: '_.cloudfront.net/A' is not subdomain of 'd2xproa6koigec.cloudfront.net' ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756593] Re: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143
Not having very serious problems with my Linux per se (Kernel: 4.15.0-122-generic i686 Bits: 32 Desktop: MATE 1.20.1 Distro: Linux Mint 19.1 Tessa) I also wonder about these irritating initramfs-tools messages saying "ORDER ignored: not executable", although they don't seem to be error messages: maybe it is meant that these scripts are "not executable". But anyway i've got a question, maybe a silly one: Would it make sense to alter the access privileges of these scripts by giving them execute permission? ** Attachment added: "initramfs-tools error messages "ORDER ignored: not executable"" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1756593/+attachment/5426041/+files/initramfs-tools-Meldungen%20scripts.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756593 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1756593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Thanks, I installed bind9 1:9.16.1-0ubuntu2.4 from proposed and I'll report back in two or three weeks with the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Hi Christian, I'm now seeing the warning message from the patch in my log and BIND has _not_ crashed: Oct 06 21:30:52 named[14587]: timed out resolving 'e4478.a.akamaiedge.net/A/IN': 2606:4700:4700::#53 Oct 06 21:30:53 named[14587]: timed out resolving 'e6858.dsce9.akamaiedge.net/A/IN': 1.1.1.1#53 Oct 06 21:30:53 named[14587]: timed out resolving 'e4478.a.akamaiedge.net/A/IN': 1.1.1.1#53 Oct 06 21:30:54 named[14587]: resolver.c:5107: unexpected error: Oct 06 21:30:54 named[14587]: '_.facebook.com/A' is not subdomain of 'c10r.facebook.com' So this looks good now :) Can you release the patch in the regular BIND package for Focal? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Hi Christian, thanks for the PPA! I installed the new version and I'm now running 1:9.16.1-0ubuntu2.4~ppa1. I'll report back if BIND crashes again or if the "..is not subdomain of..." message from the patch is logged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897725] Re: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command f
Everything went through smoothly now. Maybe this was connected to the fact that my first attempt to upgrade stopped with an "unresolvable problem" with the advice to disable ppas. I did that using synaptic, reloaded repository information and started the next try to upgrade, which was then stopped as described in my original report above. Anyway, all problems are gone now, for whatever reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897725 Title: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command for reporting the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897725] Re: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command f
Hm, strange, but after I shut down my computer and started it new and then started the software updater, it proceeded happily and without further complaint with "updating" (not "upgrading"). It's running now, I hope the system will be fine in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897725 Title: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command for reporting the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897725] [NEW] I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command
Public bug reported: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade from 18.04 to 20.04. No further information about the problem was given before the "If none of this applies", just after that and an empty line the command for reporting the problem. Before trying to upgrade I installed all available updates to 18.04, and then got the message that my system was up to date but the upgrade was available. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Tue Sep 29 13:16:18 2020 InstallationDate: Installed on 2018-08-14 (776 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-09-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897725 Title: I got "An unresolvable problem occurred while calculating the upgrade." while trying to upgrade to focal fossa. No further information about the problem was given, just the command for reporting the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Sure, I can test the packages from the PPA. However, I also don't have a way to reproduce the crash. I could only leave the PPA version running for some time (e.g., two weeks) and see whether it crashes or not... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
I agree, the Debian bug #969448 looks very similar to the crashes I experienced. Is there a timeline for the Debian patches to be merged into Ubuntu's BIND? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
It seems that this has already been reported upstream in https://gitlab.isc.org/isc-projects/bind9/-/issues/1997 and was fixed in 9.16.6. A CVE number was assigned as well, CVE-2020-8621 https://kb.isc.org/docs/cve-2020-8621. Please pull the fix into Focal's BIND. ** Bug watch added: gitlab.isc.org/isc-projects/bind9/-/issues #1997 https://gitlab.isc.org/isc-projects/bind9/-/issues/1997 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8621 ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896740] [NEW] BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))
Public bug reported: I'm running Ubuntu 20.04 and bind9 1:9.16.1-0ubuntu2.3. BIND sometimes crashes with: Sep 23 10:10:12 named[1146]: timed out resolving 'www.independent.co.uk/TYPE65/IN': 2606:4700:4700::1001#53 Sep 23 10:10:12 named[1146]: timed out resolving 'ssc.independent.co.uk/TYPE65/IN': 2606:4700:4700::1001#53 Sep 23 10:10:13 named[1146]: timed out resolving 'www.independent.co.uk/TYPE65/IN': 1.0.0.1#53 Sep 23 10:10:13 named[1146]: timed out resolving 'ssc.independent.co.uk/TYPE65/IN': 1.0.0.1#53 Sep 23 10:10:14 named[1146]: timed out resolving 'www.independent.co.uk/TYPE65/IN': 2606:4700:4700::#53 Sep 23 10:10:14 named[1146]: timed out resolving 'ssc.independent.co.uk/TYPE65/IN': 2606:4700:4700::#53 Sep 23 10:10:15 named[1146]: timed out resolving 'www.independent.co.uk/TYPE65/IN': 1.1.1.1#53 Sep 23 10:10:16 named[1146]: timed out resolving 'ssc.independent.co.uk/TYPE65/IN': 1.1.1.1#53 Sep 23 10:10:16 named[1146]: resolver.c:5105: INSIST(dns_name_issubdomain(>name, >domain)) failed, back trace Sep 23 10:10:16 named[1146]: #0 0x558b762dce43 in ?? Sep 23 10:10:16 named[1146]: #1 0x7f390cf32ac0 in ?? Sep 23 10:10:16 named[1146]: #2 0x7f390d0fb12d in ?? Sep 23 10:10:16 named[1146]: #3 0x7f390d0fe940 in ?? Sep 23 10:10:16 named[1146]: #4 0x7f390d104888 in ?? Sep 23 10:10:16 named[1146]: #5 0x7f390d108f21 in ?? Sep 23 10:10:16 named[1146]: #6 0x7f390d109a66 in ?? Sep 23 10:10:16 named[1146]: #7 0x7f390d109ec6 in ?? Sep 23 10:10:16 named[1146]: #8 0x7f390cf59fe1 in ?? Sep 23 10:10:16 named[1146]: #9 0x7f390ca22609 in ?? Sep 23 10:10:16 named[1146]: #10 0x7f390c943103 in ?? Sep 23 10:10:16 named[1146]: exiting (due to assertion failure) The crash has ocurred repeatedly on multiple hosts. In all cases I observed BIND has logged timeouts immediately before each crash. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1896740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895028] [NEW] Updat fro 19.04 to 20.04 chrases
Public bug reported: Update chrash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Sep 9 18:34:46 2020 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-09-09 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895028 Title: Updat fro 19.04 to 20.04 chrases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1895028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
I tested kernel 5.4.0-46-generic #50 from focal-proposed. This version seems to fix the problem, I could not reproduce it any more. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
I can confirm that 5.4.59-050459-generic #202008190333 seems to work, I could not reproduce the problem there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome
Since this occurs in other, non-snap-based browsers as well (e.g., Firefox and Vivaldi), I think that this issue need to be handled separately from #1858636. ** Changed in: fonts-noto-color-emoji (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/1859926 Title: fonts-noto-color-emoji not making pretty emojis in google chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
add: error/failure only happens when security is set to WPA3-Personal WPA2 hotspot works fine! this is: Intel Wireless 8260 driver=iwlwifi-5.4.0-42 firmware=36.77d01142.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
hotspot function also fails for me checked /etc/NetworkManager/NetworkManager.conf:wifi.scan-rand-mac-address=no also grep -r 'ap_scan=2' /etc turned up nothing so i am puzzled where/why ap_scan=2 would be set installed hostapd pkg but this did not fix it tangential: seems redhat had this failure mode in 2017 and nixos in 2019, dunno if related, workarounds vary https://github.com/NixOS/nixpkgs/issues/67956 https://bugzilla.redhat.com/show_bug.cgi?id=1463245 https://bugzilla.redhat.com/show_bug.cgi?id=1518190 probably related to https://marc.info/?l=linux-kernel=151221956904515=2 ** Bug watch added: github.com/NixOS/nixpkgs/issues #67956 https://github.com/NixOS/nixpkgs/issues/67956 ** Bug watch added: Red Hat Bugzilla #1463245 https://bugzilla.redhat.com/show_bug.cgi?id=1463245 ** Bug watch added: Red Hat Bugzilla #1518190 https://bugzilla.redhat.com/show_bug.cgi?id=1518190 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886169] Re: "nl80211 driver interface is not designed to be used with ap_scan=2"
add: DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886169 Title: "nl80211 driver interface is not designed to be used with ap_scan=2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1886169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
I downloaded and installed the packages from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.8-rc4/amd64/ and tested 5.8.0-050800-generic #202007052030. I could not reproduce the problem in this version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
Thanks for the advice for bisecting! I found the commits causing the problem: After bb4fb62a863ea6131bdac77b21faa9444a605c58 (SUNRPC: Add "@len" parameter to gss_unwrap()) NFS with Kerberos is completely broken: $ mount -v /nfs/share mount.nfs: trying text-based options 'sec=krb5p,soft,intr,bg,timeo=100,retrans=2,vers=4.2,addr=:::1::1,clientaddr=:::1::dbfb' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed After c711ec1aa0c8ff7d979d7f12d1d09df46f349d61 (SUNRPC: Fix GSS privacy computation of auth->au_ralign) mounts work again but the crashes shown in the previous comments occur. ** 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
I tried bisecting the kernel as described in #22. However, I used the URL git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal instead of git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic, I hope that's correct. The fakeroot command works and builds the kernel. However, doing make later fails with: *** *** Configuration file ".config" not found! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make: *** [Makefile:695: .config] Error 1 I don't know how to go from here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
Is there a tutorial available on how to bisect the kernel and install and test the bisected version? To me it seems the problem only occurs in connection with NFS. I could not reproduce the problem when NFS is not used. However, after reading data from NFS mounts the problem reliably occurs within a few minutes. Here's a log from a third machine: [ 359.319126] BUG: unable to handle page fault for address: 9d95f6147697 [ 359.319132] #PF: supervisor read access in kernel mode [ 359.319134] #PF: error_code(0x) - not-present page [ 359.319136] PGD 378401067 P4D 378401067 PUD 0 [ 359.319141] Oops: [#1] SMP PTI [ 359.319146] CPU: 2 PID: 321 Comm: jbd2/sda6-8 Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 359.319148] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B85M Pro4, BIOS P2.50 12/11/2015 [ 359.319154] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 359.319158] Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 4a 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 359.319161] RSP: 0018:a8984060b7c8 EFLAGS: 00010282 [ 359.319163] RAX: 9d95f6147697 RBX: RCX: 0001 [ 359.319165] RDX: 0019 RSI: 00092a20 RDI: 00031f90 [ 359.319167] RBP: a8984060b7f8 R08: 9d954dab1f90 R09: 9d953f8132b8 [ 359.319169] R10: 9d953f8276c8 R11: 0029 R12: 9d95f6147697 [ 359.319171] R13: 00092a20 R14: 9d954ada4380 R15: 9d954ada4380 [ 359.319174] FS: () GS:9d954da8() knlGS: [ 359.319176] CS: 0010 DS: ES: CR0: 80050033 [ 359.319178] CR2: 9d95f6147697 CR3: 000377a0a002 CR4: 001606e0 [ 359.319180] Call Trace: [ 359.319187] ? mempool_alloc_slab+0x17/0x20 [ 359.319192] mempool_alloc_slab+0x17/0x20 [ 359.319196] mempool_alloc+0x64/0x180 [ 359.319201] ? __enqueue_entity+0x96/0xa0 [ 359.319206] sg_pool_alloc+0x4f/0x60 [ 359.319211] __sg_alloc_table+0x10b/0x170 [ 359.319214] sg_alloc_table_chained+0x47/0xa0 [ 359.319217] ? mac_pton+0xb0/0xb0 [ 359.319222] scsi_init_io+0x52/0x180 [ 359.319227] sd_setup_read_write_cmnd+0x67/0x710 [ 359.319231] sd_init_command+0x11a/0x472 [ 359.319235] scsi_queue_rq+0x32e/0xa00 [ 359.319239] blk_mq_dispatch_rq_list+0x96/0x5a0 [ 359.319243] ? deadline_remove_request+0x4e/0xb0 [ 359.319246] ? dd_dispatch_request+0x1/0x1f0 [ 359.319250] blk_mq_do_dispatch_sched+0x67/0x100 [ 359.319254] blk_mq_sched_dispatch_requests+0x12d/0x180 [ 359.319259] __blk_mq_run_hw_queue+0x5a/0x110 [ 359.319263] __blk_mq_delay_run_hw_queue+0x15b/0x160 [ 359.319267] blk_mq_run_hw_queue+0x92/0x120 [ 359.319270] blk_mq_sched_insert_requests+0x74/0x100 [ 359.319273] blk_mq_flush_plug_list+0x1e8/0x290 [ 359.319277] blk_flush_plug_list+0xe3/0x110 [ 359.319280] blk_finish_plug+0x26/0x34 [ 359.319287] jbd2_journal_commit_transaction+0xda5/0x17e8 [ 359.319293] kjournald2+0xb6/0x280 [ 359.319297] ? wait_woken+0x80/0x80 [ 359.319301] kthread+0x104/0x140 [ 359.319304] ? commit_timeout+0x20/0x20 [ 359.319307] ? kthread_park+0x90/0x90 [ 359.319312] ret_from_fork+0x35/0x40 [ 359.319315] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm msr vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) amdgpu amd_iommu_v2 gpu_sched aufs hid_logitech_hidpp cmac algif_hash joydev algif_skcipher af_alg overlay bnep input_leds hid_logitech_dj hid_generic btusb uas btrtl intel_rapl_msr btbcm btintel usbhid bluetooth hid usb_storage ecdh_generic ecc intel_rapl_common x86_pkg_temp_thermal nls_iso8859_1 intel_powerclamp mei_hdcp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg coretemp snd_hda_codec snd_hda_core kvm_intel snd_hwdep snd_pcm kvm snd_seq_midi radeon snd_seq_midi_event snd_rawmidi snd_seq crct10dif_pclmul ghash_clmulni_intel ttm snd_seq_device snd_timer aesni_intel drm_kms_helper crypto_simd snd cryptd i2c_algo_bit glue_helper fb_sys_fops syscopyarea mei_me intel_cstate sysfillrect mei sysimgblt intel_rapl_perf soundcore mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt [ 359.319364] nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c parport_pc ip6table_filter ip6_tables ppdev iptable_filter bpfilter lp parport drm sunrpc ip_tables x_tables autofs4 crc32_pclmul e1000e ahci i2c_i801 lpc_ich libahci video [ 359.319386] CR2: 9d95f6147697 [ 359.319389] ---[ end trace b059e600d0f4c10e ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about
[Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
Log from another machine: [ 1388.217900] BUG: unable to handle page fault for address: 8cf4f6fc5d86 [ 1388.217907] #PF: supervisor read access in kernel mode [ 1388.217908] #PF: error_code(0x) - not-present page [ 1388.217910] PGD 75201067 P4D 75201067 PUD 0 [ 1388.217913] Oops: [#4] SMP PTI [ 1388.217916] CPU: 3 PID: 471 Comm: dmcrypt_write/2 Tainted: G D 5.4.0-40-generic #44-Ubuntu [ 1388.217918] Hardware name: Hewlett-Packard HP EliteBook 8540w/1521, BIOS 68CVD Ver. F.60 11/11/2015 [ 1388.217923] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1388.217925] Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 76 4f 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1388.217927] RSP: 0018:9b3200977948 EFLAGS: 00010282 [ 1388.217928] RAX: 8cf4f6fc5d86 RBX: RCX: 0001 [ 1388.217929] RDX: 001f RSI: 00092a20 RDI: 00031ca0 [ 1388.217930] RBP: 9b3200977978 R08: 8cf4b3af1ca0 R09: 8cf4a08138b8 [ 1388.217931] R10: 8cf4b3ad7848 R11: 002d R12: 8cf4f6fc5d86 [ 1388.217932] R13: 00092a20 R14: 8cf4b227c380 R15: 8cf4b227c380 [ 1388.217934] FS: () GS:8cf4b3ac() knlGS: [ 1388.217935] CS: 0010 DS: ES: CR0: 80050033 [ 1388.217936] CR2: 8cf4f6fc5d86 CR3: 7480a000 CR4: 06e0 [ 1388.217937] Call Trace: [ 1388.217944] ? mempool_alloc_slab+0x17/0x20 [ 1388.217948] mempool_alloc_slab+0x17/0x20 [ 1388.217950] mempool_alloc+0x64/0x180 [ 1388.217956] ? try_to_wake_up+0x224/0x6a0 [ 1388.217960] ? __blk_bios_map_sg+0xe5/0x4c0 [ 1388.217964] sg_pool_alloc+0x4f/0x60 [ 1388.217968] __sg_alloc_table+0x10b/0x170 [ 1388.217971] sg_alloc_table_chained+0x47/0xa0 [ 1388.217972] ? mac_pton+0xb0/0xb0 [ 1388.217976] scsi_init_io+0x52/0x180 [ 1388.217981] sd_setup_read_write_cmnd+0x67/0x710 [ 1388.217984] ? __blk_mq_get_tag+0x28/0x80 [ 1388.217986] sd_init_command+0x11a/0x472 [ 1388.217988] scsi_queue_rq+0x32e/0xa00 [ 1388.217990] blk_mq_dispatch_rq_list+0x96/0x5a0 [ 1388.217993] ? deadline_remove_request+0x4e/0xb0 [ 1388.217995] ? dd_dispatch_request+0x1/0x1f0 [ 1388.217998] blk_mq_do_dispatch_sched+0x67/0x100 [ 1388.218000] blk_mq_sched_dispatch_requests+0x12d/0x180 [ 1388.218003] __blk_mq_run_hw_queue+0x5a/0x110 [ 1388.218005] __blk_mq_delay_run_hw_queue+0x15b/0x160 [ 1388.218008] blk_mq_run_hw_queue+0x92/0x120 [ 1388.218010] blk_mq_sched_insert_requests+0x74/0x100 [ 1388.218012] blk_mq_flush_plug_list+0x1e8/0x290 [ 1388.218013] ? blk_mq_make_request+0x35f/0x5b0 [ 1388.218016] blk_flush_plug_list+0xe3/0x110 [ 1388.218018] blk_finish_plug+0x26/0x34 [ 1388.218024] dmcrypt_write+0x155/0x170 [dm_crypt] [ 1388.218028] kthread+0x104/0x140 [ 1388.218030] ? crypt_iv_lmk_ctr+0xd0/0xd0 [dm_crypt] [ 1388.218032] ? kthread_park+0x90/0x90 [ 1388.218037] ret_from_fork+0x35/0x40 [ 1388.218039] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bnep bluetooth ecdh_generic ecc msr nls_iso8859_1 pata_pcmcia snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_powerclamp coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm snd_rawmidi intel_cstate uvcvideo pcmcia iwldvm snd_seq mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 libarc4 input_leds joydev videobuf2_common r852 hp_wmi snd_seq_device sm_common iwlwifi snd_timer sparse_keymap serio_raw videodev nand intel_ips nand_ecc mc bch r592 yenta_socket nandcore mtd pcmcia_rsrc memstick snd pcmcia_core cfg80211 mei_me wmi_bmof mei soundcore hp_accel lis3lv02d input_polldev tpm_infineon mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 [ 1388.218087] nf_defrag_ipv4 libcrc32c sch_fq_codel ip6table_filter ip6_tables iptable_filter parport_pc ppdev bpfilter lp parport sunrpc ip_tables x_tables autofs4 dm_crypt crct10dif_pclmul nouveau crc32_pclmul mxm_wmi i2c_algo_bit ghash_clmulni_intel ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops aesni_intel firewire_ohci sdhci_pci crypto_simd firewire_core cqhci ahci psmouse cryptd glue_helper sdhci libahci drm crc_itu_t lpc_ich e1000e wmi video [ 1388.218115] CR2: 8cf4f6fc5d86 [ 1388.218119] ---[ end trace 53f76f5ab9db54e9 ]--- [ 1388.218121] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1388.218124] Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 76 4f 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1388.218125] RSP: 0018:9b32020e7900 EFLAGS: 00010282 [ 1388.218127] RAX: 8cf4f6fc5d86 RBX: RCX:
[Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
apport information ** Tags added: apport-collected ** Description changed: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2:
[Bug 1886277] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389701/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389700/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389702/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389713/+files/WifiSyslog.txt ** 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/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389712/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389707/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389703/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389709/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389705/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389711/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886277] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1886277/+attachment/5389704/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
