[Kernel-packages] [Bug 1832625] Re: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different
** Changed in: ubuntu-z-systems Status: New => Triaged -- 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/1832625 Title: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: pkey: Indicate old mkvp only if old and curr. mkvp are different Symptom: zkey validate shows wrong information about master key registers Problem: When the CCA master key is set twice with the same master key, then the old and the current master key are the same and thus the verification patterns are the same, too. The check to report if a secure key is currently wrapped by the old master key erroneously reports old mkvp in this case. Solution: Fix this by checking current and old mkvp and report OLD only if current and old mkvp are different. Reproduction: Change the CCA master key but set the exact same master key that is already used. Then do a 'zkey validate' command on a secure key Component: kernel 5.1 rc1 Upstream-ID: ebb7c695d3bc7a4986b92edc8d9ef43491be183e This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by default. But should also be applied to 18.04 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832625/+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 1826516] Re: bluetooh mouse lag when use bluetooth hedphones
** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1826516 Title: bluetooh mouse lag when use bluetooth hedphones Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works. When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags terribly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 09:19:08 2019 InstallationDate: Installed on 2018-12-22 (124 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20LW000YPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW000YPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW000YPB dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:21:6B:EA:3C:5F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0 TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1826516/+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 1832988] Re: Intel 8260 Bluetooth not working
Please test this kernel: https://people.canonical.com/~khfeng/lp1832988/ -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1833028] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1833028 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Disco) Status: New => Incomplete -- 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/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: This is a new test for overlayfs: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 <<>> initiation_status="ok" duration=3 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833028/+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 1832101] Re: systemd-networkd: Lost carrier e1000
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/ -- 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/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] Jun 8 12:11:17 mc2 kernel: [30304.199102] RIP: 0010:cpuidle_enter_state+0xbd/0x450 Jun 8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8
[Kernel-packages] [Bug 1833028] [NEW] fanotify06 from ubuntu_ltp_syscalls failed
Public bug reported: This is a new test for overlayfs: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 <<>> initiation_status="ok" duration=3 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Incomplete ** Tags: 5.0 amd64 apport-bug disco ubuntu-ltp-syscalls uec-images ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Tags added: 5.0 ubuntu-ltp-syscalls ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: This is a new test for overlayfs: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 3 got no event
[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- 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/1504445 Title: FocalTech touchpad stops working after suspend Status in linux package in Ubuntu: Fix Released Bug description: I have an Asus V502LX the persian version of the Asus K501LX. I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to install the kernel 4.1.6 to have the touchpad recognised. Under kernel 3.19.30, as I am running now to file in this bug, the touchpad is recognised as a simple mouse (no two fingers scrolling...) and the problem I am describing below is also present... I noticed one problem. The Focaltech touchpad is not working after suspending the computer. Here is what I could find about the touchpad in /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0012 Version= N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 Before suspending the computer, I can deactivate and activate again the touchpad with the hotkey of my keyboard without problem. However, once the computer suspended, nothing work to re-activate the touchpad. I tried a solution given on internet but it doesn't work properly. I created a file here /etc/pm/sleep.d/trackpad sudo gedit /etc/pm/sleep.d/trackpad and add the following #!/bin/sh case "$1" in suspend|hibernate) modprobe -r psmouse; resume|thaw) modprobe psmouse; esac With this file, the computer refuse to suspend. The touchpad keep working so it does something but I can't make my computer sleeping... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 12:05:16 2015 InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yogo 2073 F pulseaudio /dev/snd/controlC0: yogo 2073 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. K501LX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 04/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K501LX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K501LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K501LX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1823126] Re: touchpad doesn't work (not listed in xinput)
[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1823126 Title: touchpad doesn't work (not listed in xinput) Status in linux-signed package in Ubuntu: Expired Bug description: Hello, My touchpad worked yesterday, but today it is not working. I tried to search all information about synaptics touchpad on my Xubuntu 16.04 but touchpad information are not listed with xinput and other command. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 4 09:21:52 2019 InstallationDate: Installed on 2017-11-06 (513 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1823126/+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 1752613] Re: Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts.
[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe (Ubuntu) Status: Incomplete => Expired -- 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/1752613 Title: Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts. Status in linux package in Ubuntu: Expired Status in linux-signed-hwe package in Ubuntu: Expired Bug description: Following update from kernel 4.13.0-32-generic to 4.13.0-36-generic, my Hyper-V 2012 R2 hosted Ubunntu servers experienced problems with memory allocation--they reported total assigned memory less than the initial allocation of the dynamic memory configuration, corresponding with 98% memory utilization and over 35 load average. I was able to boot back to 4.13.0-32-generic, and the issue went away. I was also able to resolve the issue by changing the servers from dynamic memory allocations (512 initial 4096 max) to static memory allocations (4096 static). Sar memory snapshots as follows, only change was kernel booted: Linux 4.13.0-36-generic (servername) 03/01/2018 _x86_64_(4 CPU) 09:14:34 AM kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit kbactive kbinact kbdirty 09:14:35 AM 6312409676 98.48 1528 28696 2416712 257.02 37948 4697628 09:14:36 AM 7268408720 98.25 1368 27944 2418800 257.24 38360 45096 124 Average: 6790409198 98.37 1448 28320 2417756 257.13 38154 4603676 __ Linux 4.13.0-32-generic (servername) 03/01/2018 _x86_64_(4 CPU) 09:31:02 AM kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit kbactive kbinact kbdirty 09:31:03 AM 1276908 1885452 59.62 32256735348 2728356 74.01798260768032 260 09:31:04 AM 1276908 1885452 59.62 32264735348 2728356 74.01798304768036 280 Average: 1276908 1885452 59.62 32260735348 2728356 74.01798282768034 270 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 10:17:06 2018 InstallationDate: Installed on 2016-08-25 (552 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752613/+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 1819305] Re: Synaptic touchpad not working
[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1819305 Title: Synaptic touchpad not working Status in linux-signed package in Ubuntu: Expired Bug description: nan ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 10:17:53 2019 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1819305/+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 1774824] Re: la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi
[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1774824 Title: la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi Status in linux-signed package in Ubuntu: Expired Bug description: ubuntu budgi x64 bits no me reconoce mi tarjeta wifi Qualcomm Atheros AR9287 Wireless Network Adapter ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Jun 2 17:29:50 2018 InstallationDate: Installed on 2018-06-02 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774824/+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 1824953] Re: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1824953 Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Expired Bug description: Upgrade from cosmic to disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 3431 F pulseaudio Date: Tue Apr 16 09:01:08 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-14 (366 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-16 (0 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824953/+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 1752613] Re: Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1752613 Title: Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts. Status in linux package in Ubuntu: Expired Status in linux-signed-hwe package in Ubuntu: Expired Bug description: Following update from kernel 4.13.0-32-generic to 4.13.0-36-generic, my Hyper-V 2012 R2 hosted Ubunntu servers experienced problems with memory allocation--they reported total assigned memory less than the initial allocation of the dynamic memory configuration, corresponding with 98% memory utilization and over 35 load average. I was able to boot back to 4.13.0-32-generic, and the issue went away. I was also able to resolve the issue by changing the servers from dynamic memory allocations (512 initial 4096 max) to static memory allocations (4096 static). Sar memory snapshots as follows, only change was kernel booted: Linux 4.13.0-36-generic (servername) 03/01/2018 _x86_64_(4 CPU) 09:14:34 AM kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit kbactive kbinact kbdirty 09:14:35 AM 6312409676 98.48 1528 28696 2416712 257.02 37948 4697628 09:14:36 AM 7268408720 98.25 1368 27944 2418800 257.24 38360 45096 124 Average: 6790409198 98.37 1448 28320 2417756 257.13 38154 4603676 __ Linux 4.13.0-32-generic (servername) 03/01/2018 _x86_64_(4 CPU) 09:31:02 AM kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit kbactive kbinact kbdirty 09:31:03 AM 1276908 1885452 59.62 32256735348 2728356 74.01798260768032 260 09:31:04 AM 1276908 1885452 59.62 32264735348 2728356 74.01798304768036 280 Average: 1276908 1885452 59.62 32260735348 2728356 74.01798282768034 270 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 10:17:06 2018 InstallationDate: Installed on 2016-08-25 (552 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752613/+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 1833018] Re: After Installing Updates, system fails to boot on first try
Does kernel parameter "nopti" help? -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1821394] Re: vmx tests fail in kvm_unit_tests
** Tags removed: 5.0.0 ** Tags added: 5.0 ubuntu-kvm-unit-tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1821394 Title: vmx tests fail in kvm_unit_tests Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test" PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails INFO: Processor supports accessed and dirty flag PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails FAIL:
[Kernel-packages] [Bug 1830316] Re: ksm06* from mm test suite in LTP failed on D
These tests have passed on node amaura, not naunamm. Need to check if this is hw-specific. ** Tags added: 5.0 disco oem-osp1 ubuntu-ltp -- 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/1830316 Title: ksm06* from mm test suite in LTP failed on D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on node "grumman". Test failed with: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY startup='Thu May 23 14:41:43 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06 stime=1558622503 dur=0 exit=exited stat=2 core=no cu=0 cs=0 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_1 stime=1558622504 dur=0 exit=exited stat=2 core=no cu=0 cs=1 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_2 stime=1558622504 dur=1 exit=exited stat=2 core=no cu=0 cs=25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830316/+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 1832988] Re: Bluetooth not working
If the above command doesn't work then I would next focus on a possible kernel problem in: [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) ** Summary changed: - Bluetooth not working + Intel 8260 Bluetooth not working -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable
[Kernel-packages] [Bug 1832988] Re: Bluetooth not working
The attached RfKill.txt seems to suggest that Bluetooth is only turned off in software. So maybe this is just a gnome-shell GUI bug, or gnome- bluetooth. To confirm this, please try turning it on by running this command in a terminal: rfkill unblock 0 ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Incomplete -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure
[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco
This is affecting OEM-OSP1 (5.0.0-1009.10-oem-osp1) as well, we might need to rebase this fix to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829812 Title: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Bug description: [SRU Justification] == Impact == Some upstream stable change modified the bpf selftest to use a function that probes for existing eBPF program types. However that function does not exist in the 5.0 kernel sources. == Fix == Picking two additional changes from upstream (which only modify the tools sub-directory), allows to compile the selftests again. == Risk of Regression == Since the kernel itself is not touched, the risk is low. == Testcase == With build-essential installed and the Disco kernel tree cloned: cd tools/testing/selftests/ TARGET=net make --- This test will failed to build on 5.0.0-16 Disco. 5.0.0-16 Disco + 5.0.0-15 source code - build OK 5.0.0-16 Disco + 5.0.0-16 source code - Failed Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for unsupported program types) in our tree is the cause (upstream commit: 8184d44c) Which uses a "recently introduced bpf_probe_prog_type()" to skip test. And we don't have it implemented. make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' gcc -o /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read -static urandom_read.c -Wl,--build-id make -C ../../../lib/bpf OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ make[2]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf' Auto-detecting system features: ...libelf: [ on ] ... bpf: [ on ] HOSTCC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o HOSTLD /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep-in.o LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/nlattr.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/btf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf_errno.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/str_error.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/netlink.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_prog_linfo.o LD /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf-in.o LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.so LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_libbpf make[2]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf' gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../includetest_verifier.c /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' test_verifier.c: In function ‘do_test_single’: test_verifier.c:15951:22: warning: implicit declaration of function ‘bpf_probe_prog_type’; did you mean
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Pat, Re comment #19, your crash (hang) reports there seem to show the gnome- shell process behaving normally (in poll) and not stuck at all. That doesn't tell us much but it would support the theory in comment #31. ** Summary changed: - Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it + Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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
Re: [Kernel-packages] [Bug 1833018] Re: After Installing Updates, system fails to boot on first try
On 6/16/19 6:51 PM, Eduardo Alcober wrote: > Just eliminate the first command. just > > sudo grub-install > sudo update-grub > > from your normal user. > > Sorry, Thanks. > The grub-install required a device name. I specified: sudo grub-install /dev/sda It said it was successful, and the "sudo update-grub" completed normally, as well. When I powered on the machine after shutting down, I got the GRUB menu, as expected. However, the error again occurred, so that appears to have had no effect. The particular error this time, was that it hung (with screen garbage visible), and I had to hold down the power button to turn it off. -- Sincerely, Aere -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it
Interesting one of the commits mentioned above: 37efe80ce85f drm/vmwgfx: use monotonic event timestamps (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f) is related to what I changed in the latest update to mutter: https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72 The latest update to mutter requires monotonic event timestamps in the kernel driver in order to work properly. It should kind of work without them, but that fallback is untested... So if that is the problem then you might find reverting to the previous mutter version also works around the issue(?). You can download the debs: https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2/+build/16644915 and then try installing them together: dpkg -i *.deb ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Eoan) Status: New => Invalid ** Changed in: mutter (Ubuntu Bionic) Status: New => Incomplete ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Indeed there was a kernel update to 18.04 around the same time as the mutter update which I thought was causing this bug. ** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Bionic) ** No longer affects: mutter (Ubuntu Eoan) ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Invalid ** Summary changed: - Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it + Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1833018] Re: After Installing Updates, system fails to boot on first try
Just eliminate the first command. just sudo grub-install sudo update-grub from your normal user. Sorry, Thanks. -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+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 1833018] Re: After Installing Updates, system fails to boot on first try
Hi, Have you tried reinstalling grub? It's recommended after a big upgrade. The sequence of commands is as follows: su - sudo grub-install sudo update-grub After this the machine should boot normally. Keep in touch. Greetings, EAC. -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+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 1833018] Re: After Installing Updates, system fails to boot on first try
When I boot, but specify the other partition (also Lubuntu 18.04.2) - the one that originally started having the boot problems - it boots successfully. When I boot, but specify the originally-installed kernel (linux- image-4.15.0-20-generic), it also boots successfully. Sometimes, on the boots that fail, it just hangs, and I have to hold down the power button to turn it off. It appears, that after initially powering on, and just booting from the first GRUB menu entry, it always fails in some manner the first time. -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+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 1833018] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+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 1833018] [NEW] After Installing Updates, system fails to boot on first try
Public bug reported: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug bionic i386 -- 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/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug
[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
Changed kernel parameter on Dell D620 and Dell 530s - both booting properly first time since upgrade from kernel 47. Thanks -- 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/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) Status in linux package in Ubuntu: Confirmed Bug description: NOTE: Boot problems on TWO different laptops after Software Updater updated to kernel 4.15.0-48 Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu desktop. Both fresh installs from minimal CD in early April, originally kernel 0.4.15.0-47, both working fine. Bug report filed on THIS MACHINE: HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel integrated graphics controller GM965/GL960 (with kernel command line parameter ¨video=SVIDEO-1:d¨) SYMPTOM: 4.15.0-48 requires a second ´recovery´ boot to get it up and running. Will not boot properly after a normal shutdown - screen goes funny and it hangs Does boot successfully after a hard shutdown - detects improper shutdown, loads grub menu, then boot successfully Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48 Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots normally after a normal shutdown) OTHER MACHINE: Even older!!! ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility Radeon 9600 GPU. Running with command line parameter "forcepae". SYMPTOM: Won't boot at all. Was working fine under 4.15.0-47 as originally installed, until software updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I can't even get into the grub menu to try the older kernel. More Info on what I've already tried for troubleshooting (on the HP6710b) is outlined in https://answers.launchpad.net/ubuntu/+question/680486 Happy to provide more info if needed, but I'm just an end user user and new to Linux, so will be on a learning curve at this end. (and apologies in advance if this a user problem, and not an actual bug). Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1681 F pulseaudio CurrentDesktop: XFCE Date: Mon May 6 21:16:34 2019 MachineType: Hewlett-Packard HP Compaq 6710b PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DDU Ver. F.13 dmi.board.name: 30C0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.2E dmi.chassis.asset.tag: SGH8080272 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6710b dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael1034 F pulseaudio /dev/snd/controlC0: michael1034 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. W1N Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
ethtool reports "highdma: on [fixed]", and won't let me switch it off. -- 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/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] Jun 8 12:11:17 mc2 kernel: [30304.199102] RIP: 0010:cpuidle_enter_state+0xbd/0x450 Jun 8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7
[Kernel-packages] [Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
I have same issue here in 2019. 01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) M3N notebook 4.15.0-51-generic Ubuntu 18.04.2 LTS a lot of: [11414.173675] ipw2100: Fatal interrupt. Scheduling firmware restart. [12674.408121] ipw2100: Fatal interrupt. Scheduling firmware restart. [64189.132057] ipw2100: wlp1s4: Firmware did not initialize. [64189.132061] ipw2100: wlp1s4: Failed to start the firmware. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/5271053/+files/dmesg.log -- 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/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Baltix: Invalid Bug description: / ATTENTION I believe this issue is specific to the error that a chipset that is not 802.11G capable will return when it picks up an a beacon from a router that is not mixed-mode, but 802.11G specific. Please verify. Remove mixed-mode from your G routers, and see if you can get this repeated. Then add back mix mode and see if it goes away and if you're connected with 802.11B. / [ Current Status ] The ipw2100 driver was last updated on 2007-01-31. That tarball release contained an issues file that described this particular bug: Firmware restart is detected randomly -- After running one or two days, Intel PRO/Wireless 2100 Network Connection driver will only occasionally restart the firmware. "ipw2100: Fatal interrupt. Scheduling firmware restart" To resolve this problem, the system must be rebooted. Defect #329 [ Original Description ] Since I've upgrade to Breezy, ipw2100 driver no longer works and in dmesg I've got plenty "Fatal interrupt. Scheduling firmware restart." I'm always able to do an iwlist : % sudo iwlist eth1 scanning eth1 Scan completed : ... Cell 02 - Address: 00:07:CB:51:65:E0 ESSID:"gaspard" Protocol:IEEE 802.11b Mode:Master Channel:11 Encryption key:on Bit Rate:11 Mb/s Extra: Rates (Mb/s): 1 2 5.5 11 Quality=92/100 Signal level=-36 dBm Extra: Last beacon: 31ms ago But the card no longer register. It stays "unassociated" whatever I've tried : % sudo iwconfig eth1 essid gaspard key open XX mode auto % sudo iwconfig eth1 eth1 unassociated ESSID:"gaspard" Nickname:"ipw2100" Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power:off Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:4D7E-7ED3-1D Security mode:open Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Sometimes, it works for a short time and after half an hour or an hour, it crash again. I've tried to upgrade ipw2100 and the firmware. No way. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+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 1832961] Re: 3.5mm audio jack whistles on headphones
Hello Hui, Sadly the kernel 5.2-rc4 dont run correctly on my Laptop. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087 Regards -- 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/1832961 Title: 3.5mm audio jack whistles on headphones Status in linux package in Ubuntu: Confirmed Bug description: 3.5mm audio jack whistles on headphones on Dell 9570 laptop --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 2094 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (214 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.173.6 Tags: tessa Uname: Linux 4.18.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832961/+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 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
This is reported upstream: https://github.com/raspberrypi/linux/issues/2881 ** Bug watch added: github.com/raspberrypi/linux/issues #2881 https://github.com/raspberrypi/linux/issues/2881 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1825235/+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 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on
I would uninstall those packages and I will see about getting 5.0 kernel source code and apply the patch so it can be tested -- 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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+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 1832613] Re: You can't scroll "indefinitely" without performance penalty >:]
Speed reset: page up + page down if you are near top end page down + page up if you are near bottom end Avoid any hindrance: scroll without hitting top or bottom end Affected: Chromium browser, Thunar, etc. -- 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/1832613 Title: You can't scroll "indefinitely" without performance penalty >:] Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Unknown Bug description: Anything that's allowed to set lowest to highest setting seems simply broken for some reason. e.g. volume, brightness settings are broken, as is scroll (web browser for example). More interesting example would be relocating focused tab to first position before closing it, for example in Chromium browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+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 1832988] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1832988 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1832988] [NEW] Bluetooth not working
Public bug reported: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description:Ubuntu 19.04 Release:19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco kernel-bluetooth ** Attachment added: "output of "sudo lspci -vnvn"" https://bugs.launchpad.net/bugs/1832988/+attachment/5271010/+files/lspci-vnvn.log -- 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/1832988 Title: Bluetooth not working Status in linux package in Ubuntu: New Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no
Re: [Kernel-packages] [Bug 1832963] Re: sound doesn't work
I don't know if this will help any but: I ran pavucontrol and HDMI/DisplayPort says unplugged. On Sat, Jun 15, 2019 at 9:27 PM Michael wrote: > beyond the scope of my abilities > > On Sat, Jun 15, 2019 at 9:14 PM Michael wrote: > >> installing that is beyond me. >> >> On Sat, Jun 15, 2019 at 9:10 PM Hui Wang wrote: >> >>> Probably a vga_switchroot problem. >>> >>> Please test the latest mainline kernel: >>> >>> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc4/ >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1832963 >>> >>> Title: >>> sound doesn't work >>> >>> Status in linux package in Ubuntu: >>> Confirmed >>> >>> Bug description: >>> after installing new kernel RV770 HDMI Audio [Radeon HD >>> 4850/4870](Radeon 4850 512MB GODR3 PCI-E Dual Slot Fansin. reported as >>> Disabled and off in sound preferences->hardware >>> --- >>> ProblemType: Bug >>> ApportVersion: 2.20.9-0ubuntu7.6 >>> Architecture: amd64 >>> AudioDevicesInUse: >>>USERPID ACCESS COMMAND >>>/dev/snd/controlC0: bmike1 1895 F pulseaudio >>>/dev/snd/controlC2: bmike1 1895 F pulseaudio >>>/dev/snd/controlC1: bmike1 1895 F pulseaudio >>> CurrentDesktop: MATE >>> DistroRelease: Linux Mint 19.1 >>> InstallationDate: Installed on 2019-01-15 (151 days ago) >>> InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 >>> MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H >>> Package: linux (not installed) >>> ProcFB: 0 radeondrmfb >>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic >>> root=UUID=6298f990-6b80-4665-80ab-e83034a72ae5 ro quiet splash >>> crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M >>> vt.handoff=1 >>> ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 >>> RelatedPackageVersions: >>>linux-restricted-modules-5.0.0-16-generic N/A >>>linux-backports-modules-5.0.0-16-generic N/A >>>linux-firmware1.173.6 >>> RfKill: >>>0: phy0: Wireless LAN >>> Soft blocked: no >>> Hard blocked: no >>> Tags: tessa >>> Uname: Linux 5.0.0-16-generic x86_64 >>> UpgradeStatus: No upgrade log present (probably fresh install) >>> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo >>> _MarkForUpload: True >>> dmi.bios.date: 09/16/2009 >>> dmi.bios.vendor: Award Software International, Inc. >>> dmi.bios.version: F4 >>> dmi.board.name: GA-MA785G-UD3H >>> dmi.board.vendor: Gigabyte Technology Co., Ltd. >>> dmi.board.version: x.x >>> dmi.chassis.type: 3 >>> dmi.chassis.vendor: Gigabyte Technology Co., Ltd. >>> dmi.modalias: >>> dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: >>> dmi.product.name: GA-MA785G-UD3H >>> dmi.sys.vendor: Gigabyte Technology Co., Ltd. >>> >>> To manage notifications about this bug go to: >>> >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832963/+subscriptions >>> >> >> >> -- >> :-)~MIKE~(-: >> > > > -- > :-)~MIKE~(-: > -- :-)~MIKE~(-: -- 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/1832963 Title: sound doesn't work Status in linux package in Ubuntu: Confirmed Bug description: after installing new kernel RV770 HDMI Audio [Radeon HD 4850/4870](Radeon 4850 512MB GODR3 PCI-E Dual Slot Fansin. reported as Disabled and off in sound preferences->hardware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmike1 1895 F pulseaudio /dev/snd/controlC2: bmike1 1895 F pulseaudio /dev/snd/controlC1: bmike1 1895 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-01-15 (151 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=6298f990-6b80-4665-80ab-e83034a72ae5 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend
With newer kernel 4.15 for example, it does work out of the box. -- 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/1504445 Title: FocalTech touchpad stops working after suspend Status in linux package in Ubuntu: Triaged Bug description: I have an Asus V502LX the persian version of the Asus K501LX. I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to install the kernel 4.1.6 to have the touchpad recognised. Under kernel 3.19.30, as I am running now to file in this bug, the touchpad is recognised as a simple mouse (no two fingers scrolling...) and the problem I am describing below is also present... I noticed one problem. The Focaltech touchpad is not working after suspending the computer. Here is what I could find about the touchpad in /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0012 Version= N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 Before suspending the computer, I can deactivate and activate again the touchpad with the hotkey of my keyboard without problem. However, once the computer suspended, nothing work to re-activate the touchpad. I tried a solution given on internet but it doesn't work properly. I created a file here /etc/pm/sleep.d/trackpad sudo gedit /etc/pm/sleep.d/trackpad and add the following #!/bin/sh case "$1" in suspend|hibernate) modprobe -r psmouse; resume|thaw) modprobe psmouse; esac With this file, the computer refuse to suspend. The touchpad keep working so it does something but I can't make my computer sleeping... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 12:05:16 2015 InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yogo 2073 F pulseaudio /dev/snd/controlC0: yogo 2073 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. K501LX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 04/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K501LX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K501LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K501LX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I've tested the kernel 4.15.0-52 (from khfeng) on my laptop and found: THE FLICKERING IS GONE! Screen is O.K. in text and graphic - mode. Console switching works too. So, Paul's bugfix seems to work! Many thanks! I found one small thing: the new radeon.ko - module identifies itself still as "... Initialized radeon 2.50.0 20080528"; same like the buggy version. So it is difficult to distinguish the "good" from the "buggy" - module. -- 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/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+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
