[Kernel-packages] [Bug 2048701] Re: [i915] Screen freeze, kernel crash
AFAIKT this bug is resolved in 6.5.0-17-generic, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048701 Title: [i915] Screen freeze, kernel crash Status in linux-hwe-6.5 package in Ubuntu: New Bug description: After updating from 23.04 to 23.10 Screen freezes on boot. Booting with 23.04 kernel 6.2.0-36 still works. After getting 6.5.11-060511 from kernel ppa it works fine. From journal of failed X: jan 08 22:14:06 chromium kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] applying backlight present quirk jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] [ENCODER:76:DDI A/PHY A] HPD is down, disabling eDP jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] *ERROR* crtc 45: Can't calculate constants, dotclock = 0! jan 08 22:14:06 chromium kernel: [ cut here ] jan 08 22:14:06 chromium kernel: i915 :00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) jan 08 22:14:06 chromium kernel: WARNING: CPU: 1 PID: 101 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+> jan 08 22:14:06 chromium kernel: Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper cec polyval> jan 08 22:14:06 chromium kernel: CPU: 1 PID: 101 Comm: (udev-worker) Not tainted 6.5.0-14-generic #14-Ubuntu jan 08 22:14:06 chromium kernel: Hardware name: Acer Peppy, BIOS 03/02/2017 jan 08 22:14:06 chromium kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 df 49 68 e4 48 c7 c1 48 b5 71 c0 48 89 da 48 c7 c7 50 e3 71 c0 48 89 > jan 08 22:14:06 chromium kernel: RSP: 0018:a231804c3658 EFLAGS: 00010046 jan 08 22:14:06 chromium kernel: RAX: RBX: 933d80c7be30 RCX: jan 08 22:14:06 chromium kernel: RDX: RSI: RDI: jan 08 22:14:06 chromium kernel: RBP: a231804c36c8 R08: R09: jan 08 22:14:06 chromium kernel: R10: R11: R12: jan 08 22:14:06 chromium kernel: R13: 933d8b6f04a8 R14: a231804c36ec R15: 053f jan 08 22:14:06 chromium kernel: FS: 7fed1ae408c0() GS:933df8b0() knlGS: jan 08 22:14:06 chromium kernel: CS: 0010 DS: ES: CR0: 80050033 jan 08 22:14:06 chromium kernel: CR2: 56204b159120 CR3: 00010027c004 CR4: 000706e0 jan 08 22:14:06 chromium kernel: Call Trace: jan 08 22:14:06 chromium kernel: jan 08 22:14:06 chromium kernel: ? show_regs+0x6d/0x80 jan 08 22:14:06 chromium kernel: ? __warn+0x89/0x160 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? report_bug+0x17e/0x1b0 jan 08 22:14:06 chromium kernel: ? handle_bug+0x51/0xa0 jan 08 22:14:06 chromium kernel: ? exc_invalid_op+0x18/0x80 jan 08 22:14:06 chromium kernel: ? asm_exc_invalid_op+0x1b/0x20 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? _raw_spin_lock_irqsave+0xe/0x20 jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: drm_crtc_get_last_vbltimestamp+0x56/0x90 [drm] jan 08 22:14:06 chromium kernel: drm_reset_vblank_timestamp+0x73/0x100 [drm] jan 08 22:14:06 chromium kernel: drm_crtc_vblank_on+0xa9/0x1a0 [drm] jan 08 22:14:06 chromium kernel: ? assert_vblank_disabled+0x1d/0xd0 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_vblank_on+0x34/0x90 [i915] jan 08 22:14:06 chromium kernel: intel_modeset_setup_hw_state+0x1ea/0x540 [i915] jan 08 22:14:06 chromium kernel: ? drm_modeset_lock_all_ctx+0x99/0x1d0 [drm] jan 08 22:14:06 chromium kernel: ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0xa0 [drm] jan 08 22:14:06 chromium kernel: intel_display_driver_probe_nogem+0x186/0x250 [i915] jan 08 22:14:06 chromium kernel: i915_driver_probe+0x315/0x5b0 [i915] jan 08 22:14:06 chromium kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] jan 08 22:14:06 chromium kernel: ? acpi_dev_found+0x64/0x80 jan 08 22:14:06 chromium kernel: i915_pci_probe+0xd0/0x170 [i915] jan 08 22:14:06 chromium kernel: local_pci_probe+0x44/0xb0 jan 08 22:14:06 chromium kernel: pci_call_probe+0x55/0x190
[Kernel-packages] [Bug 2048701] [NEW] Xorg freeze
Public bug reported: After updating from 23.04 to 23.10 Screen freezes on boot. Booting with 23.04 kernel 6.2.0-36 still works. After getting 6.5.11-060511 from kernel ppa it works fine. >From journal of failed X: jan 08 22:14:06 chromium kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] applying backlight present quirk jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] [ENCODER:76:DDI A/PHY A] HPD is down, disabling eDP jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] *ERROR* crtc 45: Can't calculate constants, dotclock = 0! jan 08 22:14:06 chromium kernel: [ cut here ] jan 08 22:14:06 chromium kernel: i915 :00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) jan 08 22:14:06 chromium kernel: WARNING: CPU: 1 PID: 101 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+> jan 08 22:14:06 chromium kernel: Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper cec polyval> jan 08 22:14:06 chromium kernel: CPU: 1 PID: 101 Comm: (udev-worker) Not tainted 6.5.0-14-generic #14-Ubuntu jan 08 22:14:06 chromium kernel: Hardware name: Acer Peppy, BIOS 03/02/2017 jan 08 22:14:06 chromium kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 df 49 68 e4 48 c7 c1 48 b5 71 c0 48 89 da 48 c7 c7 50 e3 71 c0 48 89 > jan 08 22:14:06 chromium kernel: RSP: 0018:a231804c3658 EFLAGS: 00010046 jan 08 22:14:06 chromium kernel: RAX: RBX: 933d80c7be30 RCX: jan 08 22:14:06 chromium kernel: RDX: RSI: RDI: jan 08 22:14:06 chromium kernel: RBP: a231804c36c8 R08: R09: jan 08 22:14:06 chromium kernel: R10: R11: R12: jan 08 22:14:06 chromium kernel: R13: 933d8b6f04a8 R14: a231804c36ec R15: 053f jan 08 22:14:06 chromium kernel: FS: 7fed1ae408c0() GS:933df8b0() knlGS: jan 08 22:14:06 chromium kernel: CS: 0010 DS: ES: CR0: 80050033 jan 08 22:14:06 chromium kernel: CR2: 56204b159120 CR3: 00010027c004 CR4: 000706e0 jan 08 22:14:06 chromium kernel: Call Trace: jan 08 22:14:06 chromium kernel: jan 08 22:14:06 chromium kernel: ? show_regs+0x6d/0x80 jan 08 22:14:06 chromium kernel: ? __warn+0x89/0x160 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? report_bug+0x17e/0x1b0 jan 08 22:14:06 chromium kernel: ? handle_bug+0x51/0xa0 jan 08 22:14:06 chromium kernel: ? exc_invalid_op+0x18/0x80 jan 08 22:14:06 chromium kernel: ? asm_exc_invalid_op+0x1b/0x20 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? _raw_spin_lock_irqsave+0xe/0x20 jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: drm_crtc_get_last_vbltimestamp+0x56/0x90 [drm] jan 08 22:14:06 chromium kernel: drm_reset_vblank_timestamp+0x73/0x100 [drm] jan 08 22:14:06 chromium kernel: drm_crtc_vblank_on+0xa9/0x1a0 [drm] jan 08 22:14:06 chromium kernel: ? assert_vblank_disabled+0x1d/0xd0 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_vblank_on+0x34/0x90 [i915] jan 08 22:14:06 chromium kernel: intel_modeset_setup_hw_state+0x1ea/0x540 [i915] jan 08 22:14:06 chromium kernel: ? drm_modeset_lock_all_ctx+0x99/0x1d0 [drm] jan 08 22:14:06 chromium kernel: ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0xa0 [drm] jan 08 22:14:06 chromium kernel: intel_display_driver_probe_nogem+0x186/0x250 [i915] jan 08 22:14:06 chromium kernel: i915_driver_probe+0x315/0x5b0 [i915] jan 08 22:14:06 chromium kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] jan 08 22:14:06 chromium kernel: ? acpi_dev_found+0x64/0x80 jan 08 22:14:06 chromium kernel: i915_pci_probe+0xd0/0x170 [i915] jan 08 22:14:06 chromium kernel: local_pci_probe+0x44/0xb0 jan 08 22:14:06 chromium kernel: pci_call_probe+0x55/0x190 jan 08 22:14:06 chromium kernel: pci_device_probe+0x84/0x120 jan 08 22:14:06 chromium kernel: really_probe+0x1c4/0x410 jan 08 22:14:06 chromium kernel: __driver_probe_device+0x8c/0x180 jan 08 22:14:06 chromium kernel: driver_probe_device+0x24/0xd0 jan 08 22:14:06 chromium kernel: __driver_attach+0x10b/0x210 jan 08 22:14:06 chromium kernel: ? __pfx___driver_attach+0x10/0x10 jan 08 22:14:06 chromium kernel:
[Kernel-packages] [Bug 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
Good news, I am running 5.11.0-5c5 from ubuntu kernel ppa and the problem seems to be resolved . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
Still no improvement with ubuntu ppa kernel 5.10.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434452/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
Obviously above apport collected with 5.6 kernel as I can't login with 5.8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434454/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434453/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434443/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434441/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434448/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434445/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434442/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434449/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434450/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434437/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/543/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434446/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434439/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434438/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434440/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434447/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434451/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2017 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
apport information ** Tags added: apport-collected ** Description changed: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ferry 1098 F pulseaudio + /dev/snd/controlC0: ferry 1102 F pipewire-media- + /dev/snd/seq:ferry 1097 F pipewire + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2017-07-13 (1220 days ago) + InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai + Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Acer Peppy + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 + ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 + RelatedPackageVersions: + linux-restricted-modules-5.6.0-1032-oem N/A + linux-backports-modules-5.6.0-1032-oem N/A + linux-firmware 1.190.1 + Tags: groovy + Uname: Linux 5.6.0-1032-oem x86_64 + UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/02/2017 + dmi.bios.vendor: coreboot + dmi.chassis.type: 3 + dmi.chassis.vendor: Acer + dmi.modalias: dmi:bvncoreboot:bvr:bd03/02/2017:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: + dmi.product.name: Peppy + dmi.product.version: 1.0 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1904293/+attachment/5434436/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Confirmed Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ferry 1098 F pulseaudio /dev/snd/controlC0: ferry 1102 F pipewire-media- /dev/snd/seq:ferry 1097 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2017-07-13 (1220 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0489:e056 Foxconn / Hon Hai Bus 002 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Peppy Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1032-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1032.33-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1032-oem N/A linux-backports-modules-5.6.0-1032-oem N/A linux-firmware 1.190.1 Tags: groovy Uname: Linux 5.6.0-1032-oem x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (20 days ago) UserGroups:
[Kernel-packages] [Bug 1904293] [NEW] [i915] GPU hangs on Haswell (Acer 720p)
Public bug reported: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Fedora) Importance: Unknown Status: Unknown ** Tags: groovy ** Bug watch added: Red Hat Bugzilla #1843274 https://bugzilla.redhat.com/show_bug.cgi?id=1843274 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1843274 Importance: Unknown Status: Unknown ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904293 Title: [i915] GPU hangs on Haswell (Acer 720p) Status in linux package in Ubuntu: New Status in linux package in Fedora: Unknown Bug description: Since linux kernel 5.7 Haswell GPU's hang after logging in with sddm. This affects Groovy (linux 5.8) both with Ubuntu and Kubuntu. A work around is to boot with and earlier (5.6). The issue is known as: https://gitlab.freedesktop.org/drm/intel/-/issues/2413 and probable duplicates: https://gitlab.freedesktop.org/drm/intel/-/issues/2584 https://gitlab.freedesktop.org/drm/intel/-/issues/1805 Apparently the problem is resolved by: https://patchwork.freedesktop.org/patch/395580/?series=82783=1 Please consider backporting this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298646/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298637/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298639/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298647/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298643/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298638/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298645/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298641/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298640/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298642/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298644/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298636/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ferry 2280 F pulseaudio DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a InstallationDate: Installed on 2012-11-19 (2526 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183 RfKill: Tags: eoan Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848935] Re: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs
apport information ** Tags added: apport-collected ** Description changed: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs-progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. - In principle a script can be devised to save the failing inodes with - new, or when available btrfs-progs could be updated to 5.3 to repair the - file system. In any case it should be considered that the failing inodes - might be present on multiple snapshots of the fs. + In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ferry 2280 F pulseaudio + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=UUID=72896b7c-29c8-4560-af37-7ebda2e01c1a + InstallationDate: Installed on 2012-11-19 (2526 days ago) + InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) + IwConfig: + lono wireless extensions. + + eth1 no wireless extensions. + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/@boot/vmlinuz-5.0.0-32-generic root=UUID=27155120-9ef8-47fb-b248-eaac2b7c8375 ro rootflags=subvol=@ quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-32-generic N/A + linux-backports-modules-5.0.0-32-generic N/A + linux-firmware1.183 + RfKill: + + Tags: eoan + Uname: Linux 5.0.0-32-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-18 (2 days ago) + UserGroups: adm cdrom dialout dip fax floppy lp lpadmin plugdev sambashare scanner sudo syslog wheel wireshark + _MarkForUpload: True + dmi.bios.date: 07/11/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.90 + dmi.board.name: Z77 Extreme4 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1848935/+attachment/5298635/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: Confirmed Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to
[Kernel-packages] [Bug 1848935] [NEW] Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs
Public bug reported: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs-progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs eoan ftbfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: New Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
Debian removed the package because they disabled kernel support. Ubuntu removed the package because Debian did, but kept kernel support. Strange. Nevertheless I took the package from Xenial and installed on Bionic, nothing breaks dependencies. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy Status in linux package in Ubuntu: Confirmed Status in mcelog package in Ubuntu: Confirmed Bug description: There is no mcelog package in bionic. $ sudo apt install mcelog Reading package lists... Done Building dependency tree Reading state information... Done Package mcelog is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mcelog' has no installation candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
I have a similar issue with Meizu MX4 which pairs, connects but drops the connection to the car kit after being connected 2 sec. This bug hasn't been resolved in 1 1/2 year time and ota5 - ota14 releases. Now we hear that there will not be a ota15 for a long while and maybe even never for the Meizu and BQ, it looks it will never be fixed. I really don't think ubuntu phone has a future it we can't get a simple thing to work like hands free calling in the car, or playing music over the car speakers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds
This is still an issue with OTA14. I am a bit disappointed to hear there will not be a OTA15 soon and possibly even never for this device. Canonical, do you really think you can be successful in phone/touch if you give up something basic as bluetooth? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds
With OTA13 I managed to play music 1 or 2 times. Mostly it continues to disconnect immediately after connecting. The only difference I can think of is when I get in the car, start the engine and try to connect it fails, while if I wait a while it might work (but normally I don't have time to play after start driving). I may have something to do with the car trying to connect the handsfree phone function while the phone tries to connect the 'headphone' function for playback. I noticed on my desktop also a bt connection to a phone breaks when connecting to a second phone. May be related? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
On my Renault Laguna (2010) with TomTom Carminat I managed to pair, but connect doesn't seem to work. I ssh'ed into the phone (Arale) while connecting and saw that it actually does connect, but is disconnected after 2 seconds. This seems to confuse the TomTom shows it is trying to connect while in reality it was connected until the connection broke. I didn't see any reason why it disconnects in log etc. But maybe I'm looking in the wrong place. I would say it's about time we get this fixed. It seems to be some sort of timing issue. I'd be happy to collect logs, just let me know how. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
My Meizu MX4 is paired with my car (Renault with Carminat TomTom), but the connection breaks within 2 sec. after connecting. The sad thing is that it did work a bit before OTA 9. Will this be fixed by the new silo? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds
This problem still happens with OTA11 on Meizu MX7. The car kit is a Carminat (TomTom) in a Renault Laguna. Using bluetoothctl I can see the connection is established (there is no problem with pairing as in other bug reports). However the connection is disconnected after about 2 seconds. In a very early version (can't remember which OTA) bluetooth actually did work but only after a reboot. What can I do to get this fixed in OTA 12? I can ssh into my phone while connecting etc, but I didn't see any error messages. I just disconnects. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496102] Re: Bluetooth connection breaks in a few seconds
My Meizy MX7 with OTA10 breaks the connection to my car kit in about 2 seconds I ssh'ed into the phone during trying to connect to my car kit to see whats going on: - the car kit is paired -the car kit is trusted - the connection is established then disconnected after to seconds -not error messages (in bluetoothctl) I have this phone now about 1 /1/2 year and it would be really nice if I could connect to my own car, as everybody else with a Android can. What can I do to debug this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
My Meizu with OTA 6 seems to pair with my car (Renault, with built-in TomTom, phone sees the car as My_Radiosat, car see the phone as "MX4 Ubuntu Edit" truncated from Edition), however it does not connect most of the time. I managed to get it to connect a few times (audio), but sound does not come from the car speakers but from the phone. Also phone functions from the car don't work. Selecting the phone to dial out cause a bluetooth reconnect that fail after a while. (these functions worked with android phones of course). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 403303] Re: power manager reports 1% battery even though it is full on Asus Eee PC netbook
See #53 above. I have been updating my eeepc 900 with each new kubuntu release and have not seen this problem since. The metering is not very accurate and drops with 20% starting from 100% each 15 minutes or so. Yeah, the battery is nearing it's end-of-life. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/403303 Title: power manager reports 1% battery even though it is full on Asus Eee PC netbook Status in DeviceKit based power management D-Bus backend: Unknown Status in “devicekit-power” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-power-manager after logging in, I see a dialog box that says my battery may be broken and that it only has 1% charge, yet it's been plugged in for a long time, and the battery meter shows that it's full. Will post screenshot. The netbook I'm running this on is an Eee900, and this is on the A3 release of karmic UNR. ProblemType: Bug Architecture: i386 Date: Wed Jul 22 22:08:05 2009 DistroRelease: Ubuntu 9.10 Package: gnome-power-manager 2.27.2-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-3.19-generic SourcePackage: gnome-power-manager Tags: ubuntu-unr Uname: Linux 2.6.31-3-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/devicekit-power/+bug/403303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
