[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Still seeing the error message on the following setup: - Kernel: 4.12.0-041200-generic (downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/) - Ubuntu 17.04 - ThinkStation P310 [ 1130.350050] drm: not enough stolen space for compressed buffer (need 29491200 more bytes), disabling. Hint: you may be able to increase stolen memory size in the BIOS to avoid this. [ 1130.433925] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 1130.434005] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [ 1146.868877] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. If I get the problem again, are any specific log files of interest? -- 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/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
[Kernel-packages] [Bug 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709816 Title: linux-aws: 4.4.0-1031.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709816/+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 1709812] Re: linux: 4.4.0-92.115 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress -- 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/1709812 Title: linux: 4.4.0-92.115 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709812/+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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker
This bug was fixed in the package linux-aws - 4.4.0-1031.40 --- linux-aws (4.4.0-1031.40) xenial; urgency=low * linux-aws: 4.4.0-1031.40 -proposed tracker (LP: #1709816) [ Ubuntu: 4.4.0-92.115 ] * linux: 4.4.0-92.115 -proposed tracker (LP: #1709812) * Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032) - Revert "netfilter: synproxy: fix conntrackd interaction" -- Kleber Sacilotto de Souza Thu, 10 Aug 2017 12:59:26 +0200 ** Changed in: linux-aws (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: linux-aws (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709816 Title: linux-aws: 4.4.0-1031.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709816/+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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker
This bug was fixed in the package linux-aws - 4.4.0-1031.40 --- linux-aws (4.4.0-1031.40) xenial; urgency=low * linux-aws: 4.4.0-1031.40 -proposed tracker (LP: #1709816) [ Ubuntu: 4.4.0-92.115 ] * linux: 4.4.0-92.115 -proposed tracker (LP: #1709812) * Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032) - Revert "netfilter: synproxy: fix conntrackd interaction" -- Kleber Sacilotto de Souza Thu, 10 Aug 2017 12:59:26 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709816 Title: linux-aws: 4.4.0-1031.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709816/+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 1709812] Re: linux: 4.4.0-92.115 -proposed tracker
This bug was fixed in the package linux - 4.4.0-92.115 --- linux (4.4.0-92.115) xenial; urgency=low * linux: 4.4.0-92.115 -proposed tracker (LP: #1709812) * Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032) - Revert "netfilter: synproxy: fix conntrackd interaction" -- Kleber Sacilotto de Souza Thu, 10 Aug 2017 10:29:51 +0200 ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709812 Title: linux: 4.4.0-92.115 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709812/+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 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
This bug was fixed in the package linux - 4.4.0-92.115
---
linux (4.4.0-92.115) xenial; urgency=low
* linux: 4.4.0-92.115 -proposed tracker (LP: #1709812)
* Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032)
- Revert "netfilter: synproxy: fix conntrackd interaction"
-- Kleber Sacilotto de Souza Thu, 10 Aug
2017 10:29:51 +0200
--
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/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+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 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
This bug was fixed in the package linux - 4.4.0-92.115
---
linux (4.4.0-92.115) xenial; urgency=low
* linux: 4.4.0-92.115 -proposed tracker (LP: #1709812)
* Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032)
- Revert "netfilter: synproxy: fix conntrackd interaction"
-- Kleber Sacilotto de Souza Thu, 10 Aug
2017 10:29:51 +0200
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Tuesday, 15. August 2017 09:30 UTC + kernel-stable-phase:Promoted to updates ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Tuesday, 15. August 2017 09:30 UTC - kernel-stable-phase:Promoted to updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709816 Title: linux-aws: 4.4.0-1031.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709816/+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 1709812] Re: linux: 4.4.0-92.115 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Tuesday, 15. August 2017 09:34 UTC + kernel-stable-phase:Promoted to updates ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Tuesday, 15. August 2017 09:34 UTC - kernel-stable-phase:Promoted to updates -- 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/1709812 Title: linux: 4.4.0-92.115 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709812/+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 1709300] Re: linux-aws: 4.4.0-1032.41 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709300 Title: linux-aws: 4.4.0-1032.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709296 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709300/+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 1709296] Re: linux: 4.4.0-93.116 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- 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/1709296 Title: linux: 4.4.0-93.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709296/+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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1709816 Title: linux-aws: 4.4.0-1031.40 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1709812 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709816/+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 1709288] Re: linux: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709288 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1709289,1709290 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709288/+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 1709290] Re: linux-armadaxp: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1709290 Title: linux-armadaxp: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1709288 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709290/+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 1709812] Re: linux: 4.4.0-92.115 -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709812 Title: linux: 4.4.0-92.115 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709813 derivatives: 1709814,1709815,1709816,1709817 -- swm properties -- boot-testing-requested: true phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709812/+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 1710601] Re: bluetoothctl fails to connect
bluetoothd is still running after the problem occurs. there is a /var/crash/_usr_lib_blueman_blueman-rfcomm-watcher.0.crash which in my opinion refers to an unrelated incident involving blueman. if you want I can upload the file. -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ;
[Kernel-packages] [Bug 1710601] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932681/+files/Lspci.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:sessio
[Kernel-packages] [Bug 1710601] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932680/+files/JournalErrors.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam
[Kernel-packages] [Bug 1710601] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932682/+files/Lsusb.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:sessio
[Kernel-packages] [Bug 1710601] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932688/+files/UdevDb.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:sess
[Kernel-packages] [Bug 1710601] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932687/+files/ProcModules.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_uni
[Kernel-packages] [Bug 1710601] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932684/+files/ProcCpuinfoMinimal.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[
[Kernel-packages] [Bug 1710601] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932683/+files/ProcCpuinfo.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_uni
[Kernel-packages] [Bug 1710601] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932686/+files/ProcInterrupts.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: p
[Kernel-packages] [Bug 1710601] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932679/+files/Dependencies.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_u
[Kernel-packages] [Bug 1710601] Re: bluetoothctl fails to connect
apport information ** Tags added: apport-collected xenial ** Description changed: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:53:18 george sudo[1520]: pam_unix(sudo:session): session closed for user root these errors are common, as you can see in comments to this bug report: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349 user@george:~$ lsmod | grep b
[Kernel-packages] [Bug 1710601] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932685/+files/ProcEnviron.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_uni
[Kernel-packages] [Bug 1710601] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932690/+files/rfkill.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:sess
[Kernel-packages] [Bug 1710601] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932689/+files/getfacl.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:s
[Kernel-packages] [Bug 1710601] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932691/+files/syslog.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:sess
[Kernel-packages] [Bug 1710601] Re: bluetoothctl fails to connect
This is not a crash. Nothing crashes. It just disconnects immediately after connect and bluetoothctl is frozen without sudo. After running apport-collect bluetooth started working without sudo, but it still failed to connect. This is weird, since I did not use the GUI applet to connect. Thank you for your help. -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Direct
[Kernel-packages] [Bug 1710868] [NEW] memory-hotplug test needs to be fixed
Public bug reported: SRU Justification: Impact: The memory-hotplug test in the kernel tree (tools/testing/selftests/memory-hotplug/) needs to be fixed: 1. The test will pass even the memory blocks are failed to be offlined [1]. 2. It's using a random number generator to decide if each memory block needs to be offlined, which is not ideal for testing as the block it tries to unplug might be different between two runs. 3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. It's being used as the percentage to get a memory block offlined instead. Fix: Apply the following patch from upstream can fix these issues: 593f9278 - selftests: typo correction for memory-hotplug test a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test 72441ea5 - selftests: check percentage range for memory-hotplug test 02d8f075 - selftests: add missing test name in memory-hotplug test 5ff0c60b - selftests: fix memory-hotplug test Testcase: Run the script directly, it will fail when all memory blocks are busy. And it will try to unplug memory blocks in a fixed order. Regression Potential: Negligible, it's just affecting this specific test case among those testing tools. [1] https://paste.ubuntu.com/25318445/ ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1710868 Title: memory-hotplug test needs to be fixed Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: The memory-hotplug test in the kernel tree (tools/testing/selftests/memory-hotplug/) needs to be fixed: 1. The test will pass even the memory blocks are failed to be offlined [1]. 2. It's using a random number generator to decide if each memory block needs to be offlined, which is not ideal for testing as the block it tries to unplug might be different between two runs. 3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. It's being used as the percentage to get a memory block offlined instead. Fix: Apply the following patch from upstream can fix these issues: 593f9278 - selftests: typo correction for memory-hotplug test a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test 72441ea5 - selftests: check percentage range for memory-hotplug test 02d8f075 - selftests: add missing test name in memory-hotplug test 5ff0c60b - selftests: fix memory-hotplug test Testcase: Run the script directly, it will fail when all memory blocks are busy. And it will try to unplug memory blocks in a fixed order. Regression Potential: Negligible, it's just affecting this specific test case among those testing tools. [1] https://paste.ubuntu.com/25318445/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710868/+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 1710868] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1710868 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710868 Title: memory-hotplug test needs to be fixed Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: The memory-hotplug test in the kernel tree (tools/testing/selftests/memory-hotplug/) needs to be fixed: 1. The test will pass even the memory blocks are failed to be offlined [1]. 2. It's using a random number generator to decide if each memory block needs to be offlined, which is not ideal for testing as the block it tries to unplug might be different between two runs. 3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. It's being used as the percentage to get a memory block offlined instead. Fix: Apply the following patch from upstream can fix these issues: 593f9278 - selftests: typo correction for memory-hotplug test a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test 72441ea5 - selftests: check percentage range for memory-hotplug test 02d8f075 - selftests: add missing test name in memory-hotplug test 5ff0c60b - selftests: fix memory-hotplug test Testcase: Run the script directly, it will fail when all memory blocks are busy. And it will try to unplug memory blocks in a fixed order. Regression Potential: Negligible, it's just affecting this specific test case among those testing tools. [1] https://paste.ubuntu.com/25318445/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710868/+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 1710877] [NEW] Fn Keys Not working Ubuntu 16.04 Asus FX553Vd
Public bug reported: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Sleep Button /dev/input/event1: Power Button /dev/input/event2: Lid Switch /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Video Bus /dev/input/event6: Video Bus /dev/input/event7: ITE Tech. Inc. ITE Device(8910) /dev/input/event8: Asus WMI hotkeys /dev/input/event9: USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs.tar.gz" https://bugs.launchpad.net/bugs/1710877/+attachment/4932734/+files/logs.tar.gz -- 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/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: New Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
The "delayinit" kernel seems to work! The keyboard is usable when the computer first boots, and every time I unplug and plug it back in. I did that while following the output of dmesg -w and got the following: [ 80.205969] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 81.468240] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20 [ 81.468244] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 81.468246] usb 3-3: Product: Corsair STRAFE RGB Gaming Keyboard [ 81.468247] usb 3-3: Manufacturer: Corsair [ 81.468249] usb 3-3: SerialNumber: 0B03F020AEBD18445619787AF5001946 [ 86.703197] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:1B1C:1B20.0005/input/input23 [ 86.703780] hid-generic 0003:1B1C:1B20.0005: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair STRAFE RGB Gaming Keyboard] on usb-:00:14.0-3/input0 [ 86.705875] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input24 [ 86.706203] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input25 [ 86.706403] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input26 [ 86.706640] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input27 [ 86.706854] hid-generic 0003:1B1C:1B20.0006: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair STRAFE RGB Gaming Keyboard] on usb-:00:14.0-3/input1 [ 86.706941] usbhid 3-3:1.2: couldn't find an input interrupt endpoint I haven't tried the devicequalifier kernel yet, will try that now. -- 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/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireles
[Kernel-packages] [Bug 1478696] Re: dell-laptop: Incorrect keyboard backlight detection
Um hello! Is anybody home? Has there been any progress on this bug? Is there a way to find out? Ah! Because it's happening now on my inspiron n4050! -- 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/1478696 Title: dell-laptop: Incorrect keyboard backlight detection Status in linux package in Ubuntu: Triaged Bug description: I own Dell Inspiron M5110 (Q15R). This laptop has no keyboard backlight, but dell-laptop claims otherwise. My syslog was getting spammed with "Keyboard brightness level control not supported" as dell-laptop was trying to get/set backlight values. In dell-laptop there is kbd_led_present variable, but on my M5110 it's being set to true: ret = kbd_init_info(); (...) if (kbd_token_bits != 0 || ret == 0) kbd_led_present = true; kbd_token_bits is 0, but so is ret. kbd_init_info method is only returning != 0 if kbd_get_info is returning != 0 (Basing on this: http://linux.dell.com/cgi-bin/cgit.cgi/libsmbios.git/tree/src/bin/smbios-keyboard-ctl#n667) kbd_get_info method returns only cbRES1 value of following smbios call : cbClass 4 cbSelect 11 cbArg1 0x0 And it returns 0... I found that any cbRES of this call is giving me nothing but zeros, as if it wasn't defined in my BIOS. I have it's newest version for my laptop: [0.00] SMBIOS 2.7 present. [0.00] DMI: Dell Inc. Inspiron M5110/0X7W03, BIOS A05 03/22/2012 However, if "cbRES3, byte2 Number of keyboard light brightness levels" is 0 as well, that should mean backlight is not available, right? I'm attaching possible fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478696/+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 1710877] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1710877 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710877/+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 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
The "devicequalifier" kernel doesn't appear to work. It presents a similar error either on boot or when hot-plugging the keyboard: [ 37.680914] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 48.097499] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20 [ 48.097505] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 48.097508] usb 3-3: Product: Corsair STRAFE RGB Gaming Keyboard [ 48.097510] usb 3-3: Manufacturer: Corsair [ 51.331414] usb 3-3: can't set config #1, error -71 The error code has changed from -110 to -71, but the behavior seems to be very similar to that of the original bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: d
[Kernel-packages] [Bug 1709889] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2017-08-15 09:26 EDT---
Here is what I am observing, and what leads me to think that "cfq" may not
(yet) be a good choice for the default io-sched.
The test exerciser, HTX (https://github.com/open-power/HTX - POWER arch
only), causes stress on CFQ during certain cycles. I set the debug
timeout threshold for completion of I/Os at 60 seconds (upon timeout,
debugging is printed and then io_schedule() called after which more
debugging is printed). It is known that I/O delays seem to vary
continuously throughout the range, but using a timeout lower than 60
just produced too much output.
During certain cycles, where about 1 million I/Os per hour are being
performed on each disk, we see timeouts being triggered. Essentially,
the timeout happens because CFQ has not even submitted the I/O to SCSI
yet. Earlier debugging showed that the once the I/O actually gets
submitted to SCSI it completes promptly.
Without the patch 5be6b75610ce these I/Os could (sometimes) take an hour
or more to get submitted to SCSI. With the patch, that delay time seems
to max out at around 110 seconds, which is a great improvement however
still indicates a problem.
I typically see about 400-500 I/Os trip the 60-second timeout during a
given ~2 hour cycle (estimated 4 million I/Os total), so it is not a
huge percentage. However, the I/Os affected seem to be related, possibly
by process or thread, and so this could be detrimental to an
application. Note, the number of I/Os taking between 30 and 60 seconds
is not known, but is expected to be much higher. Even 30 seconds may be
an undesirable number. It's not clear just how CFQ chooses the delay
value and what overrides it.
On a run with the scheduler set to "deadline", I never see any I/Os trip
the 60-second timeout.
I think this shows undesirable behavior in CFQ, possibly a bug, and that
it should not be the default scheduler - especially for servers. Is
there some evidence that shows CFQ to be better than deadline in
general?
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
th
[Kernel-packages] [Bug 1709889] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2017-08-15 09:32 EDT---
I should also add that the data indicates there is an instability to the delay,
with the initial stalled I/Os maxing out at about 70 seconds, then the next
cycle (~10 hours later) and subsequent 2 shows max values in the 90-100 second
range, and the following 5 cycles show numbers around 110 seconds (but tapering
off). I think this unpredictability is further indication of a bug in CFQ.
Clearly it does not live up to it's name, at least for these particular I/Os.
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Sorry for slow feedback Unfortunately the issue is still there: Aug 15 12:52:58 phs08 kernel: [0.00] Linux version 4.11.0-14-generic (root@ryzen) (gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ) #20 SMP Wed Aug 9 20:56:51 CST 2017 (Ubuntu 4.11.0-14.20-generic 4.11.12) Aug 15 12:52:58 phs08 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro Tue Aug 15 13:31:03 BST 2017: performing suspend Tue Aug 15 14:11:07 BST 2017: Awake. Aug 15 14:11:07 phs08 kernel: [ 2297.422103] nvme nvme0: disabling APST... Aug 15 14:11:07 phs08 kernel: [ 2297.423143] nvme nvme0: setting power state to 0... ... Aug 15 14:11:07 phs08 kernel: [ 2302.067538] PM: resume of devices complete after 1158.582 msecs Aug 15 14:11:07 phs08 kernel: [ 2302.067889] PM: Finishing wakeup. Aug 15 14:11:07 phs08 kernel: [ 2302.067890] Restarting tasks ... done. Aug 15 14:11:09 phs08 kernel: [ 2304.530720] r8169 :25:00.0 enp37s0: link up Aug 15 14:11:13 phs08 kernel: [ 2307.860622] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 15 14:11:13 phs08 kernel: [ 2307.864647] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 15 14:11:13 phs08 kernel: [ 2307.872508] ata1.00: configured for UDMA/133 Aug 15 14:11:13 phs08 kernel: [ 2307.876591] ata2.00: configured for UDMA/133 Aug 15 14:14:02 phs08 kernel: [ 2477.191603] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Aug 15 14:14:02 phs08 kernel: [ 2477.227261] pci_raw_set_power_state: 4 callbacks suppressed Aug 15 14:14:02 phs08 kernel: [ 2477.227266] nvme :01:00.0: Refused to change power state, currently in D3 Aug 15 14:14:02 phs08 kernel: [ 2477.227394] nvme nvme0: Removing after probe failure status: -19 Aug 15 14:14:02 phs08 kernel: [ 2477.255682] nvme0n1: detected capacity change from 500107862016 to 0 It still seems odd to me that this apparently occurs 2-3 mins after the system has woken up... One thing that confuses me is that the suspend operations like: "nvme nvme0: disabling APST..." are recorded as happening after the system has woken up ! Is this a matter of them not being logged until the system has woken up or actually not executing until the system has woken up ?... either way it is confusing to see suspend operations occuring after the system has resumed. -- 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/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: In Progress Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255
[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Zesty)
Assignee: Joseph Salisbury (jsalisbury) => Colin Ian King (colin-king)
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any previous data. A partition table is optional, in my testing I have
none.
Also, it may be desirable to run HTX somewhere other t
[Kernel-packages] [Bug 1710893] 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/1710893 Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: boot partition went full during Update of newest LTS 16 vrsion ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 1791 F pulseaudio Date: Tue Aug 15 15:41:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=9d20ba5f-c0a4-4c5c-aa75-97488a8d22a2 InstallationDate: Installed on 2014-12-27 (961 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 9461HRG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root 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. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 SourcePackage: linux Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-08-15 (0 days ago) dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461HRG 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:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461HRG:pvrThinkPadR60:rvnLENOVO:rn9461HRG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461HRG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710893/+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 1710893] [NEW] package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: boot partition went full during Update of newest LTS 16 vrsion ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 1791 F pulseaudio Date: Tue Aug 15 15:41:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=9d20ba5f-c0a4-4c5c-aa75-97488a8d22a2 InstallationDate: Installed on 2014-12-27 (961 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 9461HRG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root 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. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 SourcePackage: linux Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-08-15 (0 days ago) dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461HRG 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:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461HRG:pvrThinkPadR60:rvnLENOVO:rn9461HRG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461HRG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1710893 Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: boot partition went full during Update of newest LTS 16 vrsion ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-92-generic 4.4.0-92.115 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 1791 F pulseaudio Date: Tue Aug 15 15:41:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=9d20ba5f-c0a4-4c5c-aa75-97488a8d22a2 InstallationDate: Installed on 2014-12-27 (961 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 9461HRG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root 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. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 SourcePackage: linux Title: package linux-image-extra-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-08-15 (0 days ago) dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461HRG 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:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461HRG:pvrThinkPadR60:rvnLENOVO:rn9461HRG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461HRG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710893/+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 1710904] [NEW] linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1710904 Title: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12 Status in linux package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710904/+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 1710904] Re: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12
This was also happening with 4.11 so it's not a regression in 4.12. -- 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/1710904 Title: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12 Status in linux package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710904/+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 1710904] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1710904 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710904 Title: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12 Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710904/+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 1710877] Re: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd
apport information ** Tags added: apport-collected ** Description changed: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mlp1552 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 + InstallationDate: Installed on 2017-08-14 (1 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + 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 13d3:5654 IMC Networks + Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. GL553VD + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-91-generic N/A + linux-backports-modules-4.4.0-91-generic N/A + linux-firmware1.157.11 + Tags: xenial + Uname: Linux 4.4.0-91-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GL553VD.302 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GL553VD + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: GL553VD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932859/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs
[Kernel-packages] [Bug 1710877] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932870/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD dm
[Kernel-packages] [Bug 1710877] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932868/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL
[Kernel-packages] [Bug 1710877] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932863/+files/JournalErrors.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/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL55
[Kernel-packages] [Bug 1710877] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932872/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnAS
[Kernel-packages] [Bug 1710877] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932871/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD dmi.produ
[Kernel-packages] [Bug 1710877] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932864/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD dmi.product
[Kernel-packages] [Bug 1710877] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932869/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD
[Kernel-packages] [Bug 1710877] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932860/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD dmi.product.v
[Kernel-packages] [Bug 1710877] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932862/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD dmi.
[Kernel-packages] [Bug 1710877] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932873/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD
[Kernel-packages] [Bug 1710877] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932861/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553V
[Kernel-packages] [Bug 1710877] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932865/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD
[Kernel-packages] [Bug 1710877] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932867/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VD
[Kernel-packages] [Bug 1710877] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1710877/+attachment/4932866/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710877 Title: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS FX553VD machne. Some of my Fn keys are not working. For example, Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the keyboard LED brightness and Fn+F2(Airplane Mode). sudo dmidecode -s bios-version GL553VD.302 uname-a Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i asus [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_) [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 01072009 INTL 20160422) [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS GL553VD.302 03/06/2017 [ 3.113648] asus_wmi: ASUS WMI generic driver loaded [ 3.114634] asus_wmi: Initialization: 0x1 [ 3.114680] asus_wmi: BIOS WMI version: 8.1 [ 3.114732] asus_wmi: SFUN value: 0x4a0061 [ 3.115047] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9 [ 3.115210] asus_wmi: Number of fans: 1 sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0:Sleep Button /dev/input/event1:Power Button /dev/input/event2:Lid Switch /dev/input/event3:Power Button /dev/input/event4:AT Translated Set 2 keyboard /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:ITE Tech. Inc. ITE Device(8910) /dev/input/event8:Asus WMI hotkeys /dev/input/event9:USB2.0 UVC HD Webcam /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: ELAN1200:00 04F3:3045 Touchpad Select the device event number [0-14]: --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlp1552 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187 InstallationDate: Installed on 2017-08-14 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 RelatedPackageVersions: linux-restricted-modules-4.4.0-91-generic N/A linux-backports-modules-4.4.0-91-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.
[Kernel-packages] [Bug 1710799] Re: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure
Reassigning to collectd package, which will need to start bundling this header. ** Package changed: linux (Ubuntu) => collectd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710799 Title: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure Status in collectd package in Ubuntu: Confirmed Bug description: The collectd package fails to build in artful-proposed on x86 because linux-libc-dev 4.12.0-11.12 has dropped the asm/msr-index.h header that was previously present and which collectd's turbostat plugin relied on. Please re-add this header if possible. If there is a reason that it should not be exposed to userspace and this is a deliberate change, please reassign this bug and I will arrange to bundle it with the collectd source instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1710799/+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 1710799] Re: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure
The removal was intentional. In fact it was supposed to be removed from the exported headers in 4.2 but a mistake was made, and this was just now fixed in 4.12. The justification is in the original commit message. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b72e7464e4cf80117938e6adb8c22fdc1ca46d42 -- 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/1710799 Title: missing asm/msr-index.h in linux-libc-dev 4.12 causes collectd build failure Status in collectd package in Ubuntu: Confirmed Bug description: The collectd package fails to build in artful-proposed on x86 because linux-libc-dev 4.12.0-11.12 has dropped the asm/msr-index.h header that was previously present and which collectd's turbostat plugin relied on. Please re-add this header if possible. If there is a reason that it should not be exposed to userspace and this is a deliberate change, please reassign this bug and I will arrange to bundle it with the collectd source instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1710799/+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 1710904] Re: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12
** 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/1710904 Title: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12 Status in linux package in Ubuntu: Confirmed Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710904/+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 1704363] Re: Add firmware for Redpine 9113 chipset
@Seth, When will the Redpine RS9113 firmware available in linux-firmware for Xenial? Is anything blocking the release? -- 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/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1710501] Re: can't open synaptic package manager
I am not really able to do this I have downloaded the mainline kernel packages and put them in a separate folder (within download folder). Then I do sudo dpkg -i *.deb, then I get error telling me no such file or directory. Do I point it at the folder somehow and if so how? Can you give me the actual terminal commands? I am sorry I am not much of an expert, in fact I am not much of a anything much, so need step by step! Thanks. On 14/08/17 20:07, Joseph Salisbury wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.13 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > -- 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/1710501 Title: can't open synaptic package manager Status in linux package in Ubuntu: Incomplete Bug description: When I try and open synaptic package man. I get this message. E: The package linux-image-4.10.0-23-generic needs to be reinstalled, but I can't find an archive for it. E: Internal error opening cache (1). Please report. Before this the software updater is showing 1 update but does not update it, I click on install and it says installing a few moments but then returns to showing one update to be done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710501/+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 1709220] Comment bridged from LTC Bugzilla
--- Comment From jhop...@us.ibm.com 2017-08-15 12:06 EDT--- Thanks! Seeing good improvements with this build based on some unixbench microbenchmarks: baseline = 4.10.0-32-generic RPT fixes = 4.10.0-32.36~lp1709220 Unixbench baseline RPT fixesimprovement SMToff SMT4SMToff SMT4SMToff SMT4 Execl ? single 656.2 963.0 1583.0 1507.1 141.2% 56.5% Execl ? multi 2522.9 6527.3 4720.2 11766.7 87.1% 80.3% Sysexec ? single 487.2 715.5 787.0 1082.2 61.5% 51.3% Sysexec ? multi 1783.0 4845.2 2738.6 8029.3 53.6% 65.7% Spawn ? single 1645.0 2546.8 2632.9 3168.8 60.1% 24.4% Spawn ? multi 5877.5 17688.8 8459.9 23650.1 43.9% 33.7% Note this was on a 4core DD1 system running at 1.6GHz. -- 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/1709220 Title: RPT related fixes missing in Ubuntu 16.04.3 Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: ---Problem Description--- The following patches are missing in the ubuntu 16.04.3 kernel https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156104.html https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156105.html https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/157130.html ---uname output--- 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = power9 ---Steps to Reproduce--- Did a fork and exec benchmark to look at the performance and they pointed to radix routines. Upstream commits mentioned: commitf7327e0ba3805470cced2acfa053e795362ee41d powerpc/mm/radix: Remove unnecessary ptesync commitf6b0df55cad252fedd60aa2ba75a0207d0006283 powerpc/mm/radix: Don't do page walk cache flush when doing full mm flush commita5998fcb92552a18713b6aa5c146aa400e4d75ee powerpc/mm/radix: Optimise tlbiel flush all case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709220/+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 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop
It was never set in the first place -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+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 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop
Also, now that I am back to kernel 4.10, wireless is back but the volume keys still do not work. Some other updates were performed as well so that might be a coincidence. -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+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 1709303] Re: linux: 4.10.0-33.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- 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/1709303 Title: linux: 4.10.0-33.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709304 derivatives: 1709305 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709303/+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 1710922] [NEW] Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream
You have been subscribed to a public bug:
== Comment: #0 - Daniel Henrique Barboza - 2017-08-08
09:13:31 ==
- Host information: Ubuntu 16.10 running upstream QEMU
$ uname -a
Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
$ cat /proc/cpuinfo
processor : 0
cpu : POWER8E (raw), altivec supported
clock : 2061.00MHz
revision: 2.1 (pvr 004b 0201)
(...)
timebase: 51200
platform: PowerNV
model : 8247-42L
machine : PowerNV 8247-42L
firmware: OPAL
- qemu command line that launched the Ubuntu 17.10 ppc64el guest:
sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-kvm
-device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
--machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
4G,slots=32,maxmem=32G -drive
file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id=drive-
virtio-disk0,cache=none -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -nographic
- guest information: Ubuntu 17.10 ppc64el:
root@ubuntu1710:~# uname -a
Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu1710:~#
- Problem: hotplugging a LMB generates a guest kernel Oops:
root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
(qemu)
(qemu) object_add memory-backend-ram,id=ram1,size=1G
(qemu) device_add pc-dimm,id=dimm1,memdev=ram1
(qemu) [ 126.850952] kernel BUG at
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
[ 126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
[ 126.851428] SMP NR_CPUS=2048
[ 126.851428] NUMA
[ 126.851546] pSeries
[ 126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi
crc32c_vpmsum virtio_blk
[ 126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic
#15-Ubuntu
[ 126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
[ 126.852828] task: c000fea8 task.stack: c000fe118000
[ 126.853000] NIP: c0350268 LR: c03501e0 CTR:
[ 126.853190] REGS: c000fe11b780 TRAP: 0700 Not tainted
(4.11.0-10-generic)
[ 126.853390] MSR: 8282b033
[ 126.853396] CR: 42002422 XER: 2000
[ 126.853672] CFAR: c03501e4 SOFTE: 1
[ 126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00
0001
[ 126.853672] GPR04: c000f9901480 c000ffe21c00 003e
0003
[ 126.853672] GPR08: 0002 0003 0003
303078302d303030
[ 126.853672] GPR12: 2200 cfb8 c0110008
c000fe1810c0
[ 126.853672] GPR16: c000fe050ea8 0010 c000fc30
c000fea0
[ 126.853672] GPR20: c000f951a1a4 0004 0001
0010
[ 126.853672] GPR24: 0001 c000f951a1a0 0004
[ 126.853672] GPR28: 0001 1000
00014000
[ 126.855221] NIP [c0350268] remove_memory+0xf8/0x100
[ 126.855338] LR [c03501e0] remove_memory+0x70/0x100
[ 126.855453] Call Trace:
[ 126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100
(unreliable)
[ 126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
[ 126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
[ 126.855959] [c000fe11bbf0] [c00a9af8]
handle_dlpar_errorlog+0xa8/0x170
[ 126.856118] [c000fe11bc60] [c00a9c54]
pseries_hp_work_fn+0x94/0xa0
[ 126.856275] [c000fe11bc90] [c01071d0]
process_one_work+0x2b0/0x5a0
[ 126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670
[ 126.856563] [c000fe11bdc0] [c0110164] kthread+0x164/0x1b0
[ 126.856695] [c000fe11be30] [c000b4e8]
ret_from_kernel_thread+0x5c/0x74
[ 126.856846] Instruction dump:
[ 126.856931] 6000 387f0060 48824b19 6000 38210040 e8010010 eb81ffe0
eba1ffe8
[ 126.857088] ebc1fff0 ebe1fff8 7c0803a6 4e800020 <0fe0> 3c4c0115
3842e890
[ 126.857243] ---[ end trace 76fab848b8f01d0a ]---
[ 126.859577]
Investigating the cause I've found this kernel commit:
commit 943db62c316c578f8e2cc6fb81a5f641096b29bf
Author: Nathan Fontenot
Date: Wed Feb 15 13:45:30 2017 -0500
powerpc/pseries: Revert 'Auto-online hotplugged memory'
This reverts commit ec999072442a ("powerpc/pseries: Auto-online
hotplugged memory"), and 9dc512819e4b ("powerpc: Fix unused fun
[Kernel-packages] [Bug 1710922] [NEW] Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream
Public bug reported:
== Comment: #0 - Daniel Henrique Barboza - 2017-08-08
09:13:31 ==
- Host information: Ubuntu 16.10 running upstream QEMU
$ uname -a
Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
$ cat /proc/cpuinfo
processor : 0
cpu : POWER8E (raw), altivec supported
clock : 2061.00MHz
revision: 2.1 (pvr 004b 0201)
(...)
timebase: 51200
platform: PowerNV
model : 8247-42L
machine : PowerNV 8247-42L
firmware: OPAL
- qemu command line that launched the Ubuntu 17.10 ppc64el guest:
sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-kvm
-device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
--machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
4G,slots=32,maxmem=32G -drive
file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id=drive-
virtio-disk0,cache=none -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -nographic
- guest information: Ubuntu 17.10 ppc64el:
root@ubuntu1710:~# uname -a
Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu1710:~#
- Problem: hotplugging a LMB generates a guest kernel Oops:
root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
(qemu)
(qemu) object_add memory-backend-ram,id=ram1,size=1G
(qemu) device_add pc-dimm,id=dimm1,memdev=ram1
(qemu) [ 126.850952] kernel BUG at
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
[ 126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
[ 126.851428] SMP NR_CPUS=2048
[ 126.851428] NUMA
[ 126.851546] pSeries
[ 126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi
crc32c_vpmsum virtio_blk
[ 126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic
#15-Ubuntu
[ 126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
[ 126.852828] task: c000fea8 task.stack: c000fe118000
[ 126.853000] NIP: c0350268 LR: c03501e0 CTR:
[ 126.853190] REGS: c000fe11b780 TRAP: 0700 Not tainted
(4.11.0-10-generic)
[ 126.853390] MSR: 8282b033
[ 126.853396] CR: 42002422 XER: 2000
[ 126.853672] CFAR: c03501e4 SOFTE: 1
[ 126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00
0001
[ 126.853672] GPR04: c000f9901480 c000ffe21c00 003e
0003
[ 126.853672] GPR08: 0002 0003 0003
303078302d303030
[ 126.853672] GPR12: 2200 cfb8 c0110008
c000fe1810c0
[ 126.853672] GPR16: c000fe050ea8 0010 c000fc30
c000fea0
[ 126.853672] GPR20: c000f951a1a4 0004 0001
0010
[ 126.853672] GPR24: 0001 c000f951a1a0 0004
[ 126.853672] GPR28: 0001 1000
00014000
[ 126.855221] NIP [c0350268] remove_memory+0xf8/0x100
[ 126.855338] LR [c03501e0] remove_memory+0x70/0x100
[ 126.855453] Call Trace:
[ 126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100
(unreliable)
[ 126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
[ 126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
[ 126.855959] [c000fe11bbf0] [c00a9af8]
handle_dlpar_errorlog+0xa8/0x170
[ 126.856118] [c000fe11bc60] [c00a9c54]
pseries_hp_work_fn+0x94/0xa0
[ 126.856275] [c000fe11bc90] [c01071d0]
process_one_work+0x2b0/0x5a0
[ 126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670
[ 126.856563] [c000fe11bdc0] [c0110164] kthread+0x164/0x1b0
[ 126.856695] [c000fe11be30] [c000b4e8]
ret_from_kernel_thread+0x5c/0x74
[ 126.856846] Instruction dump:
[ 126.856931] 6000 387f0060 48824b19 6000 38210040 e8010010 eb81ffe0
eba1ffe8
[ 126.857088] ebc1fff0 ebe1fff8 7c0803a6 4e800020 <0fe0> 3c4c0115
3842e890
[ 126.857243] ---[ end trace 76fab848b8f01d0a ]---
[ 126.859577]
Investigating the cause I've found this kernel commit:
commit 943db62c316c578f8e2cc6fb81a5f641096b29bf
Author: Nathan Fontenot
Date: Wed Feb 15 13:45:30 2017 -0500
powerpc/pseries: Revert 'Auto-online hotplugged memory'
This reverts commit ec999072442a ("powerpc/pseries: Auto-online
hotplugged memory"), and 9dc512819e4b ("powerpc: Fix unused function
warning 'lm
[Kernel-packages] [Bug 1700941] Re: Redpine vendor driver - Switching to AP mode causes kernel panic
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700941 Title: Redpine vendor driver - Switching to AP mode causes kernel panic Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Switching from STA to AP mode on RS9113 Redpine Wifi-BT combo device, system reports a kernel panic. The Redpine driver (ver. 1.2 RC12) doesn't track the Linux 4.4.69 stable release which introduced following patches to mac80211 subsystem: - mac80211: pass RX aggregation window size to driver - mac80211: pass block ack session timeout to to driver - mac80211: RX BA support for sta max_rx_aggregation_subframes The Redpine driver ver. 1.2RC12 needs to be updated to handle the changes introduced in the patch: - mac80211: pass block ack session timeout to to driver (more details here: http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=U buntu-4.4.0-82.105&id=0b2141bd007213cc9c4228786f773a3c35c41c56 and https://bugs.launc hpad.net/bugs/1692900) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1700941/+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 1627828] Re: iwl3945 crashes randomly
It looks like it is indeed a power management issue. Last threee days I made and manually run this script when I login; seba@D630:~$ cat $HOME/bin/iwl_power_save.sh sudo iw dev wlp12s0 get power_save sudo iw dev wlp12s0 set power_save off sudo iw dev wlp12s0 get power_save and I haven't had any issue. Everytime I boot power management is on and I switch it off. I will report in a week. Maybe I will also switch back to the HWE kernel to make sure this is reproducible with the ubuntu kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627828 Title: iwl3945 crashes randomly Status in linux package in Ubuntu: Confirmed Bug description: Out of nothing a once properly working 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) started to crash with: Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 :0c:00.0: Error sending C_POWER_TBL: time out after 500ms. Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 :0c:00.0: set power fail, ret = -110 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 :0c:00.0: Queue 2 stuck for 2500 ms. Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 :0c:00.0: On demand firmware reload Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: Hardware restart was requested Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 33 callbacks suppressed Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 :0c:00.0: Unable to initialize device after 5 attempts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seba 1421 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Sep 26 16:38:18 2016 HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03 InstallationDate: Installed on 2016-08-28 (29 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude D630 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://he
[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- 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/1709296 Title: linux: 4.4.0-93.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709296/+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 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: In Progress Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+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 1709303] Re: linux: 4.10.0-33.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1709303 Title: linux: 4.10.0-33.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709304 derivatives: 1709305 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709303/+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 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux-gke (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-gke (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+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 1685707] Re: [Feature] CNL:UFS 2.0
Thanks, moving this to In Progress since we are currently working on the 4.13 rebase for Artful (17.10). ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress -- 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/1685707 Title: [Feature] CNL:UFS 2.0 Status in intel: New Status in linux package in Ubuntu: In Progress Bug description: UFS 2.0 - Universal Flash Storage. The Universal Flash System (UFS) is the next generation storage standard that is to replace eMMC. UFS includes the feature set of eMMC as a subset and defines a unique feature set that provides low power consumption, high data throughput, low electromagnetic interference and optimization for mass memory subsystem efficiency. UFS adopts the latest technology from other industrial standards. UFS 1 and UFS 1.1 are already supported in upstream kernel. Add the delta features between 1.1 and 2.0. Target Kernel:4.13 Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1685707/+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 1645951] Re: [Feature] GLK:New device IDs
Moving this to Fix Committed for artful since we have a 4.12 kernel
available in artful-proposed.
f80e78aa11ad754de20104233af1ce4cea8f16a5 mfd: intel-lpss: Add Intel Gemini Lake
PCI IDs
v4.11-rc1~105^2~16
8f8983a5683623b62b339d159573f95a1fce44f3 usb: dwc3: pci: add Intel Gemini Lake
PCI ID
v4.10-rc3~1^2~21^2~3
a6450cb0388ee58659be5a54a7bfe5bff09532c7 mfd: lpc_ich: Add support for Intel
Gemini Lake SoC
v4.12-rc1~113^2~10
ae2520540cb0090eb8cdba559bcb6a82266f0308 pwm: lpss: Add Intel Gemini Lake PCI ID
v4.11-rc1~40^2^2~9
9827f9eb79c56424eac6409197a290601cf78eee i2c: i801: Add support for Intel
Gemini Lake
v4.11-rc1~72^2~10
e18a80acd1365e91e3efcd69942d9073936cf851 spi: pxa2xx: Add support for Intel
Gemini Lake
v4.11-rc1~153^2~7^2
6693f9f96a0936488dd7876b8079933786e27b1b pinctrl: intel: Add Intel Gemini Lake
pin controller support
v4.11-rc1~133^2~17
2d1956d0a4e0fd586e1c72c642929e15b5f23226 mmc: sdhci-pci: Add support for Intel
GLK
v4.10-rc1~127^2~59
340837f985c2cb87ca0868d4aa9ce42b0fab3a21 intel_th: pci: Add Gemini Lake support
v4.11-rc4~1^2~13^2
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => High
** Changed in: intel
Status: New => Fix Committed
** Changed in: intel
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1645951
Title:
[Feature] GLK:New device IDs
Status in intel:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Zesty:
Fix Released
Status in linux source package in Artful:
Fix Committed
Bug description:
Placeholder for GLK(Gemini Lake) IDs that should be published.
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?id=9d887e444fa59198e6c5b54d253e8f63fe08a808
commit f80e78aa11ad ("mfd: intel-lpss: Add Intel Gemini Lake PCI IDs")
USB device/xDCI: 0x31aa v4.10 8f8983a5683623b62b339d159573f95a1fce44f3
SPI-NOR: (0x3196) enumerated from LPC device | v4.12
|a6450cb0388ee58659be5a54a7bfe5bff09532c7 |
LPC: 0x3197 | v4.12 | a6450cb0388ee58659be5a54a7bfe5bff09532c7 |
PWM: 0x31c8 v4.11-rc1 ae2520540cb0090eb8cdba559bcb6a82266f0308
SMBus: 0x31d4 v4.11-rc1 9827f9eb79c56424eac6409197a290601cf78eee
I2C: 0x31ac 0x31ae 0x31b0 0x31b2 0x31b4 0x31b6 0x31b8 0x31ba v4.11-rc1
f80e78aa11ad
HS-UART: 0x31bc 0x31be 0x31c0 0x31ee v4.11-rc1 f80e78aa11ad
SPI: 0x31c2 0x31c4 0x31c6 v4.11-rc1 f80e78aa11ad, e18a80acd136
GPIO: INT3453 v4.11-rc1 6693f9f96a0936488dd7876b8079933786e27b1b
SD Card: 0x31ca v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226
eMMC: 0x31cc v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226
SDIO: 0x31d0 v4.10 2d1956d0a4e0fd586e1c72c642929e15b5f23226
NPK: 0x318e v4.11-rc4 340837f985
HW:
Gemini Lake
Removed: Not POR
UFS: 0x31ce
Upstream Schedule:
kernel: 4.13
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645951/+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 1709296] Re: linux: 4.4.0-93.116 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1709296 Title: linux: 4.4.0-93.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709296/+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 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+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 1710922] Re: Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1710922 Title: Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Daniel Henrique Barboza - 2017-08-08 09:13:31 == - Host information: Ubuntu 16.10 running upstream QEMU $ uname -a Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux $ cat /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) (...) timebase : 51200 platform : PowerNV model : 8247-42L machine : PowerNV 8247-42L firmware : OPAL - qemu command line that launched the Ubuntu 17.10 ppc64el guest: sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable- kvm -device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr- vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1 --machine pseries,accel=kvm,usb=off,dump-guest-core=off -m 4G,slots=32,maxmem=32G -drive file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id =drive-virtio-disk0,cache=none -device virtio-blk- pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio- disk0,bootindex=1 -nographic - guest information: Ubuntu 17.10 ppc64el: root@ubuntu1710:~# uname -a Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu1710:~# - Problem: hotplugging a LMB generates a guest kernel Oops: root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information (qemu) (qemu) object_add memory-backend-ram,id=ram1,size=1G (qemu) device_add pc-dimm,id=dimm1,memdev=ram1 (qemu) [ 126.850952] kernel BUG at /build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185! [ 126.851285] Oops: Exception in kernel mode, sig: 5 [#1] [ 126.851428] SMP NR_CPUS=2048 [ 126.851428] NUMA [ 126.851546] pSeries [ 126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi crc32c_vpmsum virtio_blk [ 126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic #15-Ubuntu [ 126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn [ 126.852828] task: c000fea8 task.stack: c000fe118000 [ 126.853000] NIP: c0350268 LR: c03501e0 CTR: [ 126.853190] REGS: c000fe11b780 TRAP: 0700 Not tainted (4.11.0-10-generic) [ 126.853390] MSR: 8282b033 [ 126.853396] CR: 42002422 XER: 2000 [ 126.853672] CFAR: c03501e4 SOFTE: 1 [ 126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00 0001 [ 126.853672] GPR04: c000f9901480 c000ffe21c00 003e 0003 [ 126.853672] GPR08: 0002 0003 0003 303078302d303030 [ 126.853672] GPR12: 2200 cfb8 c0110008 c000fe1810c0 [ 126.853672] GPR16: c000fe050ea8 0010 c000fc30 c000fea0 [ 126.853672] GPR20: c000f951a1a4 0004 0001 0010 [ 126.853672] GPR24: 0001 c000f951a1a0 0004 [ 126.853672] GPR28: 0001 1000 00014000 [ 126.855221] NIP [c0350268] remove_memory+0xf8/0x100 [ 126.855338] LR [c03501e0] remove_memory+0x70/0x100 [ 126.855453] Call Trace: [ 126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100 (unreliable) [ 126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0 [ 126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20 [ 126.855959] [c000fe11bbf0] [c00a9af8] handle_dlpar_errorlog+0xa8/0x170 [ 126.856118] [c000fe11bc60] [c00a9c54] pseries_hp_work_fn+0x94/0xa0 [ 126.856275] [c000fe11bc90] [c01071d0] process_one_work+0x2b0/0x5a0 [ 126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670 [ 126.856563]
[Kernel-packages] [Bug 1710941] [NEW] Bluetooth stopped working after update
Public bug reported: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A
[Kernel-packages] [Bug 1710947] [NEW] MacBookPro11, 4 patch no longer needed in 4.12.4+
Public bug reported: The patch applied in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no longer needed in artful kernels 4.12.0-11.12 and above, as a fix has made it in upstream 4.12.4+ and 4.13rc1+ kernels. The new fix is in arch/x86/pci/fixup.c, while the applied patch was in drivers/pci/quirks.c, so the conflict between the two may not be apparent using automatic merge tools. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1710947 Title: MacBookPro11,4 patch no longer needed in 4.12.4+ Status in linux package in Ubuntu: Incomplete Bug description: The patch applied in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no longer needed in artful kernels 4.12.0-11.12 and above, as a fix has made it in upstream 4.12.4+ and 4.13rc1+ kernels. The new fix is in arch/x86/pci/fixup.c, while the applied patch was in drivers/pci/quirks.c, so the conflict between the two may not be apparent using automatic merge tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710947/+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 1710947] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1710947 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710947 Title: MacBookPro11,4 patch no longer needed in 4.12.4+ Status in linux package in Ubuntu: Incomplete Bug description: The patch applied in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no longer needed in artful kernels 4.12.0-11.12 and above, as a fix has made it in upstream 4.12.4+ and 4.13rc1+ kernels. The new fix is in arch/x86/pci/fixup.c, while the applied patch was in drivers/pci/quirks.c, so the conflict between the two may not be apparent using automatic merge tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710947/+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 1710947] Re: MacBookPro11, 4 patch no longer needed in 4.12.4+
Logs not relevant, but I have confirmed that suspend works with a mainline kernel build that includes the new patch ** 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/1710947 Title: MacBookPro11,4 patch no longer needed in 4.12.4+ Status in linux package in Ubuntu: Confirmed Bug description: The patch applied in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587714 is no longer needed in artful kernels 4.12.0-11.12 and above, as a fix has made it in upstream 4.12.4+ and 4.13rc1+ kernels. The new fix is in arch/x86/pci/fixup.c, while the applied patch was in drivers/pci/quirks.c, so the conflict between the two may not be apparent using automatic merge tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710947/+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 1709929] Re: linux: 4.12.0-11.12 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-development-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-artful ** Tags removed: block-proposed -- 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/1709929 Title: linux: 4.12.0-11.12 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Confirmed Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.12.0-11.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1709929/+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 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
I've rolled three patches into a test kernel to test. I believe the best
fix is probably "cfq: Disable writeback throttling by default"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=142bbdfccc8b3e9f7342f2ce8422e76a3b45beae
The commits are:
4d608baac5f4e72b033a122b2d6d9499532c3afc "block: Initialize cfqq->ioprio_class
in cfq_get_queue()"
142bbdfccc8b3e9f7342f2ce8422e76a3b45beae "cfq: Disable writeback throttling by
default"
5be6b75610cefd1e21b98a218211922c2feb6e08 "cfq-iosched: fix the delay of
cfq_group's vdisktime under
iops mode"
You can download the packages from:
http://kernel.ubuntu.com/~cking/lp1709889/
Let me know if this helps with the 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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncu
[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset
It's included in 1.157.12, which was uploaded last week but is currently sitting in the unapproved queue. -- 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/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+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 1709616] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (5th Gen., 2017)
Two things: - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen. - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too! I can reproduce it on my local system which has "linux-image-generic- hwe-16.04" installed (4.10.0.32.34). Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference: https://patchwork.kernel.org/patch/9835823/ https://patchwork.kernel.org/patch/9835825/ So, will this bug be reopened or should I create a separate issue for the 16.04 HWE kernel? ** Bug watch added: Linux Kernel Bug Tracker #191181 https://bugzilla.kernel.org/show_bug.cgi?id=191181 -- 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/1709616 Title: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (5th Gen., 2017) Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours. The bug has been fixed upstream, see 6625914 ACPI / EC: Drop EC noirq hooks to fix a regression 9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129 (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181) and I hope this fix will make its way into a near-future kernel update to ubuntu :) Many thanks! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: micha 1783 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Wed Aug 9 12:55:20 2017 HibernationDevice: RESUME=UUID=d258b78e-8853-44ea-adac-c2c837859e92 InstallationDate: Installed on 2017-06-25 (44 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HQS03P00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-30-generic N/A linux-backports-modules-4.10.0-30-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET37W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HQS03P00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HQS03P00:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HQS03P00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HQS03P00 dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616/+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 1710967] [NEW] Following kernel upgrades, the bcmwl kernel module requires re-installation.
Public bug reported: I have recently noticed that when I perform `sudo apt update && sudo apt dist-upgrade -y` I'm having to separately run `sudo apt-get install --reinstall bcmwl-kernel-source` because otherwise the module isn't loading, and I have no wifi connections. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 15 21:11:40 2017 InstallationDate: Installed on 2017-04-06 (131 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1710967 Title: Following kernel upgrades, the bcmwl kernel module requires re- installation. Status in bcmwl package in Ubuntu: New Bug description: I have recently noticed that when I perform `sudo apt update && sudo apt dist-upgrade -y` I'm having to separately run `sudo apt-get install --reinstall bcmwl-kernel-source` because otherwise the module isn't loading, and I have no wifi connections. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 15 21:11:40 2017 InstallationDate: Installed on 2017-04-06 (131 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1710967/+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 1709889] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2017-08-15 16:36 EDT---
I will start a test with that kernel tomorrow. I will be adding my debug code
to it, so that I can track delayed I/Os if they occur. I see you posted source
code, so I can do that easily.
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any previous data. A partition table is optional, in my testing I have
none.
Also, it may b
[Kernel-packages] [Bug 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- 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/1710976 Title: Livepatch motd enhancement to show people how livepatch can help protect systems. Status in linux package in Ubuntu: Incomplete Status in update-notifier package in Ubuntu: New Bug description: This is a request to add an enhancement in our motd.d to inform users of the following: 1) that livepatch is available for their platform/kernel if they don't have it set up and installed right now. 2) When a system is protected by livepatch, and the system is currently patched (i.e., canonical-livepatch has active patches applied). 3) when a system is protected by livepatch and no livepatches exist yet for the kernel version, a single line message of 'This system is protected by canonical-livepatch." or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710976/+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 1710976] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1710976 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710976 Title: Livepatch motd enhancement to show people how livepatch can help protect systems. Status in linux package in Ubuntu: Incomplete Status in update-notifier package in Ubuntu: New Bug description: This is a request to add an enhancement in our motd.d to inform users of the following: 1) that livepatch is available for their platform/kernel if they don't have it set up and installed right now. 2) When a system is protected by livepatch, and the system is currently patched (i.e., canonical-livepatch has active patches applied). 3) when a system is protected by livepatch and no livepatches exist yet for the kernel version, a single line message of 'This system is protected by canonical-livepatch." or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710976/+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 1710978] [NEW] bluetooth stack looses connection to bluetooth devices
Public bug reported: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1709303] Re: linux: 4.10.0-33.37 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709304 derivatives: 1709305 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Friday, 11. August 2017 11:32 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 15. August 2017 21:04 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709304 derivatives: 1709305 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 15. August 2017 21:04 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1709303 Title: linux: 4.10.0-33.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709304 derivatives: 1709305 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709303/+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 1709296] Re: linux: 4.4.0-93.116 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Friday, 11. August 2017 16:31 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 15. August 2017 21:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 15. August 2017 21:02 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1709296 Title: linux: 4.4.0-93.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1709297 derivatives: 1709298,1709299,1709300,1709301 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709296/+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
