[Kernel-packages] [Bug 1757062] Re: [Apple Inc. MacBook4, 1] hibernate/resume failure [non-free: wl]
[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/1757062 Title: [Apple Inc. MacBook4,1] hibernate/resume failure [non-free: wl] Status in linux package in Ubuntu: Expired Bug description: The computer is very slow during bootup ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: wl Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cristian 6302 F pulseaudio Date: Tue Mar 20 07:41:27 2018 DuplicateSignature: hibernate/resume:Apple Inc. MacBook4,1:MB41.88Z.00C1.B00.0802091535 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=8d16b38f-7434-4b43-a54e-c59b16695944 InstallationDate: Installed on 2016-12-25 (449 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterpreterPath: /usr/bin/python3.6 MachineType: Apple Inc. MacBook4,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=9c2b8ddb-ddb0-450d-961c-854c607ab0d2 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Apple Inc. MacBook4,1] hibernate/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.family: MacBook dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757062/+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 1771733] Re: bluetooth device disappears after several minutes of use
Welp. My mouse has been working for a couple days now and has survived multiple reboots, but the problem is that I don't know what I did to get it working again. I just sat down, wiggled the mouse to wake it up out of habit, and it worked. Could be a hardware issue on my end. Close this bug I guess. Sorry for the mix up, I really have no idea what happened. -- 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/1771733 Title: bluetooth device disappears after several minutes of use Status in Ubuntu Budgie: New Status in bluez package in Ubuntu: New Bug description: I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to- date. When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA. This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:A3:4C:6E ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0 TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1757081] Re: freeze ubuntu 17.10
[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/1757081 Title: freeze ubuntu 17.10 Status in linux package in Ubuntu: Expired Bug description: I had installed Ubuntu 17.10 on a spare partition and updating it daily my system freezes frequently It does not respond to any key presses like Ctrl Alt F1 or Ctrl Alt Del. My Leptop is Lenovo-E530 which has Intel Core i5 chip. Memory is 8GB and 2048 MB swap partition. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amin 2765 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 20 12:39:56 2018 HibernationDevice: RESUME=UUID=9542262e-d4ca-4d0c-81f4-17637dfb4fe1 InstallationDate: Installed on 2018-01-17 (61 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 62723UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=91fdd5d7-664d-4cd0-bab8-07d9c8974e1a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET74WW (2.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 62723UG 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:bvrH0ET74WW(2.08):bd11/14/2012:svnLENOVO:pn62723UG:pvrThinkPadEdgeE530:rvnLENOVO:rn62723UG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E530 dmi.product.name: 62723UG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757081/+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 1756665] Re: BUG: stack guard page was hit at 00000000b87fa1ad (stack is 0000000041fff917..0000000013c05dce)
[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/1756665 Title: BUG: stack guard page was hit at b87fa1ad (stack is 41fff917..13c05dce) Status in linux package in Ubuntu: Expired Bug description: I just receive notification of an error from the bug reporter. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1926 F pulseaudio /dev/snd/controlC2: mark 1926 F pulseaudio /dev/snd/controlC1: mark 1926 F pulseaudio Date: Sun Mar 18 01:44:26 2018 DuplicateSignature: BUG: stack guard page was hit at b87fa1ad (stack is 41fff917..13c05dce) RIP: amdgpu_get_pp_num_states+0x88/0x120 [amdgpu] RSP: ae09830efd20 Failure: oops InstallationDate: Installed on 2018-02-05 (40 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180130) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=PARTUUID=FA62B0C7-C6EB-498F-ABE1-B0BF66673E75 initrd=/efi/ubuntu/initrd.img amdgpu.cik_support=1 radeon.cik_support=0 \ rw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: stack guard page was hit at b87fa1ad (stack is 41fff917..13c05dce) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: Z97M Pro4 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.90:bd05/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756665/+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
Patch for 4.14.41 kernel ** Patch added: "thomson-x6-4.14.41.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5141806/+files/thomson-x6-4.14.41.patch -- 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 1723799] Re: touchpad not working after resume on kernel 4.13
Here's dmesg after resume ** Attachment added: "dmesg after resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/5141807/+files/dmesg_after -- 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/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+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
Hi,
I had a Thomson X6 notebook, it's seems to be a Jumper Ebook 3 Pro
rebranded.
I compiled original kernel from kernel.org.
- With 4.14 RC7 version, movements, simple ou double tab click, 2 finger
gesture worked. But click buttons not.
- With 4.14 RC8 version, nothing works anymore ! I did some investigations.
I copied the "drivers/base" files from 4.14 RC7 to 4.14 RC8. I compiled the
custom kernel... and it works again (except click buttons).
- I did the same thing with the latest version currently available (4.14.41), I
had the same behavior.
- With 4.16 version, after startup/reboot, the touchpad is recognized in log
(dmesg) but it's not work. So, if I suspend and resume, gestures and even
buttons are working !
- From my 4.14.41 version already patched ("drivers/base" files from 4.14 RC7),
I copied "drivers/hid" and "drivers/input" files from 4.16.
Now, everything works : gesture and buttons after a first startup and after
suspend/resume.
I don't know if "drivers/input" files modifications are really necessary, I
will do a rollback and test later.
Obviously, I can't compile kernel if I replace files without minor
modifications.
I analyzed the code changes (drivers/base) between the 4.14 RC7 and 4.14 RC8
versions. There are only a few lines that have been modified.
So I made the reverse modifications in version 4.16, but without success.
Touchpad is still not work after startup/reboot but works only after
suspend/resume.
In all versions (4.14 RC7 original, 4.14 RC8 and 4.14.41 modified, 4.16
original), I still have error messages :
[6.326589] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/261)
[6.328725] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/8713)
[6.329796] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/261)
[6.333024] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/23334)
[6.334090] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/20745)
[6.337295] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/31302)
[6.338385] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/29952)
[6.342743] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/22281)
--
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 1723799] Re: touchpad not working after resume on kernel 4.13
I too am affected now. After suspend+resume, my touchpad isn't found. Rebooting doesn't help: I really have to turn the machine off and on again. I can attach mouse, and then if I try to open touchpad settings in Input Devices settings (I use Kubuntu), it says that Touchpad isn't found, and xinput doesn't show it either. - Fujitsu E556 laptop - 4.15.0-20-generic #21-Ubuntu I still have Ubuntu 16.04 on one SSD with the kernel 4.4.0-119-generic, and the issue doesn't appear there. I think the issue didn't appear on Kubuntu 17.04 either. I didn't try 17.10. The workaround mentioned in the original post didn't work for me. When I ran sudo modprobe i2c-hid, I got this message: rmmod: ERROR: Module i2c_hid is not currently loaded The command sudo modprobe i2c-hid completed, but the touchpad didn't start working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+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 1731784] Re: system slow to start, kernel trace on Inspiron 1525
A workaround was offered "upstream" in Comment #11: https://bugs.freedesktop.org/show_bug.cgi?id=106422#c11 I tested it successfully so far on my hardware (Inspiron 1525). 1. add "video=SVIDEO-1:d" to your kernel boot options I still have to confirm the workaround has no other important side effect. Since I am not in front of the PC (it is 1000km away, and I am accessing it through SSH), I can't really see what is happening nor check all the graphic acceleration is still there. This test will be done later, 1st week of June, when I'll have access to the PC. Then I'll have to find how to make a specific option stick cleanly in grub with new patched kernels! -- 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/1731784 Title: system slow to start, kernel trace on Inspiron 1525 Status in linux package in Ubuntu: Confirmed Bug description: The system is slow to start / log in. [ 65.504191] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:35:pipe B] flip_done timed out [ 65.608196] vblank wait timed out on crtc 1 [ 65.608270] [ cut here ] [ 65.608310] WARNING: CPU: 0 PID: 869 at /build/linux-XO_uEE/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] [ 65.608312] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter gpio_ich dell_laptop dell_smm_hwmon dell_wmi dell_smbios snd_hda_codec_idt wmi_bmof snd_hda_codec_generic dcdbas sparse_keymap coretemp snd_hda_codec_hdmi joydev input_leds snd_hda_intel serio_raw r852 sm_common nand snd_hda_codec nand_ecc snd_hda_core arc4 nand_bch bch mtd snd_hwdep r592 lpc_ich memstick iwl3945 snd_pcm snd_seq_midi snd_seq_midi_event iwlegacy mac80211 snd_rawmidi snd_seq cfg80211 snd_seq_device snd_timer snd shpchp soundcore mac_hid parport_pc ppdev lp parport ip_tables [ 65.608405] x_tables autofs4 firewire_ohci sdhci_pci ahci libahci pata_acpi i915 psmouse sdhci firewire_core crc_itu_t i2c_algo_bit sky2 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm wmi video [ 65.608439] CPU: 0 PID: 869 Comm: Xorg Tainted: GW 4.13.0-16-generic #19-Ubuntu [ 65.608442] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009 [ 65.608445] task: 9b85f7b12c00 task.stack: b032c09dc000 [ 65.608472] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] [ 65.608475] RSP: 0018:b032c09df978 EFLAGS: 00010286 [ 65.608479] RAX: 001f RBX: 9b85b40b8000 RCX: [ 65.608481] RDX: RSI: 9b85ff40dc78 RDI: 9b85ff40dc78 [ 65.608484] RBP: b032c09df9d8 R08: 0001 R09: 03a7 [ 65.608487] R10: b032c09df978 R11: R12: 0001 [ 65.608489] R13: 0170 R14: 0300028e R15: [ 65.608493] FS: 7f0e0d6c3a40() GS:9b85ff40() knlGS: [ 65.608496] CS: 0010 DS: ES: CR0: 80050033 [ 65.608499] CR2: 7fcdecee515c CR3: 79f0b000 CR4: 06f0 [ 65.608501] Call Trace: [ 65.608513] ? wait_woken+0x80/0x80 [ 65.608607] intel_get_load_detect_pipe+0x5c6/0x640 [i915] [ 65.608699] intel_tv_detect+0x145/0x4d0 [i915] [ 65.608706] ? __ext4_handle_dirty_metadata+0x87/0x1c0 [ 65.608714] ? __ww_mutex_lock_slowpath+0x16/0x20 [ 65.608737] drm_helper_probe_detect+0x4d/0x90 [drm_kms_helper] [ 65.608751] ? drm_helper_probe_detect+0x4d/0x90 [drm_kms_helper] [ 65.608766] drm_helper_probe_single_connector_modes+0xe1/0x780 [drm_kms_helper] [ 65.608770] ? __mark_inode_dirty+0x114/0x3a0 [ 65.608802] drm_mode_getconnector+0x153/0x330 [drm] [ 65.608831] ? __drm_mode_object_find+0x54/0xa0 [drm] [ 65.608860] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 65.608884] drm_ioctl_kernel+0x5d/0xb0 [drm] [ 65.608909] drm_ioctl+0x31b/0x3d0 [drm] [ 65.608937] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 65.608944] ? dput.part.23+0x2d/0x1e0 [ 65.608949] do_vfs_ioctl+0xa5/0x610 [ 65.608954] ? vfs_write+0x132/0x1a0 [ 65.608958] SyS_ioctl+0x79/0x90 [ 65.608962] entry_SYSCALL_64_fastpath+0x1e/0xa9 [ 65.608966] RIP: 0033:0x7f0e0ab30ea7 [ 65.608968] RSP: 002b:7ffc306a7b48 EFLAGS: 3246 ORIG_RAX: 0010 [ 65.608973] RAX: ffda RBX: 5649c535efc0 RCX: 7f0e0ab30ea7 [ 65.608975] RDX: 7ffc306a7b80 RSI: c05064a7 RDI: 000e [ 65.608978] RBP: 0060 R08: 000
[Kernel-packages] [Bug 1087010] Re: kworker uses 70-90% of a CPU core (hyperthreaded)
here is the mailing list post https://marc.info/?l=linux- acpi&m=152675757008502&w=2 -- 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/1087010 Title: kworker uses 70-90% of a CPU core (hyperthreaded) Status in linux package in Ubuntu: Triaged Bug description: I see high (70-90%) cpu usage from a kworker thread. Usually kworker/0:1 or kworker/0:2. This does not always happen. On some boots all is fine but once it shows, rebooting does not make it go away. WORKAROUND: Execute: echo "disable" > /sys/firmware/acpi/interrupts/gpe13 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-19-generic 3.5.0-19.30 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1965 F pulseaudio /dev/snd/pcmC0D0p: mio1965 F...m pulseaudio Date: Wed Dec 5 22:37:00 2012 HibernationDevice: RESUME=UUID=a371882c-0fe7-45e5-9adb-83da8374bc11 InstallationDate: Installed on 2012-10-10 (55 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=79674508-93de-43e0-b313-f6a9b480c606 ro crashkernel=384M-2G:64M,2G-:128M acpi_osi=Linux pcie_aspm=force i915.modeset=1 i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.semaphores=1 i915.powersave=1 snd_hda_intel.power_save_controller=1 snd_hda_intel.power_save=1 quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/mio not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-19-generic N/A linux-backports-modules-3.5.0-19-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-10-11 (55 days ago) dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE 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.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 700Z7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1568 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=3f9af81f-77f0-4438-9a4b-6722de269cbb InstallationDate: Installed on 2018-05-09 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=7c436149-ab84-40d0-919f-032364393f9b ro quiet splash video=VGA1:d nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE 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.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 700Z7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion:
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Olivier Fock, Thanks for your work on this, that is some excellent detective work. Also good to know that the "incomplete report" errors are also happening in a working setup. The buttons starting to work after you updating the drivers/hid directory is expected, I have done several fixes to the hid-mt button handling, so I was already hoping that was fixed, but the other problem was blocking testing this. So now I think we need to figure out which change exactly between the 4.14-rc7 and 4.14-rc8 drivers/base directory is causing the problem. To be clear are you talking vanilla 4.14-rc7 and 4.14-rc8 here, or Ubuntu kernel builds. Looking at your diff, one thing which you could try is reverting this in your kernel / reapplying this fix from 4.14-rc8: --- a/drivers/base/regmap/regmap.c 2018-05-16 10:10:32.0 +0200 +++ b/drivers/base/regmap/regmap.c 2017-10-29 21:58:38.0 +0100 @@ -1739,7 +1739,7 @@ return -EINVAL; if (val_len % map->format.val_bytes) return -EINVAL; - if (map->max_raw_write && map->max_raw_write < val_len) + if (map->max_raw_write && map->max_raw_write > val_len) return -E2BIG; map->lock(map->lock_arg); The fix which went into your 4.14-rc8 (I don't see this in the vanilla 4.14-rc8) is obviously correct, but it could be that this is allowing some other driver to do something somewhere which is making the touchpad not work. Something else to try is to revert this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7 Which is in 4.17-rc7 but not in any later kernels, so your copying over of the drivers/base dir from 4.17-rc7 adds that commit and it would be interesting to see if dropping that commit from your special working kernel makes it non working again. Eventually a different version of that commit did go upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=0759e80b84e34a84e7e46e2b1adb528c83d84a47 But that is slightly different, so perhaps the original fix happens to somehow make the touchpad work. Note there is no need to try reverting this commit if changing the max_raw_write check breaks/unbreaks the touchpad, then that is likely the cause and we need to debug further from there. -- 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
And a dmesg directly after boot with the non-working 4.14-rc7 + another one with the working 4.14-rc8 based one would also be good. -- 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
What would also be helpful is an acpidump of your Thomson X6 as well the output of: ls -l /sys/bus/i2c/devices -- 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 1752772] Re: r8169 ethernet card don't work after returning from suspension
So if this is the solution, how long before it gets into the standard
update to folks?
Thanks in advance,
Gary
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752772
Title:
r8169 ethernet card don't work after returning from suspension
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have noticed that the network stopped working on my desktop after
I've suspended the system and woke it up. On dmesg there are messages
like:
[ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 150.944101] do_IRQ: 3.37 No irq handler for vector
[ 150.944105] r8169 :01:00.0 enp1s0: link down
[ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
When using Xenial (from a different install), this problem is not
happening. This is happening on Bionic.
There are only two ways to restore connectivity:
1) Reboot the system;
2) Remove the r8169 module and reinsert it with modprobe.
The motherboard is a AsRock H55M-LE and the Ethernet controller is:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.172
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Mar 2 00:21:57 2018
Dependencies:
InstallationDate: Installed on 2018-02-26 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-10-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: usuario1153 F pulseaudio
/dev/snd/controlC1: usuario1153 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
Mixer name : 'VIA VT1818S'
Components : 'HDA:11060440,18492818,0010'
Controls : 40
Simple ctrls : 17
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 7
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
CurrentDesktop: LXDE
Dependencies:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
InstallationDate: Installed on 2018-02-26 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux-firmware 1.172
PackageArchitecture: all
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
RelatedPackageVersions:
linux-restricted-modules-4.15.0-10-generic N/A
linux-backports-modules-4.15.0-10-generic N/A
linux-firmware 1.172
RfKill:
Tags: bionic
Uname: Linux 4.15.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H55M-LE
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772264] [NEW] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783]
Public bug reported: Hello Team, I have a Customer who is experiencing this issue once every 2 days and here are the details of the bug : May 14 05:24:21 localhost kernel: [6006808.160001] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] May 14 05:24:21 localhost kernel: [6006808.160055] Modules linked in: ufs msdos xfs ip6table_filter ip6_tables iptable_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables udf crc_itu_t i2c_piix4 hv_balloon joydev i2c_core serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper hid_hyperv cryptd hyperv_fb pata_acpi hv_utils cfbfillrect cfbimgblt ptp cfbcopyarea hid hyperv_keyboard hv_netvsc pps_core May 14 05:24:21 localhost kernel: [6006808.160055] CPU: 5 PID: 5783 Comm: java Not tainted 4.13.0-1011-azure #14-Ubuntu May 14 05:24:21 localhost kernel: [6006808.160055] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 May 14 05:24:21 localhost kernel: [6006808.160055] task: 8b91a48fc5c0 task.stack: b5c4cd014000 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0010:fsnotify+0x1f9/0x4f0 May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 0018:b5c4cd017e08 EFLAGS: 0246 ORIG_RAX: ff0c May 14 05:24:21 localhost kernel: [6006808.160055] RAX: 0001 RBX: 8ba0f6246020 RCX: May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 8ba0f6246048 RSI: RDI: 9bc57020 May 14 05:24:21 localhost kernel: [6006808.160055] RBP: b5c4cd017ea8 R08: R09: May 14 05:24:21 localhost kernel: [6006808.160055] R10: e93042d21080 R11: R12: May 14 05:24:21 localhost kernel: [6006808.160055] R13: 8ba0f6246048 R14: R15: May 14 05:24:21 localhost kernel: [6006808.160055] FS: 7f154838a700() GS:8ba0fd74() knlGS: May 14 05:24:21 localhost kernel: [6006808.160055] CS: 0010 DS: ES: CR0: 80050033 May 14 05:24:21 localhost kernel: [6006808.160055] CR2: 7f3fcc254000 CR3: 000165c38000 CR4: 001406e0 May 14 05:24:21 localhost kernel: [6006808.160055] Call Trace: May 14 05:24:21 localhost kernel: [6006808.160055] ? new_sync_write+0xe5/0x140 May 14 05:24:21 localhost kernel: [6006808.160055] vfs_write+0x15a/0x1b0 May 14 05:24:21 localhost kernel: [6006808.160055] ? syscall_trace_enter+0xcd/0x2f0 May 14 05:24:21 localhost kernel: [6006808.160055] SyS_write+0x55/0xc0 May 14 05:24:21 localhost kernel: [6006808.160055] do_syscall_64+0x61/0xd0 May 14 05:24:21 localhost kernel: [6006808.160055] entry_SYSCALL64_slow_path+0x25/0x25 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0033:0x7f489076a2dd. #“This indicates Softlockup error message stored in the RIP Register” May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 002b:7f15483872a0 EFLAGS: 0293 ORIG_RAX: 0001 May 14 05:24:21 localhost kernel: [6006808.160055] RAX: ffda RBX: 7f1548389380 RCX: 7f489076a2dd May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 1740 RSI: 7f1548387310 RDI: 063c May 14 05:24:21 localhost kernel: [6006808.160055] RBP: 7f15483872d0 R08: 7f1548387310 R09: 7f418a55b0b8 May 14 05:24:21 localhost kernel: [6006808.160055] R10: 005b31ee R11: 0293 R12: 1740 May 14 05:24:21 localhost kernel: [6006808.160055] R13: 7f1548387310 R14: 063c R15: 7f4051e0 The customer is using Elastic and hence he submitted a issue in Elastic Search github post which they are pointing that this is a Kernel issue and not a elastic search Issue : Attached github post for reference : https://github.com/elastic/elasticsearch/issues/30667 For now, I have asked him to increase the kernel.watchdog_thresh parameter from 10 to 20 to relax the situation. The customer wants to know for sure whether this is a Kernel bug. I also asked him to perform Kernel update. However, if he is confirmed that this is a bug in the current Kernel, he is willing to do so in all the 65 servers. The customer also submitted a bug to the Java process team which seems to be causing the issue, There reply was it is a kernel issue and the following launchpad link was given although I personally think that is not really the case here. However, I may be wrong : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717 This is the Information regarding the Performance of Java process within the customer's CPU Avg. Load: Avg=3, max=9 CP
[Kernel-packages] [Bug 1772264] [NEW] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783]
You have been subscribed to a public bug by Sriharsha BS (sribs): Hello Team, I have a Customer who is experiencing this issue once every 2 days and here are the details of the bug : May 14 05:24:21 localhost kernel: [6006808.160001] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] May 14 05:24:21 localhost kernel: [6006808.160055] Modules linked in: ufs msdos xfs ip6table_filter ip6_tables iptable_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables udf crc_itu_t i2c_piix4 hv_balloon joydev i2c_core serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper hid_hyperv cryptd hyperv_fb pata_acpi hv_utils cfbfillrect cfbimgblt ptp cfbcopyarea hid hyperv_keyboard hv_netvsc pps_core May 14 05:24:21 localhost kernel: [6006808.160055] CPU: 5 PID: 5783 Comm: java Not tainted 4.13.0-1011-azure #14-Ubuntu May 14 05:24:21 localhost kernel: [6006808.160055] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 May 14 05:24:21 localhost kernel: [6006808.160055] task: 8b91a48fc5c0 task.stack: b5c4cd014000 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0010:fsnotify+0x1f9/0x4f0 May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 0018:b5c4cd017e08 EFLAGS: 0246 ORIG_RAX: ff0c May 14 05:24:21 localhost kernel: [6006808.160055] RAX: 0001 RBX: 8ba0f6246020 RCX: May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 8ba0f6246048 RSI: RDI: 9bc57020 May 14 05:24:21 localhost kernel: [6006808.160055] RBP: b5c4cd017ea8 R08: R09: May 14 05:24:21 localhost kernel: [6006808.160055] R10: e93042d21080 R11: R12: May 14 05:24:21 localhost kernel: [6006808.160055] R13: 8ba0f6246048 R14: R15: May 14 05:24:21 localhost kernel: [6006808.160055] FS: 7f154838a700() GS:8ba0fd74() knlGS: May 14 05:24:21 localhost kernel: [6006808.160055] CS: 0010 DS: ES: CR0: 80050033 May 14 05:24:21 localhost kernel: [6006808.160055] CR2: 7f3fcc254000 CR3: 000165c38000 CR4: 001406e0 May 14 05:24:21 localhost kernel: [6006808.160055] Call Trace: May 14 05:24:21 localhost kernel: [6006808.160055] ? new_sync_write+0xe5/0x140 May 14 05:24:21 localhost kernel: [6006808.160055] vfs_write+0x15a/0x1b0 May 14 05:24:21 localhost kernel: [6006808.160055] ? syscall_trace_enter+0xcd/0x2f0 May 14 05:24:21 localhost kernel: [6006808.160055] SyS_write+0x55/0xc0 May 14 05:24:21 localhost kernel: [6006808.160055] do_syscall_64+0x61/0xd0 May 14 05:24:21 localhost kernel: [6006808.160055] entry_SYSCALL64_slow_path+0x25/0x25 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0033:0x7f489076a2dd. #“This indicates Softlockup error message stored in the RIP Register” May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 002b:7f15483872a0 EFLAGS: 0293 ORIG_RAX: 0001 May 14 05:24:21 localhost kernel: [6006808.160055] RAX: ffda RBX: 7f1548389380 RCX: 7f489076a2dd May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 1740 RSI: 7f1548387310 RDI: 063c May 14 05:24:21 localhost kernel: [6006808.160055] RBP: 7f15483872d0 R08: 7f1548387310 R09: 7f418a55b0b8 May 14 05:24:21 localhost kernel: [6006808.160055] R10: 005b31ee R11: 0293 R12: 1740 May 14 05:24:21 localhost kernel: [6006808.160055] R13: 7f1548387310 R14: 063c R15: 7f4051e0 The customer is using Elastic and hence he submitted a issue in Elastic Search github post which they are pointing that this is a Kernel issue and not a elastic search Issue : Attached github post for reference : https://github.com/elastic/elasticsearch/issues/30667 For now, I have asked him to increase the kernel.watchdog_thresh parameter from 10 to 20 to relax the situation. The customer wants to know for sure whether this is a Kernel bug. I also asked him to perform Kernel update. However, if he is confirmed that this is a bug in the current Kernel, he is willing to do so in all the 65 servers. The customer also submitted a bug to the Java process team which seems to be causing the issue, There reply was it is a kernel issue and the following launchpad link was given although I personally think that is not really the case here. However, I may be wrong : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717 This is the Information regarding the Performance of Java process within
[Kernel-packages] [Bug 1772287] [NEW] package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Under Vbox ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1870 F pulseaudio Date: Fri May 11 22:56:50 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=44bf76c6-29c5-4361-baa1-ccfd72a45695 InstallationDate: Installed on 2016-07-05 (683 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e84f9ca3-7cca-43d5-a7f1-1412f9276f77 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1772287 Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Under Vbox ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1870 F pulseaudio Date: Fri May 11 22:56:50 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=44bf76c6-29c5-4361-baa1-ccfd72a45695 InstallationDate: Installed on 2016-07-05 (683 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e84f9ca3-7cca-43d5-a7f1-1412f9276f77 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772287/+subscriptions -- Mailing list: https://launchpad.n
[Kernel-packages] [Bug 1772287] Re: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1772287 Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Under Vbox ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1870 F pulseaudio Date: Fri May 11 22:56:50 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=44bf76c6-29c5-4361-baa1-ccfd72a45695 InstallationDate: Installed on 2016-07-05 (683 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e84f9ca3-7cca-43d5-a7f1-1412f9276f77 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772287/+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 1772287] 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/1772287 Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Under Vbox ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1870 F pulseaudio Date: Fri May 11 22:56:50 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=44bf76c6-29c5-4361-baa1-ccfd72a45695 InstallationDate: Installed on 2016-07-05 (683 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. docker0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e84f9ca3-7cca-43d5-a7f1-1412f9276f77 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772287/+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
Hans, - I compiled a fresh 4.14-rc8 vanilla kernel and touchpad didn't work. After applied this patch (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7), the touchpad worked again ! To compile, I need to add "#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX" in somes files. I didn't modify .h file dependency. $ grep -ri S32_MAX * base/power/qos.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX base/power/sysfs.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX base/power/domain_governor.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX base/cpu.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX Note, the unmodified file regmap.c contains this line : if (map->max_raw_write && map->max_raw_write > val_len) -- 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Some details about /sys/bus/i2c/devices/, note I used a 4.14-rc8 previously patched (#153) olivier@debian:~$ uname -a Linux debian 4.14.0-rc8 #2 SMP Sun May 20 20:25:16 CEST 2018 x86_64 GNU/Linux olivier@debian:~$ ls -l /sys/bus/i2c/devices/ total 0 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-0 -> ../../../devices/pci:00/:00:02.0/i2c-0 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-1 -> ../../../devices/pci:00/:00:02.0/i2c-1 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-10 -> ../../../devices/pci:00/:00:17.1/i2c_designware.5/i2c-10 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-11 -> ../../../devices/pci:00/:00:17.2/i2c_designware.6/i2c-11 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-12 -> ../../../devices/pci:00/:00:17.3/i2c_designware.7/i2c-12 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-2 -> ../../../devices/pci:00/:00:02.0/i2c-2 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-3 -> ../../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/i2c-3 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-4 -> ../../../devices/pci:00/:00:1f.1/i2c-4 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-5 -> ../../../devices/pci:00/:00:16.0/i2c_designware.0/i2c-5 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-6 -> ../../../devices/pci:00/:00:16.1/i2c_designware.1/i2c-6 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-7 -> ../../../devices/pci:00/:00:16.2/i2c_designware.2/i2c-7 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-8 -> ../../../devices/pci:00/:00:16.3/i2c_designware.3/i2c-8 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-9 -> ../../../devices/pci:00/:00:17.0/i2c_designware.4/i2c-9 lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-SYNA3602:00 -> ../../../devices/pci:00/:00:16.1/i2c_designware.1/i2c-6/i2c-SYNA3602:00 pi@debian:~$ -- 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
dmesg log ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5142014/+files/dmesg.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/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 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds
I thought it hang on 'scanning for btrfs', but it was actually the resume service/method causing the delay. In my case the resume/swap device is on a LV, could solve it by using this instruction (first method): https://askubuntu.com/questions/1037457/slow-boot-with-ssd-and- lvm-on-new-install-of-18-04 So it seems that if the swap is a LV, UUID no longer works (which did work fine on 17.10) and you now need to specify the mapper path instead. -- 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/1460447 Title: Boot slow, "scanning for btrfs filesystems" takes 100 seconds Status in linux package in Ubuntu: Confirmed Bug description: I installed 14.10 and used btrfs for /home. Later, I did a clean install of 15.04, using the same /home partition. Ever since then, boots have been agonizingly slow; all the delay appears to be while the message "scanning for btrfs filesystems" is diplayed early in boot. The system is an i7 with one disk: root@i7:~# fdisk /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x7f84 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 117186559 117184512 55.9G 83 Linux /dev/sda2 117186560 234373119 117186560 55.9G 83 Linux /dev/sda3 234375166 1953523711 1719148546 819.8G 5 Extended /dev/sda5 234375168 273434623 39059456 18.6G 82 Linux swap / Solaris /dev/sda6 273436672 1953523711 1680087040 801.1G 83 Linux root@i7:~# df -T | grep sd /dev/sda2 ext4 57542652 10103624 44492980 19% / /dev/sda6 btrfs840043520 172076728 665321064 21% /home I'll attach a bootchart, but I suspect the btrfs delay happens before the bootchart starts? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2176 F pulseaudio /dev/snd/controlC0: dank 2176 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 08:53:37 2015 HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223 InstallationDate: Installed on 2015-05-16 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: X58 Extreme dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+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 1769197] Re: package linux-headers-4.4.0-116 4.4.0-116.140 failed to install/upgrade: не удалось безопасно удалить «/usr/src/linux-headers-4.4.0-116/net/wireless/Kconfig»: Это н
This issue was solved by deleting this Kconfig file manuallyKconfig -- 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/1769197 Title: package linux-headers-4.4.0-116 4.4.0-116.140 failed to install/upgrade: не удалось безопасно удалить «/usr/src/linux- headers-4.4.0-116/net/wireless/Kconfig»: Это не каталог Status in linux package in Ubuntu: Confirmed Bug description: package linux-headers-4.4.0-116 is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-116 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 AptOrdering: linux-headers-4.4.0-116: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 1494 F pulseaudio Date: Fri May 4 18:36:55 2018 ErrorMessage: не удалось безопасно удалить «/usr/src/linux-headers-4.4.0-116/net/wireless/Kconfig»: Это не каталог HibernationDevice: RESUME=UUID=789c539b-4320-44c4-9954-218d7585d0f5 InstallationDate: Installed on 2016-08-20 (622 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. G31M-S2L PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=d9b61c40-e417-4525-bcfa-de20a5871b13 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 SourcePackage: linux Title: package linux-headers-4.4.0-116 4.4.0-116.140 failed to install/upgrade: не удалось безопасно удалить «/usr/src/linux-headers-4.4.0-116/net/wireless/Kconfig»: Это не каталог UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd12/29/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-S2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769197/+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 1772323] [NEW] package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/fi
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1772323 Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x- fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin .dpkg-new": niespodziewany koniec pliku lub strumienia Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772323/+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 1772324] [NEW] package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/fi
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1772324 Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x- fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin .dpkg-new": niespodziewany koniec pliku lub strumienia Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772324/+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 1772322] [NEW] package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/fi
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1772322 Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x- fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin .dpkg-new": niespodziewany koniec pliku lub strumienia Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772322/+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 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Tags added: 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+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 1772324] Re: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firm
*** This bug is a duplicate of bug 1772322 *** https://bugs.launchpad.net/bugs/1772322 ** This bug has been marked a duplicate of bug 1772322 package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia -- 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/1772324 Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x- fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin .dpkg-new": niespodziewany koniec pliku lub strumienia Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772324/+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 1772264] Re: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783]
Indeed, this problem should be fixed by the 4.13.0-1017 that's currently in -proposed on its way to -updates. The bug for the race condition should be https://bugs.launchpad.net/ubuntu/+source/linux- azure/+bug/1765564 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1772264 Title: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] Status in linux-azure package in Ubuntu: New Bug description: Hello Team, I have a Customer who is experiencing this issue once every 2 days and here are the details of the bug : May 14 05:24:21 localhost kernel: [6006808.160001] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] May 14 05:24:21 localhost kernel: [6006808.160055] Modules linked in: ufs msdos xfs ip6table_filter ip6_tables iptable_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables udf crc_itu_t i2c_piix4 hv_balloon joydev i2c_core serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper hid_hyperv cryptd hyperv_fb pata_acpi hv_utils cfbfillrect cfbimgblt ptp cfbcopyarea hid hyperv_keyboard hv_netvsc pps_core May 14 05:24:21 localhost kernel: [6006808.160055] CPU: 5 PID: 5783 Comm: java Not tainted 4.13.0-1011-azure #14-Ubuntu May 14 05:24:21 localhost kernel: [6006808.160055] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 May 14 05:24:21 localhost kernel: [6006808.160055] task: 8b91a48fc5c0 task.stack: b5c4cd014000 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0010:fsnotify+0x1f9/0x4f0 May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 0018:b5c4cd017e08 EFLAGS: 0246 ORIG_RAX: ff0c May 14 05:24:21 localhost kernel: [6006808.160055] RAX: 0001 RBX: 8ba0f6246020 RCX: May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 8ba0f6246048 RSI: RDI: 9bc57020 May 14 05:24:21 localhost kernel: [6006808.160055] RBP: b5c4cd017ea8 R08: R09: May 14 05:24:21 localhost kernel: [6006808.160055] R10: e93042d21080 R11: R12: May 14 05:24:21 localhost kernel: [6006808.160055] R13: 8ba0f6246048 R14: R15: May 14 05:24:21 localhost kernel: [6006808.160055] FS: 7f154838a700() GS:8ba0fd74() knlGS: May 14 05:24:21 localhost kernel: [6006808.160055] CS: 0010 DS: ES: CR0: 80050033 May 14 05:24:21 localhost kernel: [6006808.160055] CR2: 7f3fcc254000 CR3: 000165c38000 CR4: 001406e0 May 14 05:24:21 localhost kernel: [6006808.160055] Call Trace: May 14 05:24:21 localhost kernel: [6006808.160055] ? new_sync_write+0xe5/0x140 May 14 05:24:21 localhost kernel: [6006808.160055] vfs_write+0x15a/0x1b0 May 14 05:24:21 localhost kernel: [6006808.160055] ? syscall_trace_enter+0xcd/0x2f0 May 14 05:24:21 localhost kernel: [6006808.160055] SyS_write+0x55/0xc0 May 14 05:24:21 localhost kernel: [6006808.160055] do_syscall_64+0x61/0xd0 May 14 05:24:21 localhost kernel: [6006808.160055] entry_SYSCALL64_slow_path+0x25/0x25 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0033:0x7f489076a2dd. #“This indicates Softlockup error message stored in the RIP Register” May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 002b:7f15483872a0 EFLAGS: 0293 ORIG_RAX: 0001 May 14 05:24:21 localhost kernel: [6006808.160055] RAX: ffda RBX: 7f1548389380 RCX: 7f489076a2dd May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 1740 RSI: 7f1548387310 RDI: 063c May 14 05:24:21 localhost kernel: [6006808.160055] RBP: 7f15483872d0 R08: 7f1548387310 R09: 7f418a55b0b8 May 14 05:24:21 localhost kernel: [6006808.160055] R10: 005b31ee R11: 0293 R12: 1740 May 14 05:24:21 localhost kernel: [6006808.160055] R13: 7f1548387310 R14: 063c R15: 7f4051e0 The customer is using Elastic and hence he submitted a issue in Elastic Search github post which they are pointing that this is a Kernel issue and not a elastic search Issue : Attached github post for reference : https://github.com/elastic/elasticsearch/issues/30667 For now, I have asked him to increase the kernel.watchdog_thresh parameter from 10 to 20 to relax the situation. The customer wants to know for sure whether this is a Kernel bug. I also asked him to perform
[Kernel-packages] [Bug 1772323] Re: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firm
*** This bug is a duplicate of bug 1772322 *** https://bugs.launchpad.net/bugs/1772322 ** This bug has been marked a duplicate of bug 1772322 package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia -- 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/1772323 Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x- fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin .dpkg-new": niespodziewany koniec pliku lub strumienia Status in linux-firmware package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.17 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sun May 20 23:37:36 2018 Dependencies: ErrorMessage: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2018-02-02 (107 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.17 failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin" do "/lib/firmware/ti-connectivity/wl127x-fw-4-mr.bin.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1772323/+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 1772264] Re: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783]
FYI, the "4.13.0-38.43" set of fixes referenced in the bug you mentioned has been in Linux-azure since 4.13.0-1013. Looking at your trace, I think the fsnotify/VFS race condition I referenced in the previous comment may be more applicable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1772264 Title: watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] Status in linux-azure package in Ubuntu: New Bug description: Hello Team, I have a Customer who is experiencing this issue once every 2 days and here are the details of the bug : May 14 05:24:21 localhost kernel: [6006808.160001] watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [java:5783] May 14 05:24:21 localhost kernel: [6006808.160055] Modules linked in: ufs msdos xfs ip6table_filter ip6_tables iptable_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables udf crc_itu_t i2c_piix4 hv_balloon joydev i2c_core serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper hid_hyperv cryptd hyperv_fb pata_acpi hv_utils cfbfillrect cfbimgblt ptp cfbcopyarea hid hyperv_keyboard hv_netvsc pps_core May 14 05:24:21 localhost kernel: [6006808.160055] CPU: 5 PID: 5783 Comm: java Not tainted 4.13.0-1011-azure #14-Ubuntu May 14 05:24:21 localhost kernel: [6006808.160055] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 May 14 05:24:21 localhost kernel: [6006808.160055] task: 8b91a48fc5c0 task.stack: b5c4cd014000 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0010:fsnotify+0x1f9/0x4f0 May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 0018:b5c4cd017e08 EFLAGS: 0246 ORIG_RAX: ff0c May 14 05:24:21 localhost kernel: [6006808.160055] RAX: 0001 RBX: 8ba0f6246020 RCX: May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 8ba0f6246048 RSI: RDI: 9bc57020 May 14 05:24:21 localhost kernel: [6006808.160055] RBP: b5c4cd017ea8 R08: R09: May 14 05:24:21 localhost kernel: [6006808.160055] R10: e93042d21080 R11: R12: May 14 05:24:21 localhost kernel: [6006808.160055] R13: 8ba0f6246048 R14: R15: May 14 05:24:21 localhost kernel: [6006808.160055] FS: 7f154838a700() GS:8ba0fd74() knlGS: May 14 05:24:21 localhost kernel: [6006808.160055] CS: 0010 DS: ES: CR0: 80050033 May 14 05:24:21 localhost kernel: [6006808.160055] CR2: 7f3fcc254000 CR3: 000165c38000 CR4: 001406e0 May 14 05:24:21 localhost kernel: [6006808.160055] Call Trace: May 14 05:24:21 localhost kernel: [6006808.160055] ? new_sync_write+0xe5/0x140 May 14 05:24:21 localhost kernel: [6006808.160055] vfs_write+0x15a/0x1b0 May 14 05:24:21 localhost kernel: [6006808.160055] ? syscall_trace_enter+0xcd/0x2f0 May 14 05:24:21 localhost kernel: [6006808.160055] SyS_write+0x55/0xc0 May 14 05:24:21 localhost kernel: [6006808.160055] do_syscall_64+0x61/0xd0 May 14 05:24:21 localhost kernel: [6006808.160055] entry_SYSCALL64_slow_path+0x25/0x25 May 14 05:24:21 localhost kernel: [6006808.160055] RIP: 0033:0x7f489076a2dd. #“This indicates Softlockup error message stored in the RIP Register” May 14 05:24:21 localhost kernel: [6006808.160055] RSP: 002b:7f15483872a0 EFLAGS: 0293 ORIG_RAX: 0001 May 14 05:24:21 localhost kernel: [6006808.160055] RAX: ffda RBX: 7f1548389380 RCX: 7f489076a2dd May 14 05:24:21 localhost kernel: [6006808.160055] RDX: 1740 RSI: 7f1548387310 RDI: 063c May 14 05:24:21 localhost kernel: [6006808.160055] RBP: 7f15483872d0 R08: 7f1548387310 R09: 7f418a55b0b8 May 14 05:24:21 localhost kernel: [6006808.160055] R10: 005b31ee R11: 0293 R12: 1740 May 14 05:24:21 localhost kernel: [6006808.160055] R13: 7f1548387310 R14: 063c R15: 7f4051e0 The customer is using Elastic and hence he submitted a issue in Elastic Search github post which they are pointing that this is a Kernel issue and not a elastic search Issue : Attached github post for reference : https://github.com/elastic/elasticsearch/issues/30667 For now, I have asked him to increase the kernel.watchdog_thresh parameter from 10 to 20 to relax the situation. The customer wants to know for sure whether this is a Kernel bug. I also
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
1) This started when I did a clean install of 18.04. I was running 17.10 on the same hardware with the same kernel parameters (the "acpi_osi=!Windows 2015"). I'm afraid I can't tell you which kernel exactly, but I keep things up to date. I upgraded a few days before this report. I think it was release day actually. 2) This issue appears fixed in mainline. 4.17.0-041700rc6-generic #201805202330 SMP Sun May 20 23:31:40 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.17-rc7 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Confirmed Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1759836] Re: systemd-udevd consumes 100% of CPU
** Also affects: ubuntu-power-consumption Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use
** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: ubuntubudgie Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1771733 Title: bluetooth device disappears after several minutes of use Status in Ubuntu Budgie: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to- date. When I open bluetooth settings, I am able to see many different bluetooth devices detected by my computer, and I can connect to my bluetooth mouse (Microsoft sculpt comfort mouse). However, after several minutes of use, I find that my mouse has disconnected, and I no longer have a bluetooth icon in the top right status indicator. Then, when I open bluetooth settings, the window reads "No bluetooth found: Plug in a dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus UX305CA. This is my first bug report so please let me know if I've left out any important details and I will provide them as soon as possible. Thanks for all your hard work with Ubuntu Budgie! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:A3:4C:6E ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0 TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Sandy Patterson, the next step is to fully reverse commit bisect from kernel 4.15 to 4.17-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully commit bisecting. Also, the kernel release names are irrelevant for the purposes of bisecting. It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed. Thank you for your help. ** Tags added: needs-reverse-bisect regression-release ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1757238] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
[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/1757238 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Expired Bug description: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757238/+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 1757509] Re: [FaceCam 1000X] uvcvideo 3-2.3:1.0: Entity type for entity Processing 2 was not initialized!
[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/1757509 Title: [FaceCam 1000X] uvcvideo 3-2.3:1.0: Entity type for entity Processing 2 was not initialized! Status in linux package in Ubuntu: Expired Bug description: Hello, dmesg: [20147.228136] uvcvideo 3-2.3:1.0: Entity type for entity Processing 2 was not initialized! [20147.228146] uvcvideo 3-2.3:1.0: Entity type for entity Extension 6 was not initialized! [20147.228153] uvcvideo 3-2.3:1.0: Entity type for entity Camera 1 was not initialized! [20147.228445] input: FaceCam 1000X: FaceCam 1000X as /devices/pci:00/:00:14.0/usb3/3-2/3-2.3/3-2.3:1.0/input/input15 Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: caravena 1814 F pulseaudio /dev/snd/pcmC0D0p: caravena 1814 F...m pulseaudio /dev/snd/controlC0: caravena 1814 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 21 15:20:18 2018 InstallationDate: Installed on 2017-10-13 (159 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 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/1757509/+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 1742603] Re: Kernel 4.13.0-26.29~16.04.2 Causing Crash
[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/1742603 Title: Kernel 4.13.0-26.29~16.04.2 Causing Crash Status in linux package in Ubuntu: Expired Bug description: Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while display was way off. As you can see in the system specs below, I booted into kernel 4.10 and all is well System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia Machine: System: Gigabyte product: Z97X-UD3H-BK Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x Bios: American Megatrends v: F8 date: 09/19/2015 CPU: Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz 4: 1061 MHz Graphics: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 2560x1440@59.95hz GLX Renderer: GeForce GTX 950/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1 Card-3 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0 IF: eno1 state: down mac: Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k bus-ID: 05:00.0 IF: wlp5s0 state: up mac: Drives:HDD Total Size: 2490.5GB (1.1% used) ID-1: /dev/sda model: Crucial_CT240M50 size: 240.1GB ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB ID-3: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB ID-4: /dev/sdd model: WDC_WD10EFRX size: 1000.2GB Partition: ID-1: / size: 23G used: 14G (63%) fs: ext4 dev: /dev/sdb1 ID-2: /home size: 202G used: 6.5G (4%) fs: ext4 dev: /dev/sdb3 ID-3: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:33C Fan Speeds (in rpm): cpu: N/A Info: Processes: 218 Uptime: 29 min Memory: 1263.6/32009.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742603/+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 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) 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/1730867 Title: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation Status in intel: Incomplete Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. Target Kernel: 4.19 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730867/+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 1756833] Re: package linux-headers-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[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/1756833 Title: package linux-headers-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Expired Bug description: Practically cannot install anything, currently hangs at updating grub ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libqrencode3:amd64: Install qrencode:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1373 F pulseaudio unrz2052174 F pulseaudio /dev/snd/controlC1: gdm1373 F pulseaudio unrz2052174 F pulseaudio Date: Mon Mar 19 10:56:33 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=5a36e2b2-c485-4685-81df-2f483275fb57 InstallationDate: Installed on 2017-11-02 (136 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20HJS1NX00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=e58dc9d9-cb8f-478e-a560-c64250261725 ro quiet splash vt.handoff=7 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.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET46W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HJS1NX00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NX00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NX00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756833/+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 1757492] Re: [TOSHIBA SATELLITE S70t-A] hibernate/resume failure
[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/1757492 Title: [TOSHIBA SATELLITE S70t-A] hibernate/resume failure Status in linux package in Ubuntu: Expired Bug description: On this computer, Hibernation is OK on 16.04.1 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1611 F pulseaudio u16041 2094 F pulseaudio Date: Wed Mar 21 17:40:00 2018 DuplicateSignature: hibernate/resume:TOSHIBA SATELLITE S70t-A:1.30 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=ff32a7ea-7be8-49a9-9571-0c2da78b9285 InstallationDate: Installed on 2016-10-22 (515 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterpreterPath: /usr/bin/python3.6 MachineType: TOSHIBA SATELLITE S70t-A ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-12-generic.efi.signed root=UUID=d02c95f8-0ad8-4e44-a074-74966572da9c ro quiet splash vt.handoff=7 initrd=boot\initrd.img-4.15.0-12-generic 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.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [TOSHIBA SATELLITE S70t-A] hibernate/resume failure UpgradeStatus: Upgraded to bionic on 2018-03-21 (0 days ago) UserGroups: dmi.bios.date: 04/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE S70t-A dmi.product.version: PSKN6E-01C00KFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757492/+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 1754425] Re: Lots of pcieport and nvme kernel errors - system non-responsive
[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/1754425 Title: Lots of pcieport and nvme kernel errors - system non-responsive Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: If I open the lid, it seems that the computer flat-out doesn't wake up. HOWEVER, if I wait patiently more than 20 seconds, and press (not hold) the power button, SOMETIMES, the computer will "snap out of it" and come back to my desktop. Although RAM is 25% used, and CPU usage is around 25-50% or less (depending on apps), mouse will regularly freeze up for some seconds every 10 seconds or so. Wifi will claim to be "on", but there aren't any networks in the "select network" dialogue. Turning wifi off and then on does not fix this problem. So I'll be in this terrifying state of non-responsive every few seconds computer, with no ability to reconnect to networks and report bug. I force restart. The first restart, upon login, will hang indefinitely on a purple screen with the cursor in the middle. I will have to force restart again. Upon 2nd restart, it will boot "normally". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 12:38:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-02 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1387 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-02 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.
[Kernel-packages] [Bug 1748675] Re: Laptop freezes seconds after displaying the login screen
[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/1748675 Title: Laptop freezes seconds after displaying the login screen Status in linux package in Ubuntu: Expired Status in linux source package in Artful: Expired Bug description: My Dell Precision Laptop 5520 freezes seconds after displaying the login screen when using linux-image-4.13.0-32-generic (Includes 31, 30). Selecting 4.13.0-17-generic allows for stable operation. I am still currently installing the main line series and will report if the issue is resolved once that is installed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rhianresnick 3057 F...m pulseaudio /dev/snd/controlC0: rhianresnick 3057 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 10 18:12:26 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 HibernationDevice: RESUME=UUID=d22435f8-1e7b-46d7-b6bf-9722c30e05c1 InstallationDate: Installed on 2016-11-22 (445 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=5f8e45d9-71ed-4a72-9380-ac204117e9cd ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0N8J4R dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748675/+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 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation
[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/1730867 Title: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation Status in intel: Incomplete Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. Target Kernel: 4.19 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730867/+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 1748675] Re: Laptop freezes seconds after displaying the login screen
[Expired for linux (Ubuntu Artful) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Artful) 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/1748675 Title: Laptop freezes seconds after displaying the login screen Status in linux package in Ubuntu: Expired Status in linux source package in Artful: Expired Bug description: My Dell Precision Laptop 5520 freezes seconds after displaying the login screen when using linux-image-4.13.0-32-generic (Includes 31, 30). Selecting 4.13.0-17-generic allows for stable operation. I am still currently installing the main line series and will report if the issue is resolved once that is installed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rhianresnick 3057 F...m pulseaudio /dev/snd/controlC0: rhianresnick 3057 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 10 18:12:26 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 HibernationDevice: RESUME=UUID=d22435f8-1e7b-46d7-b6bf-9722c30e05c1 InstallationDate: Installed on 2016-11-22 (445 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=5f8e45d9-71ed-4a72-9380-ac204117e9cd ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0N8J4R dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748675/+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 1771075] Re: General Protection fault in inotify (fixed upstream)
Good news - I got the chance to test this in our production environment today for about 7 hours and no issues whatsoever. Given that this workload was triggering the issue pretty reliably within about half an hour before, I think this fix has done the trick. Thanks a bunch for your help! What are the next steps here? -- 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/1771075 Title: General Protection fault in inotify (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 10 07:57 seq crw-rw 1 root audio 116, 33 May 10 07:57 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-32-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
[Kernel-packages] [Bug 1752044] Re: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive)
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1752044 Title: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive) Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification Impact: New ath10k firmware is needed for compliance with CE-RED. Fix: Updated firmware files. Regression Potential: This update has been in upstream linux-firmware for a while now. While regressions are possible, the firmware should have seen a lot of use by now. --- To comply with CE-RED (Radio Emissions Directive), ath10k/QCA6174/hw3.0/board-2.bin and ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated. The commits are: commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2 Author: Kalle Valo AuthorDate: Thu Feb 15 15:10:51 2018 +0200 Commit: Kalle Valo CommitDate: Thu Feb 15 15:10:51 2018 +0200 ath10k: QCA6174 hw3.0: update board-2.bin Signed-off-by: Kalle Valo commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc Author: Kalle Valo AuthorDate: Thu Feb 15 15:10:51 2018 +0200 Commit: Kalle Valo CommitDate: Thu Feb 15 15:10:51 2018 +0200 ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00079-QCARMSWPZ-1 Signed-off-by: Kalle Valo To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1752044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
This bug was fixed in the package alsa-lib - 1.1.3-5ubuntu0.1 --- alsa-lib (1.1.3-5ubuntu0.1) bionic; urgency=medium * debian/patches/0009-ucm-Assure-the-user-input-card-name-not-to-exceed-ma.patch * debian/patches/0010-ucm-Load-device-specific-configuration-file-based-on.patch * debian/patches/0011-conf-ucm-Add-dual-HD-audio-codecs-config-for-Lenovo.patch * debian/patches/0012-ucm-adding-the-folder-of-card_long_name-when-finding.patch * debian/patches/0013-conf-ucm-increase-the-input-volume-for-LineIn.patch - Backport 5 patches to make audio work on Lenovo machines with dual audio codecs. (LP: #1768830) 0009-xxx.patch: 2b9b3f01 0010-xxx.patch: 4b9297e6 0011-xxx.patch: b7e56af8 (minor change for fixing patch conflict) 0012-xxx.patch: 181f8e25 (minor change for fixing patch conflict) 0013-xxx.patch: 81db276f -- Hui Wang Fri, 04 May 2018 09:15:08 +0800 ** Changed in: alsa-lib (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this
[Kernel-packages] [Bug 1768830] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this change is compatible with old version. There is no regression since there is only one folder named by card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with dual codecs, it will find the conf file by card_long_name, if it runs on other machines, the search by card_long_name will definitely fail and fall back to search by card_name, then it will be same as before. So the objective of these 5 patches is to let lenovo machines with dual codecs find the conf file by card_long_name, let other machines fail to search by card
[Kernel-packages] [Bug 1087010] Re: kworker uses 70-90% of a CPU core (hyperthreaded)
Hi Mio, Can you install linux-tools-generic and use `perf top` to see which functions cause this issue? -- 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/1087010 Title: kworker uses 70-90% of a CPU core (hyperthreaded) Status in linux package in Ubuntu: Triaged Bug description: I see high (70-90%) cpu usage from a kworker thread. Usually kworker/0:1 or kworker/0:2. This does not always happen. On some boots all is fine but once it shows, rebooting does not make it go away. WORKAROUND: Execute: echo "disable" > /sys/firmware/acpi/interrupts/gpe13 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-19-generic 3.5.0-19.30 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1965 F pulseaudio /dev/snd/pcmC0D0p: mio1965 F...m pulseaudio Date: Wed Dec 5 22:37:00 2012 HibernationDevice: RESUME=UUID=a371882c-0fe7-45e5-9adb-83da8374bc11 InstallationDate: Installed on 2012-10-10 (55 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=79674508-93de-43e0-b313-f6a9b480c606 ro crashkernel=384M-2G:64M,2G-:128M acpi_osi=Linux pcie_aspm=force i915.modeset=1 i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.semaphores=1 i915.powersave=1 snd_hda_intel.power_save_controller=1 snd_hda_intel.power_save=1 quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/mio not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-19-generic N/A linux-backports-modules-3.5.0-19-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-10-11 (55 days ago) dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE 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.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 700Z7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mio1568 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=3f9af81f-77f0-4438-9a4b-6722de269cbb InstallationDate: Installed on 2018-05-09 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z7C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=7c436149-ab84-40d0-919f-032364393f9b ro quiet splash video=VGA1:d nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAE 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.:bvrP04AAE:bd08/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 700Z7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -
