[Kernel-packages] [Bug 1381906] [NEW] [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
Public bug reported: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Anthony Wong (anthonywong) Status: New ** Tags: 201406-15271 amd64 apport-bug blocks-hwcert taipei-lab trusty ** Attachment added: Screenshot.png https://bugs.launchpad.net/bugs/1381906/+attachment/4237927/+files/Screenshot.png ** Also affects: hwe-next 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/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: New Status in “linux” package in Ubuntu: New Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1381906] Re: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
** Attachment added: dmesg.log https://bugs.launchpad.net/hwe-next/+bug/1381906/+attachment/4237944/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: New Status in “linux” package in Ubuntu: New Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+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 1381906] Re: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
After the Bluetooth is gone, boot it with a LiveUSB and reboot normally could bring it back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: New Status in “linux” package in Ubuntu: New Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+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 1371591] Re: file not initialized to 0s under some conditions on VMWare
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Bug description: Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+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 1377851] Re: Kernel panic skb_segment+0x5d7/0x980
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377851 Title: Kernel panic skb_segment+0x5d7/0x980 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: On two Ubuntu 14.04 amd64 servers with tg3 NICs acting as a openvpn gateway we recently had a lot of trouble with kernel panics (linux-image-3.13.0-36-generic 3.13.0-36.63) The panics were kind of random happening sometimes already during the boot process and sometimes a couple of hours later. The boxes were running perfectly find for a couple of months before. We believe some kind of special packet triggered the bug. Potential related bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331219 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313591 Upgrading to linux-image-3.16.3-031603-generic (3.16.3-031603.201409171435) solved the problem for us. [ 6076.726520] BUG: unable to handle kernel NULL pointer dereference at 006c [ 6076.737716] IP: [81616787] skb_segment+0x5d7/0x980 [ 6076.745780] PGD 0 [ 6076.748641] Oops: [#1] SMP [ 6076.753268] Modules linked in: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cdc_ether usbnet mii mpt3sas mpt2sas raid_class scsi_transport_sas mptctl mptbase ipmi_si ipmi_devintf dell_rbu gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 8021q garp stp mrp llc sb_edac edac_core shpchp joydev pl2303 usbserial lpc_ich wmi mei_me mei mac_hid acpi_power_meter ioatdma nf_conntrack dca lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 tg3 ahci hid_generic raid0 ptp usbhid multipath hid libahci pps_core linear [last unloaded: ipmi_si] [ 6076.850743] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.13.0-36-generic #63-Ubuntu [ 6076.861485] Hardware name: Dell Inc. PowerEdge R620/0PXXHP, BIOS 1.6.0 03/07/2013 [ 6076.872104] task: 880223841800 ti: 880223848000 task.ti: 880223848000 [ 6076.882722] RIP: 0010:[81616787] [81616787] skb_segment+0x5d7/0x980 [ 6076.894243] RSP: 0018:880227263790 EFLAGS: 00010246 [ 6076.901769] RAX: 0646 RBX: 88021f03f000 RCX: 8801ed4fff00 [ 6076.911893] RDX: 0646 RSI: 00c2 RDI: ea0007f6de00 [ 6076.971665] RBP: 880227263858 R08: fff6 R09: 0001 [ 6077.031463] R10: 88021f03e800 R11: 00010552 R12: 8801fdb1fc80 [ 6077.091313] R13: 0001 R14: R15: 0646 [ 6077.151619] FS: () GS:88022726() knlGS: [ 6077.262424] CS: 0010 DS: ES: CR0: 80050033 [ 6077.320083] CR2: 006c CR3: 01c0e000 CR4: 000407e0 [ 6077.379854] Stack: [ 6077.433555] 811a48f9 8802272772c0 fff6 000a [ 6077.546280] 00010552 006a 88021f03e800 00010020 [ 6077.658915] ffe4 00010012 001c055c 88021f03f000 [ 6077.771400] Call Trace: [ 6077.824494] IRQ [ 6077.827251] [811a48f9] ? __kmalloc_node_track_caller+0xb9/0x290 [ 6077.933211] [8168149d] tcp_gso_segment+0x10d/0x3f0 [ 6077.988641] [81691822] inet_gso_segment+0x132/0x360 [ 6078.043154] [810a5db2] ? enqueue_task_fair+0x422/0x6c0 [ 6078.097358] [81623ffc] skb_mac_gso_segment+0x9c/0x180 [ 6078.150464] [816a0fb4] gre_gso_segment+0x134/0x370 [ 6078.202321] [8109828d] ? ttwu_do_activate.constprop.74+0x5d/0x70 [ 6078.255348] [81691822] inet_gso_segment+0x132/0x360 [ 6078.306129] [8109a800] ? try_to_wake_up+0x240/0x2c0 [ 6078.355712] [81623ffc] skb_mac_gso_segment+0x9c/0x180 [ 6078.404660] [8162413d] __skb_gso_segment+0x5d/0xb0 [ 6078.452918] [8162444a] dev_hard_start_xmit+0x18a/0x560 [ 6078.501057] [8164360e] sch_direct_xmit+0xee/0x1c0 [ 6078.548821] [81624a50]
[Kernel-packages] [Bug 1375266] Re: amd-iommu: kernel BUG lockup after shutting down KVM guest using PCI passthrough/PCIe bridge
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375266 Title: amd-iommu: kernel BUG lockup after shutting down KVM guest using PCI passthrough/PCIe bridge Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: SRU Justification: [Impact] When using a KVM VM and adding certain combinations of PCI/PCI-e devices an oops and freeze can occur when shutting down a VM. [Fix] Commit 9b29d3c6510407d91786c1cf9183ff4debb3473a which is upstream in 3.17-rc2 and in stable/3.16.y. This fix changes how cleanup_domain detaches device, instead of using the list_for_each_entyr_safe macro, it just iterates through the devices and removes the first element. [Test Case] Create KVM VM with a specific configuration of PCI/PCIe devices, and shutdown the VM. See https://bugzilla.kernel.org/show_bug.cgi?id=81841 for details. -- This kernel lockup bug was reported to and fixed upstream: https://bugzilla.kernel.org/show_bug.cgi?id=81841 Please backport the stable kernel patch to Ubuntu kernels (at least trusty, which I use in this setup): https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9b29d3c6510407d91786c1cf9183ff4debb3473a ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Mon Sep 29 16:19:50 2014 HibernationDevice: RESUME=UUID=54378db4-8de4-45f0-b7cb-2d8e1097139d InstallationDate: Installed on 2014-09-04 (25 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=a8f2d0ae-f43e-47de-9ef9-99fed8c9c78e ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: FM2A88X Extreme6+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd01/24/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme6+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1375266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1352056] Re: linux: kdump on Ubuntu 14.04 is not generating a dump.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352056 Title: linux: kdump on Ubuntu 14.04 is not generating a dump. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use crashdumps to do kernel debugging. [Fix] Commit upstream and already in utopic: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=429d2e8342954d337abe370d957e78291032d867 [Test Case] Taken from: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe https://help.ubuntu.com/14.04/serverguide/kernel-crash-dump.html 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg set crashkernel=1024M sudo update-grub 3) reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show # should return no errors 6) echo 'c' | sudo tee /proc/sysrq-trigger 7) This should crash the machine and we should kexec into another kernel to dump the core, then on the next reboot we should see a crash in /var/crash/* -- ---Problem Description--- kdump is not producing a dump on powerKVM LE P8 Ubuntu 14.04 ---uname output--- 3.13.0-30-generic ---Additional Hardware Info--- Power8 LE configuration. ---Patches Installed--- 1324544 - kdump-config load fails with vmlinux kernel (vs. vmlinuz) Machine Type = 8247-22L ---Steps to Reproduce--- Installed kdump-tools 1.5.5-2ubuntu1 and crash 7.0.3-3ubuntu3. Updated /etc/default/kdump-tools, first I updated just USE_KDUMP=1. Rebooted the node and see: root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash crashkernel=384M-:128M root@c656f2n02:~# cat /proc/sys/kernel/sysrq 1 root@c656f2n02:~# cat /proc/sys/kernel/sysrq 1 root@c656f2n02:~# ^Cnd /proc | grep sysrq root@c656f2n02:~# kdump-config status current state : ready to kdump root@c656f2n02:~# kdump-config show USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: current state:ready to kdump kexec command: /sbin/kexec -p --args-linux --command-line=root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash irqpoll maxcpus=1 nousb --initrd=/boot/initrd.img-3.13.0-30-generic /boot/vmlinux-3.13.0-30-generic root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_crash_loaded 1 root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_loaded 0 echo c /proc/sysrq-trigger root@c656f2n02:/var/log# echo c /proc/sysrq-trigger [ 1956.014243] SysRq : Trigger a crash [ 1956.014328] Unable to handle kernel paging request for data at address 0x [ 1956.014404] Faulting instruction address: 0xc0586c2c [ 1956.014468] Oops: Kernel access of bad area, sig: 11 [#1] [ 1956.014518] SMP NR_CPUS=2048 NUMA PowerNV [ 1956.014570] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 rdma_ucm(OF) ib_ucm(OF) rdma_cm(OF) iw_cm(OF) ib_ipoib(OF) ib_cm(OF) ib_uverbs(OF) ib_umad(OF) mlx5_ib(OF) mlx5_core(OF) mlx4_ib(OF) ib_sa(OF) ib_mad(OF) ib_core(OF) ib_addr(OF) mlx4_en(OF) mlx4_core(OF) compat(OF) nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache rtc_generic powernv_rng ses enclosure ipr [ 1956.015306] CPU: 146 PID: 2522 Comm: bash Tainted: GF O 3.13.0-30-generic #54-Ubuntu [ 1956.015394] task: c03fcabda120 ti: c03fcac58000 task.ti: c03fcac58000 [ 1956.015469] NIP: c0586c2c LR: c0587b8c CTR: c0586c00 [ 1956.015543] REGS: c03fcac5b820 TRAP: 0300 Tainted: GF O (3.13.0-30-generic) [ 1956.015617] MSR: 90009033 SF,HV,EE,ME,IR,DR,RI,LE CR: 42422822 XER: 2000 [ 1956.015804] CFAR: c0009318 DAR: DSISR: 4200 SOFTE: 0 GPR00: c0587b8c c03fcac5baa0 c162e840 0063 GPR04: c2f45bd0 c2f564c8 00015ad0 c1827480 GPR08:
[Kernel-packages] [Bug 1372482] Re: mount.cifs does not work with the 3.13.0.36-generic kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372482 Title: mount.cifs does not work with the 3.13.0.36-generic kernel Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Invalid Bug description: mount.cifs //server_ip/share_name mount_point -o user=user Password... mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) From syslog: Sep 22 15:41:04 ds1205 kernel: [ 11.778362] [ cut here ] Sep 22 15:41:04 ds1205 kernel: [ 11.778370] WARNING: CPU: 3 PID: 2253 at /build/buildd/linux-3.13.0/fs/cifs/transport.c:313 smb_send_rqst+0x215/0x270 [cifs]() Sep 22 15:41:04 ds1205 kernel: [ 11.778371] Send length mismatch(send_length=72 smb_buf_length=2164260932) Sep 22 15:41:04 ds1205 kernel: [ 11.778372] Modules linked in: cuse rfcomm bnep bluetooth binfmt_misc snd_hda_codec_realtek nls_utf8 cifs fscache intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_hda_codec kvm_intel kvm snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc ghash_clmulni_intel i915 snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw snd_rawmidi gf128mul snd_seq glue_helper ablk_helper snd_seq_device drm_kms_helper cryptd snd_timer drm keucr(C) parport_pc i2c_algo_bit hid_generic snd mei_me ppdev mei usb_storage lp soundcore serio_raw lpc_ich parport wmi mac_hid video usbhid hid psmouse ahci libahci r8169 mii Sep 22 15:41:04 ds1205 kernel: [ 11.778395] CPU: 3 PID: 2253 Comm: mount.cifs Tainted: GWC3.13.0-36-generic #63-Ubuntu Sep 22 15:41:04 ds1205 kernel: [ 11.778396] Hardware name: Hewlett-Packard HP Pro 3500 Series/2ABF, BIOS 8.11 10/24/2012 Sep 22 15:41:04 ds1205 kernel: [ 11.778397] 0009 8800ccaf7bb0 8171e569 8800ccaf7bf8 Sep 22 15:41:04 ds1205 kernel: [ 11.778399] 8800ccaf7be8 8106775d 8800ccaf7d00 88020fecb800 Sep 22 15:41:04 ds1205 kernel: [ 11.778401] 8800ccaf7cc8 0001 8800ccaf7c48 Sep 22 15:41:04 ds1205 kernel: [ 11.778403] Call Trace: Sep 22 15:41:04 ds1205 kernel: [ 11.778406] [8171e569] dump_stack+0x45/0x56 Sep 22 15:41:04 ds1205 kernel: [ 11.778408] [8106775d] warn_slowpath_common+0x7d/0xa0 Sep 22 15:41:04 ds1205 kernel: [ 11.778409] [810677cc] warn_slowpath_fmt+0x4c/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778415] [a04904c5] smb_send_rqst+0x215/0x270 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778417] [81690218] ? __inet_stream_connect+0x208/0x320 Sep 22 15:41:04 ds1205 kernel: [ 11.778422] [a049055d] smb_sendv+0x3d/0x40 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778426] [a0490588] smb_send+0x28/0x30 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778430] [a047a15d] generic_ip_connect+0x30d/0x3e0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778432] [811a1d65] ? __kmalloc+0x55/0x230 Sep 22 15:41:04 ds1205 kernel: [ 11.778437] [a047e69c] cifs_mount+0x85c/0xaf0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778440] [a046d040] cifs_do_mount+0xa0/0x4d0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778442] [811c10a9] mount_fs+0x39/0x1b0 Sep 22 15:41:04 ds1205 kernel: [ 11.778444] [811dc447] vfs_kern_mount+0x67/0x110 Sep 22 15:41:04 ds1205 kernel: [ 11.778446] [811deca4] do_mount+0x244/0xb20 Sep 22 15:41:04 ds1205 kernel: [ 11.778448] [811530be] ? __get_free_pages+0xe/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778450] [811de8e6] ? copy_mount_options+0x36/0x170 Sep 22 15:41:04 ds1205 kernel: [ 11.778451] [811df873] SyS_mount+0x83/0xc0 Sep 22 15:41:04 ds1205 kernel: [ 11.778453] [8172efad] system_call_fastpath+0x1a/0x1f Sep 22 15:41:04 ds1205 kernel: [ 11.778454] ---[ end trace 826c79e22eb80bab ]--- Sep 22 15:41:04 ds1205 kernel: [ 11.779826] CIFS VFS: Error connecting to socket. Aborting operation. Sep 22 15:41:04 ds1205 kernel: [ 11.779890] CIFS VFS: cifs_mount failed w/return code = -5 I cannot mount share from Samba 3.6.6, but I can mount a share from a Windows 2003 server.
[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371316 Title: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: SRU justification Impact: when using IMA with aufs in trusty potential exists for very hard to diagnose lockups. Testcase: enable IMA and use an aufs filesystem. Regression Potential: the fix is an upstream cherry-pick from the version of aufs in Utopic which is used widly for lxc there so regression potential is low. The fix removes code which also lessens the risk. === The trusty kernel misses the following patch that already landed in utopic with the recent aufs update: https://github.com/sfjro/aufs3-linux/commit/7aac34b421441b701cd0e6de4685b51e4c462d67 This unbreaks aufs with IMA (Integrity Measurement Architecture) enabled. When IMA is enabled and mmaps are being tracked, the kernel hits a lock ordering bug because a needed semaphore is already held. This patch fixes this issue by not calling out to IMA for the access to the underlying file. However IMA will still see the access to the file in the merged aufs, which should be good enough. Please cherry-pick above patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+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 1358116] Re: The mute led status can't be kept after s3/s4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 Status in HWE Next Project: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: Steps to Reproduce: 1.Unbundle Ubuntu 14WWLTAL6ak on Some HP laptops 2. Turn off the sound via Mute button, the Mute LED is turned to Amber. 3. Put UUT S3 or S4 and resume = the Mute LED will turn to White. Customer Impact: Mute LED show wrong indicate after S3/S4/Resume. This bug is for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+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 1374389] Re: [i915_bdw] Backported bugfixes
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1374389 Title: [i915_bdw] Backported bugfixes Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Bug description: This set of backports fixes some issues in i915_bdw: drm/i915/bdw: Remove BDW preproduction W/As until C stepping. drm/i915: Add the WaCsStallBeforeStateCacheInvalidate:bdw workaround. drm/i915: Refactor Broadwell PIPE_CONTROL emission into a helper. drm/i915: Replace hardcoded cacheline size with macro drm/i915/bdw: Cleanup pre prod workarounds drm/i915/bdw: Apply workarounds in render ring init function drm/i915: call lpt_init_clock_gating on BDW too drm/i915/bdw: Disable idle DOP clock gating drm/i915/bdw: 3D_CHICKEN3 has write mask bits drm/i915: add null render states for gen6, gen7 and gen8 - Add new workarounds and remove those that cause issues on production HW - Also makes sure the WA's are applied on GPU reset, suspend resume et al - fixes various cases when the GPU can get hung drm/i915: respect the VBT minimum backlight brightness drm/i915: extract backlight minimum brightness from VBT drm/i915: shuffle panel code - fix a bug where changing the panel brightness to lowest value actually turns the panel off drm/i915/bdw: Add 42ms delay for IPS disable - fix the panel getting confused and corrupt when changing resolutions back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374389/+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 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349768 Title: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justificaton: [Impact] Users of ipvs may encounter dropped packets and message such as: [70325.516724] IPv6 header not found [Fix] Commit eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa. [Regression Potential] This changes NFPROTO_IPV4 to NFPROTO_IPV6 as we'd expect this nf_hook_ops struct to be in the code. -- I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs loadbalancer and dnsmasq server for pxebooting servers. After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading /linux TFTP transfer, with the transfer stalling roughly ~1000 blocks into the transfer: 10:30:51.011728 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.011924 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 10:30:51.012012 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.012183 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 stracing dnsmasq I noticed something very odd: sendto() on the socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start persistently returning EPERM in mid-transfer, even when dnsmasq continued to periodically retry: select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249834}) recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4 lseek(16, 1410816, SEEK_SET) = 1410816 read(16, \25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v..., 1408) = 1408 sendto(17, \0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = 1412 select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249839}) recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4 lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) This was with all iptables rules unloaded (so no OUTPUT -j DENY) and apparmor profiles torn down. I also noticed the following dmesgs appearing at roughly similar times to the tftp transfers getting stuck (although not coinciding exactly with the stall): [70325.516724] IPv6 header not found The error pointed to ipvs (which I am using on the same host as an IPv4 NAT loadbalancer): http://archive.linuxvirtualserver.org/html/lvs-devel/2012-08/msg00018.html http://comments.gmane.org/gmane.comp.linux.lvs.devel/3614 I then tore down the ipvs rules (service keepalived stop) and unloaded the modules (rmmod ip_vs_rr ip_vs), and the issue resolved itself - the stalled dnsmasq-tftp transfer
[Kernel-packages] [Bug 1354397] Re: Latest fixes from storvsc scsi drivers for Hyper-V/Azure
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354397 Title: Latest fixes from storvsc scsi drivers for Hyper-V/Azure Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: A number of significant fixes have landed upstream for Hyper-V/Azure clouds. The upstream devs for this recommend we apply the below list of patches: commit 26b9fd8b3452dcf0a8862e307ee23f442f63fb51 Author: K. Y. Srinivasan k...@microsoft.com Date: Fri Jul 18 17:11:27 2014 +0200 sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O timeout commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:26 2014 -0700 Drivers: scsi: storvsc: Change the limits to reflect the values on the host commit 52f9614dd8294e95d2c0929c2d4f64b077ae486f Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:27 2014 -0700 Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported by the Host commit 8caf92d80526f3d7cc96831ec18b384ebcaccdf0 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:28 2014 -0700 Drivers: scsi: storvsc: Filter commands based on the storage protocol version commit adb6f9e1a8c6af1037232b59edb11277471537ea Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:29 2014 -0700 Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol version commit 56b26e69c8283121febedd12b3cc193384af46b9 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:30 2014 -0700 Drivers: scsi: storvsc: Implement a eh_timed_out handler commit f885fb73f64154690c2158e813de56363389ffec Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:31 2014 -0700 drivers: scsi: storvsc: Set srb_flags in all cases commit 3533f8603d28b77c62d75ec899449a99bc6b77a1 Author: K. Y. Srinivasan k...@microsoft.com Date: Sat Jul 12 09:48:32 2014 -0700 drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6 Author: K. Y. Srinivasan k...@microsoft.com Date: Mon Jul 21 16:06:01 2014 -0700 Drivers: add blist flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354397/+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 1375310] Re: Removing linux-image-extra-X-generic deletes initramfs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375310 Title: Removing linux-image-extra-X-generic deletes initramfs Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: Situation: linux-image-X-generic and linux-image-extra-X-generic are both installed When you remove linux-image-extra-X-generic (e.g. switching from -generic to -virtual) /boot/initrd.img-X-generic is deleted in linux-image-extra-X-generic's postrm script. This results into broken boot. At least when / is on LVM etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375310/+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 1381851] Re: [Dell Latitude E5550] Brightness control does not work on this system
Hello, Yes it works with 3.16.0-031600-generic #201408031935 ** 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/1381851 Title: [Dell Latitude E5550] Brightness control does not work on this system Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201406-15271:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201406-15271:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate:772 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3170 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3540 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3372 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 354 mAh /proc/acpi/battery/BAT0/info:design capacity low: 107 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 35 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 35 mAh /proc/acpi/battery/BAT0/info:model number:DELL 9P4D246 /proc/acpi/battery/BAT0/info:serial number: 226 /proc/acpi/battery/BAT0/info:battery type:LiP /proc/acpi/battery/BAT0/info:OEM info:LGC-LGC3.4 /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/AC/state:state: off-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled pci::01:00.0 /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:GLAN S4*disabled pci::00:19.0 /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S0*disabled /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:PBTN S3*enabled ubuntu@201406-15271:~$ dmesg | grep 'ACPI: Video' [ 12.986933] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201406-15271:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 15 23:03:45 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro
[Kernel-packages] [Bug 1381906] 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/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+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 1381906] Re: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend
[ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed [ 8996.779587] ath3k: probe of 2-3:1.0 failed with error -110 That is a common problem with a range of these ath3k cards. I have one. Have a search of previous bug reports, but there seems a lack of any real solution for the majority of them. Some say it can be a conflict on loading od usb3 driver, and/or an alternative firmware loading method is needed but has not been adopted. Bit of a mess really. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381906 Title: [Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 After S3, the Bluetooth indicator will grey out (stays at the OFF state), but rfkill show it's not blocked. Even enable it by changing it to the ON state does not help, can't find any device with it, hciconfig return nothing. Error message could be found in the dmesg output: [ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906 [ 8996.779570] Bluetooth: Loading sysconfig file failed More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio /dev/snd/controlC1: ubuntu 1726 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Oct 16 00:41:31 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381906/+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 1378856] Re: [highbank] Oops on boot loading bridge module
** Description changed: + SRU Justification: + + Impact: oops upon loading of some modules that incur in the JUMP_LABEL + optimization. + + Fix: disable JUMP_LABEL until patches that make the DEBUG_SET_NORX text + section protection can cope with the rewriting. + + Testcase: boot an armhf board, create a bridge + + brctl addbr lxcbr0 + + and watch for an oops or not. + + === + + [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [ 16.867716] sp : e76a7d78 ip : 00019d80 fp : bf2d0888 [ 16.867718] r10: r9 : bf2d8000 r8 : [ 16.867721] r7 : 0001 r6 : c0f50458 r5 : bf2d0794 r4 : bf2d06f8 [ 16.867723] r3 : bf2c6a88 r2 : ea00 r1 : ea07 r0 : bf2c6a88 [ 16.867727] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 16.867730] Control: 30c5387d Table: 276f15c0 DAC: fffd [ 16.867732] Process modprobe (pid: 1126, stack limit = 0xe76a6250) [ 16.867734] Stack: (0xe76a7d78 to 0xe76a8000) [ 16.867737] 7d60: e7608040 c0f50458 [ 16.867741] 7d80: 0001 c0435054 c0f50458 0001 0007 c0e04920 [ 16.867744] 7da0: bf2d0600 c043517c bf2d0600 bf2d0620 0007 c095c62c c095c70c [ 16.867747] 7dc0: bf2d0a24 c0dff554 c0e04920 c0e04920 e7608b80 bf2d81a0 bf2d0a24 c092661c [ 16.867751] 7de0: c0dff554 bf2d8050 e76a6038 c0309740 0001 c04836e4 [ 16.867754] 7e00: e9ce6c40 e76b8080 8040003f 0001 c043d60c e9ce6c20 [ 16.867757] 7e20: 8040003f 80150014 c043f530 0001 [ 16.867760] 7e40: 0cab 8040003f e76b8080 f0c11000 0001 bd94282a e76a7f58 [ 16.867763] 7e60: bf2d0894 e76a6000 c0dff554 e76a7f58 bf2d0888 c03d55c4 [ 16.867767] 7e80: 8000 7fff c03d2374 ebad4188 b860d1c0 bf2d0894 040c bf2d1000 [ 16.867770] 7ea0: bf2d0894 b6fef398 c0dff554 e76a7f5c c049ef68 [ 16.867773] 7ec0: bf2cd024 0001 bf2cd02c 0002 [ 16.867776] 7ee0: 6e72656b 6c65 [ 16.867779] 7f00: [ 16.867783] 7f20: bd94282a 0120 b6fef398 017b c0320ec4 [ 16.867786] 7f40: e76a6000 b860d1c0 c03d5b90 00181088 f0c11000 0002391c [ 16.867789] 7f60: f0c33fe4 f0c27059 f0c2b378 00014000 00017190 bf2d0798 000a 0001 [ 16.867793] 7f80: 0039 003a 002e 0032 001a b6ff0608 b6ff0e18 [ 16.867796] 7fa0: b6ff0990 c0320d20 b6ff0608 b6ff0e18 b6fef398 b6ff0968 [ 16.867799] 7fc0: b6ff0608 b6ff0e18 b6ff0990 017b b8615288 b860d1c0 [ 16.867803] 7fe0: bef98a38 bef98a28 b6fe6177 b6f5b2b2 40010030 705f646e 696c6275 [ 16.867812] [c0a20494] (patch_text) from [c0434ffc] (__jump_label_update+0x64/0x6c) [ 16.867819] [c0434ffc] (__jump_label_update) from [c0435054] (jump_label_update+0x50/0x9c) [ 16.867826] [c0435054] (jump_label_update) from [c043517c] (static_key_slow_inc+0xdc/0xe0) [ 16.867835] [c043517c] (static_key_slow_inc) from [c095c62c] (nf_register_hook+0xc0/0xcc) [ 16.867842] [c095c62c] (nf_register_hook) from [c095c70c] (nf_register_hooks+0x38/0x78) [ 16.867861] [c095c70c] (nf_register_hooks) from [bf2d81a0] (br_netfilter_init+0x38/0xe98 [bridge]) [ 16.867895] [bf2d81a0] (br_netfilter_init [bridge]) from [bf2d8050] (br_init+0x50/0xd0 [bridge]) [ 16.867911] [bf2d8050] (br_init [bridge]) from [c0309740] (do_one_initcall+0xdc/0x20c) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378856 Title: [highbank] Oops on boot loading bridge module Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: oops upon loading of some modules that incur in the JUMP_LABEL optimization. Fix: disable JUMP_LABEL until patches that make the DEBUG_SET_NORX text section protection can cope with the rewriting. Testcase: boot an armhf board, create a bridge brctl addbr
[Kernel-packages] [Bug 1327228] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
I don't understand why this bug was opened as it's the exact duplicate as 1322068 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327228 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in “linux” package in Ubuntu: Expired Bug description: After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as usual. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dominique 2178 F pulseaudio Date: Fri Jun 6 15:55:10 2014 HibernationDevice: RESUME=UUID=5f05316b-0e09-4e60-bead-13b15361722b InstallationDate: Installed on 2013-11-28 (190 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcEnviron: LANGUAGE=fr_CH:fr TERM=xterm PATH=(custom, no user) LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=29055597-db44-462a-82cf-e2ca53ea3755 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.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-05-20 (16 days ago) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327228/+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 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
Yes, I think I can confirm this (not sure because I've been testing since yesterday but it is working for the moment), with utopic packages (kernel and firmware 1.136) on linux mint 17, I have been able to download big files all the night and this morning network still working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1354975 Title: iwlwifi Intel 7260 Wifi disconnects Status in Unity Linux: New Status in “linux-firmware” package in Ubuntu: Incomplete Bug description: I experience frequent disconnects and auth issues, never more than 30 minutes without a disconnect. Sometimes dozens of disconnects in a few minutes. This happens with the default 7260-8 firmware. Tried replacing the -8 with -9 ucode. Failed to load due to API version. This loaded the -7 driver which seems to be more stable. Tested against 2.4ghz APs (Apple, Netgear, Linksys). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2577 F pulseaudio /dev/snd/controlC1: steve 2577 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 10 17:49:06 2014 HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6 InstallationDate: Installed on 2013-12-28 (225 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+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 1349879] Re: powering off an usb3 device causes kernel to resume immediately after suspend
Tested again with v3.17.1-utopic: still the same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend Status in “linux” package in Ubuntu: Confirmed Bug description: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+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 830915] Re: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file
Just remove the files and directories belonging to the old version(s) in /var/lib/dkms/vboxhost and run sudo /etc/init.d/vboxdrv setup again to fix it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/830915 Title: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file Status in “dkms” package in Ubuntu: Confirmed Bug description: Настраивается пакет linux-image-3.0.0-9-generic (3.0.0-9.12) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic Error! Could not locate dkms.conf file. File: does not exist. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic update-initramfs: Generating /boot/initrd.img-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.0.0-9-generic Found initrd image: /boot/initrd.img-3.0.0-9-generic Found linux image: /boot/vmlinuz-3.0.0-8-generic Found initrd image: /boot/initrd.img-3.0.0-8-generic Found linux image: /boot/vmlinuz-2.6.38-10-generic Found initrd image: /boot/initrd.img-2.6.38-10-generic Found memtest86+ image: /boot/memtest86+.bin Found Ubuntu Natty (development branch) (11.04) on /dev/sdb5 done This, however, doesn't seem to be fatal. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: dkms 2.2.0.2-1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 22 12:43:31 2011 InstallationMedia: Xubuntu 10.10 Maverick Meerkat - Release amd64 (20101008.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: dkms UpgradeStatus: Upgraded to oneiric on 2011-08-10 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/830915/+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 1381927] [NEW] linux: 3.16.0-22.30 -proposed tracker
Public bug reported: This bug is for tracking the 3.16.0-22.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 16. October 2014 08:06 UTC kernel-phase-changed:Thursday, 16. October 2014 08:06 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug utopic ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Tags added: utopic ** Also affects: kernel-development-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New = In Progress ** Changed in: kernel-development-workflow Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Status: New = Invalid ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) = Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381927 Title: linux: 3.16.0-22.30 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Utopic: Invalid Bug description: This bug is for tracking the 3.16.0-22.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 16. October 2014 08:06 UTC kernel-phase-changed:Thursday, 16. October 2014 08:06 UTC kernel-phase:Prepare To manage notifications about this bug go to:
[Kernel-packages] [Bug 1375266] Re: amd-iommu: kernel BUG lockup after shutting down KVM guest using PCI passthrough/PCIe bridge
Wow, amazing what kind of bureaucracy getting a small fix in involves. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375266 Title: amd-iommu: kernel BUG lockup after shutting down KVM guest using PCI passthrough/PCIe bridge Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: SRU Justification: [Impact] When using a KVM VM and adding certain combinations of PCI/PCI-e devices an oops and freeze can occur when shutting down a VM. [Fix] Commit 9b29d3c6510407d91786c1cf9183ff4debb3473a which is upstream in 3.17-rc2 and in stable/3.16.y. This fix changes how cleanup_domain detaches device, instead of using the list_for_each_entyr_safe macro, it just iterates through the devices and removes the first element. [Test Case] Create KVM VM with a specific configuration of PCI/PCIe devices, and shutdown the VM. See https://bugzilla.kernel.org/show_bug.cgi?id=81841 for details. -- This kernel lockup bug was reported to and fixed upstream: https://bugzilla.kernel.org/show_bug.cgi?id=81841 Please backport the stable kernel patch to Ubuntu kernels (at least trusty, which I use in this setup): https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9b29d3c6510407d91786c1cf9183ff4debb3473a ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-35-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Mon Sep 29 16:19:50 2014 HibernationDevice: RESUME=UUID=54378db4-8de4-45f0-b7cb-2d8e1097139d InstallationDate: Installed on 2014-09-04 (25 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=a8f2d0ae-f43e-47de-9ef9-99fed8c9c78e ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: FM2A88X Extreme6+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd01/24/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme6+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1375266/+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 1275879] Re: Kernel panic
Diego: Thanks for testing. I had a look at the logs, but all I was able to find out was that I had an off-by-one error in some of the checks I added that causes them to trigger on full pages in addition to cases which actually cause the problem. As a result I think most if not all of the warnings in your logs are false positives. Sorry for the mistake. I've fixed that and uploaded a new build, so anyone who has been testing the last one should switch to this one. http://people.canonical.com/~sforshee/lp1275879/linux-3.13.0-38.65+lp1278579v201410160939/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1275879 Title: Kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: I run ubuntu servers 13.04, 13.10, and 14.04 on the AWS cloud. Whenever I install haproxy and nginx on the same server, after hitting it for a while, a kernel panic is caused. However, the kernel panic does not show up in ubuntu 12.04. The kernel panic is pasted at the end of the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+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 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
** Changed in: linux-firmware (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1354975 Title: iwlwifi Intel 7260 Wifi disconnects Status in Unity Linux: New Status in “linux-firmware” package in Ubuntu: Fix Released Bug description: I experience frequent disconnects and auth issues, never more than 30 minutes without a disconnect. Sometimes dozens of disconnects in a few minutes. This happens with the default 7260-8 firmware. Tried replacing the -8 with -9 ucode. Failed to load due to API version. This loaded the -7 driver which seems to be more stable. Tested against 2.4ghz APs (Apple, Netgear, Linksys). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2577 F pulseaudio /dev/snd/controlC1: steve 2577 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 10 17:49:06 2014 HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6 InstallationDate: Installed on 2013-12-28 (225 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+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 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system
I'm not familiar with the hotkeys, just a bit with the LEDs that could be physically located on them. Could you reassign to a hotkey expert perhaps? ** Changed in: linux (Ubuntu) Assignee: David Henningsson (diwic) = Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by xev or sudo showkey -s But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381856/+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 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system
** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) = Hui Wang (hui.wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next Project: Triaged Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by xev or sudo showkey -s But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381856/+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 1372482] Re: mount.cifs does not work with the 3.13.0.36-generic kernel
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372482 Title: mount.cifs does not work with the 3.13.0.36-generic kernel Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Invalid Bug description: mount.cifs //server_ip/share_name mount_point -o user=user Password... mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) From syslog: Sep 22 15:41:04 ds1205 kernel: [ 11.778362] [ cut here ] Sep 22 15:41:04 ds1205 kernel: [ 11.778370] WARNING: CPU: 3 PID: 2253 at /build/buildd/linux-3.13.0/fs/cifs/transport.c:313 smb_send_rqst+0x215/0x270 [cifs]() Sep 22 15:41:04 ds1205 kernel: [ 11.778371] Send length mismatch(send_length=72 smb_buf_length=2164260932) Sep 22 15:41:04 ds1205 kernel: [ 11.778372] Modules linked in: cuse rfcomm bnep bluetooth binfmt_misc snd_hda_codec_realtek nls_utf8 cifs fscache intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_hda_codec kvm_intel kvm snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc ghash_clmulni_intel i915 snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw snd_rawmidi gf128mul snd_seq glue_helper ablk_helper snd_seq_device drm_kms_helper cryptd snd_timer drm keucr(C) parport_pc i2c_algo_bit hid_generic snd mei_me ppdev mei usb_storage lp soundcore serio_raw lpc_ich parport wmi mac_hid video usbhid hid psmouse ahci libahci r8169 mii Sep 22 15:41:04 ds1205 kernel: [ 11.778395] CPU: 3 PID: 2253 Comm: mount.cifs Tainted: GWC3.13.0-36-generic #63-Ubuntu Sep 22 15:41:04 ds1205 kernel: [ 11.778396] Hardware name: Hewlett-Packard HP Pro 3500 Series/2ABF, BIOS 8.11 10/24/2012 Sep 22 15:41:04 ds1205 kernel: [ 11.778397] 0009 8800ccaf7bb0 8171e569 8800ccaf7bf8 Sep 22 15:41:04 ds1205 kernel: [ 11.778399] 8800ccaf7be8 8106775d 8800ccaf7d00 88020fecb800 Sep 22 15:41:04 ds1205 kernel: [ 11.778401] 8800ccaf7cc8 0001 8800ccaf7c48 Sep 22 15:41:04 ds1205 kernel: [ 11.778403] Call Trace: Sep 22 15:41:04 ds1205 kernel: [ 11.778406] [8171e569] dump_stack+0x45/0x56 Sep 22 15:41:04 ds1205 kernel: [ 11.778408] [8106775d] warn_slowpath_common+0x7d/0xa0 Sep 22 15:41:04 ds1205 kernel: [ 11.778409] [810677cc] warn_slowpath_fmt+0x4c/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778415] [a04904c5] smb_send_rqst+0x215/0x270 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778417] [81690218] ? __inet_stream_connect+0x208/0x320 Sep 22 15:41:04 ds1205 kernel: [ 11.778422] [a049055d] smb_sendv+0x3d/0x40 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778426] [a0490588] smb_send+0x28/0x30 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778430] [a047a15d] generic_ip_connect+0x30d/0x3e0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778432] [811a1d65] ? __kmalloc+0x55/0x230 Sep 22 15:41:04 ds1205 kernel: [ 11.778437] [a047e69c] cifs_mount+0x85c/0xaf0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778440] [a046d040] cifs_do_mount+0xa0/0x4d0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778442] [811c10a9] mount_fs+0x39/0x1b0 Sep 22 15:41:04 ds1205 kernel: [ 11.778444] [811dc447] vfs_kern_mount+0x67/0x110 Sep 22 15:41:04 ds1205 kernel: [ 11.778446] [811deca4] do_mount+0x244/0xb20 Sep 22 15:41:04 ds1205 kernel: [ 11.778448] [811530be] ? __get_free_pages+0xe/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778450] [811de8e6] ? copy_mount_options+0x36/0x170 Sep 22 15:41:04 ds1205 kernel: [ 11.778451] [811df873] SyS_mount+0x83/0xc0 Sep 22 15:41:04 ds1205 kernel: [ 11.778453] [8172efad] system_call_fastpath+0x1a/0x1f Sep 22 15:41:04 ds1205 kernel: [ 11.778454] ---[ end trace 826c79e22eb80bab ]--- Sep 22 15:41:04 ds1205 kernel: [ 11.779826] CIFS VFS: Error connecting to socket. Aborting operation. Sep 22 15:41:04 ds1205 kernel: [ 11.779890] CIFS VFS: cifs_mount failed w/return code = -5 I cannot mount share from Samba 3.6.6, but I can mount a share from a Windows 2003 server. But it works with 3.13.0.35-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pt 2204 F pulseaudio /dev/snd/pcmC0D0p: pt 2204
[Kernel-packages] [Bug 1374389] Re: [i915_bdw] Backported bugfixes
they've been tested extensively during the past few weeks, and have not caused new issues but fixed bugs; verification done ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1374389 Title: [i915_bdw] Backported bugfixes Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Bug description: This set of backports fixes some issues in i915_bdw: drm/i915/bdw: Remove BDW preproduction W/As until C stepping. drm/i915: Add the WaCsStallBeforeStateCacheInvalidate:bdw workaround. drm/i915: Refactor Broadwell PIPE_CONTROL emission into a helper. drm/i915: Replace hardcoded cacheline size with macro drm/i915/bdw: Cleanup pre prod workarounds drm/i915/bdw: Apply workarounds in render ring init function drm/i915: call lpt_init_clock_gating on BDW too drm/i915/bdw: Disable idle DOP clock gating drm/i915/bdw: 3D_CHICKEN3 has write mask bits drm/i915: add null render states for gen6, gen7 and gen8 - Add new workarounds and remove those that cause issues on production HW - Also makes sure the WA's are applied on GPU reset, suspend resume et al - fixes various cases when the GPU can get hung drm/i915: respect the VBT minimum backlight brightness drm/i915: extract backlight minimum brightness from VBT drm/i915: shuffle panel code - fix a bug where changing the panel brightness to lowest value actually turns the panel off drm/i915/bdw: Add 42ms delay for IPS disable - fix the panel getting confused and corrupt when changing resolutions back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374389/+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 1381968] [NEW] Fstrim destroys data on loopback device
You have been subscribed to a public bug: I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS. The setup contains a loopback device (/dev/loop3) mounted into a software raid 1 (/dev/md2). After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've discovered that it wiped all data on the loopback device from the raid. fstrim-all skips check because the loopback device is part of device mapper raid. if [ ${REALDEV#/dev/dm-} != $REALDEV ]; then echo device $DEV is on devmapper, skipping TRIM feature check Issue can be reproduced on raid setup and plain loopback mount setup! Here is step-by-step how to reproduce the issue: 1.) create sparse image file dd of=/sparse-file bs=1k seek=1024000 2.) losetup loopback device losetup /dev/loop3 /sparse-file 3.) create raid1 mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3 4.) create fs mkfs.ext4 /dev/md2 4.1.) check sparse-file size ls -lash /sparse-file 5.) mount and copy data mount /dev/md2 /mnt copy some random files on /mnt 5.1.) check sparse-file size again ls -lash /sparse-file - size indicates it contains the copied data 6.) destroy loopback via fstrim fstrim -v /mnt 7.) data is wiped umount /mnt ls -lash /sparse-file - size indicates that all data is wiped out! fsck -v -f /dev/md2 - will report infinite errors on filesystem I could not find any similiar bugreport. Best Regards Daniel ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: dataloss fstrim kernel-bug loopback -- Fstrim destroys data on loopback device https://bugs.launchpad.net/bugs/1381968 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381973] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1381973 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381973] [NEW] keyutils ftbfs on the buildds with the 12.04 LTS kernel
Public bug reported: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. ** Affects: keyutils (Ubuntu) Importance: High Status: Confirmed ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Tags: ftbfs precise ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381973] Re: keyutils ftbfs on the buildds with the 12.04 LTS kernel
** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381968] Re: Fstrim destroys data on loopback device
I could not create missing logs because of: It appears you are currently running a mainline kernel I've upgraded to mainline kernel 3.17.1-031701-generic #201410150735, thought it maybe contains a bugfix for this. As the server runs in production-environment a restart is not that easy. I've detected this issue running the default ubuntu kernel. Do you still need logs? ** 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/1381968 Title: Fstrim destroys data on loopback device Status in “linux” package in Ubuntu: Confirmed Bug description: I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS. The setup contains a loopback device (/dev/loop3) mounted into a software raid 1 (/dev/md2). After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've discovered that it wiped all data on the loopback device from the raid. fstrim-all skips check because the loopback device is part of device mapper raid. if [ ${REALDEV#/dev/dm-} != $REALDEV ]; then echo device $DEV is on devmapper, skipping TRIM feature check Issue can be reproduced on raid setup and plain loopback mount setup! Here is step-by-step how to reproduce the issue: 1.) create sparse image file dd of=/sparse-file bs=1k seek=1024000 2.) losetup loopback device losetup /dev/loop3 /sparse-file 3.) create raid1 mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3 4.) create fs mkfs.ext4 /dev/md2 4.1.) check sparse-file size ls -lash /sparse-file 5.) mount and copy data mount /dev/md2 /mnt copy some random files on /mnt 5.1.) check sparse-file size again ls -lash /sparse-file - size indicates it contains the copied data 6.) destroy loopback via fstrim fstrim -v /mnt 7.) data is wiped umount /mnt ls -lash /sparse-file - size indicates that all data is wiped out! fsck -v -f /dev/md2 - will report infinite errors on filesystem I could not find any similiar bugreport. Best Regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+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 1381927] Re: linux: 3.16.0-23.30 -proposed tracker
** Summary changed: - linux: 3.16.0-22.30 -proposed tracker + linux: 3.16.0-23.30 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381927 Title: linux: 3.16.0-23.30 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Utopic: Invalid Bug description: This bug is for tracking the 3.16.0-22.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 16. October 2014 08:06 UTC kernel-phase-changed:Thursday, 16. October 2014 08:06 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1381927/+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 1381968] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1381968 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/1381968 Title: Fstrim destroys data on loopback device Status in “linux” package in Ubuntu: Confirmed Bug description: I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS. The setup contains a loopback device (/dev/loop3) mounted into a software raid 1 (/dev/md2). After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've discovered that it wiped all data on the loopback device from the raid. fstrim-all skips check because the loopback device is part of device mapper raid. if [ ${REALDEV#/dev/dm-} != $REALDEV ]; then echo device $DEV is on devmapper, skipping TRIM feature check Issue can be reproduced on raid setup and plain loopback mount setup! Here is step-by-step how to reproduce the issue: 1.) create sparse image file dd of=/sparse-file bs=1k seek=1024000 2.) losetup loopback device losetup /dev/loop3 /sparse-file 3.) create raid1 mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3 4.) create fs mkfs.ext4 /dev/md2 4.1.) check sparse-file size ls -lash /sparse-file 5.) mount and copy data mount /dev/md2 /mnt copy some random files on /mnt 5.1.) check sparse-file size again ls -lash /sparse-file - size indicates it contains the copied data 6.) destroy loopback via fstrim fstrim -v /mnt 7.) data is wiped umount /mnt ls -lash /sparse-file - size indicates that all data is wiped out! fsck -v -f /dev/md2 - will report infinite errors on filesystem I could not find any similiar bugreport. Best Regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+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 1381968] Re: Fstrim destroys data on loopback device
sorry, somehow assigned to wrong package ** Package changed: openjdk-6 (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381968 Title: Fstrim destroys data on loopback device Status in “linux” package in Ubuntu: Confirmed Bug description: I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS. The setup contains a loopback device (/dev/loop3) mounted into a software raid 1 (/dev/md2). After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've discovered that it wiped all data on the loopback device from the raid. fstrim-all skips check because the loopback device is part of device mapper raid. if [ ${REALDEV#/dev/dm-} != $REALDEV ]; then echo device $DEV is on devmapper, skipping TRIM feature check Issue can be reproduced on raid setup and plain loopback mount setup! Here is step-by-step how to reproduce the issue: 1.) create sparse image file dd of=/sparse-file bs=1k seek=1024000 2.) losetup loopback device losetup /dev/loop3 /sparse-file 3.) create raid1 mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3 4.) create fs mkfs.ext4 /dev/md2 4.1.) check sparse-file size ls -lash /sparse-file 5.) mount and copy data mount /dev/md2 /mnt copy some random files on /mnt 5.1.) check sparse-file size again ls -lash /sparse-file - size indicates it contains the copied data 6.) destroy loopback via fstrim fstrim -v /mnt 7.) data is wiped umount /mnt ls -lash /sparse-file - size indicates that all data is wiped out! fsck -v -f /dev/md2 - will report infinite errors on filesystem I could not find any similiar bugreport. Best Regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+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 1378663] Re: AMD Radeon R2[1002:9853] Unable to reach full screen on external monitor with fglrx
Hello Anthony, Yes, the default value is 8%, it reaches full screen after tuning this value down to 0% Thanks ** 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/1378663 Title: AMD Radeon R2[1002:9853] Unable to reach full screen on external monitor with fglrx Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201403-14840 Dell Inspiron 3441 The external monitor resolution cannot be set to higher than 1680x1050, or it won't be displayed on full-screen. It will have a gap between the edge of the desktop and the monitor edge. Steps: 1. Install 14.04.1 + fglrx 2. Connect to an external monitor with HDMI cable Expected result: * The desktop displayed on the external monitor should be full-screen displayed Actual result: * With resolution higer than 1680x1050, it will have a gap between the edge of the desktop and the monitor edge. ubuntu@201403-14840:~$ xrandr -q Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 16384 x 16384 LVDS connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.0 + 48.0 1280x768 60.0*48.0 1280x720 60.0 48.0 1024x768 60.0 48.0 800x60060.0 48.0 640x48060.0 48.0 DFP1 connected 1920x1080+1280+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.0*+ 50.0 59.9 60.1 50.0 60.0 1776x1000 50.0 59.9 50.0 60.0 1680x1050 50.0 60.0 1400x1050 50.0 60.0 1600x900 50.0 60.0 1280x1024 50.0 75.0 60.0 1440x900 50.0 59.9 1280x960 50.0 60.0 1280x768 50.0 60.0 1280x720 60.0 50.0 59.9 1024x768 50.0 75.0 70.1 60.0 1152x648 50.0 59.9 800x60050.0 72.2 75.0 60.3 56.2 720x57659.9 50.0 720x48050.0 60.0 59.9 640x48050.0 75.0 72.8 66.6 60.0 59.9 CRT1 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1911 F pulseaudio /dev/snd/controlC0: ubuntu 1911 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 02:54:32 2014 HibernationDevice: RESUME=UUID=101b2112-3f0a-4b08-aea9-668051efacbf InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3441 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e1f357a4-fcde-45fc-a0b5-b785f2de7298 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: Inspiron 3441 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd04/28/2014:svnDellInc.:pnInspiron3441:pvrNotSpecified:rvnDellInc.:rnInspiron3441:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3441 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1378663/+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 1372482] Re: mount.cifs does not work with the 3.13.0.36-generic kernel
Confirming here, too: Cifs mounting with 3.13.0-38-generic/trusty- proposed works again Thanks for fixing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1372482 Title: mount.cifs does not work with the 3.13.0.36-generic kernel Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Invalid Bug description: mount.cifs //server_ip/share_name mount_point -o user=user Password... mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) From syslog: Sep 22 15:41:04 ds1205 kernel: [ 11.778362] [ cut here ] Sep 22 15:41:04 ds1205 kernel: [ 11.778370] WARNING: CPU: 3 PID: 2253 at /build/buildd/linux-3.13.0/fs/cifs/transport.c:313 smb_send_rqst+0x215/0x270 [cifs]() Sep 22 15:41:04 ds1205 kernel: [ 11.778371] Send length mismatch(send_length=72 smb_buf_length=2164260932) Sep 22 15:41:04 ds1205 kernel: [ 11.778372] Modules linked in: cuse rfcomm bnep bluetooth binfmt_misc snd_hda_codec_realtek nls_utf8 cifs fscache intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_hda_codec kvm_intel kvm snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc ghash_clmulni_intel i915 snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw snd_rawmidi gf128mul snd_seq glue_helper ablk_helper snd_seq_device drm_kms_helper cryptd snd_timer drm keucr(C) parport_pc i2c_algo_bit hid_generic snd mei_me ppdev mei usb_storage lp soundcore serio_raw lpc_ich parport wmi mac_hid video usbhid hid psmouse ahci libahci r8169 mii Sep 22 15:41:04 ds1205 kernel: [ 11.778395] CPU: 3 PID: 2253 Comm: mount.cifs Tainted: GWC3.13.0-36-generic #63-Ubuntu Sep 22 15:41:04 ds1205 kernel: [ 11.778396] Hardware name: Hewlett-Packard HP Pro 3500 Series/2ABF, BIOS 8.11 10/24/2012 Sep 22 15:41:04 ds1205 kernel: [ 11.778397] 0009 8800ccaf7bb0 8171e569 8800ccaf7bf8 Sep 22 15:41:04 ds1205 kernel: [ 11.778399] 8800ccaf7be8 8106775d 8800ccaf7d00 88020fecb800 Sep 22 15:41:04 ds1205 kernel: [ 11.778401] 8800ccaf7cc8 0001 8800ccaf7c48 Sep 22 15:41:04 ds1205 kernel: [ 11.778403] Call Trace: Sep 22 15:41:04 ds1205 kernel: [ 11.778406] [8171e569] dump_stack+0x45/0x56 Sep 22 15:41:04 ds1205 kernel: [ 11.778408] [8106775d] warn_slowpath_common+0x7d/0xa0 Sep 22 15:41:04 ds1205 kernel: [ 11.778409] [810677cc] warn_slowpath_fmt+0x4c/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778415] [a04904c5] smb_send_rqst+0x215/0x270 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778417] [81690218] ? __inet_stream_connect+0x208/0x320 Sep 22 15:41:04 ds1205 kernel: [ 11.778422] [a049055d] smb_sendv+0x3d/0x40 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778426] [a0490588] smb_send+0x28/0x30 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778430] [a047a15d] generic_ip_connect+0x30d/0x3e0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778432] [811a1d65] ? __kmalloc+0x55/0x230 Sep 22 15:41:04 ds1205 kernel: [ 11.778437] [a047e69c] cifs_mount+0x85c/0xaf0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778440] [a046d040] cifs_do_mount+0xa0/0x4d0 [cifs] Sep 22 15:41:04 ds1205 kernel: [ 11.778442] [811c10a9] mount_fs+0x39/0x1b0 Sep 22 15:41:04 ds1205 kernel: [ 11.778444] [811dc447] vfs_kern_mount+0x67/0x110 Sep 22 15:41:04 ds1205 kernel: [ 11.778446] [811deca4] do_mount+0x244/0xb20 Sep 22 15:41:04 ds1205 kernel: [ 11.778448] [811530be] ? __get_free_pages+0xe/0x50 Sep 22 15:41:04 ds1205 kernel: [ 11.778450] [811de8e6] ? copy_mount_options+0x36/0x170 Sep 22 15:41:04 ds1205 kernel: [ 11.778451] [811df873] SyS_mount+0x83/0xc0 Sep 22 15:41:04 ds1205 kernel: [ 11.778453] [8172efad] system_call_fastpath+0x1a/0x1f Sep 22 15:41:04 ds1205 kernel: [ 11.778454] ---[ end trace 826c79e22eb80bab ]--- Sep 22 15:41:04 ds1205 kernel: [ 11.779826] CIFS VFS: Error connecting to socket. Aborting operation. Sep 22 15:41:04 ds1205 kernel: [ 11.779890] CIFS VFS: cifs_mount failed w/return code = -5 I cannot mount share from Samba 3.6.6, but I can mount a share from a Windows 2003 server. But it works with 3.13.0.35-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pt 2204 F pulseaudio
[Kernel-packages] [Bug 1357723] Re: No sound after rebooting from Windows (ALC1150)
I have this bug , very annoying . the only way to get sound to work is unplug power cord from PC for ~20 seconds and restart Ubuntu 14.04. After entering Windows sound in Ubuntu distorted again. (motherboard GA-Z97X-SLI , dual boot Windows 8.1 and Ubuntu 14.04 gnome) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1357723 Title: No sound after rebooting from Windows (ALC1150) Status in “linux” package in Ubuntu: Confirmed Bug description: I get no sound from line-out (green) plug after rebooting from Windos. I found out, that sound channels are just swapped, so the line-out is now assigned to the black jack. If i stop the machine, and do a cold-boot right into GNU/Linux, then it is green again. I couldn't reorder it with hda-jack-retask either. I found at least one person affected by this problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421/comments/35 MOBO: Gigabyte GA-H97-D3H codec: ALC1150 (HDA-intel) sys: Ubuntu-14.04 / Linux-mint 17 default installs kernel: Ubuntu 3.13.0-34.60-generic (64 bit) dmesg: (no difference on cold boot, and reboot from windows) [3.813038] snd_hda_intel :00:1b.0: irq 48 for MSI/MSI-X [3.828489] hda_codec: ALC1150: SKU not ready 0x [3.828906] autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [3.828907]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.828907]hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [3.828908]mono: mono_out=0x0 [3.828908]dig-out=0x11/0x0 [3.828909]inputs: [3.828910] Front Mic=0x19 [3.828911] Rear Mic=0x18 [3.828911] Line=0x1a [3.828912] realtek: No valid SSID, checking pincfg 0x for NID 0x1d [3.828912] realtek: Enable default setup for auto mode as fallback [3.842157] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input16 [3.842238] input: HDA Intel PCH Line Out Side as /devices/pci:00/:00:1b.0/sound/card0/input15 [3.842268] input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card0/input14 [3.842415] input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card0/input13 [3.843987] input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card0/input12 [3.845304] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input11 [3.846477] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [3.846592] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card0/input9 --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laca 1827 F pulseaudio /dev/snd/controlC0: laca 1827 F pulseaudio /dev/snd/pcmC0D0p: laca 1827 F...m pulseaudio DistroRelease: Ubuntu 14.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H97-D3H NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=23864803-a370-4772-b8cb-77f2f9bf3e2d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.4 RfKill: Tags: qiana Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-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: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-D3H 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/1357723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
Ok I think I know what's happening : When I'm connected to a 2.4 Ghz Network, connection is stable, disconnections comes only on 5 Ghz Network. Could someone test downloading big files on these two kind of networks to confirm ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1354975 Title: iwlwifi Intel 7260 Wifi disconnects Status in Unity Linux: New Status in “linux-firmware” package in Ubuntu: Fix Released Bug description: I experience frequent disconnects and auth issues, never more than 30 minutes without a disconnect. Sometimes dozens of disconnects in a few minutes. This happens with the default 7260-8 firmware. Tried replacing the -8 with -9 ucode. Failed to load due to API version. This loaded the -7 driver which seems to be more stable. Tested against 2.4ghz APs (Apple, Netgear, Linksys). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2577 F pulseaudio /dev/snd/controlC1: steve 2577 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 10 17:49:06 2014 HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6 InstallationDate: Installed on 2013-12-28 (225 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+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 1344405] Re: Kernel missing /proc/keys
** Also affects: linux (Ubuntu Precise) 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/1344405 Title: Kernel missing /proc/keys Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: New Status in “linux” source package in Trusty: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy linux-generic linux-generic: Installed: 3.13.0.24.28 Candidate: 3.13.0.32.38 Version table: 3.13.0.32.38 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages *** 3.13.0.24.28 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status - When attempting to clear NFS uid/gid cache I ran nfsidmap -c expected Result no response, nfsidmap does not return anything if it completes properly example: [root@quebec ~]# nfsidmap -c [root@quebec ~]# What did happen root@u1404vm:~# nfsidmap -c nfsidmap: fopen(/proc/keys) failed: No such file or directory I checked /proc and the /proc/key-users file and the /proc/sys/kernel/keys directory were there. I Looked up Kernel Key Management and saw that /proc/keys was needed to hold the key pairs used by the kernel. From Google'ng the following kernel option needs to be enabled CONFIG_KEYS_DEBUG_PROC_KEY or /proc/keys does not get created. I checked /boot/config-3.13.0-24-generic and that option is not enabled. I checked this on both Centos 6.5/7 and Mageia and they are enabled and /proc/keys exist, nfsidmap -c works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1344405/+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 1381973] Re: keyutils ftbfs on the buildds with the 12.04 LTS kernel
This bug was fixed in the package keyutils - 1.5.9-5ubuntu1 --- keyutils (1.5.9-5ubuntu1) utopic; urgency=medium * Disable the tests, hanging on the distro buildd kernels (12.04 LTS). Verified that the tests succeed with the 14.04 LTS kernels. Addresses: LP: #1381973. -- Matthias Klose d...@ubuntu.com Thu, 16 Oct 2014 11:45:19 +0200 ** Changed in: keyutils (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381973] Re: keyutils ftbfs on the buildds with the 12.04 LTS kernel
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381973] Re: keyutils ftbfs on the buildds with the 12.04 LTS kernel
the keyutils tests should be reenabled after the updated kernel is in place ** Changed in: keyutils (Ubuntu) Status: Fix Released = 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/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1381999] [NEW] FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support
Public bug reported: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support, plus fixing the ftbfs on arm64 as seen in the test rebuild. upstream changes: http://people.redhat.com/~anderson/crash.changelog.html ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Tags added: ftbfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1381999 Title: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support Status in “crash” package in Ubuntu: New Bug description: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support, plus fixing the ftbfs on arm64 as seen in the test rebuild. upstream changes: http://people.redhat.com/~anderson/crash.changelog.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1381999/+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 1382005] [NEW] wifi dropping since kernel update on XPS15 using Intel AC7260
Public bug reported: I've noticed since a recent kernel update that my XPS 15 running Ubuntu 14.04 keeps dropping my 5ghz wifi connection and subsequently that connection s not available from the drop-down list in the network manager applet, only the 2.4ghz connections are. The wifi card is an Intel AC 7260 and I see there have been other bug reports about problems with the latest driver (https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569) Possibly a duplicate but wanted to register this independently first, in case not. Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: macdonaldj 2764 F pulseaudio /dev/snd/controlC0: macdonaldj 2764 F pulseaudio /dev/snd/controlC1: macdonaldj 2764 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 12:22:36 2014 HibernationDevice: RESUME=UUID=cc4b90f7-dd70-4bed-9535-466f4d3232dd InstallationDate: Installed on 2014-02-01 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-37-generic ro root=UUID=b777b47d-285a-4b52-a670-5c2d81c81dcc initrd=boot\initrd.img-3.13.0-37-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-21 (177 days ago) dmi.bios.date: 07/16/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/16/2014:svnDellInc.:pnXPS159530:pvrA06:rvnDellInc.:rnXPS159530:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382005 Title: wifi dropping since kernel update on XPS15 using Intel AC7260 Status in “linux” package in Ubuntu: New Bug description: I've noticed since a recent kernel update that my XPS 15 running Ubuntu 14.04 keeps dropping my 5ghz wifi connection and subsequently that connection s not available from the drop-down list in the network manager applet, only the 2.4ghz connections are. The wifi card is an Intel AC 7260 and I see there have been other bug reports about problems with the latest driver (https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1293569) Possibly a duplicate but wanted to register this independently first, in case not. Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: macdonaldj 2764 F pulseaudio /dev/snd/controlC0: macdonaldj 2764 F pulseaudio /dev/snd/controlC1: macdonaldj 2764 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 12:22:36 2014 HibernationDevice: RESUME=UUID=cc4b90f7-dd70-4bed-9535-466f4d3232dd InstallationDate: Installed on 2014-02-01 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-37-generic ro root=UUID=b777b47d-285a-4b52-a670-5c2d81c81dcc initrd=boot\initrd.img-3.13.0-37-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-21 (177 days ago) dmi.bios.date: 07/16/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/16/2014:svnDellInc.:pnXPS159530:pvrA06:rvnDellInc.:rnXPS159530:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A06
[Kernel-packages] [Bug 494292] Re: 'Disable Trackpad while typing...' option ignored on Macbook Pro 5, 2
*** This bug is a duplicate of bug 240738 *** https://bugs.launchpad.net/bugs/240738 On my macbook pro 8,2 this fixed it: xinput set-prop 10 Synaptics Palm Detection 1 and just to be on the safe side I also turn off the tap: xinput set-prop 10 Synaptics Tap Action 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/494292 Title: 'Disable Trackpad while typing...' option ignored on Macbook Pro 5,2 Status in “linux” package in Ubuntu: Confirmed Bug description: This bug originally exhibited itself as: Macbook Pro 5,2 trackpad spurious input, jumps to horizontal screen edges While typing the mouse occasionally jumps horizontally to the edge of the screen. It is not consistent which edge it jumps to. I notice this due to xmouse. I believe this is due to the touchpad being overly sensitive. By tapping the very edges of the trackpad (similar to how my palms might touch the trackpad while typing) I am able to sporadically reproduce this behavior. As such, I believe that this can best be fixed by the trackpad driver either watching for this kind of behavior while typing, or the 'Disable touchpad while typing' option (which I have enabled) having an increased timeout. Actually, now that I test this, I'm able to use the touchpad while holding down keys on the keyboard. This bug should almost certainly be applied against the maintainer of that package, as that option is not respected on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/494292/+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 1381973] Re: keyutils ftbfs on the buildds with the 12.04 LTS kernel
** Branch linked: lp:ubuntu/keyutils -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381973 Title: keyutils ftbfs on the buildds with the 12.04 LTS kernel Status in “keyutils” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: keyutils ftbfs on the buildds with the 12.04 LTS kernel. works ok with the 14.04 LTS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1381973/+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 1382005] 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/1382005 Title: wifi dropping since kernel update on XPS15 using Intel AC7260 Status in “linux” package in Ubuntu: Confirmed Bug description: I've noticed since a recent kernel update that my XPS 15 running Ubuntu 14.04 keeps dropping my 5ghz wifi connection and subsequently that connection s not available from the drop-down list in the network manager applet, only the 2.4ghz connections are. The wifi card is an Intel AC 7260 and I see there have been other bug reports about problems with the latest driver (https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1293569) Possibly a duplicate but wanted to register this independently first, in case not. Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: macdonaldj 2764 F pulseaudio /dev/snd/controlC0: macdonaldj 2764 F pulseaudio /dev/snd/controlC1: macdonaldj 2764 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 16 12:22:36 2014 HibernationDevice: RESUME=UUID=cc4b90f7-dd70-4bed-9535-466f4d3232dd InstallationDate: Installed on 2014-02-01 (256 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.13.0-37-generic ro root=UUID=b777b47d-285a-4b52-a670-5c2d81c81dcc initrd=boot\initrd.img-3.13.0-37-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-21 (177 days ago) dmi.bios.date: 07/16/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/16/2014:svnDellInc.:pnXPS159530:pvrA06:rvnDellInc.:rnXPS159530:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382005/+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 1247712] Re: Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via jockey-gtk
** Changed in: linux-lts-trusty (Ubuntu) Importance: Undecided = Critical -- 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/1247712 Title: Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via jockey-gtk Status in Jockey driver manager: Invalid Status in “bcmwl” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Confirmed Status in “linux-lts-trusty” package in Ubuntu: New Status in “bcmwl” source package in Precise: Confirmed Status in “jockey” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Confirmed Status in “linux-lts-trusty” source package in Precise: New Status in “bcmwl” package in Baltix: Confirmed Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux = 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at Downloading and installing driver The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[a045d020] [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 88001b405d78 R08: R09: Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 3684 R11: 0293 R12: 88001b405da0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105690] R13: a08643e0 R14: 880031788098 R15: 8800317880f8 Nov 3 21:34:14 201012-6925
[Kernel-packages] [Bug 1352056] Re: linux: kdump on Ubuntu 14.04 is not generating a dump.
Just verified this in a trusty power8 KVM. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1352056 Title: linux: kdump on Ubuntu 14.04 is not generating a dump. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] Users of ppc64el hardware need the ability to use crashdumps to do kernel debugging. [Fix] Commit upstream and already in utopic: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=429d2e8342954d337abe370d957e78291032d867 [Test Case] Taken from: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe https://help.ubuntu.com/14.04/serverguide/kernel-crash-dump.html 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg set crashkernel=1024M sudo update-grub 3) reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show # should return no errors 6) echo 'c' | sudo tee /proc/sysrq-trigger 7) This should crash the machine and we should kexec into another kernel to dump the core, then on the next reboot we should see a crash in /var/crash/* -- ---Problem Description--- kdump is not producing a dump on powerKVM LE P8 Ubuntu 14.04 ---uname output--- 3.13.0-30-generic ---Additional Hardware Info--- Power8 LE configuration. ---Patches Installed--- 1324544 - kdump-config load fails with vmlinux kernel (vs. vmlinuz) Machine Type = 8247-22L ---Steps to Reproduce--- Installed kdump-tools 1.5.5-2ubuntu1 and crash 7.0.3-3ubuntu3. Updated /etc/default/kdump-tools, first I updated just USE_KDUMP=1. Rebooted the node and see: root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash crashkernel=384M-:128M root@c656f2n02:~# cat /proc/sys/kernel/sysrq 1 root@c656f2n02:~# cat /proc/sys/kernel/sysrq 1 root@c656f2n02:~# ^Cnd /proc | grep sysrq root@c656f2n02:~# kdump-config status current state : ready to kdump root@c656f2n02:~# kdump-config show USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: current state:ready to kdump kexec command: /sbin/kexec -p --args-linux --command-line=root=UUID=87986483-5fec-4b4d-b22e-bf2a72096df8 ro quiet splash irqpoll maxcpus=1 nousb --initrd=/boot/initrd.img-3.13.0-30-generic /boot/vmlinux-3.13.0-30-generic root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_crash_loaded 1 root@c656f2n02:/boot/grub# cat /sys/kernel/kexec_loaded 0 echo c /proc/sysrq-trigger root@c656f2n02:/var/log# echo c /proc/sysrq-trigger [ 1956.014243] SysRq : Trigger a crash [ 1956.014328] Unable to handle kernel paging request for data at address 0x [ 1956.014404] Faulting instruction address: 0xc0586c2c [ 1956.014468] Oops: Kernel access of bad area, sig: 11 [#1] [ 1956.014518] SMP NR_CPUS=2048 NUMA PowerNV [ 1956.014570] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 rdma_ucm(OF) ib_ucm(OF) rdma_cm(OF) iw_cm(OF) ib_ipoib(OF) ib_cm(OF) ib_uverbs(OF) ib_umad(OF) mlx5_ib(OF) mlx5_core(OF) mlx4_ib(OF) ib_sa(OF) ib_mad(OF) ib_core(OF) ib_addr(OF) mlx4_en(OF) mlx4_core(OF) compat(OF) nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache rtc_generic powernv_rng ses enclosure ipr [ 1956.015306] CPU: 146 PID: 2522 Comm: bash Tainted: GF O 3.13.0-30-generic #54-Ubuntu [ 1956.015394] task: c03fcabda120 ti: c03fcac58000 task.ti: c03fcac58000 [ 1956.015469] NIP: c0586c2c LR: c0587b8c CTR: c0586c00 [ 1956.015543] REGS: c03fcac5b820 TRAP: 0300 Tainted: GF O (3.13.0-30-generic) [ 1956.015617] MSR: 90009033 SF,HV,EE,ME,IR,DR,RI,LE CR: 42422822 XER: 2000 [ 1956.015804] CFAR: c0009318 DAR: DSISR: 4200 SOFTE: 0 GPR00: c0587b8c c03fcac5baa0 c162e840 0063 GPR04: c2f45bd0 c2f564c8 00015ad0 c1827480 GPR08: c0dfe840 0001 00015ad0 GPR12: 42422822 c7e5ff00 01002fe90648 1016e008 GPR16: 1013ad70 01002fe94648 1016fed0 1016e008 GPR20: 100c31e0 10171fc8 1016f840 GPR24: 0004 0001 c14b7dc8 GPR28: c1974c90 0063
[Kernel-packages] [Bug 1371591] Re: file not initialized to 0s under some conditions on VMWare
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Precise) ** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Status in “linux-lts-trusty” package in Ubuntu: New Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Triaged Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+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 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors
Yes, I can confirm that the trusty-proposed 3.13.0-38 kernel resolves this issue. The dnsmasq-tftp transfer succeeds in my test environment without any of the symptoms that were present with the trusty- updates/security kernels between -30 and -37, nor do I notice any regressions in my (IPv4) ipvs ruleset. $ uname -a Linux catcp2-test 3.13.0-38-generic #65-Ubuntu SMP Thu Oct 9 11:36:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy linux-image-generic linux-image-generic: Installed: 3.13.0.38.45 Candidate: 3.13.0.38.45 Version table: *** 3.13.0.38.45 0 50 http://fi.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status ... ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349768 Title: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justificaton: [Impact] Users of ipvs may encounter dropped packets and message such as: [70325.516724] IPv6 header not found [Fix] Commit eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa. [Regression Potential] This changes NFPROTO_IPV4 to NFPROTO_IPV6 as we'd expect this nf_hook_ops struct to be in the code. -- I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs loadbalancer and dnsmasq server for pxebooting servers. After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading /linux TFTP transfer, with the transfer stalling roughly ~1000 blocks into the transfer: 10:30:51.011728 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.011924 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 10:30:51.012012 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.012183 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 stracing dnsmasq I noticed something very odd: sendto() on the socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start persistently returning EPERM in mid-transfer, even when dnsmasq continued to periodically retry: select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249834}) recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4 lseek(16, 1410816, SEEK_SET) = 1410816 read(16, \25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v..., 1408) = 1408 sendto(17, \0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = 1412 select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249839}) recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4 lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) This was with all iptables rules unloaded (so no OUTPUT -j DENY) and apparmor profiles torn down. I also noticed the following dmesgs appearing at roughly similar times to the tftp transfers getting stuck (although not coinciding exactly with the stall): [70325.516724] IPv6 header not found The error pointed to ipvs (which I am using on the same host as an IPv4 NAT loadbalancer):
[Kernel-packages] [Bug 1379849] Re: [LENOVO 767374G] suspend/resume failure
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379849 Title: [LENOVO 767374G] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: problem of standby ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 1753 F pulseaudio Date: Fri Oct 10 18:19:44 2014 DuplicateSignature: suspend/resume:LENOVO 767374G:7NETC2WW (2.22 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4eb1ea2b-34e7-49d4-a952-8bcd4a2e6266 InstallationDate: Installed on 2014-09-19 (20 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 767374G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=261f869f-bbc3-4a18-ad23-b90ad80e21de ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [LENOVO 767374G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 767374G 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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn767374G:pvrThinkPadX61:rvnLENOVO:rn767374G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 767374G dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379849/+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 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
** Summary changed: - Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via jockey-gtk + Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk -- 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/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey driver manager: Invalid Status in “bcmwl” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Confirmed Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “jockey” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Confirmed Status in “linux-lts-trusty” source package in Precise: Confirmed Status in “bcmwl” package in Baltix: Confirmed Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux = 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at Downloading and installing driver The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[a045d020] [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 88001b405d78 R08: R09: Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 3684 R11: 0293 R12:
[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-trusty (Ubuntu) Status: New = Confirmed -- 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/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey driver manager: Invalid Status in “bcmwl” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Confirmed Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “jockey” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Confirmed Status in “linux-lts-trusty” source package in Precise: Confirmed Status in “bcmwl” package in Baltix: Confirmed Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux = 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at Downloading and installing driver The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[a045d020] [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 88001b405d78 R08: R09: Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 3684 R11: 0293 R12: 88001b405da0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105690] R13:
[Kernel-packages] [Bug 1279690] Re: kernel panic when inserting wl.ko for Broadcom BCM4352 wireless adapter [14e4:43b1] on 12.04.4
*** This bug is a duplicate of bug 1247712 *** https://bugs.launchpad.net/bugs/1247712 OK, I think I misunderstood the result from the test report, as per Taihsiang Ho's comment in: https://bugs.launchpad.net/ubuntu/+source /linux-lts-raring/+bug/1247712/comments/62 This issue still exist in 12.04.5 with 3.13 kernel, I will revert the bug status here. Sorry for the inconvenience. ** Changed in: linux-lts-trusty (Ubuntu) Status: Fix Released = Confirmed ** Changed in: bcmwl (Ubuntu) Status: Fix Released = Confirmed ** This bug has been marked a duplicate of bug 1247712 Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk -- 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/1279690 Title: kernel panic when inserting wl.ko for Broadcom BCM4352 wireless adapter [14e4:43b1] on 12.04.4 Status in Broadcom Feature Request and Bug Reporting: Fix Released Status in “bcmwl” package in Ubuntu: Confirmed Status in “linux-lts-trusty” package in Ubuntu: Confirmed Bug description: Dell Latitude E5540 http://www.ubuntu.com/certification/hardware/201307-13942/ on 12.04.4 steps to reproduce this bug: 1. get the propietary driver which jockey tells you [1] 2. sudo dkms install -m bcmwl -v 6.20.155.1+bdcom [2] 3. sudo modprobe wl 4. lsmod | grep wl expected result: wl.ko is working and there is wireless actual result: wl.ko was inserted but there is kernel panic. wireless didn't work. [1] the steps to get the propietary driver in my case is 1. after installation 12.04.4, jockey will tell you there is propietary driver for the wireless. 2. click jockey to download and install the driver. 3. jockey will be on the stage of the downloading dialogue window 4. go to check the /var/log/jockey.log, I found * jockey has downloaded the driver and built the wl.ko * Segmentation fault after the dkms was installed [2] build and install the dkms, it looks ok for this step ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-15-generic 3.11.0-15.25~precise1 [modified: boot/vmlinuz-3.11.0-15-generic] ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-15-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1729 F pulseaudio /dev/snd/controlC0: ubuntu 1729 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf7e34000 irq 63' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 21 Simple ctrls : 3 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e3 irq 64' Mixer name : 'Realtek ALC292' Components : 'HDA:10ec0292,102805e0,0011' Controls : 28 Simple ctrls : 13 Date: Thu Feb 13 03:04:26 2014 HibernationDevice: RESUME=UUID=1298de9b-ef85-4107-b9ef-1fc727c3c1f9 InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Latitude E5540 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=aa9d3605-02da-4754-b862-7cb1a34c839d ro quiet splash initcall_debug RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.79.9 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-lts-saucy UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0V19JF dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd09/19/2013:svnDellInc.:pnLatitudeE5540:pvr01:rvnDellInc.:rn0V19JF:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom/+bug/1279690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New = Confirmed -- 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/1247712 Title: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk Status in Jockey driver manager: Invalid Status in “bcmwl” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Confirmed Status in “linux-lts-trusty” package in Ubuntu: Confirmed Status in “bcmwl” source package in Precise: Confirmed Status in “jockey” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Confirmed Status in “linux-lts-trusty” source package in Precise: Confirmed Status in “bcmwl” package in Baltix: Confirmed Bug description: SRU request: Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed. [Impact] Kernel versions higher than 3.8 fail to rebind the Broadcom device to the driver thus compromising system stability. While rebinding is a nice feature it can't come at the cost of system stability. For this reason we'll disable this feature when dealing with Linux = 3.8 and preserve it in the other cases. [Test Case] Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux- lts-trusty), then use Jockey to install the broadcom wireless driver. Jockey will hang and the system will probably hang on shutdown. [Regression Potential] It should be minimal i.e. there won't be device rebinding on the livecd. This, however, shouldn't be an issue since the open broadcom driver should already work out of the box. Furthermore the test suite now covers this test case. == Description == CID: 201303-13027 Dell Inspiron 5535 CID: 201012-6925 Dell Latitude E6320 CID: 201208-11536 Dell Latitude 6430u Affected chipsets: Broadcom 4365 Broadcom 4313 [14e4:4727] (rev 01) Broadcom 43132 The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on 12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29) Steps: 1. Install Ubuntu 12.04.3 (or 12.04.4) + update 2. Boot to desktop 3. Install the Broadcom STA wireless driver via jockey-gtk Driver cannot be installed, jockey-gtk will stuck at Downloading and installing driver The last message from jockey.jog is: unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0 Error message could be found in dmesg: Nov 3 21:34:14 201012-6925 kernel: [ 528.104653] wlc_lcnphy_rx_gain_tbl_free_entry = 5 Nov 3 21:34:14 201012-6925 kernel: [ 528.104863] BUG: unable to handle kernel paging request at a045d020 Nov 3 21:34:14 201012-6925 kernel: [ 528.104906] IP: [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.104936] PGD 1c0f067 PUD 1c13063 PMD 2ea40067 PTE 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.104967] Oops: 0010 [#1] SMP Nov 3 21:34:14 201012-6925 kernel: [ 528.104988] Modules linked in: lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma] Nov 3 21:34:14 201012-6925 kernel: [ 528.105424] CPU 0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105438] Pid: 2695, comm: jockey-backend Tainted: PF O 3.8.0-33-generic #48~precise1-Ubuntu Dell Inc. Latitude E6320/ Nov 3 21:34:14 201012-6925 kernel: [ 528.105493] RIP: 0010:[a045d020] [a045d020] 0xa045d01f Nov 3 21:34:14 201012-6925 kernel: [ 528.105533] RSP: 0018:88001b405d50 EFLAGS: 00010282 Nov 3 21:34:14 201012-6925 kernel: [ 528.105558] RAX: 0001 RBX: 880031788000 RCX: Nov 3 21:34:14 201012-6925 kernel: [ 528.105590] RDX: RSI: a0861ec0 RDI: 880031788000 Nov 3 21:34:14 201012-6925 kernel: [ 528.105623] RBP: 88001b405d78 R08: R09: Nov 3 21:34:14 201012-6925 kernel: [ 528.105657] R10: 3684 R11: 0293 R12: 88001b405da0 Nov 3 21:34:14 201012-6925 kernel: [ 528.105690]
[Kernel-packages] [Bug 1379849] 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/1379849 Title: [LENOVO 767374G] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: problem of standby ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 1753 F pulseaudio Date: Fri Oct 10 18:19:44 2014 DuplicateSignature: suspend/resume:LENOVO 767374G:7NETC2WW (2.22 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4eb1ea2b-34e7-49d4-a952-8bcd4a2e6266 InstallationDate: Installed on 2014-09-19 (20 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 767374G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=261f869f-bbc3-4a18-ad23-b90ad80e21de ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [LENOVO 767374G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 767374G 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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn767374G:pvrThinkPadX61:rvnLENOVO:rn767374G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 767374G dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379849/+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 1379849] Re: [LENOVO 767374G] suspend/resume failure
I can not reproduce this on Ubuntu MATE 14.10 RC running on Thinkpad X61s. BIOS Information Vendor: LENOVO Version: 7NETC2WW (2.22 ) Release Date: 03/22/2011 System Information Manufacturer: LENOVO Product Name: 7666WJ5 Version: ThinkPad X61s Wake-up Type: Power Switch SKU Number: Not Specified Family: ThinkPad X61s ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379849 Title: [LENOVO 767374G] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: problem of standby ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 1753 F pulseaudio Date: Fri Oct 10 18:19:44 2014 DuplicateSignature: suspend/resume:LENOVO 767374G:7NETC2WW (2.22 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4eb1ea2b-34e7-49d4-a952-8bcd4a2e6266 InstallationDate: Installed on 2014-09-19 (20 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 767374G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=261f869f-bbc3-4a18-ad23-b90ad80e21de ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [LENOVO 767374G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 767374G 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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn767374G:pvrThinkPadX61:rvnLENOVO:rn767374G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 767374G dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379849/+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 1381240] Re: [Sony Corporation VGN-FZ31M] suspend/resume failure
*** This bug is a duplicate of bug 1381237 *** https://bugs.launchpad.net/bugs/1381237 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1381237 [Sony Corporation VGN-FZ31M] suspend/resume failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381240 Title: [Sony Corporation VGN-FZ31M] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: . ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: xavi 1816 F...m pulseaudio /dev/snd/controlC0: xavi 1816 F pulseaudio Date: Tue Oct 14 15:48:11 2014 DuplicateSignature: suspend/resume:Sony Corporation VGN-FZ31M:R2110J7 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=fe13fd16-e281-4bf8-b20a-d918f1cb91a4 InstallationDate: Installed on 2014-10-06 (8 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: Sony Corporation VGN-FZ31M ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=ac49ddb3-17b3-47f7-9b36-eeae60e046ee 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: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.134 SourcePackage: linux Title: [Sony Corporation VGN-FZ31M] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/21/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2110J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31M:pvrC60058DC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ31M dmi.product.version: C60058DC dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381240/+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 1381237] Re: [Sony Corporation VGN-FZ31M] suspend/resume failure
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381237 Title: [Sony Corporation VGN-FZ31M] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavi 1816 F pulseaudio Date: Tue Oct 14 18:12:20 2014 DuplicateSignature: suspend/resume:Sony Corporation VGN-FZ31M:R2110J7 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=fe13fd16-e281-4bf8-b20a-d918f1cb91a4 InstallationDate: Installed on 2014-10-06 (8 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: Sony Corporation VGN-FZ31M ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=ac49ddb3-17b3-47f7-9b36-eeae60e046ee 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: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.134 SourcePackage: linux Title: [Sony Corporation VGN-FZ31M] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/21/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2110J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31M:pvrC60058DC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ31M dmi.product.version: C60058DC dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381237/+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 1381237] Re: [Sony Corporation VGN-FZ31M] suspend/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381237 Title: [Sony Corporation VGN-FZ31M] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavi 1816 F pulseaudio Date: Tue Oct 14 18:12:20 2014 DuplicateSignature: suspend/resume:Sony Corporation VGN-FZ31M:R2110J7 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=fe13fd16-e281-4bf8-b20a-d918f1cb91a4 InstallationDate: Installed on 2014-10-06 (8 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: Sony Corporation VGN-FZ31M ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=ac49ddb3-17b3-47f7-9b36-eeae60e046ee 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: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.134 SourcePackage: linux Title: [Sony Corporation VGN-FZ31M] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/21/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2110J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31M:pvrC60058DC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ31M dmi.product.version: C60058DC dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381237/+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 1381237] 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/1381237 Title: [Sony Corporation VGN-FZ31M] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavi 1816 F pulseaudio Date: Tue Oct 14 18:12:20 2014 DuplicateSignature: suspend/resume:Sony Corporation VGN-FZ31M:R2110J7 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=fe13fd16-e281-4bf8-b20a-d918f1cb91a4 InstallationDate: Installed on 2014-10-06 (8 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: Sony Corporation VGN-FZ31M ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=ac49ddb3-17b3-47f7-9b36-eeae60e046ee 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: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.134 SourcePackage: linux Title: [Sony Corporation VGN-FZ31M] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/21/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2110J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31M:pvrC60058DC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ31M dmi.product.version: C60058DC dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381237/+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 1381927] Re: linux: 3.16.0-23.30 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: Invalid = New ** Changed in: linux (Ubuntu Utopic) Status: Invalid = 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/1381927 Title: linux: 3.16.0-23.30 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-22.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 16. October 2014 08:06 UTC kernel-phase-changed:Thursday, 16. October 2014 08:06 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1381927/+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 1379321] Re: linux: 3.16.0-22.29 -proposed tracker
** Changed in: kernel-development-workflow/package-testing Status: Confirmed = Won't Fix ** Description changed: This bug is for tracking the 3.16.0-22.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 09. October 2014 12:44 UTC kernel-phase-changed:Friday, 10. October 2014 19:00 UTC kernel-Prepare-package-end:Friday, 10. October 2014 19:00 UTC kernel-Package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-phase:PPA Testing ppa-package-testing-start:Friday, 10. October 2014 19:00 UTC + kernel-Promote-to-release-end:Thursday, 16. October 2014 13:31 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379321 Title: linux: 3.16.0-22.29 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-22.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 09. October 2014 12:44 UTC kernel-phase-changed:Friday, 10. October 2014 19:00 UTC kernel-Prepare-package-end:Friday, 10. October 2014 19:00 UTC kernel-Package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-phase:PPA Testing ppa-package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-Promote-to-release-end:Thursday, 16. October 2014 13:31 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1379321/+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 1379321] Re: linux: 3.16.0-22.29 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release Status: New = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379321 Title: linux: 3.16.0-22.29 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-22.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 09. October 2014 12:44 UTC kernel-phase-changed:Friday, 10. October 2014 19:00 UTC kernel-Prepare-package-end:Friday, 10. October 2014 19:00 UTC kernel-Package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-phase:PPA Testing ppa-package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-Promote-to-release-end:Thursday, 16. October 2014 13:31 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1379321/+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 1381927] Re: linux: 3.16.0-23.30 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1381927 Title: linux: 3.16.0-23.30 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-22.30 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 16. October 2014 08:06 UTC kernel-phase-changed:Thursday, 16. October 2014 08:06 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1381927/+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 1349768] Re: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors
@terom-u Thanks for verifying this fix! --chris -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349768 Title: kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket sendto() EPERM errors Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justificaton: [Impact] Users of ipvs may encounter dropped packets and message such as: [70325.516724] IPv6 header not found [Fix] Commit eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa. [Regression Potential] This changes NFPROTO_IPV4 to NFPROTO_IPV6 as we'd expect this nf_hook_ops struct to be in the code. -- I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs loadbalancer and dnsmasq server for pxebooting servers. After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading /linux TFTP transfer, with the transfer stalling roughly ~1000 blocks into the transfer: 10:30:51.011728 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.011924 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 10:30:51.012012 IP 10.1.1.2.43540 10.1.12.1.49165: UDP, length 1412 10:30:51.012183 IP 10.1.12.1.49165 10.1.1.2.43540: UDP, length 4 stracing dnsmasq I noticed something very odd: sendto() on the socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) would suddenly start persistently returning EPERM in mid-transfer, even when dnsmasq continued to periodically retry: select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249834}) recvfrom(17, \0\4\3\352, 4096, 0, NULL, NULL) = 4 lseek(16, 1410816, SEEK_SET) = 1410816 read(16, \25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32\221X+\v..., 1408) = 1408 sendto(17, \0\3\3\353\25\306\345f\2{\r\4)W\276\32\336q\252_\230q\213\341U\354\25\374k7\243\32..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = 1412 select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 1 (in [17], left {0, 249839}) recvfrom(17, \0\4\3\353, 4096, 0, NULL, NULL) = 4 lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) select(18, [4 5 6 7 8 9 10 11 12 15 17], [], [], {0, 25}) = 0 (Timeout) lseek(16, 1412224, SEEK_SET) = 1412224 read(16, *\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277\221\\\307\372..., 1408) = 1408 sendto(17, \0\3\3\354*\360 C\363l\320:\256~\307\236\26P\323\274%\260\362\341\232\r\243\370\224\277..., 1412, 0, {sa_family=AF_INET, sin_port=htons(49165), sin_addr=inet_addr(10.1.11.3)}, 16) = -1 EPERM (Operation not permitted) This was with all iptables rules unloaded (so no OUTPUT -j DENY) and apparmor profiles torn down. I also noticed the following dmesgs appearing at roughly similar times to the tftp transfers getting stuck (although not coinciding exactly with the stall): [70325.516724] IPv6 header not found The error pointed to ipvs (which I am using on the same host as an IPv4 NAT loadbalancer): http://archive.linuxvirtualserver.org/html/lvs-devel/2012-08/msg00018.html http://comments.gmane.org/gmane.comp.linux.lvs.devel/3614 I then tore down the ipvs rules (service keepalived stop) and unloaded the modules (rmmod ip_vs_rr ip_vs), and the issue resolved itself - the stalled dnsmasq-tftp transfer resumed! This seems to be reproducible, i.e. modprobing ip_vs and starting keepalived will cause dnsmasq-tftp to stall again, and stopping/unloading will resume. This seems to happen reproducibly on boot with -32 and -30. This does NOT seem to happen with 3.13.0-29 which I was using up until now. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 13:43 seq crw-rw 1 root audio 116, 33 Jul 29 13:43 timer AplayDevices: Error: [Errno 2] No such file
[Kernel-packages] [Bug 1378401] Re: External USB3 hard drive fails to connect (JMicron bridge 152d:0569)
Reported to usb-linux: http://thread.gmane.org/gmane.linux.usb.general/116387 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1378401 Title: External USB3 hard drive fails to connect (JMicron bridge 152d:0569) Status in “linux” package in Ubuntu: Triaged Bug description: A Hitachi 2.5 disk in USB 3 disk enclosure with JMicron chip fails to be connected on Ubuntu Trusty. The same system was booted with Utopic Unicorn Beta 2 to verify whether newer kernel resolves the problem. Unfortunatelly it does not. The disk was properly recognised only the first time it was attached. [ 346.790756] usb 4-4: new SuperSpeed USB device number 3 using xhci_hcd [ 346.807293] usb 4-4: New USB device found, idVendor=152d, idProduct=0569 [ 346.807301] usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 346.807304] usb 4-4: Product: USB to ATA/ATAPI Bridge [ 346.807307] usb 4-4: Manufacturer: JMicron [ 346.807310] usb 4-4: SerialNumber: 4A3337343030383448584B595845 [ 348.477947] usb-storage 4-4:1.0: USB Mass Storage device detected [ 348.478225] scsi7 : usb-storage 4-4:1.0 [ 348.478395] usbcore: registered new interface driver usb-storage [ 348.588835] usbcore: registered new interface driver uas [ 349.475655] scsi 7:0:0:0: Direct-Access Hitachi HTS727575A9E364 PQ: 0 ANSI: 5 [ 349.476095] sd 7:0:0:0: Attached scsi generic sg2 type 0 [ 349.476243] sd 7:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [ 349.476734] sd 7:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 349.477219] sd 7:0:0:0: [sdb] Asking for cache data failed [ 349.477224] sd 7:0:0:0: [sdb] Assuming drive cache: write through [ 349.760792] sdb: sdb1 [ 349.762218] sd 7:0:0:0: [sdb] Attached SCSI disk [ 350.097878] EXT4-fs (sdb1): recovery complete [ 350.098248] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 350.293120] systemd-hostnamed[6253]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [ 396.016083] usb 4-4: USB disconnect, device number 3 Further attempts failed, regardless of how the disk was attached: * directly to powered USB 3 port on the laptop * to USB 3 port in laptop dock * via USB 2 hub with external power [ 409.808551] usb 3-1.1: new high-speed USB device number 4 using xhci_hcd [ 409.897277] usb 3-1.1: New USB device found, idVendor=152d, idProduct=0569 [ 409.897284] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 409.897287] usb 3-1.1: Product: USB to ATA/ATAPI Bridge [ 409.897290] usb 3-1.1: Manufacturer: JMicron [ 409.897293] usb 3-1.1: SerialNumber: 4A3337343030383448584B595845 [ 409.897953] usb-storage 3-1.1:1.0: USB Mass Storage device detected [ 409.898260] scsi8 : usb-storage 3-1.1:1.0 [ 410.897754] scsi 8:0:0:0: Direct-Access Hitachi HTS727575A9E364 PQ: 0 ANSI: 5 [ 410.898406] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 410.898589] sd 8:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [ 410.899099] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 410.899549] sd 8:0:0:0: [sdb] Asking for cache data failed [ 410.899555] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 411.509408] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd [ 411.509446] xhci_hcd :00:14.0: Setup ERROR: setup context command for slot 5. [ 411.509453] usb 3-1.1: hub failed to enable device, error -22 [ 411.581221] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd [ 411.581268] xhci_hcd :00:14.0: Setup ERROR: setup context command for slot 5. [ 411.581274] usb 3-1.1: hub failed to enable device, error -22 [ 411.653254] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd [ 411.669800] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88030f78a9c0 [ 411.669808] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88030f78aa08 [ 411.749480] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd [ 411.749527] xhci_hcd :00:14.0: Setup ERROR: setup context command for slot 5. [ 411.749534] usb 3-1.1: hub failed to enable device, error -22 [ 411.821215] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd [ 411.821256] xhci_hcd :00:14.0: Setup ERROR: setup context command for slot 5. [ 411.821262] usb 3-1.1: hub failed to enable device, error -22 [ 411.893315] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2655 F pulseaudio /dev/snd/controlC0: ubuntu 2655
[Kernel-packages] [Bug 1381999] Re: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support
Approved, after much reading... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1381999 Title: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support Status in “crash” package in Ubuntu: New Bug description: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support, plus fixing the ftbfs on arm64 as seen in the test rebuild. upstream changes: http://people.redhat.com/~anderson/crash.changelog.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1381999/+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 1381999] Re: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support
** Branch linked: lp:ubuntu/utopic-proposed/crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1381999 Title: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support Status in “crash” package in Ubuntu: New Bug description: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support, plus fixing the ftbfs on arm64 as seen in the test rebuild. upstream changes: http://people.redhat.com/~anderson/crash.changelog.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1381999/+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 1348396] Re: Ubuntu 14.10 Boot issue
Failed to load COM32 file menu .c32 boot: I am getting the same issue with every daily build utopic-desktop- amd64.iso I've tried for the past 4 days. Each of these were burned onto two types of USB stick (4GB and 8GB) using unetbootin on the laptop below, and tested on the same laptop: HP ProBook 4530s, Core i5. NB: The laptop is actually running Ubuntu 14.10 (upgraded from 14.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348396 Title: Ubuntu 14.10 Boot issue Status in “linux” package in Ubuntu: Expired Bug description: when 1 installs Ubuntu 14.10 then 1 day they 1 to Upgrade or downgrade for some reason well theres a bug on that when ya boot a USB it says Failed to load COM32 file menu .c32 boot: Maybe test this on a CD Boot --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2346 F pulseaudio /dev/snd/controlC0: darkangel 2346 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=a22cc369-bf57-44d6-88c0-2de766873fd6 InstallationDate: Installed on 2014-07-20 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348396/+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 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
Currently seeing this whenever I exit a Docker container on: Linux jenkins-1 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 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/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275] [8171ed09] dump_stack+0x45/0x56 [368973.448279] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.448283] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.448286] [81229839] remove_proc_entry+0x139/0x1b0 [368973.448313] [a04f64e2]
[Kernel-packages] [Bug 1379321] Re: linux: 3.16.0-22.29 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-development-workflow Status: In Progress = Fix Released ** Description changed: This bug is for tracking the 3.16.0-22.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 09. October 2014 12:44 UTC - kernel-phase-changed:Friday, 10. October 2014 19:00 UTC kernel-Prepare-package-end:Friday, 10. October 2014 19:00 UTC kernel-Package-testing-start:Friday, 10. October 2014 19:00 UTC - kernel-phase:PPA Testing ppa-package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-Promote-to-release-end:Thursday, 16. October 2014 13:31 UTC + kernel-phase:Released + kernel-phase-changed:Thursday, 16. October 2014 15:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379321 Title: linux: 3.16.0-22.29 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Won't Fix Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: This bug is for tracking the 3.16.0-22.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 09. October 2014 12:44 UTC kernel-Prepare-package-end:Friday, 10. October 2014 19:00 UTC kernel-Package-testing-start:Friday, 10. October 2014 19:00 UTC ppa-package-testing-start:Friday, 10. October 2014 19:00 UTC kernel-Promote-to-release-end:Thursday, 16. October 2014 13:31 UTC kernel-phase:Released kernel-phase-changed:Thursday, 16. October 2014 15:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1379321/+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 1380567] Re: Music plays through device's loudspeaker when incoming call received with BT headset connected
** Summary changed: - Ring tone and music both play through device's loudspeaker when incoming call received + Music plays through device's loudspeaker when incoming call received with BT headset connected -- 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/1380567 Title: Music plays through device's loudspeaker when incoming call received with BT headset connected Status in “bluez” package in Ubuntu: New Bug description: krillin ubuntu-rtm/14.09-proposed build 101 SUMMARY: With a Bluetooth headset connected and listening to music, the ring tone and music will both play through device loudspeaker when an incoming call is received. STEPS: 1) Pair and connect the Bluetooth headset 2) Play music through headset 3) Receive an incoming call EXPECTED RESULT: The device should remain silent (as is behaviour for wired headset). The music should pause. The ring tone should play through the headset. ACTUAL RESULT: The music and the ring tone both play through the device's loudspeaker. The ring tone also plays through the headset (as expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1380567/+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 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
Hi Michael, Thanks... installing keyutils seems to work for me too (without the kernel patch). I haven't investigated too closely, but it looks like the two fixes are sort-of equivalent. The userspace fix is far more appealing, though! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1124250 Title: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth Status in “linux” package in Ubuntu: Confirmed Status in “nfs-utils” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Won't Fix Status in “nfs-utils” source package in Trusty: New Status in “linux” source package in Utopic: Won't Fix Status in “nfs-utils” source package in Utopic: Confirmed Status in “nfs-utils” package in Debian: Incomplete Status in Fedora: Unknown Bug description: I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 662 homedirs for ldap authenticated users. /etc/exports is : /exports 192.168.0.0/24(rw,fsid=0,no_subtree_check) Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch. In /etc/default/nfs-common : NEED_IDMAPD=yes In /etc/default/nfs-kernel-server : RPCNFSDCOUNT=75 RPCMOUNTDOPTS=--manage-gids 2 Clients (rhel6 x86 Ubuntu 12.04.2 i686) are mounting this nfs4 exported directory with no problems : When doing ls -l /home on this clients, I have : ... drwx-- 4 user100 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101 oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102 oldusers 4096 oct. 1 19:06 user102 drwx-- 36 user103 users4096 févr. 5 21:08 user103 drwx-- 36 user104 users4096 févr. 8 14:03 user104 drwx-- 30 user105 users4096 févr. 4 18:01 user105 drwx-- 28 user106 oldusers 4096 oct. 5 2011 user106 drwx-- 37 user107 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 user108 users4096 déc. 4 11:52 user108 drwx-- 4 user109 oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 user110 oldusers 4096 janv. 22 15:53 user109 drwx-- 31 user111 users4096 janv. 29 12:03 user110 ... uid/gid mapping works fine, authldap works fine, ... All Clients running Ubuntu 12.10 i686 or Ubuntu 12.10 amd64 are experiencing the same problem : The config files are the same that used in ubuntu 12.04. Auth ldap is correctly configured, user can log in. This is the /etc/fstab entry for /home : 192.168.0.1:/ /home nfs rw,nfsvers=4 0 0 Important lines in /etc/idmapd.conf : domain=my-domain.org [Translation] Method=nsswitch In /etc/default/nfs-common : NEED_IDMAPD=yes /etc/nsswitch.conf is : passwd: files ldap group: files ldap shadow: files ldap When doing ls -l /home there is a strange problem : drwx-- 4 4294967294 oldusers 4096 sept. 21 2011 user100 drwx-- 4 user101oldusers 4096 sept. 21 2011 user101 drwx-- 37 user102oldusers 4096 oct. 1 19:06 user102 drwx-- 36 4294967294 users4096 févr. 5 21:08 user103 drwx-- 36 4294967294 users4096 févr. 8 14:03 user104 drwx-- 30 4294967294 users4096 févr. 4 18:01 user105 drwx-- 28 4294967294 oldusers 4096 oct. 5 2011 user106 drwx-- 37 4294967294 oldusers 4096 janv. 8 14:52 user107 drwx-- 31 4294967294 users4096 déc. 4 11:52 user108 drwx-- 4 user109oldusers 4096 sept. 21 2011 user109 drwx--x--x 45 4294967294 oldusers 4096 janv. 22 15:53 user110 drwx-- 31 4294967294 users4096 janv. 29 12:03 user111 for 571 homedirs (this number varies at each reboot)/662, the owner is the value 4294967294. For the 91 remaining homedirs, the owner is correct. The gidnumber is correctly mapped for all (only 5 differents values used for gidNumber). In /var/log/syslog, I can see : For example : user110 is mapped as 4294967294. but the command id user110 returns : uid=31124(user110) gid=666(oldusers) groupes=666(oldusers) user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/ : drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19 2012 Bureau drwxr-xr-x 3 4294967294 oldusers 4096 déc. 2 2011 Documents drwxr-xr-x 2 4294967294 oldusers 4096 déc. 2 2011 Images Then, he runs touch /home/user110/test : drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19 2012 Bureau drwxr-xr-x 3 4294967294 oldusers 4096 déc. 2 2011 Documents drwxr-xr-x 2 4294967294 oldusers 4096 déc. 2 2011 Images drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test On the nfs server, If i do a ls -l in the same directory : drwxr-xr-x 8 user110 oldusers 4096 janv. 19 2012 Bureau
[Kernel-packages] [Bug 1284085] Re: unable to boot after install on 2013 macbook air
On my MacBookPro11,1 I installed 14.10 beta-2 and have the same problem. Booting from usb works, booting from harddisk not (after installation), booting from harddisk while passing nr_cpus=1 on kernel cmdline works (but only works with 1 core, obviously). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1284085 Title: unable to boot after install on 2013 macbook air Status in Release Notes for Ubuntu: Incomplete Status in “linux” package in Ubuntu: Confirmed Bug description: Booting and installing from a live usb for trusty does work. However, on restart the machine will not boot. It hangs at: https://www.dropbox.com/s/behviox991o01o1/2014-02-23%2016.15.15.jpg Per apw in #ubuntu-kernel a test to add nr_cpus=1 does work to boot the machine. Note that wifi does not work at this point, but it does work in the live usb boot. For more information I did hit this with both the 3.13.0-8 and 3.13.0-11 kernels as I tried to update. --- Original notes --- I'm attempting to install and run 14.04 trusty on a macbook air in a dual boot configuration. I have a Mac 64bit iso bootable usb device that I used to install on top of refind. The very first time I installed and setup it worked. I was in Ubuntu. I installed updates and some basic packages and when I rebooted it would no longer boot. I had gotten an updated kernel so I attempted to boot to the older -08 kernel with no luck. I then attempted to reinstall. I figured I could avoid updates for the moment. I used the USB stick to do an install using the Remove 14.04 and install option. When it was done, it would not boot just as before. I attempted to use the usb stick to rebuild grub using http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a -ubuntu-live-cd with no luck. I've tried setting boot params in grub of nomodeset noapic. When I turn off the quiet mode I get the following screenshot where it hangs very early in the boot process around Booting SMP configuration. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-generic 3.13.0.8.12 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3336 F pulseaudio /dev/snd/controlC1: ubuntu 3336 F pulseaudio CasperVersion: 1.337 CurrentDesktop: Unity CurrentDmesg: [ 149.733266] ERROR @wl_cfg80211_get_tx_power : error (-1) Date: Mon Feb 24 07:08:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140218) MachineType: Apple Inc. MacBookAir6,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B07.1311121319 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C1E88140C3E6CF dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C1E88140C3E6CF dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B07.1311121319:bd11/12/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF: dmi.product.name: MacBookAir6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1284085/+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 1381999] Re: FFe: crash-7.0.8, integrating ppc64le support, and improving arm64/arm32 support
This bug was fixed in the package crash - 7.0.8-1ubuntu1 --- crash (7.0.8-1ubuntu1) utopic; urgency=medium * FFe LP: #1381999. - 7.0.8 adds upstream support for new architectures - fixing ftbfs on arm64. * Merge with Debian; remaining changes: - Build for armhf, arm64, ppc64el. - Minor fixes for live autopkgtest. - debian/tests/live: Redirect gpg stderr to stdout, as that's the only known and expected stderr source. crash (7.0.8-1) unstable; urgency=medium * Fix for the handling of 32-bit ELF xendump dumpfiles if the guest was configured with more than 4GB of memory. Without the patch, the crash session may fail during initialization with the error message crash: vmlinux and dumpfile do not match!. * Fix for file-handling errors when a compressed vmlinux.debug file is followed by a vmlinux file on the crash command line. When the crash session ends, two errors will occur: (1) the vmlinux file will be deleted (2) the temporary uncompressed version of the vmlinux.debug file will remain in /var/tmp This problem also occurs in the highly unlikely case where a compressed vmlinux file is followed by a vmlinux.debug file on the command line, and the uncompressed temporary version of the vmlinux file is larger than the vmlinux.debug file. In that case: (1) the vmlinux.debug file will be deleted (2) the temporary uncompressed version of the vmlinux file will remain in /var/tmp * Fix for the search -t option if the system has 2064 or more tasks. Without the patch, the command fails with a dump of the crash utility memory allocation statistics, ending with search: cannot allocate any more memory!. * Fix for the mod -S command to find the debuginfo data for Red Hat kpatch modules. Without the patch, the command would display mod: cannot find or load object file for kpatch-module module. * Deprecated the mount -f option for Linux 3.13 and later kernels containing commit eee5cc2702929fd41cce28058dc6d6717f723f87, which removed the super_block.s_files list_head member and the open files list that it contained. Without the patch, the command option fails with the error message mount: invalid structure member offset: super_block_s_files * If a compressed kdump is damaged/truncated such that the bitmap data in the dumpfile header is not contained within the file, attempts to analyze it with a vmlinux file, or using the crash --osrelease or crash --log options with just the vmcore, will result in the crash utility spinning forever, endlessly performing reads of 0 bytes from the file without recognizing the EOF condition. * Fix for an ARM64 compilation failure of the embedded gdb file aarch-linux-nat.c in the Fedora fc21 rawhide environment, which uses glibc-headers-2.19.90-24.fc21. * Document the reason behind the deprecation of the mount -f option for Linux 3.13 and later kernels if the option is attempted, and in the help mount output, similar to the deprecated mount -d option. * During initialization, reject useless ARM64 (A) absolute symbols that begin with __crc_. Without the patch, several thousand of them may be displayed by sym -l prior to the first kernel virtual address symbol. * When running against an ARM64 dumpfile created with the snap.so extension module, do not attempt to read the crash_notes. Since the dumpfile was taken while running on a live system, the crash_notes, if configured into the kernel, would not contain valid data. Without the patch, the message WARNING: could not retrieve crash_notes is displayed during session initialization. * Determine the various ARM64 kernel virtual address ranges using the kernel's VA_BITS value. It currently is hardwired in the kernel to one of two values depending upon whether 4K or 64K pages are configured. However, there are plans to support 16K paqes, to make VA_BITS a configurable value, and to make the number of page-table levels configurable. Towards that end, the crash utility has been changed to determine the VA_BITS value based upon known kernel virtual addresses, and to then calculate the relevant kernel virtual address ranges on that value instead of hardwiring them based upon the page size. * Enhancement to the kmem -S option for Linux 3.2 and later kernels configured with CONFIG_SLUB to display the address of each per-cpu kmem_cache_cpu address and the contents of its per-cpu partial list. * If an ARM or ARM64 dumpfile does not contain the register sets of the active tasks in the kernel's per-cpu crash_notes, there is an initialization-time warning message indicating could not retrieve crash_notes. It has been changed to a more meaningful warning message indicating cannot retrieve registers for active tasks. * Implement support for ARM and ARM64 raw RAM dumpfiles. One or
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Anyway, to prevent random cursor movement and random mouse clicks you can force psmouse driver to reset ALPS device immediately after first invalid packet. It can be done with: $ echo 1 /sys/module/psmouse/drivers/serio:psmouse/serio1/resetafter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 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/1258837/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Why is this bug still in state incomplete?? What is there 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 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/1258837/+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 1376771] Re: DisplayLink Attached Display Adapter and Monitor Not Recognized
By the way... I wanted to apologize for the curt, arrogant and condescending part of my post in #16 on this bug. I know those guys on the development lists are busy and responding to many inquiries. Still, I very much appreciate the cordial response from Bernie. And, if anyone knows of a product that would allow Ubuntu/Linux to reliably drive a couple of monitors off a USB 3.0 port please let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376771 Title: DisplayLink Attached Display Adapter and Monitor Not Recognized Status in “linux” package in Ubuntu: Triaged Bug description: DisplayLink Plug and Play Universal docking Station DELL Model: D3000 MFG: ACP075US SN: 1309017059 All ports on the device are recocognized and function correctly except the display adapter. Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 This problem also exists under trusty. 14.04 My intention is to drive 2 external monitors with this device. This specific device has no issues under Windows 8.1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-20-generic 3.16.0-20.27 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gesker 2140 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 2 08:54:53 2014 HibernationDevice: RESUME=UUID=8d719d41-d691-447b-8dd0-29bbdd631465 InstallationDate: Installed on 2014-08-24 (38 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: System76, Inc. Gazelle Professional ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-20-generic root=UUID=5dc9a0a5-84ba-495e-b644-8d11f37bece5 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-20-generic N/A linux-backports-modules-3.16.0-20-generic N/A linux-firmware 1.134 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-09-26 (5 days ago) dmi.bios.date: 05/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp7 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376771/+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 1382128] [NEW] No bluetooth interfaces after suspend
Public bug reported: sudo killall bluetoothd helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 16 18:58:03 2014 InstallationDate: Installed on 2014-08-14 (62 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1018P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=UUID=abb4e533-fc94-4834-83ed-0920535dd8ad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1018P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd01/03/2011:svnASUSTeKComputerINC.:pn1018P:pvrx.x:rvnASUSTeKComputerINC.:rn1018P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1018P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 74:F0:6D:AB:B8:6D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:913753 acl:1548 sco:0 events:858 errors:0 TX bytes:14 acl:811 sco:0 commands:402 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1382128 Title: No bluetooth interfaces after suspend Status in “bluez” package in Ubuntu: New Bug description: sudo killall bluetoothd helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 16 18:58:03 2014 InstallationDate: Installed on 2014-08-14 (62 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1018P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=UUID=abb4e533-fc94-4834-83ed-0920535dd8ad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1018P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd01/03/2011:svnASUSTeKComputerINC.:pn1018P:pvrx.x:rvnASUSTeKComputerINC.:rn1018P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1018P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:F0:6D:AB:B8:6D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:913753 acl:1548 sco:0 events:858 errors:0 TX bytes:14 acl:811 sco:0 commands:402 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382128/+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 1129865] Re: [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect anything at all
Same problem, Trusty Tahr, lsusb: Bus 001 Device 003: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1129865 Title: [Broadcom Combo BT/Wifi Card] 21D3 21D7 Bluetooth does not detect anything at all Status in “linux” package in Ubuntu: Won't Fix Status in “linux” source package in Precise: Won't Fix Status in “linux” source package in Quantal: Won't Fix Bug description: Tried several attemtps to scan for new bluetooth devices (BT icon - Set up new device). I tried this with three bluetooth headsets, a bluetooth mouse and a cellphone, in an environment where there are multiple active bluetooth targets that are discoverable. The bluetooth adapter on this system did not, at any time, detect ANY bluetooth device. I verified MY devices by pairing them all with my own laptop and all three were pairable. rfkill indicates that there are no blocks ubuntu@201107-8317:~$ rfkill list 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no and syslog shows where the device entered discovery but it failed to detect anything. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-38-generic 3.2.0-38.60 ProcVersionSignature: Ubuntu 3.2.0-38.60-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1769 F pulseaudio /dev/snd/controlC0: ubuntu 1769 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xa0344000 irq 52' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0xa034 irq 16' Mixer name : 'Realtek ALC269VB' Components : 'HDA:10ec0269,102804c3,00100100' Controls : 18 Simple ctrls : 10 Date: Tue Feb 19 01:50:56 2013 HibernationDevice: RESUME=UUID=7cf2dba5-3ce7-4345-8773-ac7bd6078a79 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. Dell System Inspiron M4110 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic root=UUID=b677d5d5-25d4-4eae-b0c2-84a4e8c5dd92 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-38-generic N/A linux-backports-modules-3.2.0-38-generic N/A linux-firmware1.79.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Q4E3A3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX19:bd07/22/2011:svnDellInc.:pnDellSystemInspironM4110:pvr:rvnDellInc.:rnQ4E3A3:rvrA11:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron M4110 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1129865/+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 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
I can reproduce this regularly on two physical computers but I haven't seen this at all on two virtual machines (vmware guests running ubuntu server 14.04.01). All running kernel 3.13.0-37-generic (64bit) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275] [8171ed09] dump_stack+0x45/0x56 [368973.448279] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.448283] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.448286] [81229839] remove_proc_entry+0x139/0x1b0 [368973.448313]
[Kernel-packages] [Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
For me happens on 3.13.0-37-generic, not using docker but VirtualBox -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 ii linux-image-3.13.0-37-generic 3.13.0-37.64amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP sloeuillet@SLoeuillet-DE107:/sfr$ uname -a Linux SLoeuillet-DE107 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Today, I encountered 2 quite identical stack traces in my dmesg, related to nfs : [368973.412120] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.412122] name 'fs/nfsfs' [368973.412123] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.412164] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.412166] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.412171] Workqueue: netns cleanup_net [368973.412172] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.412176] 88006a875cb8 8106773d 0005 [368973.412179] a05168a8 88011b418b30 0100 88006a875d18 [368973.412182] Call Trace: [368973.412188] [8171ed09] dump_stack+0x45/0x56 [368973.412192] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.412195] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.412198] [81229839] remove_proc_entry+0x139/0x1b0 [368973.412217] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.412225] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.412228] [8161b409] ops_exit_list.isra.1+0x39/0x60 [368973.412231] [8161bc90] cleanup_net+0x110/0x250 [368973.412235] [810839c2] process_one_work+0x182/0x450 [368973.412237] [810847b1] worker_thread+0x121/0x410 [368973.412240] [81084690] ? rescuer_thread+0x430/0x430 [368973.412243] [8108b492] kthread+0xd2/0xf0 [368973.412246] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412249] [8172f77c] ret_from_fork+0x7c/0xb0 [368973.412251] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [368973.412253] ---[ end trace bb78fe56a3dcb678 ]--- [368973.448199] WARNING: CPU: 1 PID: 15607 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [368973.448201] name 'fs/nfsfs' [368973.448203] Modules linked in: cdc_acm nfsv3 rpcsec_gss_krb5 8021q garp stp mrp llc cuse bnep rfcomm bluetooth nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc binfmt_misc fscache hp_wmi sparse_keymap snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco snd_seq_device serio_raw snd_timer ttm drm_kms_helper snd kvm edac_core soundcore drm edac_mce_amd k8temp i2c_algo_bit i2c_piix4 tpm_infineon shpchp wmi mac_hid parport_pc ppdev lp parport hid_generic usbhid hid tg3 psmouse ptp pps_core floppy ahci libahci [368973.448250] CPU: 1 PID: 15607 Comm: kworker/u8:1 Tainted: GW 3.13.0-37-generic #64-Ubuntu [368973.448252] Hardware name: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [368973.448257] Workqueue: netns cleanup_net [368973.448259] 0009 88006a875c80 8171ed09 88006a875cc8 [368973.448263] 88006a875cb8 8106773d 0005 [368973.448265] a05168a8 88011b418b30 0100 88006a875d18 [368973.448268] Call Trace: [368973.448275] [8171ed09] dump_stack+0x45/0x56 [368973.448279] [8106773d] warn_slowpath_common+0x7d/0xa0 [368973.448283] [810677ac] warn_slowpath_fmt+0x4c/0x50 [368973.448286] [81229839] remove_proc_entry+0x139/0x1b0 [368973.448313] [a04f64e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [368973.448322] [a04fc5b2] nfs_net_exit+0x12/0x20 [nfs] [368973.448325]
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Still a problem with latest BIOS A11 released by Dell a day ago. Just to keep the bug alive, because it very much is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 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/1258837/+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 1371591] Re: file not initialized to 0s under some conditions
** Summary changed: - file not initialized to 0s under some conditions on VMWare + file not initialized to 0s under some conditions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions Status in “linux” package in Ubuntu: In Progress Status in “linux-lts-trusty” package in Ubuntu: New Status in “linux” source package in Precise: Invalid Status in “linux-lts-trusty” source package in Precise: Triaged Status in “linux” source package in Trusty: Fix Committed Status in “linux-lts-trusty” source package in Trusty: Invalid Bug description: Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to leak from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
The problem with resetafter is that it causes the CPU to thrash given how often the driver gets out of sync. I tried doing that on my system, and it made it completely unusable (could barely type enough characters to update modprobe and regenerate initram. So far I've been living with loading the driver as proto=exps. I don't really use / want to use the touchpad itself, so the loss of functions doesn't matter as much to me. I do care, however, that in this mode, the kernel sees both devices as a single basic mouse, so I can't disable the touchpad to prevent accidental hits. Sad to hear that A11 hasn't changed anything; I've been holding off upgrading the BIOS as I worry about bricking the system. Does it fix anything? The keyboard repeat? Does anyone know if that is related to this or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 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/1258837/+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 1380567] Re: Music plays through device's loudspeaker when incoming call received with BT headset connected
** Tags added: touch-2014-10-30 -- 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/1380567 Title: Music plays through device's loudspeaker when incoming call received with BT headset connected Status in “bluez” package in Ubuntu: New Bug description: krillin ubuntu-rtm/14.09-proposed build 101 SUMMARY: With a Bluetooth headset connected and listening to music, the ring tone and music will both play through device loudspeaker when an incoming call is received. STEPS: 1) Pair and connect the Bluetooth headset 2) Play music through headset 3) Receive an incoming call EXPECTED RESULT: The device should remain silent (as is behaviour for wired headset). The music should pause. The ring tone should play through the headset. ACTUAL RESULT: The music and the ring tone both play through the device's loudspeaker. The ring tone also plays through the headset (as expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1380567/+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 1300914] Re: External screen undetected after first plug
What does the output of xrandr show when VGA is working, and when it is not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300914 Title: External screen undetected after first plug Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04, the external screen plugged on VGA is detected and get activated correctly. However, if I unplug it and then replug it later, it is not detected anymore and the screen receives no signal. A way to get it back to work is to reboot or simply suspend the computer. Sorry but I have no idea of what package is handling that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300914/+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 1269412] Re: via-rhine kernel module: PHY status 786d, resetting
Same issue here with newest kernel 3.13.0-37, after a few hours the network dies and I have to reboot :/ Oct 15 20:09:43 hostname kernel: via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Oct 15 20:10:03 hostname kernel: via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Oct 15 20:11:36 hostname syslog-ng[780]: syslog-ng starting up; version='3.5.3' Oct 15 20:11:36 hostname syslog-ng[780]: EOF on control channel, closing connection; Oct 15 20:11:36 hostname kernel: init: plymouth-upstart-bridge main process ended, respawning Oct 16 06:20:41 hostname kernel: perf samples too long (2504 2500), lowering kernel.perf_event_max_sample_rate to 5 Oct 16 07:35:47 hostname kernel: [ cut here ] Oct 16 07:35:47 hostname kernel: WARNING: CPU: 1 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() Oct 16 07:35:47 hostname kernel: NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out Oct 16 07:35:47 hostname kernel: Modules linked in: nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_realtek ppdev snd_hda_intel snd_hda_codec snd_hwdep kvm_amd snd_pcm snd_page_alloc kvm sn d_timer snd k8temp soundcore serio_raw edac_core edac_mce_amd i2c_viapro shpchp parport_pc mac_hid lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx pata_acpi xor raid6_pq r aid1 raid0 via_rhine mii pata_via sata_via multipath floppy linear Oct 16 07:35:47 hostname kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.13.0-37-generic #64-Ubuntu Oct 16 07:35:47 hostname kernel: Hardware name: MICRO-STAR INTERNATIONAL CO., LTD MS-7253/MS-7253, BIOS V1.7 10/23/2007 Oct 16 07:35:47 hostname kernel: 0009 88007bd03d98 8171ed09 88007bd03de0 Oct 16 07:35:47 hostname kernel: 88007bd03dd0 8106773d 880036a02000 Oct 16 07:35:47 hostname kernel: 880036b80280 0001 0001 88007bd03e30 Oct 16 07:35:47 hostname kernel: Call Trace: Oct 16 07:35:47 hostname kernel: IRQ [8171ed09] dump_stack+0x45/0x56 Oct 16 07:35:47 hostname kernel: [8106773d] warn_slowpath_common+0x7d/0xa0 Oct 16 07:35:47 hostname kernel: [810677ac] warn_slowpath_fmt+0x4c/0x50 Oct 16 07:35:47 hostname kernel: [81643936] dev_watchdog+0x276/0x280 Oct 16 07:35:47 hostname kernel: [816436c0] ? dev_graft_qdisc+0x80/0x80 Oct 16 07:35:47 hostname kernel: [810742f6] call_timer_fn+0x36/0x100 Oct 16 07:35:47 hostname kernel: [816436c0] ? dev_graft_qdisc+0x80/0x80 Oct 16 07:35:47 hostname kernel: [8107528f] run_timer_softirq+0x1ef/0x2f0 Oct 16 07:35:47 hostname kernel: [8106cb8c] __do_softirq+0xec/0x2c0 Oct 16 07:35:47 hostname kernel: [8106d0d5] irq_exit+0x105/0x110 Oct 16 07:35:47 hostname kernel: [81731c05] smp_apic_timer_interrupt+0x45/0x60 Oct 16 07:35:47 hostname kernel: [8173059d] apic_timer_interrupt+0x6d/0x80 Oct 16 07:35:47 hostname kernel: EOI [8104f596] ? native_safe_halt+0x6/0x10 Oct 16 07:35:47 hostname kernel: [8101c92f] default_idle+0x1f/0xc0 Oct 16 07:35:47 hostname kernel: [8101ca0f] amd_e400_idle+0x3f/0x110 Oct 16 07:35:47 hostname kernel: [8101d1f6] arch_cpu_idle+0x26/0x30 Oct 16 07:35:47 hostname kernel: [810bed85] cpu_startup_entry+0xc5/0x290 Oct 16 07:35:47 hostname kernel: [8104131d] start_secondary+0x21d/0x2d0 Oct 16 07:35:47 hostname kernel: ---[ end trace bff8a7011b945391 ]--- Oct 16 07:35:47 hostname kernel: via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Oct 16 07:35:51 hostname kernel: via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Oct 16 07:35:55 hostname kernel: via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269412 Title: via-rhine kernel module: PHY status 786d, resetting Status in “linux” package in Ubuntu: Confirmed Bug description: kernel version: 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux the mainboard is asus A8V-VM SE if i receive for half hour at 100Mbit full speed with partimage the network card hangs and this is the dmesg output: [ 2022.004060] WARNING: CPU: 0 PID: 3435 at /build/buildd/linux-3.11.0/net/sched/sch_generic.c:260 dev_watchdog+0x1ef/0x200() [ 2022.004066] NETDEV WATCHDOG: eth1 (via-rhine): transmit queue 0 timed out [ 2022.004069] Modules linked in: usblp pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat
[Kernel-packages] [Bug 1300914] Re: External screen undetected after first plug
Sorry, I have changed both the computer and the desktop environment since then. I had work to do and needed reliable settings quickly. I have achieved this with a Thinkpad and KDE. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300914 Title: External screen undetected after first plug Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04, the external screen plugged on VGA is detected and get activated correctly. However, if I unplug it and then replug it later, it is not detected anymore and the screen receives no signal. A way to get it back to work is to reboot or simply suspend the computer. Sorry but I have no idea of what package is handling that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300914/+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 1382221] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1382221 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/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Incomplete Bug description: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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 1382221] [NEW] please add linux nvme block driver commit
Public bug reported: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: trusty ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Incomplete Bug description: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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 1382221] Re: please add linux nvme block driver commit
We already confirmed the bug and fix upstream during 3.14 merge. I should have marked the commit for stable. I (embarrassingly) wrote the original code that committed this bug upstream, but I also wrote and committed the fix! :) ** Patch added: Fixes the bug, attaching patch committed upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+attachment/4238516/+files/ubuntu.patch ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Confirmed Bug description: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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 1380567] Re: Music plays through device's loudspeaker when incoming call received with BT headset connected
And I'm assuming your headset also supports HSP besides A2DP. If only A2DP is supported, the ideal behaviour is still to play through the device's loudspeaker. -- 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/1380567 Title: Music plays through device's loudspeaker when incoming call received with BT headset connected Status in “bluez” package in Ubuntu: Invalid Bug description: krillin ubuntu-rtm/14.09-proposed build 101 SUMMARY: With a Bluetooth headset connected and listening to music, the ring tone and music will both play through device loudspeaker when an incoming call is received. STEPS: 1) Pair and connect the Bluetooth headset 2) Play music through headset 3) Receive an incoming call EXPECTED RESULT: The device should remain silent (as is behaviour for wired headset). The music should pause. The ring tone should play through the headset. ACTUAL RESULT: The music and the ring tone both play through the device's loudspeaker. The ring tone also plays through the headset (as expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1380567/+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 1380567] Re: Music plays through device's loudspeaker when incoming call received with BT headset connected
We don't yet support inband ringtone for BT headsets, so it's expected for the ringtone to play through the device's loudspeaker. Also, even when that gets supported, it's still the desired behaviour to also play on the device's loudspeaker, together with wired/bt headset (which is not yet the case). For the music issue, that's covered at bug 1239432. ** Changed in: bluez (Ubuntu) Status: New = Invalid -- 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/1380567 Title: Music plays through device's loudspeaker when incoming call received with BT headset connected Status in “bluez” package in Ubuntu: Invalid Bug description: krillin ubuntu-rtm/14.09-proposed build 101 SUMMARY: With a Bluetooth headset connected and listening to music, the ring tone and music will both play through device loudspeaker when an incoming call is received. STEPS: 1) Pair and connect the Bluetooth headset 2) Play music through headset 3) Receive an incoming call EXPECTED RESULT: The device should remain silent (as is behaviour for wired headset). The music should pause. The ring tone should play through the headset. ACTUAL RESULT: The music and the ring tone both play through the device's loudspeaker. The ring tone also plays through the headset (as expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1380567/+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