[Kernel-packages] [Bug 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1638996 Title: apparmor's raw_data file in securityfs is sometimes truncated Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Hi, It looks like sometimes apparmor's securityfs output is sometimes truncated, root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# ls -al total 0 drwxr-xr-x 3 root root 0 Nov 3 16:45 . drwxr-xr-x 13 root root 0 Nov 3 16:44 .. -r--r--r-- 1 root root 0 Nov 3 16:45 attach -r--r--r-- 1 root root 0 Nov 3 16:45 mode -r--r--r-- 1 root root 0 Nov 3 16:45 name drwxr-xr-x 3 root root 0 Nov 3 16:45 profiles -r--r--r-- 1 root root 0 Nov 3 16:45 raw_abi -r--r--r-- 1 root root 46234 Nov 3 16:45 raw_data -r--r--r-- 1 root root 0 Nov 3 16:45 raw_hash -r--r--r-- 1 root root 0 Nov 3 16:45 sha1 root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# cat raw_data > /tmp/out root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# ls -al /tmp/out -rw-r--r-- 1 root root 4009 Nov 3 16:55 /tmp/out and 2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/ 2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size of the policy 2016-11-03 10:59:20 @jjohansen tych0: hrmm interesting, can you zip up the /tmp/out file so I can see it looks like a complete policy file? 2016-11-03 11:00:03 @jjohansen something is definitely not right there. hrmmm 2016-11-03 11:00:26 @jjohansen the size is set by the input buffer size 2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out 2016-11-03 11:00:36 tych0 yeah, i assume 2016-11-03 11:01:15 @jjohansen my guess is something is messing up in the seq_file walk of the policy 2016-11-03 11:02:38 @jjohansen tych0: yep the file is truncated, can you open a bug and I will start looking for it 2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux? 2016-11-03 11:03:35 @jjohansen tych0: yeah for now, just linux 2016-11-03 11:03:43 @jjohansen we can add others if needed later 2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue sometimes it works and sometimes it doesn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638996/+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 1660832] Re: unix domain socket cross permission check failing with nested namespaces
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- 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/1660832 Title: unix domain socket cross permission check failing with nested namespaces Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Confirmed Status in linux source package in Yakkety: Fix Released Status in apparmor source package in Zesty: Confirmed Status in linux source package in Zesty: Fix Released Bug description: When using nested namespaces policy within the nested namespace is trying to cross validate with policy outside of the namespace that is not visible to it. This results the access being denied and with no way to add a rule to policy that would allow it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1660834] Re: apparmor label leak when new label is unused
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1660834 Title: apparmor label leak when new label is unused Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: When a new label is created, it is created with a proxy in a circular ref count that is broken by replacement. However if the label is not used it will never be replaced and the circular ref count will never be broken resulting in a leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1660833] Re: apparmor reference count bug in label_merge_insert()
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1660833 Title: apparmor reference count bug in label_merge_insert() Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: @new does not have a reference taken locally and should not have its reference put locally either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1660836 Title: apparmor auditing denied access of special apparmor .null fi\ le Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: When an fd is disallowed from being inherited during exec, instead of closed it is duped to a special apparmor/.null file. This prevents the fd from being reused by another file in case the application expects the original file on a give fd (eg stdin/stdout etc). This results in a denial message like [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" op\ eration="file_inherit" namespace="root//lxd-t_" profile="/sbin/dhc\ lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" denied_m\ ask="wr" fsuid=165536 ouid=165536 Further access to the fd is resultin in the rather useless denial message of [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" op\ eration="file_perm" namespace="root//lxd-t_" profile="/sbin/dhclie\ nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" denied_\ mask="w" fsuid=165536 ouid=0 since we have the original denial, the noisy and useless .null based denials can be skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1660840 Title: apparmor oops in bind_mnt when dev_path lookup fails Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Bind mounts can oops when devname lookup fails because the devname is unintialized and used in auditing the denial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
Please describe the failure, including the logs so I can analyze. Just because the container fails to start does not mean that the fix is bad. There can be other issues that result in the failure. Specifically this bug is for the denial message seen in comment #5 and not the denied messages (unlink) in comment #9, which are a separate issue. It appears to be working for me, with yakkety and zesty -- 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/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in tor package in Ubuntu: New Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Fix Released Status in tor source package in Xenial: New Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Confirmed Status in tor source package in Yakkety: New Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1660849] Re: apparmor refcount leak of profile namespace when removing profiles
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1660849 Title: apparmor refcount leak of profile namespace when removing profiles Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: When doing profile removal, the parent ns of the profiles is taken, but the reference isn't being put, resulting in the ns never being freed even after it is removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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 1656121] Re: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- 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/1656121 Title: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace Status in AppArmor: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is based on a discussion with jjohansen on IRC. While working on a feature for snapd (https://github.com/snapcore/snapd/pull/2624) we came across an unexpected EACCES that only seems to happen when apparmor is in the loop. The kernel log shows something interesting. The full log is available here: http://paste.ubuntu.com/23789099/ Jan 12 23:16:43 autopkgtest kernel: [ 498.616822] audit: type=1400 audit(1484259403.009:67): apparmor="ALLOWED" operation="open" info="Failed name lookup - disconnected path" error=-13 profile="snap .test-snapd-tools.cmd//null-/usr/bin/snap//null-/usr/lib/snapd/snap- confine" name="" pid=25299 comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 The code that triggers this is reproduced below (also visible here https://github.com/snapcore/snapd/pull/2624/files) +void sc_reassociate_with_pid1_mount_ns() +{ +int init_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1; +int self_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1; + +debug("checking if the current process shares mount namespace" + "with the init process"); + +init_mnt_fd = open("/proc/1/ns/mnt", + O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH); +if (init_mnt_fd < 0) { +die("cannot open mount namespace of the init process (O_PATH)"); +} +self_mnt_fd = open("/proc/self/ns/mnt", + O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH); +if (self_mnt_fd < 0) { +die("cannot open mount namespace of the current process (O_PATH)"); +} +char init_buf[128], self_buf[128]; +memset(init_buf, 0, sizeof init_buf); +if (readlinkat(init_mnt_fd, "", init_buf, sizeof init_buf) < 0) { +die("cannot perform readlinkat() on the mount namespace file " +"descriptor of the init process"); +} +memset(self_buf, 0, sizeof self_buf); +if (readlinkat(self_mnt_fd, "", self_buf, sizeof self_buf) < 0) { +die("cannot perform readlinkat() on the mount namespace file " +"descriptor of the current process"); +} +if (memcmp(init_buf, self_buf, sizeof init_buf) != 0) { +debug("the current process does not share mount namespace with " + "the init process, re-association required"); +// NOTE: we cannot use O_NOFOLLOW here because that file will always be a +// symbolic link. We actually want to open it this way. +int init_mnt_fd_real +__attribute__ ((cleanup(sc_cleanup_close))) = -1; +init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC); +if (init_mnt_fd_real < 0) { +die("cannot open mount namespace of the init process"); +} +if (setns(init_mnt_fd_real, CLONE_NEWNS) < 0) { +die("cannot re-associate the mount namespace with the init process"); +} +} else { +debug("re-associating is not required"); +} +} The specific part that causes the error is: + init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC); The call to open returns -1 and errno set to 13 (EACCES) despite using attach_disconnected. The code in question is executed from a seguid root executable that runs under a complain-mode profile (it is started from a process that is already confined with such a profile). All of the profiles are using attach_disconnected. I can reproduce this issue each time by running: spread -debug -v qemu:ubuntu-16.04-64:tests/regression/lp-1644439 Against the code in this pull request: https://github.com/snapcore/snapd/pull/2624 Which is git://github.com/zyga/snapd in the "reassociate-fix" branch Appropriate qemu images can be made using instructions from: https://github.com/zyga/spread-qemu-images I'm also happy to try any test kernels as I can easily run those. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1656121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1669807] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1669807 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/1669807 Title: Allow Unity8 to run inside Virtualbox Status in linux package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Fix Released Bug description: Vboxvideo lacks PRIME support. A patch has been sent upstream. https://www.virtualbox.org/pipermail/vbox-dev/2017-March/014293.html It may take some time until that hits the repository. I attached a patch I tested on zesty and allows unity8 to run virtualbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669807/+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 1669807] Re: Allow Unity8 to run inside Virtualbox
@kernel folks, please look at: https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?id=bcdf0a6d1924367b99cf5c30b5f0e8f9bd0cb079 ** Package changed: virtualbox (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Fix Released => Fix Committed ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Changed in: virtualbox (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1669807 Title: Allow Unity8 to run inside Virtualbox Status in linux package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Fix Released Bug description: Vboxvideo lacks PRIME support. A patch has been sent upstream. https://www.virtualbox.org/pipermail/vbox-dev/2017-March/014293.html It may take some time until that hits the repository. I attached a patch I tested on zesty and allows unity8 to run virtualbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669807/+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 1591053] Re: PS/2 mouse does not work on Dell embedded computer
** Changed in: hwe-next 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/1591053 Title: PS/2 mouse does not work on Dell embedded computer Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Bug description: [Steps] 1. Plug in a PS/2 mouse to PS/2 mouse jack 2. Boot system (note that PS/2 does not support hotplug so device must be cold booted) 3. Check if PS/2 mouse works [Expected result] PS/2 mouse should work [Actual] PS/2 mouse does not work in Ubuntu. * Note that: - PS/2 keyboard does not have this issue, works correctly in both BIOS & OS - PS/2 mouse works correctly only in BIOS and does not work in OS To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1591053/+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 1669807] [NEW] Allow Unity8 to run inside Virtualbox
You have been subscribed to a public bug: Vboxvideo lacks PRIME support. A patch has been sent upstream. https://www.virtualbox.org/pipermail/vbox-dev/2017-March/014293.html It may take some time until that hits the repository. I attached a patch I tested on zesty and allows unity8 to run virtualbox. ** Affects: linux (Ubuntu) Importance: High Status: Fix Committed ** Tags: patch -- Allow Unity8 to run inside Virtualbox https://bugs.launchpad.net/bugs/1669807 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1606129] Re: [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84]
this is fixed in 4.8 and up, bumping i915_bpo to 4.8 is not going to happen so essentially wontfixed for 4.4. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hwe-next 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/1606129 Title: [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: i915_bpo in Xenial doesn't support certain graphic chips which already in used for OEM projects. We either got black screen or hardware acceleration doesn't work. There's a series of patches from up to v4.8 kernel need to be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1606129/+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 1609742] Re: [i915_bpo] Sync with v4.7
** Changed in: linux (Ubuntu) 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/1609742 Title: [i915_bpo] Sync with v4.7 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Upstream v4.7 added Kabylake support for DMC firmware and a couple of bugfixes. Sync i915_bpo with it and un-revert a commit which got fixed upstream. Also drop two workarounds: drm/i915/edp: Add WaKVMNotificationOnConfigChange:bdw - it's only for BDW which doesn't use i915_bpo drm/i915/skl: Add WAC6entrylatency - it didn't end up in 4.7 rest of the diff consists of minor style changes between the preliminary set of workarounds in the previous update and v4.7. This has been tested on KBL & SKL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609742/+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 1652499] Re: Cannot hibernate properly ; systemd-sleep hangs
** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652499 Title: Cannot hibernate properly ; systemd-sleep hangs Status in linux package in Ubuntu: Confirmed Bug description: Hello, on recent kernels including 4.4.0-57-generic, I observe more often than not the following behaviour after clicking the Hibernate button in XFCE4 interface : 1. Screen becomes black 2. No hard drive activity, which is suspicious 3. Moving the mouse shows the "locked screen" lightdm prompt 4. Unlocking the session, I get back to it ; things seems to work as usual except the ethernet connection is down 5. ps aux | grep hib shows that there is a /lib/systemd/systemd-sleep hibernate running 6. if I kill this process, the computer finally hibernates 7. booting the computer again resumes the session (with networking enabled) but with persistent graphical glitches on some parts of the interface, most visibly a. in my terminal, all occurrences of the letter b are scrambled b. in all windows, the maximise/minimise/close buttons are scrambled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu13 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 25 10:36:33 2016 InstallationDate: Installed on 2016-09-07 (108 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652499/+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 1532127] Re: [SKL] Disable DP MST
DP MST works fine in later kernels ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1532127 Title: [SKL] Disable DP MST Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Won't Fix Bug description: Turns out that Displayport Multi-Stream Transport has not been implemented for Skylake, causing blank screen issues (now that hangs have been fixed..) when plugging external displays to outputs connected to the MST hub. Disabling DP MST allows at least one of the outputs to work, if there are several behind the hub. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1532127/+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 1114872] Re: [hsw backport] kernel oops, Xorg freeze
assuming this has fixed itself since ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1114872 Title: [hsw backport] kernel oops, Xorg freeze Status in Linux: Confirmed Status in OEM Priority Project: Invalid Status in fglrx-installer package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: [ 144.450359] Process Xorg (pid: 2629, threadinfo 880043272000, task 88004094) [ 144.450429] Stack: [ 144.450450] 88006e64 880065bc6800 8800432739a8 a0adb131 [ 144.450530] 8817 8800 8133b4b4 [ 144.450608] 880043273958 0001 882e 43273968 [ 144.450686] Call Trace: [ 144.450734] [] haswell_crtc_enable+0x531/0x6d0 [i915_hsw] [ 144.450802] [] ? snprintf+0x34/0x40 [ 144.450870] [] intel_set_mode+0x6e7/0xa40 [i915_hsw] [ 144.450952] [] intel_crtc_set_config+0x83d/0x960 [i915_hsw] [ 144.451041] [] drm_mode_setcrtc+0x308/0x560 [drm] [ 144.451118] [] ? intel_crtc_gamma_set+0x63/0x70 [i915_hsw] [ 144.451198] [] drm_ioctl+0x47c/0x540 [drm] [ 144.451274] [] ? drm_mode_setplane+0x3b0/0x3b0 [drm] [ 144.451339] [] ? _raw_spin_unlock_bh+0x19/0x20 [ 144.451400] [] do_vfs_ioctl+0x8a/0x340 [ 144.451454] [] sys_ioctl+0x91/0xa0 [ 144.451505] [] system_call_fastpath+0x16/0x1b [ 144.451559] Code: e0 b8 b1 a0 31 c0 e8 16 e6 57 e0 e9 7f fe ff ff 90 55 48 89 e5 53 48 83 ec 08 0f 1f 44 00 00 89 f0 89 d3 48 8b 84 c7 30 22 00 00 <8b> 90 68 03 00 00 48 8b 07 48 8b 80 48 03 00 00 48 8b 40 08 f6 [ 144.451924] RIP [] assert_fdi_tx+0x1a/0xa0 [i915_hsw] [ 144.452005] RSP [ 144.452038] CR2: 036c ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2~ppa10 ProcVersionSignature: Ubuntu 3.5.0-21.32~precise1-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sun Feb 3 17:16:40 2013 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-watauga2-precise-amd64-norecovery-20121213-1 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Haswell Integrated Graphics Controller [8086:0406] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2112] Advanced Micro Devices [AMD] nee ATI Device [1002:6611] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2112] InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20121213-14:54 MachineType: Intel Corporation Shark Bay Client platform MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, user) LANG=C SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=31d7b71f-6b0a-4a24-aae5-954441657611 ro text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2012 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0100.R02.1211210527 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Grays Reef dmi.board.vendor: Intel Corp. dmi.board.version: 3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0100.R02.1211210527:bd11/21/2012:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnGraysReef:rvr3:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental:
[Kernel-packages] [Bug 1669127] hainzel (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/hainzel__4.10.0-11.13__2017-03-06_06-11-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1669127] hainzel (amd64) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/hainzel__4.10.0-11.13__2017-03-06_05-13-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1591053] Re: PS/2 mouse does not work on Dell embedded computer
** Changed in: hwe-next Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1591053 Title: PS/2 mouse does not work on Dell embedded computer Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Steps] 1. Plug in a PS/2 mouse to PS/2 mouse jack 2. Boot system (note that PS/2 does not support hotplug so device must be cold booted) 3. Check if PS/2 mouse works [Expected result] PS/2 mouse should work [Actual] PS/2 mouse does not work in Ubuntu. * Note that: - PS/2 keyboard does not have this issue, works correctly in both BIOS & OS - PS/2 mouse works correctly only in BIOS and does not work in OS To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1591053/+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 1439608] Re: [Dell Inspiron 7347] Cannot select multiple file by click and drag with two fingers
** Changed in: hwe-next Assignee: Phidias (phidias-chiang) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439608 Title: [Dell Inspiron 7347] Cannot select multiple file by click and drag with two fingers Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: CID: 201406-15234 Dell Inspiron 7347 User cannot do the "click and drag" on the clickpad with more than one finger on 14.04.2 (3.16 kernel) Steps: 1. Open your home directory. 2. Press the clickpad with one finger, and move the cursor across several files with another finger 3. Put a finger on the clickpad and try to move the cursor across several files after click on the clickpad with another hand. Expected results: * You should be able to select multiple files Actual result: * Cursor won't move, you can't select multiple files with step 2 or 3, the only way to do this selection is to press the clickpad with one finger and move the cursor with it (or do a double tap and hold) BTW, I'm not sure if it's a by-design feature. ubuntu@201406-15234:~$ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ DLL0674:00 06CB:75DB UNKNOWNid=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ubuntu@201406-15234:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 2 05:46:21 2015 InstallationDate: Installed on 2015-04-02 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1631 F pulseaudio /dev/snd/controlC1: ubuntu 1631 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b6c7cf5c-0a78-408f-862d-c62ba28c98ac InstallationDate: Installed on 2015-04-02 (4 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 7347 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=0fe5720c-22b1-4853-b50a-38b2e444332b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 01V010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd06/30/2014:svnDellInc.:pnInspiron7347:pvr00h:rvnDellInc.:rn01V010:rvrD02:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 7347 dmi.product.version: 00h dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1439608/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1616763] Re: System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]
** Changed in: linux-firmware (Ubuntu) Assignee: Ying-Chun Liu (paulliu) => (unassigned) ** Changed in: hwe-next Assignee: Ying-Chun Liu (paulliu) => Kai-Heng Feng (kaihengfeng) -- 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/1616763 Title: System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260] Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: Intel 8260 BT module can't pair to BT 4.0 keyboard or mouse. There's already a new firmware to fix this issue and has passed our test: commit a4bbc8112cc04fcc0e0861e8b72197b6cb83ab83 Author: Tedd Ho-Jeong AnDate: Wed Jun 8 12:53:26 2016 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616763/+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 1669671] Re: ubuntu_lttng_smoke_test failed on Yakkety arm64
Hello Joseph, Just tested with -39, YES, this issue can be reproduced http://pastebin.ubuntu.com/24122809/ Colin, please feel free to use ms10-34-mcdivittB0-kernel to debug this, this system won't be used if we're not re-spinning any 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/1669671 Title: ubuntu_lttng_smoke_test failed on Yakkety arm64 Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.8.0-40.43 Yakkety on arm64 Failed test case: == lttng smoke test trace open/close system calls == FAILED (did not trace any open system calls) Summary: 14 passed, 1 failed Complete log: http://pastebin.ubuntu.com/24100141/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669671/+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 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
** Changed in: hwe-next/xenial Assignee: Phidias (phidias-chiang) => Anthony Wong (anthonywong) ** Changed in: hwe-next/yakkety Assignee: Phidias (phidias-chiang) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Phidias (phidias-chiang) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs Status in HWE Next: New Status in HWE Next xenial series: New Status in HWE Next yakkety series: New Status in linux package in Ubuntu: Triaged Bug description: This device is appearing in some OEM machines. WORKAROUND: sudo apt-get install build-essential linux-headers-generic git git clone https://github.com/hadess/rtl8723as.git cd rtl8723as make sudo make install sudo depmod -a sudo modprobe r8723bs cat /sys/bus/sdio/devices/mmc1:0001:1/* 0x07 0xb723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory sdio:c07v024CdB723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory SDIO_CLASS=07 SDIO_ID=024C:B723 MODALIAS=sdio:c07v024CdB723 0x024c WORKAROUND 2: Install this DKMS driver package: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963 InstallationDate: Installed on 2016-05-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer One S1002 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.name: Popcorn dmi.board.vendor: Acer dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: One S1002 dmi.product.version: 1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+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 1578305] Re: Stoney powerplay support
** Changed in: hwe-next 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/1578305 Title: Stoney powerplay support Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: I'd love to submit a patch right now but I can't since the clone is taking way too long... The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83 you need to insert case CHIP_STONEY: before CHIP_CARRIZO to get ST to successfully init with the amdgpu module. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: amd1533 F pulseaudio /dev/snd/controlC0: amd1533 F pulseaudio CurrentDesktop: Unity Date: Wed May 4 12:35:10 2016 HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917 InstallationDate: Installed on 2016-05-04 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enx54b80aefee18 no wireless extensions. enx1a1b9c20 no wireless extensions. lono wireless extensions. MachineType: AMD Gardenia-ST ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 amdgpu.powerplay=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: WGY5930N_Weekly_15_09_3 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Gardenia-ST dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Gardenia-ST dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1578305/+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 1512997] Re: Support Edge Gateway's WIFI LED
** Changed in: hwe-next/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/1512997 Title: Support Edge Gateway's WIFI LED Status in HWE Next: Fix Released Status in HWE Next vivid series: Fix Released Status in HWE Next xenial series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code for controlling LED in mwifiex). It is requested to be ON and OFF when the radio is on and off accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1512997/+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 1483628] Re: e1000e hangs the system on suspend
** Changed in: hwe-next Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1483628 Title: e1000e hangs the system on suspend Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: System hangs on suspend if ethernet cable is plugged in. Suspend would work again either by removing cable or e1000e.ko. Kernel version: 3.19.0-25.26 Device info: 00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:15b7] (rev 31) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483628/+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 1493674] Re: [Dell Inspiron 3558] System can't pass the suspend 30 cycles stress test
** Changed in: hwe-next Assignee: Phidias (phidias-chiang) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Phidias (phidias-chiang) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1493674 Title: [Dell Inspiron 3558] System can't pass the suspend 30 cycles stress test Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: CID: 201411-16162 Dell Insprion 3558 This system can pass a single suspend test but can't pass the 30 cycles suspend stress test. It will hang somewhere in the process (not sure if it's resuming or suspending). With: * screen off * keyboard not responding * does not respond to power button, you can't wake it up with that However If you hold the power button for a while, you will hear that the HDD stop spinning. Steps: 1. Install 14.04.2 + updates (3.16.0-46) 2. Run the 30 cycle S3 stress test with checkbox Expected result: * System works fine after this stress test Actual result: * System hung during testing. Reproduce rate: > 80% ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-46-generic 3.16.0-46.62~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 9 00:13:04 2015 InstallationDate: Installed on 2015-08-21 (18 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3664 F pulseaudio /dev/snd/controlC0: ubuntu 3664 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9fa2e333-2ce2-4516-bac7-66262283cd6e InstallationDate: Installed on 2015-08-21 (19 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3558 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-46-generic root=UUID=3010c416-a6ed-4b18-93ea-09ed5c3ebd5a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: linux-restricted-modules-3.16.0-46-generic N/A linux-backports-modules-3.16.0-46-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 032010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3558:pvr01:rvnDellInc.:rn032010:rvrD02:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1493674/+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 1560835] Re: Enable multitouch function on precision touchpad for Vivid
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Wily) Status: In Progress => Won't Fix -- 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/1560835 Title: Enable multitouch function on precision touchpad for Vivid Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Won't Fix Status in linux source package in Xenial: Fix Released Bug description: [Impact] Multitouch feature is not enabled on some platforms with new Win8 precision touchpad because it can't fetch the report from the device. In worst case it can even break the multitouch device. [Fix] There's one commit to fix this issue: commit 171202b6fee80d777d18bb8a53b3e4361d97f389 Author: Mika WesterbergDate: Wed Oct 7 15:33:43 2015 +0300 HID: multitouch: Fetch feature reports on demand for Win8 devices In addition, this commit may cause some issue on ELAN touchpad, and there's another commit to improve the fix: commit e47b1e449ea70d76c38a50c04cde60a72bc7ebde Author: Benjamin Tissoires Date: Tue Dec 1 12:41:38 2015 +0100 HID: multitouch: fix input mode switching on some Elan panels Both commits can be clean picked, and are already in Xenial. [Test] The patched Vivid kernel is tested on two platforms and both worked before and after suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1560835/+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 1532127] Re: [SKL] Disable DP MST
** Changed in: linux (Ubuntu Wily) Status: Triaged => Won't Fix ** Changed in: hwe-next 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/1532127 Title: [SKL] Disable DP MST Status in HWE Next: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Won't Fix Bug description: Turns out that Displayport Multi-Stream Transport has not been implemented for Skylake, causing blank screen issues (now that hangs have been fixed..) when plugging external displays to outputs connected to the MST hub. Disabling DP MST allows at least one of the outputs to work, if there are several behind the hub. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1532127/+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 1647936] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1647936 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/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+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 1670247] [NEW] Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5 card
Public bug reported: == Comment: #0 - Carol L. Soto- 2017-03-03 22:23:11 == ---Problem Description--- Mellanox CX4/CX5 IB if running IPoIB in connected mode, it does not have the hw checksum so when running IPoIB in power system the performance is low. with iperf and 4 threads we get [ 8] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48536 [ 4] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48538 [ 5] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48540 [ 6] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48542 [ 8] 0.0-10.0 sec 9.07 GBytes 7.79 Gbits/sec [ 4] 0.0-10.0 sec 9.16 GBytes 7.87 Gbits/sec [ 5] 0.0-10.0 sec 9.13 GBytes 7.84 Gbits/sec [ 6] 0.0-10.0 sec 9.18 GBytes 7.88 Gbits/sec [SUM] 0.0-10.0 sec 36.5 GBytes 31.4 Gbits/sec if we add the following patches: >From 68201fbbb04a030864f8560b05d43d8019f7f8df Mon Sep 17 00:00:00 2001 From: Michael Ellerman Date: Thu, 11 Aug 2016 16:03:14 +1000 Subject: powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS >From b492f7e4e07a28e706db26cf4943bb0911435426 Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:10:55 +1100 Subject: powerpc/64: Fix checksum folding in csum_tcpudp_nofold and ip_fast_csum_nofold >From d4fde568a34a93897dfb9ae64cfe9dda9d5c908c Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:15:42 +1100 Subject: powerpc/64: Use optimized checksum routines on little-endian then I can get with iperf [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 23.0 GBytes 19.7 Gbits/sec [ 6] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 5] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 7] 0.0-10.0 sec 22.9 GBytes 19.6 Gbits/sec [SUM] 0.0-10.0 sec 91.7 GBytes 78.7 Gbits/sec Contact Information = Carol Soto/cls...@us.ibm.com ---uname output--- 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:22:53 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Need a power system and Mellanox CX4 IB card. Machine Type = P8 ---Steps to Reproduce--- just run iperf with IPoIB in connected mode and will see aroung 30Gbits/sec. If we add the patches then we can get more than 70Gbits/sec. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-152252 severity-high targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-152252 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670247 Title: Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5 card Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Carol L. Soto - 2017-03-03 22:23:11 == ---Problem Description--- Mellanox CX4/CX5 IB if running IPoIB in connected mode, it does not have the hw checksum so when running IPoIB in power system the performance is low. with iperf and 4 threads we get [ 8] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48536 [ 4] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48538 [ 5] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48540 [ 6] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48542 [ 8] 0.0-10.0 sec 9.07 GBytes 7.79 Gbits/sec [ 4] 0.0-10.0 sec 9.16 GBytes 7.87 Gbits/sec [ 5] 0.0-10.0 sec 9.13 GBytes 7.84 Gbits/sec [ 6] 0.0-10.0 sec 9.18 GBytes 7.88 Gbits/sec [SUM] 0.0-10.0 sec 36.5 GBytes 31.4 Gbits/sec if we add the following patches: From 68201fbbb04a030864f8560b05d43d8019f7f8df Mon Sep 17 00:00:00 2001 From: Michael Ellerman Date: Thu, 11 Aug 2016 16:03:14 +1000 Subject: powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS From b492f7e4e07a28e706db26cf4943bb0911435426 Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:10:55 +1100 Subject: powerpc/64: Fix checksum folding in csum_tcpudp_nofold and ip_fast_csum_nofold From d4fde568a34a93897dfb9ae64cfe9dda9d5c908c Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:15:42 +1100 Subject: powerpc/64: Use optimized checksum routines on little-endian then I can get with iperf [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 23.0 GBytes 19.7 Gbits/sec [ 6] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 5] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 7] 0.0-10.0 sec 22.9 GBytes 19.6 Gbits/sec [SUM] 0.0-10.0 sec 91.7 GBytes 78.7 Gbits/sec Contact
[Kernel-packages] [Bug 1557989] Re: having btrfs installed as the fs is causing a crash when trying to install the intel-microcode package
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557989 Title: having btrfs installed as the fs is causing a crash when trying to install the intel-microcode package Status in linux package in Ubuntu: Expired Bug description: I am able to reproduce a bug which causes a kernel panic when the following conditions are met: 1. Xubuntu 16.04 beta 1 is installed 2. btrfs is used as the filesystem 3. The intel-microcode package is installed after the initial system setup is complete I have got an actual photo of the screen when the crash happens as I was unable to locate the correct log file where this would have shown up. I can provide any logs that may be useful ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.7 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Mar 16 10:00:14 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-15 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guts 1798 F pulseaudio /dev/snd/controlC0: guts 1798 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-28 (90 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Vostro 3300 NonfreeKernelModules: nvidia_uvm nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=2ca3e37e-f0ef-40ea-b0af-041ef5aaeee8 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3300:pvrA12:rvnDellInc.:rn07JC8T:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Vostro 3300 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557989/+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 1617900] Re: Headset mic detection on some variants of Dell Inspiron 5468
** 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/1617900 Title: Headset mic detection on some variants of Dell Inspiron 5468 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: On some Dell Inspiron 5468 variants, headset mic device is not detected. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1617900/+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 1609606] Re: Mic mute hotkey does not work on usb keyboard [03f0:2f4a]
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609606 Title: Mic mute hotkey does not work on usb keyboard [03f0:2f4a] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: Press the MIC mute function key on the USB keyboard [03f0:2f4a] doesn't emit any keyevent nor acpi event. T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 23 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=2f4a Rev=00.10 S: Manufacturer=Chicony S: Product=HP Business Slim Keyboard C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1609606/+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 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616318 Title: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter to Dekstop. 3) Insert the USB 3.1 key in the thunderbolt port. 4) Remove the USB 3.1 key from the thunderbolt port. 5) Insert the USB 3.1 key in the thunderbolt port. Expected results: Can detect the USB 3.1 key and system will not hang. Actual results: System Hang To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616318/+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 1670247] [NEW] Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5 card
You have been subscribed to a public bug: == Comment: #0 - Carol L. Soto- 2017-03-03 22:23:11 == ---Problem Description--- Mellanox CX4/CX5 IB if running IPoIB in connected mode, it does not have the hw checksum so when running IPoIB in power system the performance is low. with iperf and 4 threads we get [ 8] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48536 [ 4] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48538 [ 5] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48540 [ 6] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48542 [ 8] 0.0-10.0 sec 9.07 GBytes 7.79 Gbits/sec [ 4] 0.0-10.0 sec 9.16 GBytes 7.87 Gbits/sec [ 5] 0.0-10.0 sec 9.13 GBytes 7.84 Gbits/sec [ 6] 0.0-10.0 sec 9.18 GBytes 7.88 Gbits/sec [SUM] 0.0-10.0 sec 36.5 GBytes 31.4 Gbits/sec if we add the following patches: >From 68201fbbb04a030864f8560b05d43d8019f7f8df Mon Sep 17 00:00:00 2001 From: Michael Ellerman Date: Thu, 11 Aug 2016 16:03:14 +1000 Subject: powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS >From b492f7e4e07a28e706db26cf4943bb0911435426 Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:10:55 +1100 Subject: powerpc/64: Fix checksum folding in csum_tcpudp_nofold and ip_fast_csum_nofold >From d4fde568a34a93897dfb9ae64cfe9dda9d5c908c Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:15:42 +1100 Subject: powerpc/64: Use optimized checksum routines on little-endian then I can get with iperf [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 23.0 GBytes 19.7 Gbits/sec [ 6] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 5] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 7] 0.0-10.0 sec 22.9 GBytes 19.6 Gbits/sec [SUM] 0.0-10.0 sec 91.7 GBytes 78.7 Gbits/sec Contact Information = Carol Soto/cls...@us.ibm.com ---uname output--- 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:22:53 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Need a power system and Mellanox CX4 IB card. Machine Type = P8 ---Steps to Reproduce--- just run iperf with IPoIB in connected mode and will see aroung 30Gbits/sec. If we add the patches then we can get more than 70Gbits/sec. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-152252 severity-high targetmilestone-inin--- -- Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5 card https://bugs.launchpad.net/bugs/1670247 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind
** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1630285 Title: mwifiex_pcie crashes after several bind/unbind Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bin Keep doing the bind/unbind actions, it would crash very soon. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630285/+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 1654088] Re: Video decoding was stuck with radeon errors in dmesg while playing back a movie with VLC
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654088 Title: Video decoding was stuck with radeon errors in dmesg while playing back a movie with VLC Status in linux package in Ubuntu: Expired Bug description: Ubuntu 16.04.1, 64bit, desktop. All packages up to date. Played back a movie with VLC. At a random point VLC was stuck decoding the video and repeated a short sequence of frames indefinitely. There were no decoding artifacts. Subtitle continued to play back, but the audio completely stopped. Mouse was moving, desktop was functional. Might worth mentioning: The problem is more frequent while copying files over the network to an external disk drive connected via USB 2.0. Problem frequency seems to increase with additional CPU, USB 2.0 or network side-load. I don't know which one, it might not be related at all. (Yesterday I had a similar problem with radeon errors logged into syslog, like this former bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130 In that case the desktop and the video ended up completely frozen, but I could log in to the machine.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: csalad 1643 F...m pulseaudio /dev/snd/controlC0: csalad 1643 F pulseaudio Date: Wed Jan 4 22:55:18 2017 HibernationDevice: RESUME=UUID=967e54d7-9887-4bec-9cf5-ef2c2208ed16 InstallationDate: Installed on 2016-12-04 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: HP ProLiant MicroServer ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic root=UUID=48f28c43-5a3b-403c-b41d-97f98f5838ab ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd01/17/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654088/+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 1650054] Re: Dell Precision 5520 & 3520 freezes at login screent
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650054 Title: Dell Precision 5520 & 3520 freezes at login screent 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: When Precision 5520 & 3520 run on iGPU (Intel video only) mode, they hang at login screen, i.e. bbswitch tries to turn off the dGPU To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1650054/+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 1664809] Re: [0bda:0328] Card reader failed after S3
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1664809 Title: [0bda:0328] Card reader failed after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Summary: [0bda:0328] Card reader failed after S3 Steps: 1. Check card reader can be used before S3 2. Enter into S3 3. Resume from S3 4. Insert SD/MMC/SDHC into the card reader Expected results: Card reader passed after S3 Actual results: Card reader failed after S3 The card reader device is gone from lsusb Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1664809/+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 1667066] kernel02 (s390x.zVM) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/kernel02__4.8.0-40.43__2017-03-06_03-51-00/results-index.html -- 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/1667066 Title: linux: 4.8.0-40.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress 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 Yakkety: 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1652946] Re: Vlan on physical interface breaks TCP
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP Status in linux package in Ubuntu: Expired Bug description: ### More info: http://serverfault.com/questions/820689/tcp-handshake-error-syn-and-syn-ack-packets-are-not-recognised/ ### Kernel version ```bash # uname -a Linux docker-host 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ``` ### Step to reproduce: - I use proxmox hypervisor and create virtual machine with virtio nic - Take ubuntu-server 16.04.1 https://www.ubuntu.com/download/server/thank-you?version=16.04.1=amd64 - Install in minimal installation - Execute: ```bash # ip link add link ens18 name ens18.111 type vlan id 111 # ip addr add 192.168.111.80/24 dev ens18.111 # ip link set ens18.111 up # ping 192.168.111.1 PING 192.168.111.1 (192.168.111.1) 56(84) bytes of data. 64 bytes from 192.168.111.1: icmp_seq=1 ttl=64 time=17.9 ms 64 bytes from 192.168.111.1: icmp_seq=2 ttl=64 time=18.8 ms 64 bytes from 192.168.111.1: icmp_seq=3 ttl=64 time=18.5 ms ^C --- 192.168.111.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 17.932/18.455/18.841/0.414 m # nslookup > server 192.168.111.1 Default server: 192.168.111.1 Address: 192.168.111.1#53 > google.com Server: 192.168.111.1 Address: 192.168.111.1#53 Non-authoritative answer: Name: google.com Address: 173.194.222.139 Name: google.com Address: 173.194.222.113 Name: google.com Address: 173.194.222.100 Name: google.com Address: 173.194.222.102 Name: google.com Address: 173.194.222.138 Name: google.com Address: 173.194.222.101 > type cv Server: 192.168.111.1 Address: 192.168.111.1#53 ** server can't find type: NXDOMAIN > google.com ;; connection timed out; no servers could be reached ^C ``` I tested this issue on arch linux iso and it's work properly ```bash # uname -a Linux archiso 4.8.11-1-ARCH #1 SMP PREEMPT SUN Nov 27 09:26:14 CET 2016 x86_64 FNU/Linux ``` --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 29 02:29 seq crw-rw 1 root audio 116, 33 Dec 29 02:29 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/docker--host-swap InstallationDate: Installed on 2016-12-28 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/docker--host-root ro ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-31-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.2:cvnQEMU:ct1:cvrpc-i440fx-2.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1652778] Re: package linux-image-4.8.0-32-generic 4.8.0-32.34 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652778 Title: package linux-image-4.8.0-32-generic 4.8.0-32.34 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: Occurred during a routine upgrade. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-32-generic 4.8.0-32.34 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crimbo 2482 F pulseaudio /dev/snd/controlC2: crimbo 2482 F pulseaudio /dev/snd/controlC1: crimbo 2482 F pulseaudio Date: Tue Dec 27 11:57:47 2016 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=32377484-2af6-4aea-be08-97476f041091 InstallationDate: Installed on 2013-01-03 (1453 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic root=UUID=e9a20112-f8b1-4deb-9d2a-5e75f19be81f 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-36ubuntu11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8712u Title: package linux-image-4.8.0-32-generic 4.8.0-32.34 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VII GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd03/09/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIGENE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652778/+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 1653009] Re: Ubuntu 16.04 fails to boot from Sandisk usb stick with latest kernels
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653009 Title: Ubuntu 16.04 fails to boot from Sandisk usb stick with latest kernels Status in linux package in Ubuntu: Expired Bug description: There is a regression from 4.4.0-45.66 to 4.4.0-47.68. While booting I get error: [6.669572] usb 2-1.2: device descriptor read/64, error -110 and booting process fails resuming to BusyBox The workaround is to unplug and replug the usb stick and the booting process goes further [ 15.652666] usb 2-1.2: new high-speed USB device number 7 using ehci-pci [ 15.746752] usb 2-1.2: New USB device found, idVendor=0781, idProduct=5583 [ 15.748238] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.749708] usb 2-1.2: Product: Ultra Fit [ 15.751156] usb 2-1.2: Manufacturer: SanDisk [ 15.752588] usb 2-1.2: SerialNumber: 4C530001160413113001 [ 15.758906] usb-storage 2-1.2:1.0: USB Mass Storage device detected On 4.4.0-45.66 kernel everything works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darek 1386 F pulseaudio CurrentDesktop: LXDE Date: Wed Dec 28 22:14:27 2016 HibernationDevice: RESUME=UUID=e7e49edd-f274-4ac4-ae57-ebbeb8082257 InstallationDate: Installed on 2015-11-10 (414 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=ee3725ef-3af5-4853-84aa-d4526d8e6014 ro priority=low rootwait RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-23 (249 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653009/+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 1616781] Re: DINO2M - System hangs with a black screen during s4 stress test
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616781 Title: DINO2M - System hangs with a black screen during s4 stress test 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: System hangs with a black screen during s4 stress test Keyboard backlight LED is still on and adjustable, but tty1 is not avalible to switch to. System needs to be hardware shutdown. Steps: 1. install Ubuntu 16.04 and boot to OS 2. run s4 stress test (30 cycles) 3. check if the test can be completed Expected results: Test should be able to be completed Actual results: System hangs with a black screen Additional information: BIOS: 99.2.22 CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4x) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616781/+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 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
** No longer affects: hwe-next -- 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/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in Broadcom Team: New Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Triaged Status in bcmwl source package in Trusty: Fix Committed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-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 --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom/+bug/1173761/+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 1606147] Re: [APL][SAUCE] Slow system response time due to a monitor bug
** Changed in: hwe-next 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/1606147 Title: [APL][SAUCE] Slow system response time due to a monitor bug 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: [Impact] We've found a bug on some Apollo Lake system makes it runs very slow. From upstream it is caused by following reason: "Monitored cached line may not wake up from mwait on certain Goldmont based CPUs. This patch will avoid calling current_set_polling_and_test() and thereby not set the TIF_ flag. The result is that we'll always send IPIs for wakeups." [Fix] Upstream already provided a workaround[1] to fix this problem. This patches haven't been merged in latest(v4.7) release but already in linux-next. To fix this issue in Xenial it also needs another commit introduces macros use in the workaround: commit 970442c599b22ccd644ebfe94d1d303bf6f87c05 Author: Dave HansenDate: Thu Jun 2 17:19:27 2016 -0700 x86/cpu/intel: Introduce macros for Intel family numbers This workaround checks CPU families and certain features, so no further regressions is expected [1]: https://lkml.org/lkml/2016/7/6/469 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1606147/+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 1622469] Re: New device ID for Kabypoint
** Changed in: hwe-next 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/1622469 Title: New device ID for Kabypoint Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Intel has some new Kaby Lake platforms come with new Kaybpoint PCH, and need to backport the support to Xenial release. Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs following two patches: https://lkml.org/lkml/2016/7/4/403 http://marc.info/?l=linux-i2c=146945783426903=2 These patches only add some pid specific codes and it won't cause any regression in my opinion, so I think it's ok to backport them in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1622469/+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 1630857] Re: Dell Precision Trackpoint not working after suspend
** Changed in: hwe-next 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/1630857 Title: Dell Precision Trackpoint not working after suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter Desktop. 3) Suspend system. 4) Using the trackpoint. 5) Click the left button with DualPoint stick. 6) Click the right button with DualPoint stick. 7) Click the middle button with DualPoint stick. 8) Double-click the left button with DualPoint stick. Expected results: Trackpoint and DualPoint stick can work after suspend. Actual results: Trackpoing and DualPoint stick not working after suspend. Manufacturer: Dell Inc. ProductName: Precision 7500 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630857/+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 1634380] Re: BT still shows off after resume by wireless hotkey
** Changed in: hwe-next 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/1634380 Title: BT still shows off after resume by wireless hotkey Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Bug description: Summary: BT still shows off after resume by wireless hotkey Steps: 1) Install ubuntu 16.04 2) Press the wireless hotkey 3) Check the WiFi/BT status 4) Press the wireless hotkey again 5) Check the WiFi/BT status Expected results: Can turn on/off the WiFi/BT by wireless hotkey Actual results: Can turn off the WiFi/BT by wireless hotkey, but the BT is still off after press the hotkey again. WiFi didn't has this issue. Can't turn on the BT in the system setting, need reboot the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1634380/+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 1635177] Re: mfd: intel-lpss: Add default I2C device properties for Apollo Lake
** Changed in: hwe-next 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/1635177 Title: mfd: intel-lpss: Add default I2C device properties for Apollo Lake Status in HWE Next: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: We need this patch for all Apollo Lake platforms for enabling the touchpad. This patch was cherry-picked from c50cdd62dda3f885c1e6ca8b3d5a0851c911ec54. And later backported to 4.4 kernel. It is because for Apollo Lake, the default freq/falling-time is incorrect. So it makes the i2c acts weird. Please consider SRU this commit. Impact: All touchpad on Apollo Lake work unstable on i2c mode. Sometimes it will fallback to PS/2 mode and lost some functionality. Fix: touchpad works good on i2c mode. Tested: The patch is tested on many Dell ApolloLake laptops and works good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1635177/+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 1642470] Re: SRU. Please re-enable CONFIG_DRM_MGAG200.
** Changed in: hwe-next Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: oem-priority Status: Triaged => Won't Fix ** Changed in: oem-priority/xenial Status: New => Won't Fix -- 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/1642470 Title: SRU. Please re-enable CONFIG_DRM_MGAG200. Status in HWE Next: Won't Fix Status in OEM Priority Project: Won't Fix Status in OEM Priority Project xenial series: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: A new Dell Precision workstation uses Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642470/+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 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: New Status in linux package in Ubuntu: New Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+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 1667066] kernel02 (s390x.zVM) - tests ran: 16, failed: 4
tests ran: 16, failed: 4; http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/kernel02__4.8.0-40.43__2017-03-06_03-39-00/results-index.html -- 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/1667066 Title: linux: 4.8.0-40.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress 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 Yakkety: 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1667066] kernel02 (s390x.zVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/kernel02__4.8.0-40.43__2017-03-06_03-10-00/results-index.html -- 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/1667066 Title: linux: 4.8.0-40.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress 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 Yakkety: 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1450324] Re: Realtek Bluetooth 8723A/8723B/8761A/8821A support
** Changed in: hwe-next Status: New => Won't Fix ** Changed in: hwe-next/trusty Status: New => Won't Fix ** Changed in: hwe-next/vivid Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix ** Changed in: linux-lts-vivid (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux-lts-trusty (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1450324 Title: Realtek Bluetooth 8723A/8723B/8761A/8821A support Status in HWE Next: Won't Fix Status in HWE Next trusty series: Won't Fix Status in HWE Next vivid series: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux-lts-trusty package in Ubuntu: Won't Fix Status in linux-lts-vivid package in Ubuntu: Won't Fix Bug description: We need the following 2 commits to support Realtek bt devices http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=a2698a9bf9b0cfcf7e556946e04c4456a13a6f5a http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=c57ddfaea6ec8b1d96f863f7fcfc5554b5dc44c7 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1450324/+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 1591053] Re: PS/2 mouse does not work on Dell embedded computer
** Changed in: hwe-next Assignee: Phidias (phidias-chiang) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Phidias (phidias-chiang) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591053 Title: PS/2 mouse does not work on Dell embedded computer Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Steps] 1. Plug in a PS/2 mouse to PS/2 mouse jack 2. Boot system (note that PS/2 does not support hotplug so device must be cold booted) 3. Check if PS/2 mouse works [Expected result] PS/2 mouse should work [Actual] PS/2 mouse does not work in Ubuntu. * Note that: - PS/2 keyboard does not have this issue, works correctly in both BIOS & OS - PS/2 mouse works correctly only in BIOS and does not work in OS To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1591053/+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 1535513] Re: Enable suspend function for i2c-hid device in Vivid
** Changed in: hwe-next 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/1535513 Title: Enable suspend function for i2c-hid device in Vivid Status in HWE Next: Fix Released Status in HWE Next vivid series: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Fix Released Bug description: [Impact] On some platforms the touchpad relies on pinctrl devices to provide GPIO interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and will lose the config after suspend/resume, then touchpad can't be used. Also, there is a racing condition in i2c-hid module which makes touchpad unusable when waking up. [Fix] This fix has two parts. First part is to enable the suspend/resume function in pinctrl-cherryview: commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e Refs: [HEAD] Author: Mika WesterbergDate: Thu Dec 4 12:32:50 2014 +0200 pinctrl: cherryview: Save and restore pin configs over system sleep The second part is to eliminate the racing condition in i2c-hid: commit 9a327405014f4ef4cdad67a0686db82b9f23c62c Author: Mika Westerberg Date: Mon Dec 21 15:26:31 2015 +0200 HID: i2c-hid: Prevent sending reports from racing with device reset To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1535513/+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 1667066] kernel02 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/kernel02__4.8.0-40.43__2017-03-06_03-08-00/results-index.html -- 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/1667066 Title: linux: 4.8.0-40.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress 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 Yakkety: 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1667066] kernel02 (s390x.zVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-40.43-generic/kernel02__4.8.0-40.43__2017-03-06_02-56-00/results-index.html -- 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/1667066 Title: linux: 4.8.0-40.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress 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 Yakkety: 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1669469] Re: Black screen after switching to UEFI boot and prime-select nvidia.
Small update: installing 16.10 fresh but without the `yakkety-proposed` repo seems to be functional along with the nvidia drivers. I noticed that if I adhere to `yakkety-proposed`, an update to from 4.8.0-39 to 4.8.0-40 is mandatory, as well as other packages: binutils coreutils cups cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dbus dbus-user-session dbus-x11 desktop-file-utils gdb gdbserver gir1.2-gtk-3.0 gnome-software gnome-software-common gtk-update-icon-cache klibc-utils lib32z1 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdbus-1-3 libgail-3-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libklibc libpci3 libthunarx-2-0 libzmq5 linux-generic linux-headers-generic linux-image-generic linux-libc-dev linux-signed-generic linux-signed-image-generic linux-tools-common linux-tools-virtual pciutils python3-update-manager resolvconf snap-confine snapd sudo thermald thunar thunar-data ubuntu-core-launcher update-manager update-manager-core zlib1g When running without those, I also noticed graphic artifacts (screen corruption, remanent pieces of the frame not being redrawn etc) when using the graphic-drivers 378 nvidia drivers. Everything is fine when using the 367 version from the regular Ubuntu repos. Please advise on any further test. -- 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/1669469 Title: Black screen after switching to UEFI boot and prime-select nvidia. Status in linux package in Ubuntu: Confirmed Bug description: Note that this issue is reproducible on two computers, both running a fresh install from Xubuntu 16.10. Also, everything was running fine on both computers until recently. Also, running the Nouveau driver works. When installing any recent version of the nvidia driver (I tried with the 367 and 375 from vanilla repos, then the 375 and 378 from the graphics-driver PPA), I cannot get lightdm to start if `prime-select nvidia` is issued and rebooted. The screen is black with an artifact of a cursor on the top left screen (But it's not blinking, I think it's just a video frame being displayed and not updated at all). I experimented using various settings, and also installed bumblebee to diagnose. I got the nvidia GPU to work in some circumstances using `primusrun` and `optirun` so I know the card function on both computers. I'm not sure what to include in this bug report, the logs are rare and don't show very much information. A bit of interesting fact, is that since the problem is showing the regular XFCE compositor has VSync correctly on the intel card (Is it related?). Another interesting fact, is that since the problem is showing, having compton's `glx-no-rebind-pixmap` set to true makes menus not appear in chromium-based applications (Is it related?). Also, but I'm not sure: it might be since I've switched to UEFI boots. Not sure what else to include in this report, please advise. --- Ubuntu 4.8.0-39.42-generic 4.8.17 --- Description: Ubuntu 16.10 Release: 16.10 --- [...] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel modules: nvidiafb, nouveau, nvidia_378_drm, nvidia_378 [...] --- nvidia-378: Installed: 378.13-0ubuntu0~gpu16.10.3 Candidate: 378.13-0ubuntu0~gpu16.10.3 Version table: *** 378.13-0ubuntu0~gpu16.10.3 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status nvidia-settings: Installed: 378.09-0ubuntu0~gpu16.10.1 Candidate: 378.09-0ubuntu0~gpu16.10.1 Version table: *** 378.09-0ubuntu0~gpu16.10.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status 367.35-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages nvidia-prime: Installed: 0.8.4 Candidate: 0.8.4 Version table: *** 0.8.4 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doodloo3812 F pulseaudio /dev/snd/controlC1: doodloo3812 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=e5604457-e1ec-4402-9d6f-958b2a51b6b0 InstallationDate: Installed on 2017-02-27 (3 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64
[Kernel-packages] [Bug 1666209] Re: PPC new 4.4.0-63-powerpc63-smp kernel kills networking
I am not sure anyone is actually looking into it. Updating to kernel version 64 resulted it system assigning yet another new name for the interfaces, which in turn screwed up the networking. In my case, as I was ready for that, I just listed what the system now called the interfaces, edited the /etc/network/interfaces file to include the new names and, after a reboot, the system got connected. It is a workaround, but that's all I can do for 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/1666209 Title: PPC new 4.4.0-63-powerpc63-smp kernel kills networking Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: After upgrading to a new kernel (4.4.0-63-powerpc64-smp) completely lost ethernet. Looks like the kernel doesn't load a module for my interface (driver r8169). Rolling back to previous kernel version fixes networking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666209/+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 1666209] Re: PPC new 4.4.0-63-powerpc63-smp kernel kills networking
I am having exactly the same problem as reported as Bug #1666209, ever since I updated from 4.4.0-62. The last working kernel is 4.4.0-62. May I expect that the problem will be solved by an automatic update of the kernel? Or can I do something to repair it myself? -- 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/1666209 Title: PPC new 4.4.0-63-powerpc63-smp kernel kills networking Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: After upgrading to a new kernel (4.4.0-63-powerpc64-smp) completely lost ethernet. Looks like the kernel doesn't load a module for my interface (driver r8169). Rolling back to previous kernel version fixes networking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666209/+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 1510723] Re: intel i915 driver segfaults: WARNING: ...drivers/gpu/drm/i915/intel_display.c:11100 intel_check_page_flip+0xfc/0x110 [i915]()
** Changed in: linux Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510723 Title: intel i915 driver segfaults: WARNING: ...drivers/gpu/drm/i915/intel_display.c:11100 intel_check_page_flip+0xfc/0x110 [i915]() Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: Adding tags for upstream because I've already tested it and it's still the case for 4.3-rc7. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: int1393 F pulseaudio CurrentDesktop: KDE Date: Wed Oct 28 00:38:55 2015 HibernationDevice: RESUME=UUID=a9a75bdb-fa57-454a-88c6-9f2c8d324bd0 MachineType: ASUSTeK COMPUTER INC. X502CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq resume=/dev/mapper/ocz-swap_1 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X502CA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X502CA 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.:bvrX502CA.209:bd06/09/2013:svnASUSTeKCOMPUTERINC.:pnX502CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX502CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X502CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1510723/+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 1668031] Re: Network adapter keeps on hanging up
Hello Joseph, That's not so easy to confirm (for upstream). In the cause of confirming this bug - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657907 - I've installed an upstream kernel and that bug was still present, and it also occurs every hour or so. The difference between them, as far as I can tell, that that bug (1657907) logs a firmware crash, and this one (1668031) does not. I cannot, however, actively provocate the one or the other. Are you able to see, if this bug is actually a different one? My current workaround is, that I constantly have 2 terminal emulator windows open: one that is pinging google, so that I can see, when the connection is gone, and one in which I `sudo service network-manager restart`, when it is. Let me know, if there is anything else I can do. -- 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/1668031 Title: Network adapter keeps on hanging up Status in linux package in Ubuntu: Incomplete Bug description: Every hour or so, I'm unable to access the internet through this laptop. dmesg usually reports errors related to the network adapter, but not always. Disconnecting from the current Wifi network and connecting to another, usually works. Immediately connecting to the original network after that does not cause the problem to reoccur. At least, not for another hour or so. I'm not sure how to better describe this bug. The network also provides a nfs drive that is mounted on the laptop, if that is significant. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-39-generic 4.8.0-39.42 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruud 2810 F pulseaudio CurrentDesktop: Unity Date: Sun Feb 26 02:13:55 2017 HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b InstallationDate: Installed on 2016-11-08 (109 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668031/+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 1451233] Re: 10ec:b723 [Lenovo B5400] Realtek RTL8723BE drops connection until reboot
Recent updates had a mixed effect: with Linux 4.9.11-200.fc25, the network manager sees more/all wifi networks and connects to them but then drops quickly. -- 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/1451233 Title: 10ec:b723 [Lenovo B5400] Realtek RTL8723BE drops connection until reboot Status in linux package in Ubuntu: Triaged Bug description: I have a Lenovo B5400 laptop with RTL8723BE wireless module. Using 802.11n the internet connection constantly getting lost after a random duration (usually after 20-30 minutes). The NetworkManager applet does not recognize it (still looks like i have a connection), but when I try do disconnect and connect again, there is only one useful information I can find in dmesg: "wlan0: deauthenticating from [ap mac address] by local choice (Reason: 3=DEAUTH_LEAVING)" Reinserting the driver (modprobe -r rtl8723be and modprobe rtl8723) used to be my only workaround, but it does not work anymore and now I have to reboot. Router Manufacturer: EDIMAX Model: BR-6214K Firmware version: 1.40 2008/11/03 08:33:04 Switching to 802.11g (54Mb/s) shows a small performance improvement while browsing websites. However there are still random "ping jumps" and the connection still drops (maybe 1-2 minutes later than usual at least). The following improves performance, but I am still encountering some minor performance issues while playing online games (random lag spikes): sudo nano /etc/modprobe.d/rtl8723be.conf options rtl8723be ips=0 fwlps=0 --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pk 1907 F pulseaudio /dev/snd/controlC0: pk 1907 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=4ce160f4-029c-4fd5-ba3f-254c6e3e33dd InstallationDate: Installed on 2015-05-24 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20278 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=a9da170f-b86b-434f-910b-00929ceb8420 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 RelatedPackageVersions: linux-restricted-modules-3.16.0-38-generic N/A linux-backports-modules-3.16.0-38-generic N/A linux-firmware 1.127.12 Tags: trusty Uname: Linux 3.16.0-38-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/03/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J7ET61WW (2.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20278 QB0 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ7ET61WW(2.06):bd03/03/2014:svnLENOVO:pn20278:pvrB5400:rvnLENOVO:rn20278QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20278 dmi.product.version: B5400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451233/+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 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank
This problem still exists in 16.10 server with the 4.8.0-39-generic x86_64 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/1593261 Title: Using "splash" Linux boot option causes IPMI console view to blank Status in linux package in Ubuntu: Confirmed Bug description: I'm using a set of blade servers with SuperMicro BIOS and IPMI console viewing capabilities. I use the Ubuntu netboot options with a PXE server to install. I've installed Ubuntu 12.04 and 14.04 on these systems, and everything works great. However, when I install Ubuntu 16.04 (and this is true both if I upgrade from Ubuntu 14.04 with do-release-upgrade AND when I install a fresh copy directly via the Ubuntu 16.04 netboot image via PXE), then the install works but when I reboot the IPMI console is completely blank: no cursor, no text, no typing shows anything. I can still SSH to the system (except of course the default netboot install doesn't include sshd for some bizarre reason so I had to play some tricks and rerun the install multiple times :-/). After a lot of experimentation I discovered that if I edit the /etc/default/grub file and remove the "splash" setting from GRUB_CMDLINE_LINUX_DEFAULT variable and re-run update-grub, then things worked fine and I was able to boot properly without losing access to the IPMI console. One more note: this is definitely a kernel issue because when I choose the older 14.04 kernel (3.13 or similar) from the boot menu on the system I upgraded from 14.04 to 16.04, with the "splash" setting still in the grub config and no other changes (so userspace is still all 16.04), I had no problems with the IPMI console viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593261/+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 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
Confirmed *NFA364xp.bin and qca61x4_2_2.bin usage by Windows. linux- firmware's version is definitely not up-to-date for this card as it refers to NFA324i (see the paste link). ** Attachment added: ".inf file parsed by Windows" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+attachment/4831855/+files/killer-wireless-firmware.png -- 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/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: Confirmed Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04
[Kernel-packages] [Bug 1670154] 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/1670154 Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux- headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-39 (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uhuru 2394 F pulseaudio /dev/snd/controlC1: uhuru 2394 F pulseaudio /dev/snd/controlC2: uhuru 2394 F pulseaudio Date: Wed Mar 1 22:32:59 2017 ErrorMessage: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise HibernationDevice: RESUME=UUID=96b2f8e3-8186-46c4-8475-124db407e9ba InstallationDate: Installed on 2016-01-27 (402 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp5s8no wireless extensions. MachineType: Dell Inc. Dimension 9100 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=4c460bad-c68b-438c-aebc-70f7efc5103d 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-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X8582 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dimension 9100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670154/+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 1670154] [NEW] package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-ne
Public bug reported: ubuntu 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-39 (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uhuru 2394 F pulseaudio /dev/snd/controlC1: uhuru 2394 F pulseaudio /dev/snd/controlC2: uhuru 2394 F pulseaudio Date: Wed Mar 1 22:32:59 2017 ErrorMessage: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise HibernationDevice: RESUME=UUID=96b2f8e3-8186-46c4-8475-124db407e9ba InstallationDate: Installed on 2016-01-27 (402 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp5s8no wireless extensions. MachineType: Dell Inc. Dimension 9100 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=4c460bad-c68b-438c-aebc-70f7efc5103d 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-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X8582 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dimension 9100 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package yakkety -- 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/1670154 Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux- headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-39 (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uhuru 2394 F pulseaudio /dev/snd/controlC1: uhuru 2394 F pulseaudio /dev/snd/controlC2: uhuru 2394 F pulseaudio Date: Wed Mar 1 22:32:59 2017 ErrorMessage: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise HibernationDevice: RESUME=UUID=96b2f8e3-8186-46c4-8475-124db407e9ba InstallationDate: Installed on 2016-01-27 (402 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp5s8no wireless extensions. MachineType: Dell Inc. Dimension 9100 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=4c460bad-c68b-438c-aebc-70f7efc5103d 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-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non permise UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X8582 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dimension 9100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670154/+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 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
** Description changed: - I experience a very poor 802.11ac performance of a QCA6174 Wireless card - (Killer Wireless 1535). + Update: added some forensics in the paste (a long read): + http://paste.ubuntu.com/24118478/ + + TL;DR with a bit of intuition: + We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. + + 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) + qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 + + + Original message: + -- + I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: - uname -r + uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers - lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) - Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- - Kernel driver in use: ath10k_pci - Kernel modules: ath10k_pci - + Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter + Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- + Kernel driver in use: ath10k_pci + Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04 18:28:34 ubuntu kernel: ath: EEPROM indicates we should expect a direct regpair map Mar 04 18:28:34 ubuntu kernel: ath: Country
[Kernel-packages] [Bug 1670137] Re: zfs l2arc cache inhibits proper suspend
Same results with 4.8 kernel & pm_trace as above: Linux mp 4.8.0-39-generic #42~16.04.1-Ubuntu SMP Mon Feb 20 15:06:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux 2017-03-05 10:032017-03-05 15:03 UTCKernelOops linux- image-4.8.0-39-generic https://errors.ubuntu.com/oops/85158246-01bc-11e7-98ee-fa163ebeb28a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: zfs l2arc cache inhibits proper suspend Status in zfs-linux package in Ubuntu: New Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1669127] onza (amd64) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onza__4.10.0-11.13__2017-03-05_14-52-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1670137] Re: zfs l2arc cache inhibits proper suspend
Occurs while suspend to ram, attempted pm_trace (sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"): ... [1.196689] Key type encrypted registered [1.196712] AppArmor: AppArmor sha1 policy hashing enabled [1.442937] evm: HMAC attrs: 0x1 [1.444273] Magic number: 12:578:178 [1.444323] acpi device:0e: hash matches [1.444345] platform: hash matches [1.444671] rtc_cmos 00:02: setting system clock to 2016-12-22 12:09:40 UTC (1482408580) [1.444925] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.444927] EDD information not available. [1.445014] PM: Hibernation image not present or could not be loaded. [1.445962] Freeing unused kernel memory: 1480K (81f42000 - 820b4000) ... More data points: https://errors.ubuntu.com/oops/3a52bdf6-01b6-11e7-b175-fa163e839e11 https://errors.ubuntu.com/oops/8423d2c6-01b6-11e7-84d4-fa163ebeb28a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: zfs l2arc cache inhibits proper suspend Status in zfs-linux package in Ubuntu: New Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1670137] Re: zfs l2arc cache inhibits proper suspend
Precision 5510 BIOS version: 1.2.19 (latest) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: zfs l2arc cache inhibits proper suspend Status in zfs-linux package in Ubuntu: New Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1670137] [NEW] zfs l2arc cache inhibits proper suspend
Public bug reported: Please see: 2017-03-05 09:032017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: zfs l2arc cache inhibits proper suspend Status in zfs-linux package in Ubuntu: New Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1670127] 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/1670127 Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Dont know why it is broken or how to fix it, but when it stopped working my Wi-Fi stopped working. Having to hard wire the computer to get connection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-62-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf68 1518 F pulseaudio Date: Sun Mar 5 07:41:49 2017 DpkgHistoryLog: Start-Date: 2017-03-05 07:40:59 Commandline: apt-get install -f Requested-By: wolf68 (1000) Install: linux-headers-4.4.0-62-generic:amd64 (4.4.0-62.83, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.59.62, 4.4.0.62.65), linux-headers-4.4.0-62:amd64 (4.4.0-62.83, 4.4.0-62.83) DuplicateSignature: package:linux-headers-4.4.0-62-generic:(not installed) Unpacking linux-headers-4.4.0-62 (4.4.0-62.83) over (4.4.0-62.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-62_4.4.0-62.83_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.4.0-62/include/dt-bindings/spmi/spmi.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e9f425ba-b6df-4bb9-a18f-405ac1b1573c InstallationDate: Installed on 2016-08-30 (187 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp4s0no wireless extensions. Lsusb: Bus 002 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1564 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=28266855-d72f-4df6-bb23-a31f0c8df94c 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.6 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 08CNC9 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1564:pvrA13:rvnDellInc.:rn08CNC9:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1564 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670127/+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 1670127] [NEW] package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs
Public bug reported: Dont know why it is broken or how to fix it, but when it stopped working my Wi-Fi stopped working. Having to hard wire the computer to get connection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-62-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf68 1518 F pulseaudio Date: Sun Mar 5 07:41:49 2017 DpkgHistoryLog: Start-Date: 2017-03-05 07:40:59 Commandline: apt-get install -f Requested-By: wolf68 (1000) Install: linux-headers-4.4.0-62-generic:amd64 (4.4.0-62.83, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.59.62, 4.4.0.62.65), linux-headers-4.4.0-62:amd64 (4.4.0-62.83, 4.4.0-62.83) DuplicateSignature: package:linux-headers-4.4.0-62-generic:(not installed) Unpacking linux-headers-4.4.0-62 (4.4.0-62.83) over (4.4.0-62.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-62_4.4.0-62.83_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.4.0-62/include/dt-bindings/spmi/spmi.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e9f425ba-b6df-4bb9-a18f-405ac1b1573c InstallationDate: Installed on 2016-08-30 (187 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp4s0no wireless extensions. Lsusb: Bus 002 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1564 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=28266855-d72f-4df6-bb23-a31f0c8df94c 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.6 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 08CNC9 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1564:pvrA13:rvnDellInc.:rn08CNC9:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1564 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package need-duplicate-check 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/1670127 Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Dont know why it is broken or how to fix it, but when it stopped working my Wi-Fi stopped working. Having to hard wire the computer to get connection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-62-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf68 1518 F pulseaudio Date: Sun Mar 5 07:41:49 2017 DpkgHistoryLog: Start-Date: 2017-03-05 07:40:59 Commandline: apt-get install -f Requested-By: wolf68 (1000) Install: linux-headers-4.4.0-62-generic:amd64 (4.4.0-62.83, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.59.62, 4.4.0.62.65), linux-headers-4.4.0-62:amd64 (4.4.0-62.83, 4.4.0-62.83) DuplicateSignature: package:linux-headers-4.4.0-62-generic:(not installed) Unpacking linux-headers-4.4.0-62 (4.4.0-62.83) over (4.4.0-62.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-62_4.4.0-62.83_all.deb (--unpack): unable to open
[Kernel-packages] [Bug 1669127] onza (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onza__4.10.0-11.13__2017-03-05_13-19-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1669815] Re: Kernel panic when plugging in USB Wifi USB adapter
I installed the kernel 4.4.0 provided by jsalisbury. This works for me: $ uname -a Linux media-desktop 4.4.0-64-generic #85~lp1666421 SMP Wed Feb 22 21:37:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsusb | grep "Edimax" Bus 001 Device 002: ID 7392:7822 Edimax Technology Co., Ltd $ ifconfig wlx74da3894b952 wlx74da3894b952: flags=4163mtu 1500 inet 192.168.1.52 netmask 255.255.255.0 broadcast 192.168.1.255 ether 74:da:38:94:b9:52 txqueuelen 1000 (Ethernet) RX packets 3327 bytes 2122333 (2.1 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2755 bytes 370569 (370.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I don't know much about the different kernel versions. Would It be possible to apply the modification to the 4.8.0 kernel as well, so I can test that, too? I tested * booting without device attached, then attaching it after boot. * booting with device attached. Both works fine. Should I test anything else? -- 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/1669815 Title: Kernel panic when plugging in USB Wifi USB adapter Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to linux-image-4.8.0-38-generic) the kernel panics as soon as I plug in the Wifi adapter (Edimax EW-7612UAn Wifi USB Adapter). The coredump logs BUG: unable to handle kernel NULL pointer dereference @0048 IP: [] rtl_lps_leave+0x17/0x50 [rtlwifi] PGD 0 Ooops: [#1] SMP This is followed by the Modules linked in, Hardware info, Stack trace. At the end of the trace it says: Kernel panic - not syncing: Fatal exception in interrupt. I uploaded a console screenshot here: IMG_20170222_230239.jpg and I didn't find anything suspicious in syslog or kernel log, most probably because the kernel panics almost instantly after plugging the usb adapter in. Updating to linux-image-4.8.0-39-generic does not solve the issue as well. Only way to work around the issue is to select the 4.8.0-37 image from the grub bootmenu. The problem is not related to a specific USB port. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669815/+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 1669127] onza (i386) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onza__4.10.0-11.13__2017-03-05_11-42-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1670109] 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/1670109 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: This is an intentional duplicate as I cannot run `apport-collect 1652815` on LP: #1652815 give that it is not my bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 [modified: boot/vmlinuz-4.10.0-9-generic] ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sergiusens 2578 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Mar 5 03:40:53 2017 InstallationDate: Installed on 2017-03-03 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic.efi.signed root=UUID=5a918452-eacc-4c1c-8e82-eb79f6a94ca2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-9-generic N/A linux-backports-modules-4.10.0-9-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2016 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1414.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1414.768:bd12/06/2016:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670109/+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 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS
I've added to apport data to LP: #1670109 For the record, 4.10 is the first Ubuntu kernel to support the 'Microsoft Surface Type Cover' keyboard and touchpad, but the touchpad support is very basic (no multitouch). For the touchscreen and pen to work one would need the out of tree patches mentioned in the original report. -- 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/1652815 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive Expected Behaviour: Pen/Touch function Actual Behaviour: Pen/Touch do not work or respond to anything Kernel/Ubuntu Versions: All Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to function. This is because touch processing is accelerated by the Intel Skylake GPU. IPTS driver can be found here: https://github.com/ipts-linux-org/ipts- linux-new/wiki Kernel compile under Debian with other Surface-specific patches can be found here: https://github.com/jimdigriz/debian-mssp4 On Reddit there are some custom kernels floating around with support patched in: https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+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 1670109] [NEW] Surface Pro 4 Touch/Pen requires IPTS
Public bug reported: This is an intentional duplicate as I cannot run `apport-collect 1652815` on LP: #1652815 give that it is not my bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 [modified: boot/vmlinuz-4.10.0-9-generic] ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sergiusens 2578 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Mar 5 03:40:53 2017 InstallationDate: Installed on 2017-03-03 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic.efi.signed root=UUID=5a918452-eacc-4c1c-8e82-eb79f6a94ca2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-9-generic N/A linux-backports-modules-4.10.0-9-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2016 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1414.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1414.768:bd12/06/2016:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1670109 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: New Bug description: This is an intentional duplicate as I cannot run `apport-collect 1652815` on LP: #1652815 give that it is not my bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 [modified: boot/vmlinuz-4.10.0-9-generic] ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sergiusens 2578 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Mar 5 03:40:53 2017 InstallationDate: Installed on 2017-03-03 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic.efi.signed root=UUID=5a918452-eacc-4c1c-8e82-eb79f6a94ca2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-9-generic N/A linux-backports-modules-4.10.0-9-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2016 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1414.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1414.768:bd12/06/2016:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670109/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
Hi there! still got this problem with the KDE Neon distribution based upon Ubuntu 16.04. Solved this problem with a little shell-script based on this thread: http://askubuntu.com/questions/765233/pulseaudio-fails-to-set-card- profile-to-a2dp-sink-how-can-i-see-the-logs-and The script is attached. FIRST OF ALL: Change the devices MAC-address in the variable inside the script! (can be found with "bluetoothctl" --> Device) - Made a "chmod a-x bluetooth_headphone_reactivation.sh" to make it executable. For automatic execution _at startup_ (only works if headset is already turned on): - Added the script to the start/shutdown scripts in KDEs' control panel For fast manual execution: - Added an entry to the application-starter (you can also set a keyboad shortcut like "CTRL+ALT+H" and/or pin this starter to the window bar) ** Attachment added: "kde bluetooth headphone set a2dp_sink profile script workaround" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197/+attachment/4831629/+files/bluetooth_headphone_reactivation.sh -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1669127] onza (amd64) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onza__4.10.0-11.13__2017-03-05_10-07-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1669127] onza (i386) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onza__4.10.0-11.13__2017-03-05_08-30-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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 1669127] onibi (amd64) - tests ran: 64, failed: 1
tests ran: 64, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/onibi__4.10.0-11.13__2017-03-05_07-17-00/results-index.html -- 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/1669127 Title: linux: 4.10.0-11.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete 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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-11.13 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 -- 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/1669127/+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