[Kernel-packages] [Bug 1451277] Re: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE)
>From LKML conversation, fix https://lkml.org/lkml/2014/11/20/581 is not likely to be applied upstream, because it probably just papers over the real bug. The real issue appears with the patch series "scsi: convert host_busy to atomic_t" that causes regressions on some hardware configurations. Might not be due to this series either, but to some other race that this change helps triggering. I wonder if papering over can be acceptable downstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451277 Title: Extremely high IOWait and processes hungs after utopic->vivid upgrade with Iomega Zip drive (IDE) Status in linux package in Ubuntu: Confirmed Bug description: On Kubuntu, 64 bit AMD Phenom2 machine with 4 cores, and old (Geoforge 7025) Nvidia graphics. Using LVM. Machine also has a 2 disk software raid (mirroring). The machine was working fine before the upgrade, now it is almost impossible to use it... I see Wait in Top always above 60%; in dmesg after a few minutes that the machine is up even if the machine does nothing. I see hung processes (typically vgs, but occasionally also others). LVM related commands (e.g. lvdisplay) almost always hung at the terminal. I also see in ps some kernel workers almost constantly stuck in D state. Also, the machine takes ages to shutdown. Issue remains there also if I disable X (switch off the X login manager, sddm) and check at the console. Sorry I cannot provide details with apport, but the machine has been switched off and I will not be able to take it up again before a few days from now. The symptom I am observing may also be a sign of failing hardware, so please leave the bug as unconfirmed until I make some more tests or someone provide details on similar issues. In the meantime I would like to see if others are experiencing a similar serious issue. Is there anything specific that has changed between utopic and vivid, I should look into? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451277/+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 1492939] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1492939 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: Incomplete Bug description: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Nephilim1973: No, we can't "learn" anything here from Android. We have a completely different bluetooth stack which you can't compare with the Android one. Config files in /etc/bluetooth/*.conf don't help. Those problems are at other layers. > Why the BT handling is so different between Touch and Desktop ? There are quite a lot differences: * different BT chip * different UI handlers * newer kernel with updated Bluetooth stack We're currently working quite hard to update the bluetooth stack on Touch (which dates back to 2012) to a newer, more stable and reliable one. Can't give any timeline yet but it will happen soon. What I really need is a log of bluetoothd in debug mode. See https://wiki.ubuntu.com/DebuggingBluetooth for details. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1492939] [NEW] Enhancement request: please document how to build kernel in PPA
Public bug reported: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build- mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! ** 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: New Bug description: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+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 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port
For your information, last year, I reported the bug upstream at https://bugzilla.kernel.org/show_bug.cgi?id=75381 That bug report seems still active. It has been also reported on the initial driver page on Github https://github.com/FreddyXin/ax88179_178a/issues/6 Regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269883 Title: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in USB3 port yields slow performance, dmesg flooded with errors. Plugging on USB2 port, exact same situation otherwise, works well. This is reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the left, 2 USB2 ports on the right. ### When working (USB2 port) * ethernet auto-negociation is fast * mii-tool is fast (typical 0.05s) * few lines in dmesg * good performance ### When failing : * ethernet auto-negociation fails, then sometimes eventually works * mii-tool is slow (10s of seconds instead of 0.05s) time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m40.014s user 0m0.013s sys 0m0.006s time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m50.015s user 0m0.011s sys 0m0.011s time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m10.051s user 0m0.000s sys 0m0.012s But on some attempts mii-tool is fast... time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m0.057s user 0m0.011s sys 0m0.012s * DHCP eventually completes (after about 30 seconds) then ethernet works. * whole system behaviour feels a little sluggish (not very clear, though) * mii-tool still slow (10s of seconds instead of 0.05s) ## dmesg when failing Full dmesg attached. Specific lines with occurrence count at random point (obtained with "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ). 50 ei_me :00:16.0: reset: wrong host start response 51 ei_me :00:16.0: reset: unexpected enumeration response hbm. 60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING 141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Another attempt 11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110 6 net_ratelimit: 31 callbacks suppressed 9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready 10 net_ratelimit: 30 callbacks suppressed 14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel: [203182.075364] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203182.199491] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel: [203182.199504] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:37 n55sf-l kernel: [203182.944174] xhci_hcd :04:00.0:
[Kernel-packages] [Bug 1492892] Re: Implement standalone bluetooth agent handler
** Tags added: bluez5 -- 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/1492892 Title: Implement standalone bluetooth agent handler Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1492892/+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 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
I'm having this exact issue with Debian Jessie. Virtual machines running with LVM storage unpredictably failing after cron.daily. [680406.357587] EXT4-fs error (device vda1): ext4_mb_generate_buddy:757: group 49, block bitmap and bg descriptor inconsistent: 18356 vs 18355 free clusters [680406.361696] Aborting journal on device vda1-8. [680406.453757] EXT4-fs error (device vda1): ext4_journal_check_start:56: [680406.453999] EXT4-fs (vda1): Remounting filesystem read-only [680406.457551] Detected aborted journal [766809.056039] EXT4-fs (vda1): error count since last fsck: 2 [766809.056069] EXT4-fs (vda1): initial error at time 1441383430: ext4_mb_generate_buddy:757 [766809.056082] EXT4-fs (vda1): last error at time 1441383430: ext4_journal_check_start:56 [853316.576033] EXT4-fs (vda1): error count since last fsck: 2 [853316.576052] EXT4-fs (vda1): initial error at time 1441383430: ext4_mb_generate_buddy:757 [853316.576066] EXT4-fs (vda1): last error at time 1441383430: ext4_journal_check_start:56 root@collect1 ~ # uname -a Linux collect1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I noticed that one of my VM had this "dmesg -T" output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm:
[Kernel-packages] [Bug 1445458] Re: BCM4360 bcmwl-kernel-source System Freeze every few Seconds
Same bug for me as well with the BCM4360 Chipset and Broadcom 6.30.223.248 bcmwl kernel source. As soon as I turn wifi off, the freezing stops. -- 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/1445458 Title: BCM4360 bcmwl-kernel-source System Freeze every few Seconds Status in bcmwl package in Ubuntu: Confirmed Bug description: Every newer version of bcmwl-kernel-source than 6.30.223.141+bdcom- 0ubuntu2 causes complete Freezes on my System every few Seconds. Removing the wl module restores the system to its normal state. Compiling the latest version 6.30.223.248 from the Broadcom STA Source makes no difference as well as using the latest Mainline-Kernel. So some of the changes between 6.30.223.141 and 6.30.223.248 must be responsible. Version 6.30.223.248+bdcom-0ubuntu0.1 installs without any Errors but as soon as the wl Module is loaded the Freezes occur. Dmesg shows nothing of note. $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installiert: 6.30.223.141+bdcom-0ubuntu1 Installationskandidat: 6.30.223.248+bdcom-0ubuntu0.1 Versionstabelle: 6.30.223.248+bdcom-0ubuntu0.1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 6.30.223.141+bdcom-0ubuntu2 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages *** 6.30.223.141+bdcom-0ubuntu1 0 100 /var/lib/dpkg/status Hardware: Asus PCE-AC66 02:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter (rev 02) Apport-Info: ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 17 13:55:22 2015 Dependencies: adduser 3.113+nmu3ubuntu3 apt-utils 1.0.1ubuntu2.6 base-passwd 3.5.33 binutils 2.24-5ubuntu3.1 busybox-initramfs 1:1.21.0-1ubuntu1 coreutils 8.21-1ubuntu5.1 cpio 2.11+dfsg-1ubuntu1.1 cpp 4:4.8.2-1ubuntu6 cpp-4.8 4.8.2-19ubuntu1 dbus 1.6.18-0ubuntu4.3 debconf 1.5.51ubuntu2 debconf-i18n 1.5.51ubuntu2 debianutils 4.4 dkms 2.2.0.3-1.1ubuntu5.14.04 dpkg 1.17.5ubuntu5.4 e2fslibs 1.42.9-3ubuntu1.2 e2fsprogs 1.42.9-3ubuntu1.2 fakeroot 1.20-3ubuntu2 findutils 4.4.2-7 gcc 4:4.8.2-1ubuntu6 gcc-4.8 4.8.2-19ubuntu1 gcc-4.8-base 4.8.2-19ubuntu1 gcc-4.9-base 4.9.1-0ubuntu1 ifupdown 0.7.47.2ubuntu4.1 initramfs-tools 0.103ubuntu4.2 initramfs-tools-bin 0.103ubuntu4.2 initscripts 2.88dsf-41ubuntu6.1 insserv 1.14.0-5ubuntu2 iproute2 3.12.0-2 isc-dhcp-client 4.2.4-7ubuntu12.1 isc-dhcp-common 4.2.4-7ubuntu12.1 klibc-utils 2.0.3-0ubuntu1 kmod 15-0ubuntu6 libacl1 2.2.52-1 libapparmor1 2.8.95~2430-0ubuntu5.1 libapt-inst1.5 1.0.1ubuntu2.6 libapt-pkg4.12 1.0.1ubuntu2.6 libasan0 4.8.2-19ubuntu1 libatm1 1:2.5.1-1.5 libatomic1 4.8.2-19ubuntu1 libattr1 1:2.4.47-1ubuntu1 libaudit-common 1:2.3.2-2ubuntu1 libaudit1 1:2.3.2-2ubuntu1 libblkid1 2.20.1-5.1ubuntu20.4 libbz2-1.0 1.0.6-5 libc-dev-bin 2.19-0ubuntu6.6 libc6 2.19-0ubuntu6.6 libc6-dev 2.19-0ubuntu6.6 libcap2 1:2.24-0ubuntu2 libcgmanager0 0.24-0ubuntu7.3 libcloog-isl4 0.18.2-1 libcomerr2 1.42.9-3ubuntu1.2 libdb5.3 5.3.28-3ubuntu3 libdbus-1-3 1.6.18-0ubuntu4.3 libdebconfclient0 0.187ubuntu1 libdrm2 2.4.56-1~ubuntu2 libexpat1 2.1.0-4ubuntu1 libfakeroot 1.20-3ubuntu2 libgcc-4.8-dev 4.8.2-19ubuntu1 libgcc1 1:4.9.1-0ubuntu1 libgmp10 2:5.1.3+dfsg-1ubuntu1 libgomp1 4.8.2-19ubuntu1 libgpm2 1.20.4-6.1 libisl10 0.12.2-1 libitm1 4.8.2-19ubuntu1 libjson-c2 0.11-3ubuntu1.2 libjson0 0.11-3ubuntu1.2 libklibc 2.0.3-0ubuntu1 libkmod2 15-0ubuntu6 liblocale-gettext-perl 1.05-7build3 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.20.1-5.1ubuntu20.4 libmpc3 1.0.1-1ubuntu1 libmpfr4 3.1.2-1 libncurses5 5.9+20140118-1ubuntu1 libncursesw5 5.9+20140118-1ubuntu1 libnih-dbus1 1.0.3-4ubuntu25 libnih1 1.0.3-4ubuntu25 libpam-modules 1.1.8-1ubuntu2 libpam-modules-bin 1.1.8-1ubuntu2 libpam-runtime 1.1.8-1ubuntu2 libpam-systemd 204-5ubuntu20.11 libpam0g 1.1.8-1ubuntu2 libpcre3 1:8.31-2ubuntu2 libplymouth2 0.8.8-0ubuntu17.1 libpng12-0 1.2.50-1ubuntu2 libprocps3 1:3.3.9-1ubuntu2.2 libquadmath0 4.8.2-19ubuntu1 libselinux1 2.2.2-1ubuntu0.1 libsemanage-common 2.2-1 libsemanage1 2.2-1 libsepol1 2.2-1ubuntu0.1 libslang2 2.2.4-15ubuntu1 libss2 1.42.9-3ubuntu1.2 libstdc++6 4.8.2-19ubuntu1 libsystemd-daemon0 204-5ubuntu20.11 libsystemd-login0 204-5ubuntu20.11 libtext-charwidth-perl 0.04-7build3 libtext-iconv-perl 1.7-5build2 libtext-wrapi18n-perl 0.06-7 libtinfo5 5.9+20140118-1ubuntu1 libtsan0 4.8.2-19ubuntu1 libudev1
[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang
I'm, personally, prefer to install a new kernel by running "apt-get install linux-signed-generic-lts-vivid". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: Hello! Have a: >lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty with kenel 3.16.0-46-generic. Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic version. After reboot i've got this: Sep 4 09:02:52 mail kernel: [ 310.616324] igb :02:00.0 em1: Reset adapter Sep 4 09:02:52 mail kernel: [ 310.831157] igb :02:00.1 em2: Reset adapter Sep 4 09:02:56 mail kernel: [ 315.154686] igb :02:00.0 em1: igb: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:02:56 mail kernel: [ 315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:03:02 mail kernel: [ 321.608099] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:02 mail kernel: [ 321.608099] Tx Queue <6> Sep 4 09:03:02 mail kernel: [ 321.608099] TDH <23> Sep 4 09:03:02 mail kernel: [ 321.608099] TDT <23> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_use <25> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_clean<23> Sep 4 09:03:02 mail kernel: [ 321.608099] buffer_info[next_to_clean] Sep 4 09:03:02 mail kernel: [ 321.608099] time_stamp <112af> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_watch Sep 4 09:03:02 mail kernel: [ 321.608099] jiffies <11531> Sep 4 09:03:02 mail kernel: [ 321.608099] desc.status <120200> Sep 4 09:03:04 mail kernel: [ 323.607349] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:04 mail kernel: [ 323.607349] Tx Queue <6> Sep 4 09:03:04 mail kernel: [ 323.607349] TDH <23> Sep 4 09:03:04 mail kernel: [ 323.607349] TDT <23> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_use <25> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_clean<23> Sep 4 09:03:04 mail kernel: [ 323.607349] buffer_info[next_to_clean] Sep 4 09:03:04 mail kernel: [ 323.607349] time_stamp <112af> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_watch Sep 4 09:03:04 mail kernel: [ 323.607349] jiffies <11725> Sep 4 09:03:04 mail kernel: [ 323.607349] desc.status <120200> Sep 4 09:03:06 mail kernel: [ 325.606602] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:06 mail kernel: [ 325.606602] Tx Queue <6> Sep 4 09:03:06 mail kernel: [ 325.606602] TDH <23> Sep 4 09:03:06 mail kernel: [ 325.606602] TDT <23> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_use <25> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_clean<23> Sep 4 09:03:06 mail kernel: [ 325.606602] buffer_info[next_to_clean] Sep 4 09:03:06 mail kernel: [ 325.606602] time_stamp <112af> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_watch Sep 4 09:03:06 mail kernel: [ 325.606602] jiffies <11919> Sep 4 09:03:06 mail kernel: [ 325.606602] desc.status <120200> All network connections droped after that. System still unusable. Only after boot with old linux-image-3.16.0-46-generic my production mail server can work. It's a critical bug for me, can anybody help me? ethtool -i em1 driver: igb version: 5.2.13-k firmware-version: 1.61, 0x8cd5, 1.949.0 bus-info: :02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+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 1489327] Re: Upgrade kernel bluetooth stack to 4.2-rc7
This bug was fixed in the package linux-mako - 3.4.0-7.39 --- linux-mako (3.4.0-7.39) wily; urgency=low * No change rebuild to increase the package version above that of the Vivid package. -- Tim GardnerThu, 03 Sep 2015 12:00:17 -0600 ** Changed in: linux-mako (Ubuntu) Status: New => Fix Released ** Changed in: linux-flo (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1489327 Title: Upgrade kernel bluetooth stack to 4.2-rc7 Status in linux-flo package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Fix Released Bug description: [Impact] * Both mako and flo will receive an upgraded in-kernel bluetooth stack taken from 4.2-rc7 * No other devices are affected * BlueZ 4.101 still used on touch which continues to work as the kernel interface is still supported [Test Case] * testing is documented at https://wiki.ubuntu.com/Process/Merges/TestPlans/bluez [Regression Potential] * Power management issues as newly ported driver and stack prevents the device from going to sleep [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1489327/+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 1489327] Re: Upgrade kernel bluetooth stack to 4.2-rc7
This bug was fixed in the package linux-flo - 3.4.0-5.19 --- linux-flo (3.4.0-5.19) wily; urgency=low [ Simon Fels ] * Import backports 4.2-rc7 - LP: #1489327 * backports: respect already existing redefinitions in the flo tree - LP: #1489327 * backports: import HCI SMD driver - LP: #1489327 * [Config] Enable bluetooth backports - LP: #1489327 [ Upstream Kernel Changes ] * crypto: add CMAC support to CryptoAPI - LP: #1489327 * crypto: af_alg - properly label AF_ALG socket - LP: #1489327 * hid: Backport hid-generic driver - LP: #1489327 * Bluetooth: close HCI device when user channel socket gets closed - LP: #1489327 -- Tim GardnerThu, 03 Sep 2015 10:03:17 -0600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1489327 Title: Upgrade kernel bluetooth stack to 4.2-rc7 Status in linux-flo package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Fix Released Bug description: [Impact] * Both mako and flo will receive an upgraded in-kernel bluetooth stack taken from 4.2-rc7 * No other devices are affected * BlueZ 4.101 still used on touch which continues to work as the kernel interface is still supported [Test Case] * testing is documented at https://wiki.ubuntu.com/Process/Merges/TestPlans/bluez [Regression Potential] * Power management issues as newly ported driver and stack prevents the device from going to sleep [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1489327/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
I tried the fail SKL system with KH2 image. The issue Ray discovered can be reproduced without diwic's patches. So it seems not a regression issue for this fix. Before install patches, no matter HDMI plug or non-plug, the error in comment#12 could happen. With HDMI plugging: failure rate 2/2 Without HDMI plugging: failure rate 2/3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port
Thanks William for your comment. Reading activity following your links, there seems to be differences: * launchpad (here): problem starts immediately, not on receiving heavy traffic. Adapter unusable in practice on USB3 (not even for moderate activity), always ok on USB2. Also, machine feels a little sluggish but no crash, kernel panic or hang observed. * github: reports dmesg but not much detail about what's wrong * bugzilla: "transferring a huge number of files or pretty heavy files caused kernel panic: either I had a stacktrace displayed or the computer became completely unresponsive.", USB3, sometimes USB2. Might be a different bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269883 Title: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in USB3 port yields slow performance, dmesg flooded with errors. Plugging on USB2 port, exact same situation otherwise, works well. This is reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the left, 2 USB2 ports on the right. ### When working (USB2 port) * ethernet auto-negociation is fast * mii-tool is fast (typical 0.05s) * few lines in dmesg * good performance ### When failing : * ethernet auto-negociation fails, then sometimes eventually works * mii-tool is slow (10s of seconds instead of 0.05s) time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m40.014s user 0m0.013s sys 0m0.006s time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m50.015s user 0m0.011s sys 0m0.011s time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m10.051s user 0m0.000s sys 0m0.012s But on some attempts mii-tool is fast... time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m0.057s user 0m0.011s sys 0m0.012s * DHCP eventually completes (after about 30 seconds) then ethernet works. * whole system behaviour feels a little sluggish (not very clear, though) * mii-tool still slow (10s of seconds instead of 0.05s) ## dmesg when failing Full dmesg attached. Specific lines with occurrence count at random point (obtained with "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ). 50 ei_me :00:16.0: reset: wrong host start response 51 ei_me :00:16.0: reset: unexpected enumeration response hbm. 60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING 141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Another attempt 11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110 6 net_ratelimit: 31 callbacks suppressed 9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready 10 net_ratelimit: 30 callbacks suppressed 14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel:
[Kernel-packages] [Bug 1492132] Re: Fix the white noise on Dell laptop
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492132 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Fix Committed Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492132/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
The hang is not a regression, it happens if hdmi is left plugged in when rebooting/shutting down. It doesn't hang if hdmi is plugged in before booting up. This is filed now upstream: https://bugs.freedesktop.org/show_bug.cgi?id=91905 ** Bug watch added: freedesktop.org Bugzilla #91905 https://bugs.freedesktop.org/show_bug.cgi?id=91905 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1492331] Re: kernel crashes on boot (ubuntu as a Hyper-V guest)
This one does not work too. It's nearly the same except for the recovery mode crashing exactly like the standard mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492331 Title: kernel crashes on boot (ubuntu as a Hyper-V guest) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: My Ubuntu 14.04 VM (Hyper-V / Windows Server 2008 R2) crashes directly after the grub boot loader screen. Kernel packages linux- image-3.13.0-62-generic and linux-image-3.13.0-63-generic are affected while linux-image-3.13.0-61-generic works like all previous versions did. Unfortunatly no /var/log/kern.log is written at all with the affected kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+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 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
@Pat: You had any success in reproducing this again? -- 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/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: MX4 r96 This has been happening fro a few weeks Phone automatically connects to the car, you don't have to make or receive a call Leave the car and disconnect Place a call The audio starts out using the phone as expected, after a few seconds the audio switches to bluetooth You can manually change the audio in the UI This happens until you reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+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 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
Same problem on 3.16.0-48-generic, but 3.16.0-46-generic works perfect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux-lts-utopic package in Ubuntu: In Progress Status in linux-lts-utopic source package in Trusty: In Progress Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.494527] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.494941] hv_netvsc vmbus_0_16 eth0: unable to send
[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
** Changed in: linux (Ubuntu) Importance: High => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Won't Fix Bug description: Error: Kernel foolishly shuts down the computer when it overheats because of the underlying bug "Overheat due to slow fans when on 'auto'" ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/751689 ). /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down (Hardware is ok: when the fan is forced to full speed, no overheating.) Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (fix the slow fan bug affecting Lenovo Thinkpads and fix thermald failing to throttle CPU) 3. Put the computer to suspend when it's too hot. The problem has remained the same from at least Ubuntu 11.10 through 14.04 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1486898] Re: bluetooth is not working on kernel version 3.19.0-25-generic
https://lists.ubuntu.com/archives/kernel-team/2013-April/026460.html It now is missing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486898 Title: bluetooth is not working on kernel version 3.19.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: My bluetooth is not not working on ubuntu 14.04. I found that similar issue was resolved on askUbuntu. There i found out that my bluetooth is not supported on "kernel. 3.19.0-25-generic" whereas it was supported on 3.13.0-59. I am using lenovo G50 laptop. Following is the output of necessary commands. dexter@dexter-Lenovo-G50-80:~$ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ lspci -nnk | grep -iA2 net 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10) Subsystem: Lenovo Device [17aa:3821] Kernel driver in use: r8169 03:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 0bda:579a Realtek Semiconductor Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ rfkill list all 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ dmesg | grep -i bluetooth [ 18.546763] Bluetooth: Core ver 2.20 [ 18.546779] Bluetooth: HCI device and connection manager initialized [ 18.546784] Bluetooth: HCI socket layer initialized [ 18.546787] Bluetooth: L2CAP socket layer initialized [ 18.546795] Bluetooth: SCO socket layer initialized [ 18.549488] Bluetooth: RFCOMM TTY layer initialized [ 18.549496] Bluetooth: RFCOMM socket layer initialized [ 18.549500] Bluetooth: RFCOMM ver 1.11 [ 18.701848] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.701851] Bluetooth: BNEP filters: protocol multicast [ 18.701854] Bluetooth: BNEP socket layer initialized dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ uname -a Linux dexter-Lenovo-G50-80 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dexter@dexter-Lenovo-G50-80:~$ hciconfig -a dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ modinfo btusb | grep alias | grep -i 04ca alias: usb:v04CAp*d*dc*dsc*dp*icFFisc01ip01in* alias: usb:v04CAp2003d*dc*dsc*dp*ic*isc*ip*in* dexter@dexter-Lenovo-G50-80:~$ dexter@dexter-Lenovo-G50-80:~$ modinfo btusb | grep -i 105b dexter@dexter-Lenovo-G50-80:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486898/+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 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
My laptop freezes after idling over night at lockscreen. I have Lenovo y410p on Ubuntu 14.04. So far I've been able to "revive" it by going into tty (ctrl+alt+f2) and then do `unity start` which prints some some errors and then brings me to the lockscreen not frozen. The first time I login, screen will flash black for a sec and brings me back to lockscreen and I login again and it works (strange). I haven't tried disabling CPU Power Management yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 Status in linux package in Ubuntu: Confirmed Bug description: Since about the final version of 13.10 (using it since Beta 2), my Lenovo L420 which was running stable until then randomly hard freezes/locks up about once a day while idling. It never happens while I am using the PC, only when I am away. It sometimes runs through a whole night, and sometimes it freezes when I leave it idle for just an hour or so. Once it froze while the screen was not blank yet, same situation. I have tried to disable power management in KDE and run without external screen and external harddisks, just on battery with nothing connected, then it also happens. The screen is usually blank, there is no reaction to either mouse or keyboard, switching to a console not possible, connection through VNC or SSD not possible. I need to hard-shutdown by long-pressing the power button. There is nothing in dmesg or syslog, it just ends and continues with the restarts. No kernel panics or something like that. Any advice on how to trace down the issue or similar experience? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dode 2185 F pulseaudio Date: Wed Nov 27 14:06:00 2013 HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8 InstallationDate: Installed on 2013-09-08 (80 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2) MachineType: LENOVO 78545HG MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET44WW (1.21 ) dmi.board.name: 78545HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 78545HG dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1492707] Re: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', wh
This bug is due to a newer release of the kernel in precide-updates than trusty-updates, but it will only occur if you have both the "precise" and "trusty" repositories enabled (which I have because I'm using libtiff4): root@wildcat:/var/lib/dpkg/info# apt-cache policy linux-image-3.13.0-63-generic linux-image-3.13.0-63-generic: Installed: 3.13.0-63.103 Candidate: 3.13.0-63.104~precise1 Version table: 3.13.0-63.104~precise1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 3.13.0-63.103 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492707 Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 Status in linux package in Ubuntu: Confirmed Bug description: merci! ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tux1544 F pulseaudio /dev/snd/controlC0: tux1544 F pulseaudio Date: Sun Sep 6 11:15:52 2015 DpkgTerminalLog: Preparing to unpack .../linux-image-3.13.0-63-generic_3.13.0-63.104~precise1_amd64.deb ... Done. Unpacking linux-image-3.13.0-63-generic (3.13.0-63.104~precise1) over (3.13.0-63.103) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-63-generic_3.13.0-63.104~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 ErrorMessage: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 HibernationDevice: RESUME=UUID=1da2b137-e09a-4d81-b635-3d509846a761 InstallationDate: Installed on 2015-01-26 (222 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=a16e1781-c815-4cbc-b760-fe4ee43f6db9 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-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Sep 6 10:55:29 tux-To-be-filled-by-O-E-M kernel: [ 2269.128057] usblp0: removed Sep 6 10:56:16 tux-To-be-filled-by-O-E-M kernel: [ 2316.391256] systemd-hostnamed[3169]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Sep 6 11:14:41 tux-To-be-filled-by-O-E-M kernel: [ 3421.713036] init: irqbalance main process (1116) killed by TERM signal dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go
[Kernel-packages] [Bug 1492707] Re: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', wh
[precide] I mean "precise" Fix is to disable the "precide-updates" repository: root@wildcat:/etc/apt/sources.list.d# apt-cache policy linux-image-3.13.0-63-generic linux-image-3.13.0-63-generic: Installed: 3.13.0-63.103 Candidate: 3.13.0-63.103 Version table: *** 3.13.0-63.103 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492707 Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 Status in linux package in Ubuntu: Confirmed Bug description: merci! ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tux1544 F pulseaudio /dev/snd/controlC0: tux1544 F pulseaudio Date: Sun Sep 6 11:15:52 2015 DpkgTerminalLog: Preparing to unpack .../linux-image-3.13.0-63-generic_3.13.0-63.104~precise1_amd64.deb ... Done. Unpacking linux-image-3.13.0-63-generic (3.13.0-63.104~precise1) over (3.13.0-63.103) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-63-generic_3.13.0-63.104~precise1_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 DuplicateSignature: package:linux-image-3.13.0-63-generic:3.13.0-63.103:trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 ErrorMessage: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 HibernationDevice: RESUME=UUID=1da2b137-e09a-4d81-b635-3d509846a761 InstallationDate: Installed on 2015-01-26 (222 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=a16e1781-c815-4cbc-b760-fe4ee43f6db9 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-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-63-generic 3.13.0-63.103 failed to install/upgrade: trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-extra-3.13.0-63-generic 3.13.0-63.103 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Sep 6 10:55:29 tux-To-be-filled-by-O-E-M kernel: [ 2269.128057] usblp0: removed Sep 6 10:56:16 tux-To-be-filled-by-O-E-M kernel: [ 2316.391256] systemd-hostnamed[3169]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Sep 6 11:14:41 tux-To-be-filled-by-O-E-M kernel: [ 3421.713036] init: irqbalance main process (1116) killed by TERM signal dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492707/+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 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs
We have tested the patched kernel on one network intensive (high packet) workload with max_cstate=1 and ondemand governor disabled and it has lower network throughput than the default kernel had with intel_pstate=enable. There also appears to be a futex performance issue with the c4.8xlarge which we are still investigating and may be contributing to the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1477171 Title: Enable intel_pstate by default on Trusty EC2 AMIs Status in linux package in Ubuntu: In Progress Bug description: Please can the intel_pstate driver be enabled by default on the Ubuntu EC2 AMIs. On instances with support for C-states and P-States [1] there is a notable performance impact and lack of support for higher clock frequencies available due to the use of the acpi-cpufreq driver. For example on a c4.8xlarge the default frequency is limited to 2.9GHz when 3.2GHz is supported by the chip [2]. Some additional analysis is available here [3] and re-enabling it by default has been discussed [4] but this request is specifically for the EC2 AMIs. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html [3] http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647 AMI: ami-47a23a30 (eu-west-1) $ lsb_release -d Description:Ubuntu 14.04.2 LTS $ uname -a Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Default configuration (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.90 GHz available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.90 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51% (5) boost state support: Supported: yes Active: yes With intel_pstate enabled (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.20 GHz - 3.50 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.20 GHz and 3.50 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 3.20 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 12 17:19 seq crw-rw 1 root audio 116, 33 Aug 12 17:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [39221.196411] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-47a23a30 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c4.8xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=877c5daf-9427-49e3-8656-437c3f30fc84 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
[Kernel-packages] [Bug 1046800] Re: Wi-Fi intermittent and slow -- Atheros AR9287 ath9k
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1046800 Title: Wi-Fi intermittent and slow -- Atheros AR9287 ath9k Status in linux package in Ubuntu: Fix Released Bug description: Wireless transfer is extremely slow (and choppy, hangs, slows down, speeds up, stops for some time). Expectet transfer speed using ssh (one ubuntu.iso 700MB file) is 5-7MB/s Actual transfer speed using ssh (one ubuntu.iso 700MB file) is 0-1MB/s iwconfig: IEEE 802.11bgn ESSID:"Twin" Mode:Managed Frequency:2.437 GHz Access Point: 74:44:01:36:DE:44 Bit Rate=144.4 Mb/s Tx-Power=16 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=70/70 Signal level=-31 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:217 Invalid misc:804 Missed beacon:0 Additional info: I've got Ubuntu 12.04 and 12.10 on this laptop. Wireless is working as expected in 12.04. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Thu Sep 6 13:53:43 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120820) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.61 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1b8d8726d-a290-4718-9e08-d70dc2436c4f 802-3-ethernet1346798450 Wed 05 Sep 2012 12:40:50 AM CEST yes no /org/freedesktop/NetworkManager/Settings/2 Evjenveien 99bd99ae224-97f8-4563-a707-dddf57642914 802-11-wireless 1346523533 Sat 01 Sep 2012 08:18:53 PM CEST yes no /org/freedesktop/NetworkManager/Settings/1 Twin 2830871f-6c1f-4e2d-8ceb-6e594029373b 802-11-wireless 1346932350 Thu 06 Sep 2012 01:52:30 PM CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046800/+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 1490545] Re: [Hyper-V] lis daemons not active after install on Ubuntu 15.10 Wily Werewolf
In the latest daily built - Sept 7th, all 3 LIS daemons are automatically started after install & reboot. Can you please confirm if this got fixed or further tracking is needed here. root@ubuntu7sept:~# dpkg -l | grep linux-tools ii linux-tools-4.2.0-74.2.0-7.7 amd64 Linux kernel version specific tools for version 4.2.0-7 ii linux-tools-4.2.0-7-generic4.2.0-7.7 amd64 Linux kernel version specific tools for version 4.2.0-7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490545 Title: [Hyper-V] lis daemons not active after install on Ubuntu 15.10 Wily Werewolf Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: Confirmed Bug description: While testing Ubuntu 15.10 Wily Werewolf (development branch) 64bit we found that kvp, vss and fcopy daemons aren't active after install. Repro rate: 100% Repro details: Hyper-V: Server 2012 R2 Daily build version: 2015.08.31 What we did: root@ubuntu:~# apt-get install linux-tools-`uname -r` root@ubuntu:~# apt-get install linux-cloud-tools-`uname -r` In the install logs I found the following lines: hv-fcopy-daemon.service is a disabled or a static unit, not starting it. hv-vss-daemon.service is a disabled or a static unit, not starting it. hv-kvp-daemon.service is a disabled or a static unit, not starting it. After reboot, the kvp, vss and fcopy daemons should have started. All of them are inactive (dead) instead. root@ubuntu:~# systemctl status hv-kvp-daemon.service ? hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; disabled; vendor preset: enabled) Active: inactive (dead) The solution is to start each of them manually. The bellow applies to vss and fcopy daemons too. root@ubuntu:~# systemctl enable hv-kvp-daemon.service Created symlink from /etc/systemd/system/multi-user.target.wants/hv-kvp-daemon.service to /lib/systemd/system/hv-kvp-daemon.service. After reboot, the daemons are active. root@ubuntu:~# systemctl status hv-kvp-daemon.service ? hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-08-31 15:22:49 EEST; 23s ago Main PID: 899 (hv_kvp_daemon) CGroup: /system.slice/hv-kvp-daemon.service +-899 /usr/lib/linux-tools/4.1.0-3-generic/hv_kvp_daemon -n Aug 31 15:22:49 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon. Aug 31 15:22:49 ubuntu KVP[899]: KVP starting; pid is:899 Aug 31 15:22:49 ubuntu KVP[899]: KVP LIC Version: 3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490545/+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 1492939] Re: Enhancement request: please document how to build kernel in PPA
No logs should be required as this is a wishlist regarding kernel/launchpad documentation. ** 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/1492939 Title: Enhancement request: please document how to build kernel in PPA Status in linux package in Ubuntu: Confirmed Bug description: Hi, In the process of working around an issue that has appeared in the linux kernel after the patch series "convert host_busy to atomic_t" (see bug 1451277), I would like to compile kernel deb packages that work around the issue in a PPA, using patches that appeared on the LKML. Unfortunately, it is unclear to me how to build a kernel in a PPA. Simply taking the kernel source package, applying the patch, rebuilding the source package and uploading to the PPA fails to build in the PPA (due to ABI checks, I believe). I have not been able to find any up to date instruction on how to create a kernel source package with just a trivial patch on top of the current ubuntu kernel and build it in a PPA. - Instructions in https://wiki.ubuntu.com/Kernel/Dev/KernelBuildScripts do not seem recent and appear to involve much more than what is needed for my case. Most important, they fail at the invocation of the build-mkppa command. - Instructions in http://ubuntuforums.org/showthread.php?t=1682345 seem to work, but they are very unofficial and look like black magic. Specifically, what are those parameters supposed to do and why are they needed? Why do these parameter make the built kernel a very different size than the original one? A minor patch should not make this difference. Altogether, can up to date, official instructions for building the Ubuntu kernel + a patch in a PPA be added somewhere? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492939/+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 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs
Ping, any updates on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1477171 Title: Enable intel_pstate by default on Trusty EC2 AMIs Status in linux package in Ubuntu: In Progress Bug description: Please can the intel_pstate driver be enabled by default on the Ubuntu EC2 AMIs. On instances with support for C-states and P-States [1] there is a notable performance impact and lack of support for higher clock frequencies available due to the use of the acpi-cpufreq driver. For example on a c4.8xlarge the default frequency is limited to 2.9GHz when 3.2GHz is supported by the chip [2]. Some additional analysis is available here [3] and re-enabling it by default has been discussed [4] but this request is specifically for the EC2 AMIs. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html [3] http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647 AMI: ami-47a23a30 (eu-west-1) $ lsb_release -d Description:Ubuntu 14.04.2 LTS $ uname -a Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Default configuration (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.90 GHz available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.90 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51% (5) boost state support: Supported: yes Active: yes With intel_pstate enabled (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.20 GHz - 3.50 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.20 GHz and 3.50 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 3.20 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 12 17:19 seq crw-rw 1 root audio 116, 33 Aug 12 17:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [39221.196411] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-47a23a30 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c4.8xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=877c5daf-9427-49e3-8656-437c3f30fc84 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-61-generic x86_64 UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
** Attachment added: "photo of the virtual terminal after the freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458832/+files/screenshot-freeze.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+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 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
I see there was no reply, if you look at the top it says this bug is for that type card. But it is not in the Kernel yet, looks like 4.3 might have it ready. You have to do the work around described above. It did not work for me, but I have seen some config info from any successful results, and there is always some variation to my situation Lenovo G50-45 with that type card. See this link for info on this specific card in Fedora bug group and links to next Kernel info. https://bugzilla.redhat.com/show_bug.cgi?id=1257500 Bob ** Bug watch added: Red Hat Bugzilla #1257500 https://bugzilla.redhat.com/show_bug.cgi?id=1257500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+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 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
@kashyap-desai thanks for checking. AFAICT it's been at 1024 for at least the 14.04 release as well. Thanks for noting what FW status 0x3 means, that will help any future tests we 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/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+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 1492891] Re: Implement standalone bluetooth agent handler
*** This bug is a duplicate of bug 1492892 *** https://bugs.launchpad.net/bugs/1492892 ** This bug has been marked a duplicate of bug 1492892 Implement standalone bluetooth agent handler -- 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/1492891 Title: Implement standalone bluetooth agent handler Status in bluez package in Ubuntu: New Bug description: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492891/+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 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
For the records, here's a screenshot (photo) of the system after a freeze. Series of actions to get there: 1. enable kernel debug output 2. detach external mouse, to verify that messages appear 3. hit enter to get a new prompt line 4. trigger the freeze with "lsusb -v" lsusb prints the name of the device it's going to work with. Then nothing anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+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 1493181] [NEW] Light button does not work
Public bug reported: The key is not working even with fn. Soft button works ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jrgr 1505 F pulseaudio /dev/snd/controlC0: jrgr 1505 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 7 19:41:41 2015 HibernationDevice: RESUME=UUID=70146d4a-224a-43d6-b1a4-7df91acb0ab6 InstallationDate: Installed on 2015-09-04 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8b06 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=4f20374b-6d28-4619-b47c-8608fb41d2c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1493181 Title: Light button does not work Status in linux package in Ubuntu: New Bug description: The key is not working even with fn. Soft button works ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jrgr 1505 F pulseaudio /dev/snd/controlC0: jrgr 1505 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 7 19:41:41 2015 HibernationDevice: RESUME=UUID=70146d4a-224a-43d6-b1a4-7df91acb0ab6 InstallationDate: Installed on 2015-09-04 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8b06 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=4f20374b-6d28-4619-b47c-8608fb41d2c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1493181] 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/1493181 Title: Light button does not work Status in linux package in Ubuntu: Confirmed Bug description: The key is not working even with fn. Soft button works ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jrgr 1505 F pulseaudio /dev/snd/controlC0: jrgr 1505 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 7 19:41:41 2015 HibernationDevice: RESUME=UUID=70146d4a-224a-43d6-b1a4-7df91acb0ab6 InstallationDate: Installed on 2015-09-04 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03eb:8b06 Atmel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=4f20374b-6d28-4619-b47c-8608fb41d2c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493181/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
Patch verification result is positive. Please check the detail result in http://bit.ly/1ECAeth After install patches in comment #8, HDMI hot-plugging is detectable and functions works well. test platforms: TUSL4-E3-C2(SKL), MASL5-E2-C1(SKL), HOU4-E3-C1B(BDW), Inspiron 3442 (HSW) test kernel: 3.19.0-27 install patches:linux-headers-3.19.0-27-generic_3.19.0-27.29+bpo2.2_amd64.deb, linux-image-3.19.0-27-generic_3.19.0-27.29+bpo2.2_amd64.deb, linux-image-3.19.0-27-generic_3.19.0-27.29+bpo2.2_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
** Attachment added: "audio_icon_gone-log.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+attachment/4459004/+files/audio_icon_gone-log.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
One additional information for comment#17 When verified fix patch, audio icon disappeared once after reboot system with HDMI connected. Please refer attached screenshot and log. Can not recover this issue by reboot/power off system. After recover the system and check the clean system without patch, can not reproduce this issue anymore. Without patch reboot for 5 times: can not reproduce power off for times: can not reproduce With patch reboot for 5 times: can not reproduce power off for times: can not reproduce Conclusion There is no evidence that the audio icon disappear issue is a regression of this fix patch. ** Attachment added: "audio_icon_gone.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+attachment/4459003/+files/audio_icon_gone.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/1490895 Title: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: This is a long-standing bug for some Haswell, Broadwell and most Skylake machines. When the HDA audio controller is in D3, a hotplug event (i e, HDMI or DisplayPort being plugged in) fails to wake up the audio side so it never registers that something has happened. By having the i915 driver call directly into the hda driver, the HDA driver is always notified that an HDMI hotplug event has happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1468852] Re: suspen resume error
[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/1468852 Title: suspen resume error Status in linux package in Ubuntu: Expired Bug description: Whenever I suspend my system, it is not able to resume Please Help ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jun 25 23:25:34 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02aa] Subsystem: Dell Device [1028:02aa] InstallationDate: Installed on 2015-06-24 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 1545 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic root=UUID=52f6f447-e97b-4a2b-9a67-d71cba5b6df8 ro rootflags=sync quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0U315R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/27/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0U315R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 25 23:19:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 614 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468852/+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 1480615] Re: [Dell Latitude E6540] ALPS touchpad and buttons work only in a single window.
So here is where I am now with the latest kernel update from a few days ago and everything up-to-date apt-get wise: $ uname -a Linux COMPUTER 3.16.0-48-generic #64~14.04.1-Ubuntu SMP Thu Aug 20 23:03:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux As mentioned above, when I reboot, xinput report an incorrect device and there are various issues with using the touchpad. I am doing a : modprobe -r psmouse && modprobe psmouse After that xinput reports AlpsPS/2 ALPS DualPoint TouchPad correctly and from that point on, things are working mostly fine. Now and then if the touchpad stops working correctly, things are resolved by pressing Fn+F5 twice (effectively disabling then enabling the touchpad). If I ever go in suspend mode, I need to always press Fn+F5 twice to get a functional touchpad. Please advise on the next setps I should take. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480615 Title: [Dell Latitude E6540] ALPS touchpad and buttons work only in a single window. Status in linux package in Ubuntu: Confirmed Bug description: This is a kernel that has these recent ALPS related patches: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837 So after a reboot the touchpad and button work fine, at start. After a while the buttons, a single tap click, a double tap-click and the dual finger scrolling stop working on the correct front-most window and work instead on a background window. If I Alt-tab to bring the window that receives the touchpad events to front, it receives it ok, so this one window gets mouse events. Using either the touchpad or the glidepoint is then limited to this window at this point. Going to a terminal with ctrl-alt-f1 just a few seconds and then back to ctrl-alt-f7 restores things to normal for a while. Until its starts again. No dmesg nor syslog show up. ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pombreda 1995 F pulseaudio /dev/snd/controlC0: pombreda 1995 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=801124f8-51bc-4bec-accf-ba187acdece1 InstallationDate: Installed on 2015-05-16 (77 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Latitude E6540 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-45-generic root=UUID=df7edfbc-4df5-4603-a42b-c39f769bbb44 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-45-generic N/A linux-backports-modules-3.16.0-45-generic N/A linux-firmware 1.127.14 Tags: trusty Uname: Linux 3.16.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/19/2015:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 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/1480615/+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 1471969] Re: System freezing after install of latest kernel a few days ago
[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/1471969 Title: System freezing after install of latest kernel a few days ago Status in linux package in Ubuntu: Expired Bug description: My system is locking up, while using Mozilla FireFox, after installing latest version of Mint 17 kernel. I can use Ctrl-Alt-Bsp to kill the instance of FF, but this re-occurs now every time I start to use FF. Could this be a problem with kernel handling of Nvidia graphics? I have older 8600 graphics. Other sytem attributes: AMD64x2 w 4GB ram, 1TB Hard drive, Viewsonic LED 1080p, 24inch. Again, no problems with this system until a few days ago when I upgraded to latest kernel. I always install all system updates as soon as I receive notice. Any way to get back to older kernel? No previous kernel updates caused any problems! Thx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471969/+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 1471616] Re: DVB device initialisation issue
[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/1471616 Title: DVB device initialisation issue Status in linux package in Ubuntu: Expired Bug description: Hi, I have a PCI card to receive DVB television on my desktop computer. The card works, but only if I restart the computer from Windows. I believe that Windows initializes something that does not get erased when the computer restarts, and Ubuntu does not initialize this when it boots. This initialization gets erased when Ubuntu goes to sleep too. Please let me know any command that I could run to see differences between the card's configuration when it works and when it doesn't. Here is my lspci -vvnn for this device: 0b:02.0 Multimedia controller [0480]: Philips Semiconductors SAA7146 [1131:7146] (rev 01) Subsystem: KNC One Device [1894:0030] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471616/+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 1472164] Re: Laptop hangs when laptop lid is closed.
[Expired for bcmwl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bcmwl (Ubuntu) Status: Incomplete => Expired -- 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/1472164 Title: Laptop hangs when laptop lid is closed. Status in bcmwl package in Ubuntu: Expired Bug description: When I close lid my laptop hangs. It seems kernel crash. All leds are blink. # uname Linux lenovo-e43 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -rd Description:Ubuntu 15.04 Release:15.04 # cat /proc/version_signature Ubuntu 3.19.0-21.21-generic 3.19.8 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-21-generic 3.19.0-21.21 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: y 1237 F pulseaudio Date: Tue Jul 7 11:26:36 2015 HibernationDevice: RESUME=UUID=e2ce43e2-fe05-440e-aa8a-37ed70c9e5b8 InstallationDate: Installed on 2015-06-21 (15 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO Lenovo E43 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=071f2c69-8872-4ab4-a052-70efefef37ec ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 0DCN82WW dmi.board.name: LE9 dmi.board.vendor: Lenovo dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr0DCN82WW:bd07/29/2010:svnLENOVO:pnLenovoE43:pvrRev1.0:rvnLenovo:rnLE9:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: Lenovo E43 dmi.product.version: Rev 1.0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1472164/+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 1493143] [NEW] rtl8723be wifi unusable on lenovo ideapad y50-70
Public bug reported: I obtained a lenovo y50-70 a few weeks ago, and installed ubuntu 14.04.3 LTS on it (dual boot with windows 8 that came pre-installed). $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 I have not been able to get the rtl8723be wifi adapter to work yet. If it will connect to a wifi network at all (which is rare), it will be choppy (10% to 50% packet loss on a ping to the default gateway) and usually disconnect after a few minutes. The internet suggests a few work-arounds: - run with fwlps=0 ips=0 as options to the rtl8723be module (eg. http://askubuntu.com/questions/590414/wifi-problems-with-rtl8723be-in-ubuntu-14-04) - install an alternative driver (eg. http://askubuntu.com/questions/590414/wifi-problems-with-rtl8723be-in-ubuntu-14-04) http://paste.ubuntu.com/1230961 However, none of those suggested worked for me. I have tried downgrading the kernel down to 3.13.0-62, and various kernels in between, but none of that helped either. Output of the wireless-info script here: http://paste.ubuntu.com/12309610/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.19.0-26-generic 3.19.0-26.28~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 Date: Mon Sep 7 21:18:25 2015 InstallationDate: Installed on 2015-08-21 (17 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1493143 Title: rtl8723be wifi unusable on lenovo ideapad y50-70 Status in linux-lts-vivid package in Ubuntu: New Bug description: I obtained a lenovo y50-70 a few weeks ago, and installed ubuntu 14.04.3 LTS on it (dual boot with windows 8 that came pre-installed). $ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 I have not been able to get the rtl8723be wifi adapter to work yet. If it will connect to a wifi network at all (which is rare), it will be choppy (10% to 50% packet loss on a ping to the default gateway) and usually disconnect after a few minutes. The internet suggests a few work-arounds: - run with fwlps=0 ips=0 as options to the rtl8723be module (eg. http://askubuntu.com/questions/590414/wifi-problems-with-rtl8723be-in-ubuntu-14-04) - install an alternative driver (eg. http://askubuntu.com/questions/590414/wifi-problems-with-rtl8723be-in-ubuntu-14-04) http://paste.ubuntu.com/1230961 However, none of those suggested worked for me. I have tried downgrading the kernel down to 3.13.0-62, and various kernels in between, but none of that helped either. Output of the wireless-info script here: http://paste.ubuntu.com/12309610/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.19.0-26-generic 3.19.0-26.28~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 Date: Mon Sep 7 21:18:25 2015 InstallationDate: Installed on 2015-08-21 (17 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1493143/+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 1436940] Re: Atheros wifi 168c:0041(QCA6174) is not supported
** Summary changed: - Atheros wifi 168c:0041(QCA6164) is not supported + Atheros wifi 168c:0041(QCA6174) is not supported -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6174) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+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