[Kernel-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work
i can confirm this on X99 Asrock Extreme4 board sound became dummy -- 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/1768991 Title: [bytchtes8316] Sound does not work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (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=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Mediacom SmartBook 130 FullHD - M-SB130 Package: pulseaudio 1:11.1-1ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kern
[Kernel-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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/1768991 Title: [bytchtes8316] Sound does not work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (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=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Mediacom SmartBook 130 FullHD - M-SB130 Package: pulseaudio 1:11.1-1ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel
[Kernel-packages] [Bug 1770940] [NEW] Kexec reboot doesn't work on 18.04 non-EFI system
Public bug reported: Unclear whether to report it against kexec-tools or systemd. After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the following error message: Cannot find the ESP partition mount point. What's interesting is that strace shows that systemctl tries to find the EFI partition before it emits the error message, like it was expecting an EFI system. My laptop is not capable of EFI, and it wasn't a problem for previous Ubuntu releases – the „systemctl kexec” command worked fine before. Here is my systemd version: root@thinkpad:~# systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid And my kexec-tools version is 1:2.0.16-1ubuntu1. I attached an strace output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1 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 May 13 12:48:25 2018 InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "strace-kexec.log" https://bugs.launchpad.net/bugs/1770940/+attachment/5138678/+files/strace-kexec.log ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1770940 Title: Kexec reboot doesn't work on 18.04 non-EFI system Status in kexec-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Unclear whether to report it against kexec-tools or systemd. After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the following error message: Cannot find the ESP partition mount point. What's interesting is that strace shows that systemctl tries to find the EFI partition before it emits the error message, like it was expecting an EFI system. My laptop is not capable of EFI, and it wasn't a problem for previous Ubuntu releases – the „systemctl kexec” command worked fine before. Here is my systemd version: root@thinkpad:~# systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid And my kexec-tools version is 1:2.0.16-1ubuntu1. I attached an strace output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1 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 May 13 12:48:25 2018 InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1770940/+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 1768898] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-13 07:34 EDT--- Looks like the kernel was built with a conflicting version number. Beware, your kernel modules have now been tainted and you have an old kernel with newer modules. I would have expected this to be built as a separate kernel version so that you could choose boot either old or new. Normally, we would modify the EXTRAVERSION variable in the Makefile so that it added a unique identifier, such as appending "-LP1768898". -- 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/1768898 Title: smp_call_function_single/many core hangs with stop4 alone Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Recently we discovered this bug occurs just alone with stop4 which results in soft lockups/rcu stalls. ``` root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [15523.619508] systemd[1]: systemd-journald.service: Failed with result 'timeout'. [15523.619769] systemd[1]: Failed to start Journal Service. [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 21. [15523.621462] systemd[1]: Stopped Journal Service. [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 1561 (systemd-journal) in control group while starting unit. Ignoring. [15523.621756] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 69060 (systemd-journal) in control group while starting unit. Ignoring. [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched self-detected stall on CPU [15541.629958]60-: (2 GPs behind) idle=146/142/0 softirq=300022/300022 fqs=999069 [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111) [15541.630101] NMI backtrace for cpu 60 [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L 4.15.0-15-generic #16-Ubuntu [15541.630207] Call Trace: [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 (unreliable) [15541.630298] [c000201a1da96b40] [c0cf4d48] nmi_cpu_backtrace+0x1f8/0x200 [15541.630363] [c000201a1da96bd0] [c0cf4ee8] nmi_trigger_cpumask_backtrace+0x198/0x1f0 [15541.630429] [c000201a1da96c60] [c002f2d8] arch_trigger_cpumask_backtrace+0x28/0x40 [15541.630495] [c000201a1da96c80] [c01a913c] rcu_dump_cpu_stacks+0xf4/0x158 [15541.630560] [c000201a1da96cd0] [c01a81e8] rcu_check_callbacks+0x8e8/0xb40 [15541.630625] [c000201a1da96e00] [c01b64a8] update_process_times+0x48/0x90 [15541.630689] [c000201a1da96e30] [c01ce1f4] tick_sched_handle.isra.5+0x34/0xd0 [15541.630753] [c000201a1da96e60] [c01ce2f0] tick_sched_timer+0x60/0xe0 [15541.630818] [c000201a1da96ea0] [c01b7054] __hrtimer_run_queues+0x144/0x370 [15541.630883] [c000201a1da96f20] [c01b7fac] hrtimer_interrupt+0xfc/0x350 [15541.630948] [c000201a1da96ff0] [c00248f0] __timer_interrupt+0x90/0x260 [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0 [15541.631069] [c000201a1da97070] [c0009014] decrementer_common+0x114/0x120 [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180 [15541.631135] LR = smp_call_function_single+0x110/0x180 [15541.631230] [c000201a1da973d0] [c01d55e0] smp_call_function_any+0x180/0x250 [15541.631294] [c000201a1da97430] [c0acd3e8] gpstate_timer_handler+0x1e8/0x580 [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0 [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0 [15541.631488] [c000201a1da975d0] [c01b4bf8] run_timer_softirq+0x1e8/0x270 [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4 [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120 [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0 [15541.631718] [c000201a1da977a0] [c0009014] decrementer_common+0x114/0x120 [15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450 [15541.631784] LR = smp_call_function_many+0x324/0x450 [15541.631879] [c000201a1da97b00] [c0075f18] pmdp_invalidate+0x98/0xe0 [15541.631935] [c000201a1da97b30] [c03a1120] change_huge_pmd+0xe0/0x270 [15541.632000] [c000201a1da97ba0] [c0349278] change_protection_range+0xb88/0xe40 [15541.63206
[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
** Tags removed: bugnameltc-167562 severity-high triage-g
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
** Tags added: bugnameltc-167562 severity-high
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best
Hello Attempted to try v4.17-rc3 BUT, v4.17-rc3 not available in 1386 ... Attempted to try v4.17-rc4 in i386 (available) BUT got a dependency problem linux-image AND linux-base AND Got an error when installing linux base ... AND finally got an error when attempting to uninstall linux image 4.17 rc4 dpkg: erreur de traitement du paquet linux-image-4.17.0-041700rc4-generic (--remove) : le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 127 Des erreurs ont été rencontrées pendant l'exécution : linux-image-4.17.0-041700rc4-generic E: Sub-process /usr/bin/dpkg returned an error code (1) seems that bugs are multiplicating (like cartoon rabbits) So, if you have a solution to recover a clean situation, prerequired for next attempt 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/1737423 Title: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best case Status in linux package in Ubuntu: Confirmed Bug description: Under XP card detected as PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0 PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0 PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1 PCI\VEN_10DE&DEV_0221&CC_03 memory range 9400 94FF memory range C000 DFFF memory range 9200 92FF IRQ 09 IO range 03B0 03BB IO range 03C0 03DF memory range 000A 000B Processeur graphique :GeForce 6200 Version du pilote : 307.83 Prise en charge DirectX : 9.0c Horloge principale : 300 MHz Débit de données mémoire :1064 MHz Interface de mémoire :64 bits Mémoire : 256 Mo Type de mémoire : DDR2 Version BIOS vidéo : 5.44.A2.10.26 IRQ : 9 Bus : PCI correctly detected as 256Mb and working Under linux file /var/log/Xorg.0.log contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @ 0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @ 0x/131072 card bad detection ... 0xc000/536870912 correct adress, wrong size 536870912 soit 512Mo output of: sudo lshw -C display; lsb_release -a; uname -a is jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a [sudo] password for jean: *-display description: Display controller produit: 82865G Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 02 bits: 32 bits horloge: 33MHz fonctionnalités: pm bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:16 mémoire:a000-a7ff mémoire:9000-9007 portE/S:1800(taille=8) *-display description: VGA compatible controller produit: NV44A [GeForce 6200] fabriquant: NVIDIA Corporation identifiant matériel: 9 information bus: pci@:03:09.0 version: a1 bits: 32 bits horloge: 66MHz fonctionnalités: pm vga_controller bus_master cap_list rom configuration: driver=nouveau latency=40 maxlatency=1 mingnt=5 ressources: irq:21 mémoire:9400-94ff mémoire:c000-dfff mémoire:9200-92ff mémoire:e000-e001 No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename:trusty Linux jean-Soisy 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux Attempted to find where the memory size detection lies in the code, but was too far in the labyrinth for me. Regards Jean COLIN --- ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jean 2206 F pulseaudio /dev/snd/controlC0: jean 2206 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2ae1454f-4490-4a9a-aea5-55daa49c243c InstallationDate: Installed on 2015-08-08 (985 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820) MachineType: IBM 8429RG7 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-144-generic root=UUID=0f7280ad-8482-48be-9433-13ca09f7304a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-144-generic N/A linux-backports-modules-3.13.0-144-generic N/A linux-firmware 1.127.24 RfKill: 0: phy0: Wir
[Kernel-packages] [Bug 1770970] [NEW] Huawei 25G/100G Network Adapters Unsupported
Public bug reported: [Impact] Huawei 25G/100G network adapters are not usable with Ubuntu. [Test Case] On a system with one of these adapters, the hinic driver should load and enumerate devices. [Fix] We just need to teach the driver about these new PCI IDs. [Regression Risk] These are previously unsupported devices. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: Triaged ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- 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/1770970 Title: Huawei 25G/100G Network Adapters Unsupported Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: [Impact] Huawei 25G/100G network adapters are not usable with Ubuntu. [Test Case] On a system with one of these adapters, the hinic driver should load and enumerate devices. [Fix] We just need to teach the driver about these new PCI IDs. [Regression Risk] These are previously unsupported devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770970/+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 1770974] [NEW] Fix several bugs in RDMA/hns driver
Public bug reported: [Impact] Several issues in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. TBD: Summarize. [Test Case] TBD [Regression Risk] TBD ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- 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/1770974 Title: Fix several bugs in RDMA/hns driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Several issues in the RDMA/hns driver for HiSilicon network adapters have recently landed upstream. TBD: Summarize. [Test Case] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770974/+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 1768208] Re: OLED X1 yoga lenove, screen ubuntu, brightness issue
apport information ** Tags added: apport-collected ** Description changed: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: marvin 1768 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 + MachineType: LENOVO 20FRS2M600 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/23/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1FET41W (1.15 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20FRS2M600 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Yoga 1st + dmi.product.name: 20FRS2M600 + dmi.product.version: ThinkPad X1 Yoga 1st + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138826/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: Th
[Kernel-packages] [Bug 1768208] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138830/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138831/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138827/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138828/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138829/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138835/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138836/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138837/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138838/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138832/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138839/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138833/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1768208] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138840/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1770784] Comment bridged from LTC Bugzilla
--- Comment From nevd...@us.ibm.com 2018-05-13 12:11 EDT---
This Canonical bug suggests they may have seen it before,but unfortunately it
was closed without a patch because it wasn't repeatable in a later release.
The bug suggests the change occurred between 4.4 and 4.6-rcsomething.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580943
I did a git blame on rbtree.c and there were no interesting changes
introduced during that time. I did the same with mmap.c and found many
... but none that claimed to be addressing this problem.
Discussions here (https://lkml.org/lkml/2016/2/16/625) suggest it might
be related to transparent huge pages (THP).
Although none of this points to a specific solution, it does suggest
this problem has been seen before.
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3f
[Kernel-packages] [Bug 1768208] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768208/+attachment/5138834/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768208 Title: OLED X1 yoga lenove, screen ubuntu, brightness issue Status in linux package in Ubuntu: Incomplete Bug description: As with all the proceeding distros from ubuntu 16.10 the brightness of the OLED screen canot be set. Since xrander is no more present there is also no hack around this problem anymore. This bug is a killer for using the system as full brightness drains the battery quickly. OLED screens have no backlight, thus this might be the issue. 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: Tue May 1 10:45:56 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1770784] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2018-05-13 12:26 EDT---
could this similar/same as issue #1235?
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3fffb750a190
NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
CTR: LR: 3fffb74b7034XER:
CCR: 44004442MQ: 0001DAR: 3fffb748
DSISR: 4000 Syscall Result: fffe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770784/+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 1762259] Re: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline
This bug is fixed on Fedora 28. I've also tested the Opensuse Tumbleweed but their distro kernel also has this bug -- 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/1762259 Title: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline Status in linux package in Ubuntu: Incomplete Bug description: I have an DVI-I to VGA adapter on my videocard. Usually I just need to put video=1440x900 because the linux kernel fails to recognize the correct resolution, but I couldn't make it display on the screen even setting video=DVI-I:1440x900. I believe it switches to HDMI because I could experience no issues like this on my television. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: hostname 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucio 1485 F pulseaudio /dev/snd/controlC1: lucio 1485 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 8 19:40:31 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=db8a4afa-dec3-45b6-a84f-9a702c6f96ad ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 980DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd04/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762259/+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 1770993] [NEW] System freezes, random reboots and browser crashes
Public bug reported: I've been having this issue with both 18.04 and 16.04 Ubuntu MATE since I installed an Nvidia GTX 1060. The system can run stably for days, or it can start freezing randomly and I have to manually reset, or the system freezes and then reboots itself. Browsers are also affected, and I've not found one that doesn't randomly crash, though Opera is particularly affected. This is the hardware spec of my system: Computer Processor AMD FX(tm)-8120 Eight-Core Processor Memory 32938MB (4021MB used) Machine Type Desktop Operating System Ubuntu 18.04 LTS User Name xxx Date/Time Dydd Mercher 09 mis Mai 2018 00:18:57 BST Display Resolution 5760x1080 pixels OpenGL Renderer GeForce GTX 1060 6GB/PCIe/SSE2 X11 Vendor The X.Org Foundation md5sum was fine when I checked the intallation usb, and the fact that it's affected both 16.04 and 18.04 (though 18.04 significantly less) indicates there is a problem which I suspect is linked to the Nvidia graphics card in some way, as it's also been an issue with Second Life/OpenSimulator viewers that also randomly freeze requiring a hard reboot of the system. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sun May 13 18:23:17 2018 InstallationDate: Installed on 2018-04-11 (32 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1770993 Title: System freezes, random reboots and browser crashes Status in linux-signed package in Ubuntu: New Bug description: I've been having this issue with both 18.04 and 16.04 Ubuntu MATE since I installed an Nvidia GTX 1060. The system can run stably for days, or it can start freezing randomly and I have to manually reset, or the system freezes and then reboots itself. Browsers are also affected, and I've not found one that doesn't randomly crash, though Opera is particularly affected. This is the hardware spec of my system: Computer Processor AMD FX(tm)-8120 Eight-Core Processor Memory 32938MB (4021MB used) Machine Type Desktop Operating System Ubuntu 18.04 LTS User Name xxx Date/Time Dydd Mercher 09 mis Mai 2018 00:18:57 BST Display Resolution 5760x1080 pixels OpenGL Renderer GeForce GTX 1060 6GB/PCIe/SSE2 X11 Vendor The X.Org Foundation md5sum was fine when I checked the intallation usb, and the fact that it's affected both 16.04 and 18.04 (though 18.04 significantly less) indicates there is a problem which I suspect is linked to the Nvidia graphics card in some way, as it's also been an issue with Second Life/OpenSimulator viewers that also randomly freeze requiring a hard reboot of the system. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sun May 13 18:23:17 2018 InstallationDate: Installed on 2018-04-11 (32 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) 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/1770993/+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 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
QCA6174 - The most groundbreaking problem to me is the fact that suspend doesnt work well, when we return from suspend, wifi and bluetooth, same board, are not working, a restart wont fix, even if selecting a older working kernel. Looks like the only fix is shutdown, then there is no more power in the board, i guess the kernel is breaking the board in a way that it needs a full reastart, i guess the board doesnt restart completely if you just restart the computer. I can confirm that the problems started after 4.14, the last one that was really working is 4.13, i tried now with 4.17-rc3 and didnt help, tried also with the latest ath10k_pci modules from github ( https://github.com/kvalo/ath10k-firmware), no changes. I can confirm also the problem is with the kernel, because just booting with 4.13, same packages and even same lib/firmware/ath10k_pci, If i can help with something i would be happy to do, i already tried everthing i can do, thanks. Close everything i'm doing is not something great. -- 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/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04. mitch@mitch-YOGA:~$ uname -a Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Same laptop, device, working fine on 17.10. No crashes, stable wifi. Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: failed to set 5g txpower 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: failed to setup tx power 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: failed to recalc tx power: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: failed to set PS Mode 0 for vdev 0: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: failed to setup ps on vdev 0: -11 Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11) Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr id 133) entry on vdev 0 after it was supposedly removed Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_s
[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu. There are lots of AMD-Vi logged events and I get irq crashes or acpi hangups with a 'normal' boot. I got it to boot by disabling IOMMU in the BIOS and adding "iommu=soft" to the kernel booting options in grub. linux can then detect everything properly (all cores) and I've had zero crashes. The only issue is that it's using software IOMMU which could have a performance penalty because it has to copy all the data of some PCI devices to sub 4G regions. Alternatively it boots with the kernel option "acpi=off" but only detects a single core/thread. I attached a kernel log. I believe(d) this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 --- ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fixme 1487 F pulseaudio /dev/snd/controlC0: fixme 1487 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece InstallationDate: Installed on 2018-01-31 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group B350GT5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: Tags: bionic Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.asset.tag: None dmi.board.name: B350GT5 dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: None dmi.product.name: B350GT5 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+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 1771040] [NEW] Bluetooth HFP/HSP profile doesn't work in 18.04
Public bug reported:
Hardware: Bose QC35 II
When selecting the A2DP Sink profile these headphones work fine.
However, with HSP/HFP selected neither the output nor the microphone
work. The headphones will periodically say "Call from" and then break
off, and also you can hear a low grade crackling like line noise in them
the rest of the time.
Potentially relevant logs:
dmesg (the second message is repeated frequently):
[ 68.288408] input: 2C:41:A1:80:A1:C4 as /devices/virtual/input/input21
[ 78.575027] Bluetooth: hci0: last event is not cmd complete (0x0f)
Originally, I got an error like the following from ("journalctl -u bluetooth"),
but then ran "rfkill unblock bluetooth" which seems to have fixed it:
May 13 15:58:02 skylake bluetoothd[1023]: Failed to set mode: Blocked through
rfkill (0x12)
May 13 15:58:19 skylake bluetoothd[1023]: Failed to set mode: Blocked through
rfkill (0x12)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Headset
Voice gateway: getpeername: Transport endpoint is not connected (107)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Phone Book
Access: getpeername: Transport endpoint is not connected (107)
What additional information would be useful to debug this?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
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 May 13 16:33:13 2018
InstallationDate: Installed on 2018-05-13 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3406
dmi.board.asset.tag: Default string
dmi.board.name: Z170I PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3406:bd07/10/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170IPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: C8:FF:28:31:68:E4 ACL MTU: 1024:8 SCO MTU: 50:8
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:19479 acl:97 sco:0 events:730 errors:0
TX bytes:8355 acl:99 sco:3 commands:148 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
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/1771040
Title:
Bluetooth HFP/HSP profile doesn't work in 18.04
Status in bluez package in Ubuntu:
New
Bug description:
Hardware: Bose QC35 II
When selecting the A2DP Sink profile these headphones work fine.
However, with HSP/HFP selected neither the output nor the microphone
work. The headphones will periodically say "Call from" and then break
off, and also you can hear a low grade crackling like line noise in
them the rest of the time.
Potentially relevant logs:
dmesg (the second message is repeated frequently):
[ 68.288408] input: 2C:41:A1:80:A1:C4 as /devices/virtual/input/input21
[ 78.575027] Bluetooth: hci0: last event is not cmd complete (0x0f)
Originally, I got an error like the following from ("journalctl -u
bluetooth"), but then ran "rfkill unblock bluetooth" which seems to have fixed
it:
May 13 15:58:02 skylake bluetoothd[1023]: Failed to set mode: Blocked through
rfkill (0x12)
May 13 15:58:19 skylake bluetoothd[1023]: Failed to set mode: Blocked through
rfkill (0x12)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Headset
Voice gateway: getpeername: Transport endpoint is not connected (107)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Phone
Book Access: getpeername: Transport endpoint is not connected (107)
What additional information would be useful to debug this?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
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 May 13 16:33:13 2018
InstallationDate: Installed on 2018-05-13 (0 days ago)
Installatio
[Kernel-packages] [Bug 1731091] Re: The HDMI audio can't work on all Geminilake machines we have (Dell laptops or desktops)
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: hwe-next Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1731091 Title: The HDMI audio can't work on all Geminilake machines we have (Dell laptops or desktops) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Bug description: I have filed a bugzilla bug to track this issue: https://bugzilla.kernel.org/show_bug.cgi?id=197785 We have several Geminilake laptop and desktop machines, on these machines, the HW configs are same and are as shown below: the HDA controller: 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 01) the HDMI codec: Vendor Id: 0x8086280d VGA controller: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3184] (rev 01) (prog-if 00 [VGA controller]) The problem is if we boot the system without plugging the HDMI monitor, the Linux kernel can't find HDMI codec at all. If we plug the HDMI monitor before booting up, the kernel can find the HDMI codec, but there are many errors (as shown below) and the HDMI audio can't play any sound. Codec: Intel Geminilake HDMI Address: 2 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x8086280d Subsystem Id: 0x80860101 Revision Id: 0x10 No Modem Function Group found Default PCM: N/A Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power: setting=UNKNOWN, actual=UNKNOWN, Error, Clock-stop-OK, Setting-reset Invalid AFG subtree --endcollapse-- [ 25.504069] snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 [ 26.516125] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 [ 27.528058] snd_hda_intel :00:0e.0: azx_get_response timeout, switching to single_cmd mode: last cmd=0x20bf8100 [ 27.528259] azx_single_wait_for_response: 12 callbacks suppressed [ 27.547927] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1731091/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
This issue started with the version 4.13 series. The last version that
did not have the issue is 4.11.0-14.
Mainline kernel version 4.17-rc4 also exhibits the issue.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
Confirmed
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630
** Changed in: linux-oem (Ubuntu) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1766398 Title: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Incomplete Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: New Bug description: [Impact] On this Dell machine (codename: turtle bay), the microphone always shows up in the sound-setting even there is no microphone plugged in. [Fix] Without this fix, the pin will be regarded as microphone, and the jack name is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged into the jack. So the UI is confusing to users since the microphone always shows up in the UI even there is no microphone plugged. After adding this flag, the jack name is "Headset Mic Phantom", then the pulseaudio can handle its detection correctly. [Test Case] After booting up the system, and without plugging anything in the audio combo jack, there is nothing in the input tab of sound-setting, then plug a headset in the jack, the what-did-you-plug-in dialogue pops up, users can select headset mic from UI, and headset-mic shows up in the sound-setting, we can record sound via headset-mic [Regression Potential] Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC which is only used by Dell precision 3630 by now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1766398/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension
Just upgrade from Xubuntu artful to bionic, and just discovered I face
the same issue.
Only modprobe -r r8169 + modprobe r8169 restore the network.
For now running default kernek 4.15.0-20-generic.
--
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/1752772
Title:
r8169 ethernet card don't work after returning from suspension
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have noticed that the network stopped working on my desktop after
I've suspended the system and woke it up. On dmesg there are messages
like:
[ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 150.944101] do_IRQ: 3.37 No irq handler for vector
[ 150.944105] r8169 :01:00.0 enp1s0: link down
[ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
When using Xenial (from a different install), this problem is not
happening. This is happening on Bionic.
There are only two ways to restore connectivity:
1) Reboot the system;
2) Remove the r8169 module and reinsert it with modprobe.
The motherboard is a AsRock H55M-LE and the Ethernet controller is:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.172
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Mar 2 00:21:57 2018
Dependencies:
InstallationDate: Installed on 2018-02-26 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-10-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: usuario1153 F pulseaudio
/dev/snd/controlC1: usuario1153 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
Mixer name : 'VIA VT1818S'
Components : 'HDA:11060440,18492818,0010'
Controls : 40
Simple ctrls : 17
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 7
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
CurrentDesktop: LXDE
Dependencies:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
InstallationDate: Installed on 2018-02-26 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux-firmware 1.172
PackageArchitecture: all
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
RelatedPackageVersions:
linux-restricted-modules-4.15.0-10-generic N/A
linux-backports-modules-4.15.0-10-generic N/A
linux-firmware 1.172
RfKill:
Tags: bionic
Uname: Linux 4.15.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H55M-LE
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+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.
[Kernel-packages] [Bug 1738911] Re: Support realtek new codec alc257 in the alsa hda driver
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1738911 Title: Support realtek new codec alc257 in the alsa hda driver Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: Otherwise, the kernel will load generic codec driver, this will introduce lots of problem like mute/micmute hotkey can't work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738911/+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 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
Tested 1.1.3-5ubuntu0.1 on bionic, it worked well and fixed the problem. thx. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Committed Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this change is compatible with old version. There is no regression since there is only one folder named by card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with dual codecs, it will find the conf file by card_long_name, if it runs on other machines, the search by card_long_name will definitely fail and fall back to search by card_name, then it will be same as before. So the objective of these 5 patches is to let lenovo machines with dual codecs find the conf file by card_long_name, let other machines fail to search by card_long_name, then fallback to original searching method - search by card_name. [Other Info] Since I could not find the alsa-lib repository in canonical, I just generated the debdiff with "apt-get source ...". To manage notifications about this bug go
[Kernel-packages] [Bug 1768660] Re: r8169 wired link down after suspend
*** This bug is a duplicate of bug 1752772 *** https://bugs.launchpad.net/bugs/1752772 ** This bug has been marked a duplicate of bug 1752772 r8169 ethernet card don't work after returning from suspension -- 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/1768660 Title: r8169 wired link down after suspend Status in linux package in Ubuntu: Incomplete Bug description: Everytime i suspend my laptop and back it ON, my ethernet connection shows Cable Unplugged, and r8169 link down. I can mannualy turn it on with sudo rmmod r8169 and then sudo modprobe r8169 but i have to do it everytime i suspend my laptop. 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: Budgie:GNOME Date: Wed May 2 22:56:49 2018 InstallationDate: Installed on 2018-05-01 (1 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/+bug/1768660/+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 1768115] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160.
--- Comment From mdr...@us.ibm.com 2018-05-13 20:45 EDT--- (In reply to comment #30) > Created attachment 127024 [details] > Patch to add extra tlbsyncs and ptesyncs > > Try this one instead of the "Patch to add extra tlbsyncs". Ben H pointed out > that it is ptesync which is important, not tlbsync (which is actually a > no-op, though architecturally required), so this version adds a ptesync to > the guest exit path as well as the tlbsync. Just a quick update, we noticed 2 other bugs pop up a few days ago where they hit very similar traces to what's been recorded here even without doing live migration. For instance Bug 167748 - LP1770784- ISST- LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest crashes in apparmor_file_alloc_security() [13244.120032] NIP [c0503788] aa_file_perm+0x238/0x4c0 [13244.120035] LR [c0503784] aa_file_perm+0x234/0x4c0 [13244.120035] Call Trace: [13244.120039] [c4ec7b90] [c0503784] aa_file_perm+0x234/0x4c0 (unreliable) [13244.120041] [c4ec7c90] [c04fe784] common_file_perm+0x134/0x250 [13244.120044] [c4ec7d10] [c048f088] security_file_permission+0x78/0x150 [13244.120047] [c4ec7d50] [c02e49ec] rw_verify_area+0x7c/0x190 [13244.120049] [c4ec7d90] [c02e4d4c] vfs_write+0x8c/0x230 [13244.120052] [c4ec7de0] [c02e5dbc] SyS_write+0x6c/0x110 [13244.120055] [c4ec7e30] [c0009484] system_call+0x38/0xe4 which has a similar beginning call trace to the initial bug reported here. And: Bug 167480 - ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:P8 compat guest crashed & enters into xmon after few hours of LTP run. [c002b1c13c10] c02faad8 path_openat+0x88/0x3c0 [c002b1c13c90] c02fca3c do_filp_open+0xfc/0x170 [c002b1c13db0] c02e31d0 do_sys_open+0x1c0/0x3b0 [c002b1c13e30] c0009484 system_call+0x38/0xe4 which is similar to the crash I saw with filp_close. The major things those bugs have in common with this one is both the guest and host SAN disks are using block multiqueue instead of legacy deadline/cfq schedulers, which was seen to have issues WRT to other patches like the one mentioned here: https://bugzilla.linux.ibm.com/show_bug.cgi?id=167294#c47 We started testing using last Ubuntu 4.15 with a set of patches that Ziviani put together there: https://github.com/jrziviani/linux-devel/commits/BLK_MQ_CPU but I was still eventually able to hit a crash. However, when I disabled blk-mq via "scsi_mod.use_blk_mq=n dm_mod.use_blk_mq=n" in host/guest I didn't see any crashes after 130 migrations. However, I did see IO errors + read-only filesystem after extended runs, which have also been seen elsewhere with no live migration involved. So there's a possibly the bug here is related to issues seen elsewhere without live migration, and some initial evidence to suggesting that the crashes may be related to blk-mq, but not enough to say anything for certain. Ziviani is currently doing some testing with upstream kernel. If that still has issues then will move to testing potential KVM fixes but want to rule out blk-mq first since the issue may not be specific to live migration. ** Bug watch added: bugzilla.linux.ibm.com/ #167294 https://bugzilla.linux.ibm.com/show_bug.cgi?id=167294 -- 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_r
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Adding some information in case it's useful. Old - but still useful - Intel Core 2 laptop with discrete Mobility Radeon GPU. I had nvidia packages installed for development purposes years ago, but don't really use them any more. After the upgrade from 17.10 to 18.04 (only performed 2018-05-12, several days after official release), I noticed single-threaded 100% CPU usage from systemd-udevd, with modprobe starting and exiting over and over again. I saw lots of messages complaining about NVIDIA hardware not being found in dmesg output. After uninstalling the nvidia packages and rebooting, the high CPU usage seemed to go away. So at least on my system, it seems there was a conflict between having nvidia drivers present with no NVIDIA hardware available. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in bluez package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1065400] Re: Support for loading Broadcom bluetooth firmware
I have same issue as @painterengr I had the problem where the Bluetooth mouse would work at first, but then suddenly: "Bluetooh Disabled". I checked dmesg and found this: Bluetooth: hci0: Broadcom Bluetooth Device [5.279438] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1761 [5.281325] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21f3.hcd failed with error -2 [5.281333] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21f3.hcd not found Which led me to this bug reports and and I quickly found this: https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-0a5c-21f3.hcd Which I copied over to /lib/firmware/brcm/BCM20702A1-0a5c-21f3.hcd After I rebooted the machine, the Bluetooh icon was completely gone from the GUI and in settings it says "Bluetooh disabled" So using that firmware completely botched Bluetooth on my system. -- 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/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1065400] Re: Support for loading Broadcom bluetooth firmware
UPDATE: If I remove the /lib/firmware/brcm/BCM20702A1-0a5c-21f3.hcd and I reboot I get the "flaky" Bluetooth back. Sometimes I need to suspend/resume to get it back. Was hoping this firmware would fix the issue, but instead it makes it worse. -- 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/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
Found another information, if i turn off my bluetooth mouse before suspention. The crash in the module seems to be related to suspending with something connected. -- 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/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04. mitch@mitch-YOGA:~$ uname -a Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Same laptop, device, working fine on 17.10. No crashes, stable wifi. Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: failed to set 5g txpower 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: failed to setup tx power 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: failed to recalc tx power: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: failed to set PS Mode 0 for vdev 0: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: failed to setup ps on vdev 0: -11 Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11) Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr id 133) entry on vdev 0 after it was supposedly removed Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core i2c_hid wmi hid video Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: NetworkManager Tainted: GW OE4.15.0-20-generic #21-Ubuntu Apr 28 12:12:25 mitch-YOGA kernel: [12379.644697] Hardware name: LENOVO 80VF/LNVNB161216, BIOS 2JCN39WW 05/31/2017 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644741] RIP: 0010:__sta_info_destroy_pa
[Kernel-packages] [Bug 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
Sorry.. If i turn off my bluetooth mouse before suspention, the problem doesnt happen. The crash in the module seems to be related to suspending with something connected. -- 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/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04. mitch@mitch-YOGA:~$ uname -a Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Same laptop, device, working fine on 17.10. No crashes, stable wifi. Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: failed to set 5g txpower 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: failed to setup tx power 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: failed to recalc tx power: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: failed to set PS Mode 0 for vdev 0: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: failed to setup ps on vdev 0: -11 Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11) Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr id 133) entry on vdev 0 after it was supposedly removed Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core i2c_hid wmi hid video Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: NetworkManager Tainted: GW OE4.15.0-20-generic #21-Ubuntu Apr 28 12:12:25 mitch-YOGA kernel: [12379.644697] Hardware name: LENOVO 80VF/LNVNB161216, BIOS 2JCN39WW 05/31/2017 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644741] RIP: 0010:__sta_info_de
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
UPDATE: MY FIX After some digging, I decided to download the latest Bluetooth Driver from Lenovo and extracted the firmware from it. I forked Winterheart's repository and patched the firmware and it works for me. Here is the link if anyone needs: https://github.com/alecz20/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-0a5c-21f3.hcd -- 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/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+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 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker
4.15.0-1007.7 - gcp Regression test CMPL, RTB. Issue to note in gcp: libhugetlbfs - failed to build on Bionic (bug 1707887) ubuntu_kvm_unit_tests - failed due to no KVM support ubuntu_ltp - test disabled ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 1751243) Skipped / blacklisted: * ubuntu_seccomp * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1767400 Title: linux-gcp: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+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 1755638] Re: Kernel BUG at 000000009096c250 [verbose debug info unavailable]
[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/1755638 Title: Kernel BUG at 9096c250 [verbose debug info unavailable] Status in linux package in Ubuntu: Expired Bug description: I got an error from bug repporter ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1210 F pulseaudio thinkpad 1702 F pulseaudio Date: Mon Mar 12 16:53:03 2018 Failure: oops InstallationDate: Installed on 2017-12-31 (72 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) MachineType: LENOVO 4170CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=2c19a086-ca7e-4ad8-b76c-43875bf0bebe ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: Kernel BUG at 9096c250 [verbose debug info unavailable] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4170CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET49WW(1.29):bd09/14/2011:svnLENOVO:pn4170CTO:pvrThinkPadT420s:rvnLENOVO:rn4170CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420s dmi.product.name: 4170CTO dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755638/+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 1637646] Re: Black screen when booting
[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/1637646 Title: Black screen when booting Status in linux package in Ubuntu: Expired Bug description: I have just upgraded from 16.04 to 16.10. The installation has dm- crypt installed in the whole hard drive. If I try to boot up the computer with kernel 4.8.0-26, most of the time (probably 9 out of 10) the computer gives a black screen instead of prompting for the dm-crypt passphrase. I try to remove "quiet splash" from grub (I can see the grub boot menu every time) but this does not help. Even I am lucky when the system prompts me for passphrase and the computer comes up successfully, the screen goes completely black again if the screen turns off once I idle the computer for a few minutes. The computer is still running (I can login to the computer remotely), just the screen becomes unavailable no matter what key I press. I still have the old kernel 4.4.0-45 from 16.04 installed and this kernel allows me to boot up the computer every time. My computer is a HP Elitebook 745 G3 notebook with AMD PRO A10-8700B R6 APU. Please let me know if I need to provide other information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637646/+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 1770509] Re: gui crashes on login
** Also affects: gdm3 (Ubuntu) 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/1770509 Title: gui crashes on login Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in gdm3 source package in Bionic: New Status in linux source package in Bionic: Confirmed Bug description: I have installed Ubuntu 18.04 LTS on my laptop which is a Lenovo Ideapad 300 with 8GB of RAM, an Intel® Core™ i7-6500U CPU @ 2.50GHz × 4 processor and Intel® HD Graphics 520 (Skylake GT2). I have GNOME 3.28.1 which logically is latest version of GNOME coming with Ubuntu 18.04 LTS. Everything works perfectly but I found a bug which happens when logging in. When I boot my laptop (which is not dual boot, it only has Ubuntu 18.04 LTS installed), I press Enter to select the only available user (my user) and then I am prompted to enter my password. If I type my password wrong by a character more (I haven't tried a smaller or a bigger length) and then give the right password the GUI crashes. What I mean by crashing is that I get a static purple screen where I can only move my mouse pointer and nothing else. I get no desktop, no icons, no nothing. I don't know if it is a hardware incompatibility or a bug but it happens every time I follow the steps I mentioned above and then I have to hard shutdown the laptop. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1599 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=10e7b298-4d9e-47e3-a810-d58d8cf6c6ca InstallationDate: Installed on 2018-04-28 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 174f:14e9 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Q7 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=38e55cbd-3efc-41fb-a339-2c5795929cf1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN31WW:bd12/03/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q7 dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770509/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
** Description changed: + ===SRU Justification=== + [Impact] + UVC1.5 Realtek webcam on XPS 9370 does not work. + + [Test] + Both the bug reporter and I can confirm the patch from Realtek works. + + [Fix] + Use correct version control length for UVC1.5. + + [Regression Potential] + Low. This only affects UVC1.5 webcams, which is quite rare in the wild. + + ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) 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.sys.vendor: Dell Inc. -- 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/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD
[Kernel-packages] [Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
The quirk I pointed in #135 is in latest kernel. -- 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/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+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 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
May be a good idea to try older kernels in [0] to make sure it's a regression. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+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
