[Kernel-packages] [Bug 1797828] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797828 Title: Kernel Panic at reboot or shutdown Status in linux package in Ubuntu: Confirmed Bug description: I recive a kernel panel error sometimes when i reboot or shutdown my laptop. cat /proc/version_signature > version.log Ubuntu 4.15.0-36.39-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 1612 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 06:32:44 2018 InstallationDate: Installed on 2018-09-30 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Sony Corporation VGN-SZ61MN_B PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=bd884fa9-e980-4525-a3ac-d2f2545eace2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0122S5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0122S5:bd04/04/2008:svnSonyCorporation:pnVGN-SZ61MN_B:pvrJ002UJ6X:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-SZ61MN_B dmi.product.version: J002UJ6X dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797828/+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 1797828] [NEW] Kernel Panic at reboot or shutdown
Public bug reported: I recive a kernel panel error sometimes when i reboot or shutdown my laptop. cat /proc/version_signature > version.log Ubuntu 4.15.0-36.39-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 1612 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 06:32:44 2018 InstallationDate: Installed on 2018-09-30 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Sony Corporation VGN-SZ61MN_B PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=bd884fa9-e980-4525-a3ac-d2f2545eace2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0122S5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0122S5:bd04/04/2008:svnSonyCorporation:pnVGN-SZ61MN_B:pvrJ002UJ6X:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-SZ61MN_B dmi.product.version: J002UJ6X dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic kernel-bug ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1797828/+attachment/5200985/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797828 Title: Kernel Panic at reboot or shutdown Status in linux package in Ubuntu: Confirmed Bug description: I recive a kernel panel error sometimes when i reboot or shutdown my laptop. cat /proc/version_signature > version.log Ubuntu 4.15.0-36.39-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 1612 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 06:32:44 2018 InstallationDate: Installed on 2018-09-30 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Sony Corporation VGN-SZ61MN_B PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=bd884fa9-e980-4525-a3ac-d2f2545eace2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0122S5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0122S5:bd04/04/2008:svnSonyCorporation:pnVGN-SZ61MN_B:pvrJ002UJ6X:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-SZ61MN_B dmi.product.version: J002UJ6X dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797828/+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 1787204] Re: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subproces
[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/1787204
Title:
package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to
install/upgrade: installed linux-headers-4.15.0-32-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Expired
Bug description:
During an automatic system update.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-30-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: otavio 1211 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc440 irq 27'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aac011,0010
HDA:80862805,80860101,0010'
Controls : 28
Simple ctrls : 10
Date: Wed Aug 15 09:49:16 2018
ErrorMessage: installed linux-headers-4.15.0-32-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=1767a5ad-7caf-4df3-a67e-ddf2832403e8
InstallationDate: Installed on 2018-07-11 (34 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: LENOVO 4328
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic
root=UUID=b8b51864-1342-41a3-b2ef-a1454b3cd5d4 ro locale=pt_BR 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.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2
SourcePackage: linux
Title: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to
install/upgrade: installed linux-headers-4.15.0-32-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 40CN20WW(V1.07)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnLENOVO:bvr40CN20WW(V1.07):bd01/22/2011:svnLENOVO:pn4328:pvrLenovoG470:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: IDEAPAD
dmi.product.name: 4328
dmi.product.version: Lenovo G470
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787204/+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 1785480] Re: Xorg freeze (kernel general protection fault: 0000 [#1] SMP)
[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/1785480 Title: Xorg freeze (kernel general protection fault: [#1] SMP) Status in linux package in Ubuntu: Expired Bug description: Stack trace from last freeze: ~$ cat /var/log/kern.log|grep "5 15:1" Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.878703] general protection fault: [#1] SMP Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.878740] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_usb_audio snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_usbmidi_lib snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd kvm snd_seq irqbypass snd_seq_device snd_timer snd input_leds k10temp serio_raw edac_mce_amd edac_core i2c_piix4 soundcore shpchp 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 hid_generic hid_logitech_hidpp pata_acpi hid_logitech_dj usbhid hid uas usb_storage amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 firewire_ohci drm firewire_core mii pata_atiixp crc_itu_t ahci libahci wmi fjes Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879121] CPU: 2 PID: 14839 Comm: MemoryInfra Tainted: G OE 4.4.0-131-generic #157-Ubuntu Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879163] Hardware name: Gigabyte Technology Co., Ltd. GA-MA785GMT-UD2H/GA-MA785GMT-UD2H, BIOS F1 07/03/2009 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879207] task: 88022143a640 ti: 88006499c000 task.ti: 88006499c000 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879240] RIP: 0010:[] [] find_get_entry+0x34/0xa0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879280] RSP: 0018:88006499fd78 EFLAGS: 00010246 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879304] RAX: 8800603c5c28 RBX: 880069a27508 RCX: fffa Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879335] RDX: RSI: 8800603c5c28 RDI: f7ffea000763c880 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879367] RBP: 88006499fd88 R08: R09: 8800603c5b60 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879398] R10: 88006499fd58 R11: 7f44a30bf000 R12: 0314 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879429] R13: 0200 R14: 8801477fe000 R15: 01d4 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879461] FS: 7f44b1e86700() GS:88022fd0() knlGS: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879496] CS: 0010 DS: ES: CR0: 80050033 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879522] CR2: 163c8d2cc000 CR3: 1a6a5000 CR4: 06f0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879554] Stack: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879564] 880069a27500 0314 88006499fda8 811c9ed6 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879600] 8801c0071314 0315 88006499fde8 811c9fce Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879637] 8801c0071141 88006499fed8 7f44a34c 880176f208c8 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879674] Call Trace: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879690] [] mincore_page+0x26/0xa0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879715] [] __mincore_unmapped_range+0x7e/0xd0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879744] [] mincore_unmapped_range+0x1a/0x30 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.880836] [] __walk_page_range+0x32b/0x4d0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.881903] [] walk_page_range+0x65/0xe0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.882987] [] SyS_mincore+0x1b8/0x250 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.884059] [] ? mincore_unmapped_range+0x30/0x30 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.885144] [] ? __mincore_unmapped_range+0xd0/0xd0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.886256] [] ? copy_user_huge_page+0x300/0x300 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.887379] [] entry_SYSCALL_64_fastpath+0x22/0xc1 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.888534] Code: 41 54 53 48 8d 5f 08 49 89 f4 4c 89 e6 48 89 df e8 d2 3b 27 00 48 85 c0 48 89 c6 74 36 48 8b 38 48 85 ff 74 2e 40 f6 c7 03 75 52 <8b> 4f 1c 85 c9 74 d8 8d 51 01 4c 8d 47 1c 89 c8 f0 0f b1 57 1c Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.891139] RIP [] find_get_entry+0x34/0xa0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.892411] RSP Aug 5 15:15:45 GA-MA785GMT-UD2H
[Kernel-packages] [Bug 1787223] Re: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subproces
[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/1787223 Title: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: While upgrading from 16.04.5 to 18.04(.1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 15 14:28:27 2018 ErrorMessage: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=c6796c6c-41da-4ce3-931e-c09f94ba0a4b InstallationDate: Installed on 2015-07-08 (1133 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4389W1B ProcFB: ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: linux Title: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 4389W1B 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:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W510 dmi.product.name: 4389W1B dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787223/+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 1795292] Re: ELAN469D touch pad not working
Can you provide acpidump? Maybe the frequency provided by ACPI was wrong. -- 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+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 1788387] Re: After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue
Find the first bad/good -rc kernel to minimize the bisect range. -- 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/1788387 Title: After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue Status in linux package in Ubuntu: Confirmed Bug description: I'm using Xubuntu in an old system, I'm concerned because other users looking for a light OS for their old PC wouldn't be able to install or boot the 18.04 version and above. With kernel 4.4.0 the system boots without problem (xubuntu 16.04), after upgrading to kernel 4.15 the system doesn't boot anymore (18.04). This issue was present when testing kernel 4.13 too. The install crashes with an error: BIOS bug:8254 timer not connected to io-apic error on. Adding any of these commands to the boot allows the system to load properly: -acpi=off -pci=noacpi -acpi=noirq I attach the info related. Ubuntu 4.15.0-32.35-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1509 F pulseaudio /dev/snd/controlC1: 1509 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ed42d246-f10a-403e-a009-8c6428ce1a88 InstallationDate: Installed on 2018-06-12 (70 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 248a:00da Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc Dimension C521 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=467ee8bd-241d-4d11-95d9-6d9268a1dca6 ro quiet splash pci=noacpi vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788387/+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 1797628] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797628 Title: System hangs during boot at "Started configure plugged in printer" Status in linux package in Ubuntu: Confirmed Bug description: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. After this "fix," I can reboot fine without unplugging anything. This bug appears to happen right after a system update (running Software Updater and there are kernel bits to update). This is new behaviour; I had the same system setup running and booting fine under 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2018-10-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: LENOVO 2356CU8 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 529944 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356CU8 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797628/+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 1797759] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797759 Title: screen goes blank when mate loads - unable to see the login screen Status in linux package in Ubuntu: Confirmed Bug description: After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank before the login screen appears. Kernel Linux 4.15.0-36-generic x86_64. It was fine using Ubuntu Mate 16.x. I have found by booting to save mode and select boot from HDD everything works except the font is a bit large and some screens go off the bottom of the screen and I can't view this part of the screen. When checking software & updates there are no additional drivers loaded. The monitor preferences show monitor is known, resolution is 1280 x 800, refresh rates is 0 hz. None of this info can be changed. I have run the software update 3-4 times hoping that it would right itself. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Mon Oct 15 00:25:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:7008] InstallationDate: Installed on 2018-09-01 (43 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.50 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: SGH038PG56 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797759/+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 1764803] Re: failed install of nvidia-drivers-390
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1764803 Title: failed install of nvidia-drivers-390 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: insulation method using ubuntu-driver, blacklisting nouveau. also tried with the ppa added and driver from nvidia.com. All failed which hasnt happed before when installing (K)ubuntu Black screen after reboot GPU running hot Kubuntu 18.04 final beta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks Date: Tue Apr 17 17:30:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M LE] [1025:0505] InstallationDate: Installed on 2018-04-12 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Acer Aspire 5755G ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux acpi_backlight=vendor quiet nomodset splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV51_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5755G dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1764803/+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 1797759] Re: screen goes blank when mate loads - unable to see the login screen
Your kernel log suggests a problem with the GPU: [15604.676163] intel ips :00:1f.6: failed to disable graphics turbo [15609.796033] intel ips :00:1f.6: failed to disable graphics turbo [15614.915894] intel ips :00:1f.6: failed to disable graphics turbo [15620.035767] intel ips :00:1f.6: failed to disable graphics turbo The reason why recovery/safe mode works for you would be because that uses the 'nomodeset' option. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1797759 Title: screen goes blank when mate loads - unable to see the login screen Status in linux package in Ubuntu: New Bug description: After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank before the login screen appears. Kernel Linux 4.15.0-36-generic x86_64. It was fine using Ubuntu Mate 16.x. I have found by booting to save mode and select boot from HDD everything works except the font is a bit large and some screens go off the bottom of the screen and I can't view this part of the screen. When checking software & updates there are no additional drivers loaded. The monitor preferences show monitor is known, resolution is 1280 x 800, refresh rates is 0 hz. None of this info can be changed. I have run the software update 3-4 times hoping that it would right itself. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Mon Oct 15 00:25:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:7008] InstallationDate: Installed on 2018-09-01 (43 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.50 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: SGH038PG56 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797759/+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 1764803] [NEW] failed install of nvidia-drivers-390
You have been subscribed to a public bug: insulation method using ubuntu-driver, blacklisting nouveau. also tried with the ppa added and driver from nvidia.com. All failed which hasnt happed before when installing (K)ubuntu Black screen after reboot GPU running hot Kubuntu 18.04 final beta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks Date: Tue Apr 17 17:30:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M LE] [1025:0505] InstallationDate: Installed on 2018-04-12 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Acer Aspire 5755G ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux acpi_backlight=vendor quiet nomodset splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV51_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5755G dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- failed install of nvidia-drivers-390 https://bugs.launchpad.net/bugs/1764803 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- 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 1797628] Re: System hangs during boot at "Started configure plugged in printer"
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1797628 Title: System hangs during boot at "Started configure plugged in printer" Status in linux package in Ubuntu: New Bug description: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. After this "fix," I can reboot fine without unplugging anything. This bug appears to happen right after a system update (running Software Updater and there are kernel bits to update). This is new behaviour; I had the same system setup running and booting fine under 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2018-10-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: LENOVO 2356CU8 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 529944 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356CU8 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797628/+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 1797759] [NEW] screen goes blank when mate loads - unable to see the login screen
You have been subscribed to a public bug: After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank before the login screen appears. Kernel Linux 4.15.0-36-generic x86_64. It was fine using Ubuntu Mate 16.x. I have found by booting to save mode and select boot from HDD everything works except the font is a bit large and some screens go off the bottom of the screen and I can't view this part of the screen. When checking software & updates there are no additional drivers loaded. The monitor preferences show monitor is known, resolution is 1280 x 800, refresh rates is 0 hz. None of this info can be changed. I have run the software update 3-4 times hoping that it would right itself. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Mon Oct 15 00:25:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:7008] InstallationDate: Installed on 2018-09-01 (43 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.50 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: SGH038PG56 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- screen goes blank when mate loads - unable to see the login screen https://bugs.launchpad.net/bugs/1797759 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1797628] [NEW] System hangs during boot at "Started configure plugged in printer"
You have been subscribed to a public bug: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. After this "fix," I can reboot fine without unplugging anything. This bug appears to happen right after a system update (running Software Updater and there are kernel bits to update). This is new behaviour; I had the same system setup running and booting fine under 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2018-10-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: LENOVO 2356CU8 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 529944 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356CU8 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- System hangs during boot at "Started configure plugged in printer" https://bugs.launchpad.net/bugs/1797628 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1797002] Re: Bluetooth audio skips while the settings dialog is open
** Summary changed: - all my bluetooth headsets skips terribly after todays update + Bluetooth audio skips while the settings dialog is open ** Changed in: bluez (Ubuntu) Status: Invalid => New ** No longer affects: linux (Ubuntu) ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Tags added: a2dp a2dp-skip -- 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/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797198] Re: [nvidia] After login the screen goes black
** Changed in: gdm3 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Released ** Changed in: xorg-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login the screen goes black Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: When I boot Cosmic, grub is working OK and login screen is presented OK, but after login the screen goes black. When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia driver 390 is used. These bugs my be related https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192 See attachment for syslog info. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 20:12:32 2018 InstallationDate: Installed on 2018-10-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797198/+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 1727235] Re: Dell new AIO requires a new uart backlight driver
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1727235 Title: Dell new AIO requires a new uart backlight driver Status in HWE Next: New Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: [Impact] New Dell AIO platforms requires a driver that can communicate with the scalar IC FW through UART interface to get and set the brightness level. [Test] Verified on some new Dell machines and confirmed it works. [Fix] Write a new driver to handle this task. [Regression Potential] Low, it's a new driver for new interface. [Misc] Upstream maintainer ask use to re-implement this driver by the new interface, serdev, but serdev seems doesn't work with ACPI, so submit this driver as Ubuntu sauce patch for now. I'll try re-write it when I'm available. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727235/+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 1746340] Re: Samsung SSD corruption (fsck needed)
I may try that. Are we sure it's a kernel bug though? I can't remember having this problem when I used Solus OS for a while. But I may not have used for long enough since I discovered it didn't support Jack2 and was pretty much unusable to me. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
** Changed in: linux (Ubuntu)
Assignee: Nisankh Acharjya (nisankhubuntu) => (unassigned)
--
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/1797772
Title:
ideapad_laptop disables WiFi/BT radios on Lenovo Y530
Status in linux package in Ubuntu:
Incomplete
Bug description:
I've been working with a user that has a Lenovo Legion Y530-15ICH
where booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios
being disabled by the platform driver "ideapad-laptop".
Unloading or blacklisting the module solves the issue but disables
other platform ACPI interfaces:
$ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7 for 'Airplane mode') and need to use a DMI
match to disable the rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control
flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
@@ -1239,6 +1246,7 @@
int cfg;
struct ideapad_private *priv;
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok Christian, thanks for the info. You can try the kernel for now, and I also read that using ubuntu with brtfs system instead of ext4 also solves the problem, you could try -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB:
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Nisankh Acharjya (nisankhubuntu)
--
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/1797772
Title:
ideapad_laptop disables WiFi/BT radios on Lenovo Y530
Status in linux package in Ubuntu:
Incomplete
Bug description:
I've been working with a user that has a Lenovo Legion Y530-15ICH
where booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios
being disabled by the platform driver "ideapad-laptop".
Unloading or blacklisting the module solves the issue but disables
other platform ACPI interfaces:
$ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7 for 'Airplane mode') and need to use a DMI
match to disable the rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control
flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
@@ -1239,6 +1246,7 @@
int cfg;
struct ideapad_private *priv;
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Lucas! Thanks for the reply. No, I had no problems during installation. The computer just shuts down at random intervals to a black screen with all kinds of EXT4-fs errors and reports that the file system is read only. Often the disk isn't even recognized at reboot, so I have to boot into a live environment and use Gparted to fix it from there. I do music production professionally, so if I can't get it fixed relatively easily and permanently then I'll have to look elsewhere unfortunately. Thanks though. :) -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Ole Christian. First, did you have any problems in the ubuntu installation? In mine I had to try to install several times until it installed without any disk errors. Also, you can try this kernel https://people.canonical.com/~khfeng/pm961 -disable-aspm/ with this kernel parameter "nvme- core.default_ps_max_latency_us=1500". This is what worked for me, but it's not a definitive solution, I still get the error in some situations (much more rare than before though). You can read our discussion to understand it better. I guess someone is working on this bug for a definitive solution... -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion:
[Kernel-packages] [Bug 1797805] Re: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database
Hello Arne, Apparently it is a problem of libreoffice. I'm not sure. Best regards, -- Cristian Aravena Romero (caravena) ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** No longer affects: libreoffice (Ubuntu) ** Also affects: libreoffice (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/1797805 Title: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database Status in libreoffice package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hi! A few days ago I updaet my System to Ubuntu 18.04.1 LTS. Today I found out that I can't open my Libre Base Adress-Database anymore. 1) I start Libre Base.(German Version) 2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing to open my Adress-Database. 3) The Libre Base Main Window apperas with my Database. At the left side are die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 4) I choose the only form stored with this database. 5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it. 6) I restart Libre Base. It wants to repair the broken Database. It does so succesfully. 7) Continue with 3) My PC: CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2 Grafik: Intel Haswell Desktop x86/MMX/SSE2 RAM: 7.8 GB Gnome: 3.28.2 OS-TYpe: 32-bit Disks: 1.1 TB libreoffice-base: Installiert: 1:6.0.6-0ubuntu0.18.04.1 Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1 Versionstabelle: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Best regard Wannabe ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arne 2313 F pulseaudio /dev/snd/controlC0: arne 2313 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 23:20:38 2018 HibernationDevice: RESUME=UUID=47b31bba-205c-4d51-9e19-dcde4056d0cb InstallationDate: Installed on 2014-03-01 (1688 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=UUID=df276a8e-3485-4b48-b073-ebcb6e030df1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-10 (4 days ago) dmi.bios.date: 12/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd12/03/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797805/+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 1793172] Re: Black screen
Still taking a very long time to boot up. gives a different acpi error messag. THEN error message saying lvmetad missing and scans system to find suitable. any suggestions gratefully received. -- 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/1793172 Title: Black screen Status in linux package in Ubuntu: Confirmed Bug description: Black screen on start up, restart with external HDD switched on. Then get error message ACPI exception, Could not find /resolve named package element LNK [20170831/dspkginit-381]. This has occurred since upgrading form Ubuntu16, was working fine before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1930 F pulseaudio /dev/snd/controlC1: mark 1930 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 17:05:58 2018 HibernationDevice: RESUME=UUID=8b133e1e-7423-4fc9-9d2f-5b1378f24536 InstallationDate: Installed on 2014-12-08 (1380 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-16 (1 days ago) dmi.bios.date: 04/23/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793172/+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 1797805] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797805 Title: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database Status in linux package in Ubuntu: Confirmed Bug description: Hi! A few days ago I updaet my System to Ubuntu 18.04.1 LTS. Today I found out that I can't open my Libre Base Adress-Database anymore. 1) I start Libre Base.(German Version) 2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing to open my Adress-Database. 3) The Libre Base Main Window apperas with my Database. At the left side are die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 4) I choose the only form stored with this database. 5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it. 6) I restart Libre Base. It wants to repair the broken Database. It does so succesfully. 7) Continue with 3) My PC: CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2 Grafik: Intel Haswell Desktop x86/MMX/SSE2 RAM: 7.8 GB Gnome: 3.28.2 OS-TYpe: 32-bit Disks: 1.1 TB libreoffice-base: Installiert: 1:6.0.6-0ubuntu0.18.04.1 Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1 Versionstabelle: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Best regard Wannabe ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arne 2313 F pulseaudio /dev/snd/controlC0: arne 2313 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 23:20:38 2018 HibernationDevice: RESUME=UUID=47b31bba-205c-4d51-9e19-dcde4056d0cb InstallationDate: Installed on 2014-03-01 (1688 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=UUID=df276a8e-3485-4b48-b073-ebcb6e030df1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-10 (4 days ago) dmi.bios.date: 12/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd12/03/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797805/+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 1797805] [NEW] After Update to Ubuntu 18.04.1 LTS Libre Base wont open database
Public bug reported: Hi! A few days ago I updaet my System to Ubuntu 18.04.1 LTS. Today I found out that I can't open my Libre Base Adress-Database anymore. 1) I start Libre Base.(German Version) 2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing to open my Adress-Database. 3) The Libre Base Main Window apperas with my Database. At the left side are die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 4) I choose the only form stored with this database. 5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it. 6) I restart Libre Base. It wants to repair the broken Database. It does so succesfully. 7) Continue with 3) My PC: CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2 Grafik: Intel Haswell Desktop x86/MMX/SSE2 RAM: 7.8 GB Gnome: 3.28.2 OS-TYpe: 32-bit Disks: 1.1 TB libreoffice-base: Installiert: 1:6.0.6-0ubuntu0.18.04.1 Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1 Versionstabelle: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Best regard Wannabe ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arne 2313 F pulseaudio /dev/snd/controlC0: arne 2313 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 23:20:38 2018 HibernationDevice: RESUME=UUID=47b31bba-205c-4d51-9e19-dcde4056d0cb InstallationDate: Installed on 2014-03-01 (1688 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=UUID=df276a8e-3485-4b48-b073-ebcb6e030df1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-10 (4 days ago) dmi.bios.date: 12/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd12/03/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797805 Title: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database Status in linux package in Ubuntu: Confirmed Bug description: Hi! A few days ago I updaet my System to Ubuntu 18.04.1 LTS. Today I found out that I can't open my Libre Base Adress-Database anymore. 1) I start Libre Base.(German Version) 2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing to open my Adress-Database. 3) The Libre Base Main Window apperas with my Database. At the left side are die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 4) I choose the only form stored with this database. 5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it. 6) I restart Libre Base. It wants to repair the broken Database. It does so succesfully. 7) Continue with 3) My PC: CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2 Grafik: Intel Haswell Desktop x86/MMX/SSE2 RAM: 7.8 GB Gnome: 3.28.2 OS-TYpe: 32-bit Disks: 1.1 TB libreoffice-base: Installiert: 1:6.0.6-0ubuntu0.18.04.1 Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1 Versionstabelle: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I have this bug (MSI laptop, Ubuntu Studio 18.04) and it's getting quite annoying to be honest. If there's anything I can do to help remedy the situation within reasonable time (I'm about to reinstall) then let me know. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
@NiBu, Excellent! Thank you. Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent 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: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
I can now confirm that two finger scrolling is working, and tapping with two fingers works like a charm as the rightclick on Chuwi Lapbook Air. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)
The kernel has a module for this, "hid-primax", which re-orders the
received HID reports to make them compliant.
$ modinfo hid-primax
filename:
/lib/modules/4.15.0-34-lowlatency/kernel/drivers/hid/hid-primax.ko
license:GPL
author: Terry Lambert
srcversion: 9AF9EA4DBFB1326426467BB
alias: hid:b0003g*v0461p4E05
depends:hid
retpoline: Y
intree: Y
name: hid_primax
vermagic: 4.15.0-34-lowlatency SMP preempt mod_unload
signat: PKCS#7
signer:
sig_key:
sig_hashalgo: md4
$ git show f6a04605f3038
commit f6a04605f303852963f3f357d19b967aa83c172f
Author: Terry Lambert
Date: Fri Oct 14 17:18:54 2011 -0700
HID: support primax keyboards violating USB HID spec
Primax keyboards with the issue this driver addresses report modifier
keys as in band key events instead of as out of band modifier bits,
resulting in the modifier keys generating key up events immediately
before the keys they are intended to modify. This driver rewrites
the raw report data from such keyboards into USB HID 1.11 compliant
report data. It only matches the USB vendor and product IDs for the
keyboard it has been tested on. Since there are several keyboards,
notably a number of laptops and folding USB keyboards known to have
similar unresolved problem reports, the list is expected to grow.
Signed-off-by: Terry Lambert
Signed-off-by: Jiri Kosina
$ git describe --contains f6a04605f3038
v3.2-rc1~187^2^2~2
Currently the driver only supports the device ID 0461:4e05 and will need
the IDs of other devices adding in order to work with them.
# extract from drivers/hid/hid-primax.c
static const struct hid_device_id px_devices[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_PRIMAX, USB_DEVICE_ID_PRIMAX_KEYBOARD) },
{ }
};
$ grep PRIMAX drivers/hid/hid-ids.h
#define USB_VENDOR_ID_PRIMAX0x0461
#define USB_DEVICE_ID_PRIMAX_MOUSE_4D22 0x4d22
#define USB_DEVICE_ID_PRIMAX_KEYBOARD 0x4e05
#define USB_DEVICE_ID_PRIMAX_REZEL 0x4e72
Collecting additional IDs and adding them would be the best action to
take.
--
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/1771431
Title:
Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics
manufacturer)
Status in linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux package in Fedora:
Confirmed
Bug description:
Hi
I got an issue on Ubuntu 18.04 with latest packages.
uname -a:
Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
lshw:
*-usb:0
description: Keyboard
product: Lenovo USB Receiver
vendor: Lenovo
physical id: 3
bus info: usb@1:3
version: 1.05
capabilities: usb-2.00
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
My wireless keyboard is not working, Ubuntu only recognize some
special keys (Super, Ctrl, Shift, Alt)
This is a Mouse+Keyboard combo using a wireless receiver by usb:
lsusb:
Bus 001 Device 005: ID 17ef:609b Lenovo
Mouse works fine, and in Windows 10 it works with no issues.
I found multiple reported problems with this keyboard in other distros (and
from Asus too, as the real manufacturer is Primax Electronics).
https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486
https://ubuntuforums.org/showthread.php?t=2378862
https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu
https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/
REPORTS ON KERNEL MAILING LISTS:
https://www.spinics.net/lists/linux-usb/msg168719.html
https://www.spinics.net/lists/linux-input/msg56210.html
https://www.spinics.net/lists/linux-usb/msg173012.html
https://www.spinics.net/lists/linux-input/msg58221.html
There is a workaround (I still didn't tried) but it needs to compile an
specific driver.
https://github.com/y-trudeau/linux_lenovo_ultraslim_plus
There is already a kernel report about this.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-generic 4.15.0.20.23
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:
USERPID ACCESS COMMAND
/dev/snd/controlC0: julian 1342 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue May 15 15:53:41 2018
InstallationDate: Installed on 2018-05-14 (1 days ago)
InstallationMedia: Ubuntu
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Excelent! Thanks You... -- Cristian Aravena Romero (caravena) -- 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Hey Cristian, after today updates login works again - thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent 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: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1797802] Re: Erratic behavior of intel pstate CPU frequency control
Aaaah, I can see plenty of this in syslog: Oct 14 22:30:59 p5520 kernel: [ 9481.033687] CPU3: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033688] CPU7: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033718] CPU1: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033719] CPU5: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033720] CPU0: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033720] CPU4: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033722] CPU6: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.033722] CPU2: Package temperature above threshold, cpu clock throttled (total events = 5845) Oct 14 22:30:59 p5520 kernel: [ 9481.034709] CPU3: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034710] CPU0: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034711] CPU4: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034711] CPU7: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034738] CPU2: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034738] CPU6: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034739] CPU1: Package temperature/speed normal Oct 14 22:30:59 p5520 kernel: [ 9481.034740] CPU5: Package temperature/speed normal So maybe it THINKS it overheats (although it does NOT) and throttles down... -- 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/1797802 Title: Erratic behavior of intel pstate CPU frequency control Status in linux package in Ubuntu: Incomplete Bug description: I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The other times everything works fine. I don't know what triggers this weird state. Suspend / resume? Maybe. At first I thought this was maybe just a "perception issue", but then when the sluggishness happened again, I fired up i7z and it looks that CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly capable of going up to 4000 MHz! I tried to fix it by setting echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct I hoped I would force the CPU into almost max performance state this way. And indeed, once I ran these commands, i7z showed steady 3100+ MHz on all cores. Then something weird happened - when I run some mild load on the CPU, like just starting the IDE, during the startup the frequency ** dropped back to about 800-1600 MHz ** and returned to 3100 MHz after the load was gone (IDE loaded). The CPU core temperatures shown by sensors / i7z are ok and typically at about 40-50 C when this slowdown happens, so this doesn't look like thermal throttling. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pkolaczk 3281 F pulseaudio /dev/snd/pcmC0D0c: pkolaczk 3281 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 22:16:50 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=4836842e-0116-43c4-98b4-7a56427f81f1 InstallationDate: Installed on 2017-04-12 (549 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7f76b1f0-8fef-41cc-86a2-99e554cb4d40 ro acpi_rev_override quiet splash iwlwifi.power_save=1 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: Dell Inc.
[Kernel-packages] [Bug 1797802] Re: Erratic behavior of intel pstate CPU frequency control
BTW, when the system is in this weird state, CPU fans are running at the lowest speed (but running) and never go to their max speed, even under heavy CPU load like compiling stuff. Is there a hidden energy saving thing that tries to keep my CPU clock low / voltages low at high load? -- 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/1797802 Title: Erratic behavior of intel pstate CPU frequency control Status in linux package in Ubuntu: Incomplete Bug description: I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The other times everything works fine. I don't know what triggers this weird state. Suspend / resume? Maybe. At first I thought this was maybe just a "perception issue", but then when the sluggishness happened again, I fired up i7z and it looks that CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly capable of going up to 4000 MHz! I tried to fix it by setting echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct I hoped I would force the CPU into almost max performance state this way. And indeed, once I ran these commands, i7z showed steady 3100+ MHz on all cores. Then something weird happened - when I run some mild load on the CPU, like just starting the IDE, during the startup the frequency ** dropped back to about 800-1600 MHz ** and returned to 3100 MHz after the load was gone (IDE loaded). The CPU core temperatures shown by sensors / i7z are ok and typically at about 40-50 C when this slowdown happens, so this doesn't look like thermal throttling. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pkolaczk 3281 F pulseaudio /dev/snd/pcmC0D0c: pkolaczk 3281 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 22:16:50 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=4836842e-0116-43c4-98b4-7a56427f81f1 InstallationDate: Installed on 2017-04-12 (549 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7f76b1f0-8fef-41cc-86a2-99e554cb4d40 ro acpi_rev_override quiet splash iwlwifi.power_save=1 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797802/+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 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu
My Asus FX504 laptop is also affected by the issue, I'm on Ubuntu 18.04.1 (kernel 4.15), tried kernel 4.18, nothing changes, still doesn't work -- 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/1781879 Title: Latest ASUS trackpad doesn't work in Ubuntu Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput Virtual core pointer id=2[master pointer (3)] ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ↳ Logitech USB Receiver id=12 [slave pointer (2)] ↳ Logitech USB Receiver id=13 [slave pointer (2)] Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1781879/+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 1797802] Re: Erratic behavior of intel pstate CPU frequency control
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797802 Title: Erratic behavior of intel pstate CPU frequency control Status in linux package in Ubuntu: Incomplete Bug description: I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The other times everything works fine. I don't know what triggers this weird state. Suspend / resume? Maybe. At first I thought this was maybe just a "perception issue", but then when the sluggishness happened again, I fired up i7z and it looks that CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly capable of going up to 4000 MHz! I tried to fix it by setting echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct I hoped I would force the CPU into almost max performance state this way. And indeed, once I ran these commands, i7z showed steady 3100+ MHz on all cores. Then something weird happened - when I run some mild load on the CPU, like just starting the IDE, during the startup the frequency ** dropped back to about 800-1600 MHz ** and returned to 3100 MHz after the load was gone (IDE loaded). The CPU core temperatures shown by sensors / i7z are ok and typically at about 40-50 C when this slowdown happens, so this doesn't look like thermal throttling. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pkolaczk 3281 F pulseaudio /dev/snd/pcmC0D0c: pkolaczk 3281 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 22:16:50 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=4836842e-0116-43c4-98b4-7a56427f81f1 InstallationDate: Installed on 2017-04-12 (549 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7f76b1f0-8fef-41cc-86a2-99e554cb4d40 ro acpi_rev_override quiet splash iwlwifi.power_save=1 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797802/+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 1797802] [NEW] Erratic behavior of intel pstate CPU frequency control
Public bug reported: I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The other times everything works fine. I don't know what triggers this weird state. Suspend / resume? Maybe. At first I thought this was maybe just a "perception issue", but then when the sluggishness happened again, I fired up i7z and it looks that CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly capable of going up to 4000 MHz! I tried to fix it by setting echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct I hoped I would force the CPU into almost max performance state this way. And indeed, once I ran these commands, i7z showed steady 3100+ MHz on all cores. Then something weird happened - when I run some mild load on the CPU, like just starting the IDE, during the startup the frequency ** dropped back to about 800-1600 MHz ** and returned to 3100 MHz after the load was gone (IDE loaded). The CPU core temperatures shown by sensors / i7z are ok and typically at about 40-50 C when this slowdown happens, so this doesn't look like thermal throttling. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pkolaczk 3281 F pulseaudio /dev/snd/pcmC0D0c: pkolaczk 3281 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 22:16:50 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=4836842e-0116-43c4-98b4-7a56427f81f1 InstallationDate: Installed on 2017-04-12 (549 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7f76b1f0-8fef-41cc-86a2-99e554cb4d40 ro acpi_rev_override quiet splash iwlwifi.power_save=1 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug cosmic -- 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/1797802 Title: Erratic behavior of intel pstate CPU frequency control Status in linux package in Ubuntu: Incomplete Bug description: I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The other times everything works fine. I don't know what triggers this weird state. Suspend / resume? Maybe. At first I thought this was maybe just a "perception issue", but then when the sluggishness happened again, I fired up i7z and it looks that CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly capable of going up to 4000 MHz! I tried to fix it by setting echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct I hoped I would force the CPU into almost max performance state this way. And indeed, once I ran these commands, i7z showed steady 3100+ MHz on all cores. Then something weird happened - when I run some mild load on the CPU, like just starting the IDE, during the startup the frequency ** dropped back to about 800-1600 MHz ** and returned to 3100 MHz after the load was gone (IDE loaded). The CPU core temperatures shown by sensors / i7z are ok and typically at about 40-50 C when this slowdown happens, so this doesn't look like thermal throttling. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64
[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu
** Description changed: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput - Virtual core pointer id=2[master pointer (3)] -↳ Virtual core XTEST pointerid=4[slave pointer (2)] -↳ Logitech USB Receiver id=12 [slave pointer (2)] -↳ Logitech USB Receiver id=13 [slave pointer (2)] - Virtual core keyboard id=3[master keyboard (2)] - ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] - ↳ Power Button id=6[slave keyboard (3)] - ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] - ↳ Video Bus id=8[slave keyboard (3)] - ↳ Video Bus id=9[slave keyboard (3)] - ↳ Power Button id=10 [slave keyboard (3)] - ↳ Sleep Button id=11 [slave keyboard (3)] - ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] - ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] - ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] - ↳ Logitech USB Receiver id=17 [slave keyboard (3)] + Virtual core pointer id=2[master pointer (3)] + ↳ Virtual core XTEST pointerid=4[slave pointer (2)] + ↳ Logitech USB Receiver id=12 [slave pointer (2)] + ↳ Logitech USB Receiver id=13 [slave pointer (2)] + Virtual core keyboard id=3[master keyboard (2)] + ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] + ↳ Power Button id=6[slave keyboard (3)] + ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] + ↳ Video Bus id=8[slave keyboard (3)] + ↳ Video Bus id=9[slave keyboard (3)] + ↳ Power Button id=10 [slave keyboard (3)] + ↳ Sleep Button id=11 [slave keyboard (3)] + ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] + ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] + ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] + ↳ Logitech USB Receiver id=17 [slave keyboard (3)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781879 Title: Latest ASUS trackpad doesn't work in Ubuntu Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput Virtual core pointer id=2[master pointer (3)] ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ↳ Logitech USB Receiver id=12 [slave pointer (2)] ↳ Logitech USB Receiver id=13 [slave pointer (2)] Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] To manage notifications about this bug go to:
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
still happens on kernel 4.18.14 :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1718982] Re: usb usb4-port2: cannot disable (err = -32)
[ 292.710506] ACPI: Waking up from system sleep state S3 [ 292.731182] ACPI: EC: interrupt unblocked [ 292.777370] ACPI: EC: event unblocked [ 292.778140] sd 0:0:0:0: [sda] Starting disk [ 292.781554] usb 2-3: Disable of device-initiated U1 failed. [ 292.785014] usb 2-3: Disable of device-initiated U2 failed. [ 292.986598] r8169 :03:00.0 enp3s0: link down [ 293.094283] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 293.161923] atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly. [ 293.543162] xhci_hcd :00:14.0: Cannot set link state. [ 293.543261] usb usb2-port3: cannot disable (err = -32) [ 293.543278] xhci_hcd :00:14.0: Cannot set link state. [ 293.543387] usb usb2-port3: cannot disable (err = -32) [ 293.543399] xhci_hcd :00:14.0: Cannot set link state. [ 293.543498] usb usb2-port3: cannot disable (err = -32) [ 293.671027] usb 1-7: reset full-speed USB device number 4 using xhci_hcd [ 293.947196] usb 1-6: reset high-speed USB device number 3 using xhci_hcd [ 294.223368] usb 1-8: reset full-speed USB device number 5 using xhci_hcd [ 294.377015] OOM killer enabled. [ 294.377017] Restarting tasks ... [ 294.377125] usb 2-3: USB disconnect, device number 3 [ 294.386915] rfkill: input handler enabled [ 294.400895] done. [ 294.441833] PM: suspend exit [ 294.445291] rfkill: input handler disabled [ 294.659146] usb 2-3: new SuperSpeed USB device number 4 using xhci_hcd [ 294.679778] usb 2-3: New USB device found, idVendor=8086, idProduct=0a66 [ 294.679781] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 294.679783] usb 2-3: Product: Intel(R) RealSense(TM) 3D Camera (Front F200) [ 294.679784] usb 2-3: Manufacturer: Intel(R) RealSense(TM) 3D Camera (Front F200) [ 294.679786] usb 2-3: SerialNumber: 045150391502 [ 294.680803] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) 3D Camera (Front F200) (8086:0a66) [ 294.681819] uvcvideo 2-3:1.0: Entity type for entity Processing 2 was not initialized! [ 294.681821] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized! [ 294.681823] uvcvideo 2-3:1.0: Entity type for entity Extension 3 was not initialized! [ 294.681897] input: Intel(R) RealSense(TM) 3D Camer as /devices/pci:00/:00:14.0/usb2/2-3/2-3:1.0/input/input34 [ 294.682188] uvcvideo: Unknown video format 52564e49-2d90-4a58-920b-773f1f2c556b [ 294.682190] uvcvideo: Unknown video format 49524e49-2d90-4a58-920b-773f1f2c556b [ 294.682192] uvcvideo: Unknown video format 494c4552-1314-f943-a75a-ee6bbf012e23 [ 294.682286] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) 3D Camera (Front F200) (8086:0a66) [ 294.683287] uvcvideo: Unable to create debugfs 2-4 directory. [ 294.683335] uvcvideo 2-3:1.2: Entity type for entity INV_EU_STRING was not initialized! [ 294.683337] uvcvideo 2-3:1.2: Entity type for entity Camera 5 was not initialized! [ 294.683396] input: Intel(R) RealSense(TM) 3D Camer as /devices/pci:00/:00:14.0/usb2/2-3/2-3:1.2/input/input35 -- 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/1718982 Title: usb usb4-port2: cannot disable (err = -32) Status in linux package in Ubuntu: Expired Bug description: Hello, dmesg: [ 7294.705364] usb usb4-port2: cannot disable (err = -32) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-generic 4.13.0-11.12 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: caravena 1773 F...m pulseaudio /dev/snd/controlC1: caravena 1773 F pulseaudio /dev/snd/controlC0: caravena 1773 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 22 14:13:45 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (78 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-11-generic N/A linux-backports-modules-4.13.0-11-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Oummm... @NiBu, You still have problems after the updates? Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent 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: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Hello Alexey, Thanks! I close this report for your information delivered. Best Regards, -- Cristian Aravena Romero (caravena) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent 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: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1718982] Re: usb usb4-port2: cannot disable (err = -32)
I have the same error after a ubuntu upgrade from 16 LTS to 18 LTS. However only the upgraded partition has the problema, booting from a pen drive with 18 LTS everything works fine, checking a hipotiposes of home / etc dirty. -- 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/1718982 Title: usb usb4-port2: cannot disable (err = -32) Status in linux package in Ubuntu: Expired Bug description: Hello, dmesg: [ 7294.705364] usb usb4-port2: cannot disable (err = -32) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-generic 4.13.0-11.12 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: caravena 1773 F...m pulseaudio /dev/snd/controlC1: caravena 1773 F pulseaudio /dev/snd/controlC0: caravena 1773 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 22 14:13:45 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (78 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-11-generic N/A linux-backports-modules-4.13.0-11-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718982/+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 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Something in the updates made it work for me. On the latest series of updates I've noticed kernel update to 4.18.0.9.10 and gave it a try. I still observe in dmesg diagnostics dump about "Bad or missing usercopy whitelist? Kernel memory exposure attempt..." but I am able to start session with nvidia driver up and running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent 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: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+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 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
I've seen similar things recently, and seems like increase the delay after reset can alleviate the issue. Can you try something like 100ms or 200ms instead of (10 + 40)ms in [1]? [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/core/hub.c#n2889 -- 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/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate:
[Kernel-packages] [Bug 1774359] Re: could not find module by name='off'
Same problem with nvidia 410 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1774359 Title: could not find module by name='off' Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When I try to load the nvidia module it doesn't load. $ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off' modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg) $ sudo prime-select query intel $ sudo prime-offload $ cat /var/log/prime-supported.log Requires offloading $ cat /var/log/prime-offload.log Sorry the nvidia kernel module is not is loaded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 09:42:42 2018 Dependencies: InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+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 1773697] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200874/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1773697] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200880/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version:
[Kernel-packages] [Bug 1773697] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200873/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1773697] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200879/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200878/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200876/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1773697] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200877/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version:
[Kernel-packages] [Bug 1773697] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200875/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1773697] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200872/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200871/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200870/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200869/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1773697] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200868/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not Available
[Kernel-packages] [Bug 1773697] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1773697/+attachment/5200867/+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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
Journalctl output after attaching USB device on Thinkpad X220 upgraded to cosmic ... Okt 14 17:46:10 ThinkPad-X220 kernel: usb 1-1.2: new full-speed USB device number 4 using ehci-pci Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: New USB device found, idVendor=19b5, idProduct=0021, bcdDevice=25.20 Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: Product: PX USB Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: Manufacturer: Bowers & Wilkins Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: SerialNumber: ABCDEF0123456789 Okt 14 17:46:11 ThinkPad-X220 mtp-probe[13033]: checking bus 1, device 4: "/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2" Okt 14 17:46:11 ThinkPad-X220 mtp-probe[13033]: bus: 1, device: 4 was not an MTP device Okt 14 17:46:11 ThinkPad-X220 kernel: usbcore: registered new interface driver snd-usb-audio Okt 14 17:46:11 ThinkPad-X220 kernel: input: Bowers & Wilkins PX USB Consumer Control as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input16 Okt 14 17:46:11 ThinkPad-X220 kernel: input: Bowers & Wilkins PX USB as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input17 Okt 14 17:46:11 ThinkPad-X220 kernel: hid-generic 0003:19B5:0021.0001: input,hiddev2,hidraw0: USB HID v1.11 Device [Bowers & Wilkins PX USB] on usb-:00:1a.0-1.2/input2 Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) config/udev: Adding input device Bowers & Wilkins PX USB Consumer Control (/dev/input/event15) Okt 14 17:46:11 ThinkPad-X220 systemd-udevd[13036]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Bowers & Wilkins PX USB Consumer Control: Applying InputClass "libinput keyboard catchall" Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) Using input driver 'libinput' for 'Bowers & Wilkins PX USB Consumer Control' Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) systemd-logind: got fd for /dev/input/event15 13:79 fd 46 paused 0 Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Bowers & Wilkins PX USB Consumer Control: always reports core events Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option "Device" "/dev/input/event15" Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option "_source" "server/udev" Okt 14 17:46:11 ThinkPad-X220 pulseaudio[3423]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Okt 14 17:46:11 ThinkPad-X220 pulseaudio[3423]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-Bowers___Wilkins_PX_USB_ABCDEF0123456789-00" card_name="alsa_card.usb-Bowers___Wilkins_PX_USB_ABCDEF0123456789-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - Bowers & Wilkins PX USB Consumer Control: is tagged by udev as: Keyboard Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - Bowers & Wilkins PX USB Consumer Control: device is a keyboard Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - Bowers & Wilkins PX USB Consumer Control: device removed Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input16/event15" Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) XINPUT: Adding extended input device "Bowers & Wilkins PX USB Consumer Control" (type: KEYBOARD, id 13) Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option "xkb_model" "pc105" Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option "xkb_layout" "de" Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (WW) Option "xkb_variant" requires a string value Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (WW) Option "xkb_options" requires a string value Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - Bowers & Wilkins PX USB Consumer Control: is tagged by udev as: Keyboard Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - Bowers & Wilkins PX USB Consumer Control: device is a keyboard Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) config/udev: Adding input device Bowers & Wilkins PX USB (/dev/input/event16) Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) No input driver specified, ignoring this device. Okt 14 17:46:11 ThinkPad-X220
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop".
Unloading or blacklisting the module solves the issue but disables other
platform ACPI interfaces:
$ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
- model uses hot-keys Fn + F7) and need to use a DMI match to disable the
- rfkill logic.
+ model uses hot-keys Fn + F7 for 'Airplane mode') and need to use a DMI
+ match to disable the rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
@@ -1239,6 +1246,7 @@
int cfg;
struct ideapad_private *priv;
struct acpi_device *adev;
+ const char *dmi_vendor, *dmi_version;
ret = acpi_bus_get_device(ACPI_HANDLE(>dev), );
if (ret)
@@ -1257,6 +1265,10 @@
priv->platform_device = pdev;
[Kernel-packages] [Bug 1773697] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1773697 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773697/+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 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
** Also affects: linux (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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 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:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773697/+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 1796576] Re: rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic
Hello, sorry for the delay, I've tested kernel 4.15.0-38-generic, but the problem is not solved. Wifi seems, connect, but I cannot ping my domestic router...it seems that there are some problem sending packet on the Wifi connection, rather than establishing the connection with the Wifi router... Is there any other test I can perform? eno1: flags=4099 mtu 1500 ether c8:d3:ff:dd:dd:31 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Loopback locale) RX packets 799 bytes 49878 (49.8 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 799 bytes 49878 (49.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Dhclient is not working...I've set a static ip, but interface is not working... wlo1: flags=4163 mtu 1500 inet 192.168.0.110 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::1383:e55e:d490:37a7 prefixlen 64 scopeid 0x20 ether 58:00:e3:ae:66:3b txqueuelen 1000 (Ethernet) RX packets 7 bytes 610 (610.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 71 bytes 12872 (12.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlo1 IEEE 802.11 ESSID:"Linux" Mode:Managed Frequency:2.462 GHz Access Point: DC:EF:09:51:23:49 Bit Rate=150 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr=2347 B Fragment thr:off Power Management:on Link Quality=46/70 Signal level=-64 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:24 Missed beacon:0 Regards, Alessio ** Attachment added: "New dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796576/+attachment/5200858/+files/dmesg_4.15.38-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/1796576 Title: rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic Status in linux package in Ubuntu: Incomplete Bug description: Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect anymore to wifi network. The problem occurs also with linux-image-4.15.0-34-generic. Kernel version linux-headers-4.15.0-32-generic is working fine. My current configuration for rtl8723be is /etc/modprobe.d/rtlbtcoex.conf: options rtl8723be ant_sel=2 ips=0 I'm using these parameters with for rtl8723be module in order to get the correct gain for Wifi antenna. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alessio1778 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:16:55 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f InstallationDate: Installed on 2017-02-20 (593 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook 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-34-generic root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago) dmi.bios.date: 12/12/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion:
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
- disabled by the platform driver "ideapad-laptop". Unloading or
- blacklisting the module solves the issue but disables other platform
- ACPI interfaces.
+ disabled by the platform driver "ideapad-laptop".
+
+ Unloading or blacklisting the module solves the issue but disables other
+ platform ACPI interfaces:
+
+ $ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7) and need to use a DMI match to disable the
rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
-
0: ideapad_wlan: Wireless LAN
- Soft blocked: no
- Hard blocked: yes
+ Soft blocked: no
+ Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
- Soft blocked: yes
- Hard blocked: yes
+ Soft blocked: yes
+ Hard blocked: yes
3: phy0: Wireless LAN
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
4: hci0: Bluetooth
- Soft blocked: yes
- Hard blocked: no
+ Soft blocked: yes
+ Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
@@ -1239,6 +1246,7 @@
int cfg;
struct ideapad_private *priv;
[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot
Good afternoon. I faced a similar issue today and installed the suggested -35 kernel. Tt did not fix the issue for me however it seems to be an EFI related issue: 1. the grub was always empty (could get grub console from a USB install) 2. the grub console (or menu) was not available without the USB thumb (had to add manually some instructions on /etc/default/grub file to make this visible) 3. it does not seems to be a nomodeset issue as putting it on the boot options made then the graphic card stuck to 1024*780 and removing nomodeset option "fixed" the graphic card behavior The only two other options I tweaked were 1. disabling secure boot (but here again, I doubt this is the cause) 2. switch EFI from "windows EFI" to "other OS" on the UEFI BIOS settings (naming may be a little different as I am not on the BIOS status screen of this computer right now) Hope this helps. -- 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/1792134 Title: Upgrading to 4.15.0-33 caused the system to fail to boot Status in linux package in Ubuntu: Incomplete Bug description: A routine upgrade upgraded the kernel to 4.15.0-34 upon which the machine would not boot and instead booted to initramfs. Attempts to boot into recovery mode resulted in the error "Warning failed to connect to lvmetad. Falling back to device scanning." Reverting to 4.15.0-33 allowed me to boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: connor 4127 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 12:30:06 2018 HibernationDevice: RESUME=UUID=af5bdbd9-e688-4d55-a263-0d649f9b59d4 InstallationDate: Installed on 2018-07-23 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HNS1KE00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET52W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HNS1KE00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET52W(1.30):bd03/20/2018:svnLENOVO:pn20HNS1KE00:pvrThinkPadX270:rvnLENOVO:rn20HNS1KE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HNS1KE00 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792134/+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 1797772] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1797772
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1797772
Title:
ideapad_laptop disables WiFi/BT radios on Lenovo Y530
Status in linux package in Ubuntu:
Incomplete
Bug description:
I've been working with a user that has a Lenovo Legion Y530-15ICH
where booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios
being disabled by the platform driver "ideapad-laptop". Unloading or
blacklisting the module solves the issue but disables other platform
ACPI interfaces.
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7) and need to use a DMI match to disable
the rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control
flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+
[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530
** Description changed:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop". Unloading or
blacklisting the module solves the issue but disables other platform
ACPI interfaces.
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
- Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak]
[8086:0034]
- Kernel driver in use: iwlwifi
+ Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
+ Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7) and need to use a DMI match to disable the
rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
- Manufacturer: LENOVO
- Product Name: 81FV
- Version: Lenovo Legion Y530-15ICH
- Serial Number: PF18CD10
- UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
- Wake-up Type: Power Switch
- SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
- Family: Legion Y530-15ICH
+ Manufacturer: LENOVO
+ Product Name: 81FV
+ Version: Lenovo Legion Y530-15ICH
+ Serial Number: PF18CD10
+ UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
+ Wake-up Type: Power Switch
+ SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
+ Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
- {
- .ident = "Lenovo Legion Y530-15ICH",
- .matches = {
- DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
- DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
- },
- },
+ {
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
+ },
+ },
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
+
+
+ 0: ideapad_wlan: Wireless LAN
+ Soft blocked: no
+ Hard blocked: yes
+ 1: ideapad_bluetooth: Bluetooth
+ Soft blocked: yes
+ Hard blocked: yes
+ 3: phy0: Wireless LAN
+ Soft blocked: no
+ Hard blocked: no
+ 4: hci0: Bluetooth
+ Soft blocked: yes
+ Hard blocked: no
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control flag:
diff -u
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
- },
- },
- {
+ },
+ },
+ {
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION,
[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
** Changed in: gdm3 (Ubuntu) Status: Won't Fix => Incomplete ** Changed in: gdm3 (Ubuntu Cosmic) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Incomplete Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Incomplete Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Confirmed Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty. Switching to another tty then back also starts gdm. It happens on bare metal and VM. Originally, when this issue happened there was a plymouth crash reported in bug 1794292 but this issue is still happening without the plymouth crash. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: 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 -- kernel-master-bug: 1796346 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-phase:Released + kernel-phase-changed:Sunday, 14. October 2018 13:35 UTC ** Description changed: 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 -- kernel-master-bug: 1796346 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-phase:Released - kernel-phase-changed:Sunday, 14. October 2018 13:35 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1796353 Title: linux-kvm: 4.18.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Cosmic: Fix Released 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 -- kernel-master-bug: 1796346 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796353/+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 1797772] [NEW] ideapad_laptop disables WiFi/BT radios on Lenovo Y530
Public bug reported:
I've been working with a user that has a Lenovo Legion Y530-15ICH where
booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios being
disabled by the platform driver "ideapad-laptop". Unloading or
blacklisting the module solves the issue but disables other platform
ACPI interfaces.
The system has the most recent firmware:
[0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018
The wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560
[Jefferson Peak] [8086:a370] (rev 10)
Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak]
[8086:0034]
Kernel driver in use: iwlwifi
We investigated the issue extensively and built the module with
additional logic without solving the issue. It is well-known that some
Lenovo models do not have a separate hardware radio kill switch (this
model uses hot-keys Fn + F7) and need to use a DMI match to disable the
rfkill logic.
We used dmidecode to get the correct Version string:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 81FV
Version: Lenovo Legion Y530-15ICH
Serial Number: PF18CD10
UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
Family: Legion Y530-15ICH
and added it to no_hw_rfkill_list[]:
{
.ident = "Lenovo Legion Y530-15ICH",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
},
},
However, rfkill was still listing the platform devices "ideapad_wlan"
and "ideapad_bluetooth":
/sys/class/rfkill/rfkill0/hard=1
/sys/class/rfkill/rfkill0/index=0
/sys/class/rfkill/rfkill0/name=ideapad_wlan
/sys/class/rfkill/rfkill0/persistent=1
/sys/class/rfkill/rfkill0/soft=0
/sys/class/rfkill/rfkill0/state=2
/sys/class/rfkill/rfkill0/type=wlan
/sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan
RFKILL_STATE=2
/sys/class/rfkill/rfkill1/hard=1
/sys/class/rfkill/rfkill1/index=1
/sys/class/rfkill/rfkill1/name=ideapad_bluetooth
/sys/class/rfkill/rfkill1/persistent=1
/sys/class/rfkill/rfkill1/soft=1
/sys/class/rfkill/rfkill1/state=2
/sys/class/rfkill/rfkill1/type=bluetooth
/sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth
RFKILL_TYPE=bluetooth RFKILL_STATE=2
/sys/class/rfkill/rfkill3/hard=0
/sys/class/rfkill/rfkill3/index=3
/sys/class/rfkill/rfkill3/name=phy0
/sys/class/rfkill/rfkill3/persistent=0
/sys/class/rfkill/rfkill3/soft=0
/sys/class/rfkill/rfkill3/state=1
/sys/class/rfkill/rfkill3/type=wlan
/sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan
RFKILL_STATE=1
/sys/class/rfkill/rfkill4/hard=0
/sys/class/rfkill/rfkill4/index=4
/sys/class/rfkill/rfkill4/name=hci0
/sys/class/rfkill/rfkill4/persistent=0
/sys/class/rfkill/rfkill4/soft=1
/sys/class/rfkill/rfkill4/state=0
/sys/class/rfkill/rfkill4/type=bluetooth
/sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth
RFKILL_STATE=0
We then added printk(KERN_NOTICE ... in the module's
platform_driver.probe function ideapad_acpi_add() both at entry and
later to report the DMI and status of the hardware switch control flag:
diff -u /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
./ideapad-laptop.c
--- /home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c
2018-10-14 01:46:49.506088219 +0100
+++ ./ideapad-laptop.c 2018-10-14 06:19:48.843813865 +0100
@@ -1147,6 +1147,13 @@
},
},
{
+ .ident = "Lenovo Legion Y530-15ICH",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion
Y530-15ICH"),
+ },
+ },
+ {
.ident = "Lenovo Legion Y720-15IKB",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
@@ -1239,6 +1246,7 @@
int cfg;
struct ideapad_private *priv;
struct acpi_device *adev;
+ const char *dmi_vendor, *dmi_version;
ret = acpi_bus_get_device(ACPI_HANDLE(>dev), );
if (ret)
@@ -1257,6 +1265,10 @@
priv->platform_device = pdev;
priv->has_hw_rfkill_switch = !dmi_check_system(no_hw_rfkill_list);
+ dmi_vendor = dmi_get_system_info(DMI_SYS_VENDOR);
+ dmi_version = dmi_get_system_info(DMI_PRODUCT_VERSION);
+ printk(KERN_NOTICE "DMI: %s, %s. has_hw_rfkill_switch=%d\n",
dmi_vendor, dmi_version, priv->has_hw_rfkill_switch);
+
ret = ideapad_sysfs_init(priv);
if (ret)
return ret;
And this revealed that the function is not being called - the
KERN_NOTICE messages do not appear in 'dmesg' output.
This suggests:
static const struct acpi_device_id ideapad_device_ids[] = {
{ "VPC2004", 0},
is not being matched
[Kernel-packages] [Bug 1793976] Re: kvm kernel missing nbd module
This bug was fixed in the package linux-kvm - 4.18.0-1003.3
---
linux-kvm (4.18.0-1003.3) cosmic; urgency=medium
* linux-kvm: 4.18.0-1003.3 -proposed tracker (LP: #1796353)
* kvm kernel missing nbd module (LP: #1793976)
- kvm: [Config] enable BLK_DEV_NBD
[ Ubuntu: 4.18.0-9.10 ]
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an
[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker
This bug was fixed in the package linux-kvm - 4.18.0-1003.3
---
linux-kvm (4.18.0-1003.3) cosmic; urgency=medium
* linux-kvm: 4.18.0-1003.3 -proposed tracker (LP: #1796353)
* kvm kernel missing nbd module (LP: #1793976)
- kvm: [Config] enable BLK_DEV_NBD
[ Ubuntu: 4.18.0-9.10 ]
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
- iio: adc: ina2xx: avoid kthread_stop() with stale task_struct
- tsl2550: fix lux1_input error in low light
- misc: ibmvmc: Use GFP_ATOMIC under spin lock
- vmci: type promotion bug in qp_host_get_user_memory()
- siox: don't create a thread without starting it
- x86/numa_emulation: Fix emulated-to-physical node mapping
- staging: rts5208: fix missing error check on call to rtsx_write_register
- power: supply: axp288_charger: Fix initial constant_charge_current value
- misc: sram: enable clock before registering regions
- serial: sh-sci: Stop RX FIFO timer during port shutdown
- uwb: hwa-rc: fix memory leak at probe
- power: vexpress: fix corruption in notifier registration
- iommu/amd: make sure TLB to be flushed before IOVA freed
- Bluetooth: Add a new Realtek 8723DE ID 0bda:b009
- USB: serial: kobil_sct: fix modem-status error handling
- 6lowpan: iphc: reset mac_header after decompress to fix panic
- iommu/msm: Don't call iommu_device_{,un}link from atomic context
- s390/mm: correct allocate_pgste proc_handler callback
- power: remove possible deadlock when unregistering power_supply
- drm/amd/display/dc/dce: Fix multiple potential integer overflows
- drm/amd/display: fix use of uninitialized memory
- md-cluster: clear another node's suspend_area after the copy is finished
- cxgb4: Fix the condition to check if the card is T5
- RDMA/bnxt_re: Fix a couple off by one bugs
- RDMA/i40w: Hold read semaphore while looking after VMA
- RDMA/bnxt_re: Fix a bunch of off by one bugs in qplib_fp.c
- IB/core: type promotion bug in rdma_rw_init_one_mr()
- media: exynos4-is: Prevent NULL pointer dereference in
__isp_video_try_fmt()
- IB/mlx4: Test port number before querying type.
- powerpc/kdump: Handle crashkernel memory reservation failure
- media: fsl-viu: fix error handling in viu_of_probe()
- vhost_net: Avoid tx vring kicks during busyloop
- media: staging/imx: fill vb2_v4l2_buffer field entry
- IB/mlx5: Fix GRE flow specification
- include/rdma/opa_addr.h: Fix an endianness issue
- x86/tsc: Add missing header to tsc_msr.c
- ARM: hwmod: RTC: Don't assume lock/unlock will be called with irq enabled
- x86/entry/64: Add two more instruction suffixes
- ARM: dts: ls1021a: Add missing cooling device properties for CPUs
- scsi: target/iscsi: Make iscsit_ta_authentication() respect the output
buffer size
- thermal: i.MX: Allow thermal probe to fail gracefully in case of bad
calibration.
- scsi: klist: Make it safe to use klists in atomic context
- scsi: ibmvscsi: Improve strings handling
- scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion
- usb: wusbcore: security: cast sizeof to int for comparison
- ath10k: sdio: use same endpoint id for all packets in a bundle
- ath10k: sdio: set skb len for all rx packets
- powerpc/powernv/ioda2: Reduce upper limit for DMA window size
- platform/x86: asus-wireless: Fix uninitialized symbol usage
- ACPI / button: increment wakeup count only when notified
- s390/sysinfo: add missing #ifdef CONFIG_PROC_FS
- alarmtimer: Prevent overflow for relative nanosleep
- s390/dasd: correct numa_node in dasd_alloc_queue
- s390/scm_blk: correct numa_node in scm_blk_dev_setup
- s390/extmem: fix gcc 8 stringop-overflow warning
- mtd: rawnand: atmel: add module param to avoid using dma
- iio: accel: adxl345: convert address field usage in iio_chan_spec
- posix-timers: Make forward callback return s64
- posix-timers: Sanitize overrun handling
- ALSA: snd-aoa: add of_node_put() in error path
- selftests: forwarding: Tweak tc filters for mirror-to-gretap tests
- ath10k: use locked skb_dequeue for rx completions
- media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power
- media: soc_camera: ov772x: correct setting of banding filter
- media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data
- media: ov772x: add checks for register read errors
- staging: android: ashmem: Fix mmap size validation
- media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING
- staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path
- drivers/tty: add error handling for pcmcia_loop_config
- arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses
- serial: pxa: Fix an
[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1796353 Title: linux-kvm: 4.18.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: 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 -- kernel-master-bug: 1796346 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/1796353/+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 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1796353 Title: linux-kvm: 4.18.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: 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 -- kernel-master-bug: 1796346 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/1796353/+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 1774359] Re: could not find module by name='off'
Fixed it by commenting lines in 159-161 in /usr/bin/prime-select: #alias nvidia off #alias nvidia-drm off #alias nvidia-modeset off''' Also, comment lines 3-4 in /lib/modprobe.d/nvidia-graphics-drivers.conf #alias nouveau off #alias lbm-nouveau off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1774359 Title: could not find module by name='off' Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When I try to load the nvidia module it doesn't load. $ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off' modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg) $ sudo prime-select query intel $ sudo prime-offload $ cat /var/log/prime-supported.log Requires offloading $ cat /var/log/prime-offload.log Sorry the nvidia kernel module is not is loaded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 09:42:42 2018 Dependencies: InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+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 1774359] Re: could not find module by name='off'
Ubuntu 18.04 on Asus Zenbook Pro UX901V, GeForce GTX 960M, both nvidia 390 and 396. Commenting the alias lines didn't work for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1774359 Title: could not find module by name='off' Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When I try to load the nvidia module it doesn't load. $ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off' modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg) $ sudo prime-select query intel $ sudo prime-offload $ cat /var/log/prime-supported.log Requires offloading $ cat /var/log/prime-offload.log Sorry the nvidia kernel module is not is loaded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 09:42:42 2018 Dependencies: InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hello, I've tried briefly this kernel: https://people.canonical.com/~khfeng/lp1728244-testing/ on the Chuwi Lapbook Air using the current Ubuntu 18.10 (not officially released yet). Touchpad was working, no right button, but I didn't know about the GnomeTweak hack mentioned above. @urmanbm use this kernel. @kaihengfeng Is there a chance for your patches to be included in the official 18.10 kernel? It would help a lot.. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1797198] Re: [nvidia] After login the screen goes black
This bug was fixed in the http://cdimage.ubuntu.com/daily- live/20181013.1/cosmic-desktop-amd64.iso -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login the screen goes black Status in gdm3 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: When I boot Cosmic, grub is working OK and login screen is presented OK, but after login the screen goes black. When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia driver 390 is used. These bugs my be related https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192 See attachment for syslog info. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 20:12:32 2018 InstallationDate: Installed on 2018-10-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797198/+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 887793] Re: [HP 6710b] Kworker constantly taking about 100% CPU
It is not still open, it is marked as invalid.
--
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/887793
Title:
[HP 6710b] Kworker constantly taking about 100% CPU
Status in linux package in Ubuntu:
Invalid
Bug description:
I've this issue since the latest Ubuntu 11.10 version, all updates
applied till today, and it's still there. Ubuntu 11.04 did not have
this issue.
If I run top there is a Kworker constantly taking much CPU, I don't
know how to research where this comes from.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kp 1473 F pulseaudio
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4404000 irq 46'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,103c30c0,00100200
HDA:11c11040,103c1378,00100200'
Controls : 11
Simple ctrls : 9
Date: Tue Nov 8 22:29:10 2011
HibernationDevice: RESUME=UUID=ad8d4a18-9fe4-4246-ba44-85cf6b4dace5
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Compaq 6710b (GB891ET#ABH)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic
root=UUID=686d2155-83a9-4743-a2a4-8e9570ee3da6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-12-generic N/A
linux-backports-modules-3.0.0-12-generic N/A
linux-firmware1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.15
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: CNU72913PH
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68DDUVer.F.15:bd01/15/2009:svnHewlett-Packard:pnHPCompaq6710b(GB891ET#ABH):pvrF.15:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6710b (GB891ET#ABH)
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/+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
