[Kernel-packages] [Bug 1465663] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1465663 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/1465663 Title: libata Samsung SSD 8 series TRIM blacklist Status in linux package in Ubuntu: Incomplete Bug description: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465663] Re: libata Samsung SSD 8 series TRIM blacklist
As we are anticipating the issue, based on others feedback, we don't have logs. And having logs for data corruption sounds highly difficult to obtain. So, confirming it. ** 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/1465663 Title: libata Samsung SSD 8 series TRIM blacklist Status in linux package in Ubuntu: Confirmed Bug description: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465439] Re: Can't eject cd rom : Inappropriate ioctl for device
Geoff, thank you for reporting this and helping make Ubuntu better. As per www.dell.com/support/home/us/en/19/product- support/product/optiplex-320/drivers an update to your computer's buggy and outdated BIOS is available (1.1.12). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-1.1.12 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465439 Title: Can't eject cd rom : Inappropriate ioctl for device Status in linux package in Ubuntu: Incomplete Bug description: Can't eject an empty CD-Rom tray. None of the things suggested here (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At best, working from a console, I get the message above. At worst, the CD drawer grunts as though trying to eject, but doesn't open. Using a paperclip to push the hidden manual release does work, and once the tray has a CD in it, it ejects every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1662 F pulseaudio geoff 1965 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Tue Jun 16 11:28:07 2015 HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 320 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0MH651 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465663] [NEW] libata Samsung SSD 8 series TRIM blacklist
Public bug reported: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Description changed: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. - The Samsung SSD was blacklisted with that commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 + The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, - [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that- - solid/ + [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ + [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465663 Title: libata Samsung SSD 8 series TRIM blacklist Status in linux package in Ubuntu: New Bug description: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] onibi (amd64) - tests ran: 193, failed: 28
tests ran: 193, failed: 28; http://kernel.ubuntu.com/testing/onibi__3.19.0-20.20__2015-06-16_11-24-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 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:Monday, 15. June 2015 22:16 UTC kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True kernel-Package-testing-start:Tuesday, 16. June 2015 11:00 UTC kernel-phase:Testing kernel-phase-changed:Tuesday, 16. June 2015 11:00 UTC kernel-Prepare-package-end:Tuesday, 16. June 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465653] [NEW] Utopic update to 3.16.7-ckt13 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.16.7-ckt13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.16.7-ckt13 stable release: kprobes/x86: Return correct length in __copy_instruction() iio: light: hid-sensor-prox: Fix modifier iio: pressure: hid-sensor-press: Fix modifier iio: adc: xilinx: Fix register addresses iio: adc: xilinx: Fix vccaux channel .address iio: adc: xilinx: Fix VREFP scale iio: adc: xilinx: Fix VREFN sign libata: Add helper to determine when PHY events should be ignored libata: Ignore spurious PHY event on LPM policy change iio:st_sensors: Fix oops when probing SPI devices usb: gadget: configfs: Fix interfaces array NULL-termination rtlwifi: rtl8192cu: Fix kernel deadlock USB: cp210x: add ID for KCF Technologies PRN device USB: pl2303: Remove support for Samsung I330 USB: visor: Match I330 phone more precisely net: can: xilinx_can: fix extended frame handling nfsd: fix the check for confirmed openowner in nfs4_preprocess_stateid_op svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures libata: Update Crucial/Micron blacklist libata: Blacklist queued TRIM on Samsung SSD 850 Pro libata: Blacklist queued TRIM on all Samsung 800-series ACPI / init: Fix the ordering of acpi_reserve_resources() md/raid5: don't record new size if resize_stripes fails. sched: Handle priority boosted tasks proper in setscheduler() xhci: fix isoc endpoint dequeue from advancing too far on transaction error xhci: Solve full event ring by increasing TRBS_PER_SEGMENT to 256 xhci: gracefully handle xhci_irq dead device staging: gdm724x: Correction of variable usage after applying ALIGN() usb-storage: Add NO_WP_DETECT quirk for Lacie 059f:0651 devices ahci: avoton port-disable reset-quirk tty/n_gsm.c: fix a memory leak when gsmtty is removed ARM: net fix emit_udiv() for BPF_ALU | BPF_DIV | BPF_K intruction. x86/vdso: Fix the x86 vdso2c tool includes x86/vdso: Fix 'make bzImage' on older distros perf/x86/rapl: Enable Broadwell-U RAPL support drm/radeon: fix VM_CONTEXT*_PAGE_TABLE_END_ADDR handling RDMA/core: Fix for parsing netlink string attribute drm/radeon: add new bonaire pci id parisc,metag: Fix crashes due to stack randomization on stack-grows-upwards architectures firmware: dmi_scan: Fix ordering of product_uuid ext4: fix NULL pointer dereference when journal restart fails ext4: check for zero length extent explicitly jbd2: fix r_count overflows leading to buffer overflow in journal recovery mm, numa: really disable NUMA balancing by default on single node machines spi: bitbang: Make setup_transfer() callback optional igb: Fix oops on changing number of rings igb: Fix NULL assignment to incorrect variable in igb_reset_q_vector ARM: gemini: fix compiler warning due wrong data type arm64: add missing PAGE_ALIGN() to __dma_free() sound/oss: fix deadlock in sequencer_ioctl(SNDCTL_SEQ_OUTOFBAND) ARM: 8307/1: psci: move psci firmware calls out of line config: Enable NEED_DMA_MAP_STATE by default when SWIOTLB is selected staging, rtl8192e, LLVMLinux: Change extern inline to static inline kernel: use the gnu89 standard explicitly staging, rtl8192e, LLVMLinux: Remove unused inline prototype staging: wlags49_h2: fix extern inline functions staging: rtl8712, rtl8712: avoid lots of build warnings qla2xxx: remove redundant declaration in 'qla_gbl.h' ARM: mvebu: do not register custom DMA operations when coherency is disabled net: socket: Fix the wrong returns for recvmsg and sendmsg ALSA: hda - Add headphone quirk for Lifebook E752 ASoC: mc13783: Fix wrong mask value used in mc13xxx_reg_rmw() calls thermal: armada: Update Armada 380 thermal sensor coefficients mac80211: move WEP tailroom size check KVM: MMU: fix smap permission check KVM: MMU: fix CR4.SMEP=1, CR0.WP=0 with shadow pages KVM: MMU: fix SMAP virtualization storvsc: Set the SRB flags correctly when no data transfer is needed ASoC: wm8960: fix RINPUT3 audio route error ASoC: wm8994: correct BCLK DIV 348 to 384 Input: elantech - fix semi-mt protocol for v3 HW powerpc: Align TOC to 256 bytes ALSA: hda - Add Conexant codecs CX20721, CX20722, CX20723 and CX20724 ALSA: hda/realtek - ALC292 dock fix for Thinkpad L450 mmc: atmel-mci: fix bad variable type for clkdiv sd: Disable support for 256 byte/sector disks xen/events: don't bind non-percpu VIRQs with percpu chip libceph: request a new osdmap if lingering request maps to no osd crypto: s390/ghash - Fix incorrect ghash icv buffer handling. ipvs: fix memory leak in ip_vs_ctl.c tcp/ipv6: fix flow label setting
[Kernel-packages] [Bug 1465653] Re: Utopic update to 3.16.7-ckt13 stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.16.7-ckt13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.16.7-ckt13 stable release: kprobes/x86: Return correct length in __copy_instruction() iio: light: hid-sensor-prox: Fix modifier iio: pressure: hid-sensor-press: Fix modifier iio: adc: xilinx: Fix register addresses iio: adc: xilinx: Fix vccaux channel .address iio: adc: xilinx: Fix VREFP scale iio: adc: xilinx: Fix VREFN sign libata: Add helper to determine when PHY events should be ignored libata: Ignore spurious PHY event on LPM policy change iio:st_sensors: Fix oops when probing SPI devices usb: gadget: configfs: Fix interfaces array NULL-termination rtlwifi: rtl8192cu: Fix kernel deadlock USB: cp210x: add ID for KCF Technologies PRN device USB: pl2303: Remove support for Samsung I330 USB: visor: Match I330 phone more precisely net: can: xilinx_can: fix extended frame handling nfsd: fix the check for confirmed openowner in nfs4_preprocess_stateid_op svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures libata: Update Crucial/Micron blacklist - libata: Blacklist queued TRIM on Samsung SSD 850 Pro - libata: Blacklist queued TRIM on all Samsung 800-series ACPI / init: Fix the ordering of acpi_reserve_resources() md/raid5: don't record new size if resize_stripes fails. sched: Handle priority boosted tasks proper in setscheduler() xhci: fix isoc endpoint dequeue from advancing too far on transaction error xhci: Solve full event ring by increasing TRBS_PER_SEGMENT to 256 xhci: gracefully handle xhci_irq dead device staging: gdm724x: Correction of variable usage after applying ALIGN() usb-storage: Add NO_WP_DETECT quirk for Lacie 059f:0651 devices - ahci: avoton port-disable reset-quirk tty/n_gsm.c: fix a memory leak when gsmtty is removed ARM: net fix emit_udiv() for BPF_ALU | BPF_DIV | BPF_K intruction. x86/vdso: Fix the x86 vdso2c tool includes x86/vdso: Fix 'make bzImage' on older distros perf/x86/rapl: Enable Broadwell-U RAPL support drm/radeon: fix VM_CONTEXT*_PAGE_TABLE_END_ADDR handling RDMA/core: Fix for parsing netlink string attribute drm/radeon: add new bonaire pci id parisc,metag: Fix crashes due to stack randomization on stack-grows-upwards architectures firmware: dmi_scan: Fix ordering of product_uuid ext4: fix NULL pointer dereference when journal restart fails ext4: check for zero length extent explicitly jbd2: fix r_count overflows leading to buffer overflow in journal recovery mm, numa: really disable NUMA balancing by default on single node machines spi: bitbang: Make setup_transfer() callback optional igb: Fix oops on changing number of rings igb: Fix NULL assignment to incorrect variable in igb_reset_q_vector ARM: gemini: fix compiler warning due wrong data type arm64: add missing PAGE_ALIGN() to __dma_free() sound/oss: fix deadlock in sequencer_ioctl(SNDCTL_SEQ_OUTOFBAND) ARM: 8307/1: psci: move psci firmware calls out of line config: Enable NEED_DMA_MAP_STATE by default when SWIOTLB is selected staging, rtl8192e, LLVMLinux: Change extern inline to static inline kernel: use the gnu89 standard explicitly staging, rtl8192e, LLVMLinux: Remove unused inline prototype staging: wlags49_h2: fix extern inline functions staging: rtl8712, rtl8712: avoid lots of build warnings qla2xxx: remove redundant declaration in 'qla_gbl.h' ARM: mvebu: do not register custom DMA operations when coherency is disabled net: socket: Fix the wrong returns for recvmsg and sendmsg ALSA: hda - Add headphone quirk for Lifebook E752 ASoC: mc13783: Fix wrong mask value used in mc13xxx_reg_rmw() calls thermal: armada: Update Armada 380 thermal sensor coefficients mac80211: move WEP tailroom size check KVM: MMU: fix smap permission check KVM: MMU: fix CR4.SMEP=1, CR0.WP=0 with shadow pages KVM: MMU: fix SMAP virtualization storvsc: Set the SRB flags correctly when no data transfer is needed ASoC: wm8960: fix RINPUT3 audio route error ASoC: wm8994: correct BCLK DIV 348 to 384 Input: elantech - fix semi-mt protocol for v3 HW powerpc: Align TOC to 256 bytes ALSA: hda - Add Conexant codecs CX20721, CX20722, CX20723 and CX20724 ALSA: hda/realtek - ALC292 dock fix for Thinkpad L450 mmc: atmel-mci: fix bad variable type for clkdiv sd: Disable support for 256 byte/sector disks xen/events: don't bind non-percpu VIRQs with percpu chip
[Kernel-packages] [Bug 1464983] Re: [Acer Extensa 2510G] Black screen after wake up from suspend
** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+attachment/4415663/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464983 Title: [Acer Extensa 2510G] Black screen after wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: When I use NVidia 820m, after wake up I got a black screen with console cursor in the upper left corner. This problem occurs with both the proprietary and nouveau drivers. WORKAROUND: Disable the nvidia card and use the Intel integrated. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1404 F pulseaudio /dev/snd/controlC1: dmitry21 1404 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=85369393-b11e-4aa9-9876-f0fe071152a8 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Extensa 2510G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed root=UUID=62ba55e3-29b2-46df-a4a0-cdc272eafe4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464983] Re: [Acer Extensa 2510G] Black screen after wake up from suspend
** Attachment added: wakeup https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+attachment/4415662/+files/wakeup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464983 Title: [Acer Extensa 2510G] Black screen after wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: When I use NVidia 820m, after wake up I got a black screen with console cursor in the upper left corner. This problem occurs with both the proprietary and nouveau drivers. WORKAROUND: Disable the nvidia card and use the Intel integrated. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1404 F pulseaudio /dev/snd/controlC1: dmitry21 1404 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=85369393-b11e-4aa9-9876-f0fe071152a8 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Extensa 2510G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed root=UUID=62ba55e3-29b2-46df-a4a0-cdc272eafe4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465653] Re: Utopic update to 3.16.7-ckt13 stable release
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465653 Title: Utopic update to 3.16.7-ckt13 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.16.7-ckt13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.16.7-ckt13 stable release: kprobes/x86: Return correct length in __copy_instruction() iio: light: hid-sensor-prox: Fix modifier iio: pressure: hid-sensor-press: Fix modifier iio: adc: xilinx: Fix register addresses iio: adc: xilinx: Fix vccaux channel .address iio: adc: xilinx: Fix VREFP scale iio: adc: xilinx: Fix VREFN sign libata: Add helper to determine when PHY events should be ignored libata: Ignore spurious PHY event on LPM policy change iio:st_sensors: Fix oops when probing SPI devices usb: gadget: configfs: Fix interfaces array NULL-termination rtlwifi: rtl8192cu: Fix kernel deadlock USB: cp210x: add ID for KCF Technologies PRN device USB: pl2303: Remove support for Samsung I330 USB: visor: Match I330 phone more precisely net: can: xilinx_can: fix extended frame handling nfsd: fix the check for confirmed openowner in nfs4_preprocess_stateid_op svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures libata: Update Crucial/Micron blacklist ACPI / init: Fix the ordering of acpi_reserve_resources() md/raid5: don't record new size if resize_stripes fails. sched: Handle priority boosted tasks proper in setscheduler() xhci: fix isoc endpoint dequeue from advancing too far on transaction error xhci: Solve full event ring by increasing TRBS_PER_SEGMENT to 256 xhci: gracefully handle xhci_irq dead device staging: gdm724x: Correction of variable usage after applying ALIGN() usb-storage: Add NO_WP_DETECT quirk for Lacie 059f:0651 devices tty/n_gsm.c: fix a memory leak when gsmtty is removed ARM: net fix emit_udiv() for BPF_ALU | BPF_DIV | BPF_K intruction. x86/vdso: Fix the x86 vdso2c tool includes x86/vdso: Fix 'make bzImage' on older distros perf/x86/rapl: Enable Broadwell-U RAPL support drm/radeon: fix VM_CONTEXT*_PAGE_TABLE_END_ADDR handling RDMA/core: Fix for parsing netlink string attribute drm/radeon: add new bonaire pci id parisc,metag: Fix crashes due to stack randomization on stack-grows-upwards architectures firmware: dmi_scan: Fix ordering of product_uuid ext4: fix NULL pointer dereference when journal restart fails ext4: check for zero length extent explicitly jbd2: fix r_count overflows leading to buffer overflow in journal recovery mm, numa: really disable NUMA balancing by default on single node machines spi: bitbang: Make setup_transfer() callback optional igb: Fix oops on changing number of rings igb: Fix NULL assignment to incorrect variable in igb_reset_q_vector ARM: gemini: fix compiler warning due wrong data type arm64: add missing PAGE_ALIGN() to __dma_free() sound/oss: fix deadlock in sequencer_ioctl(SNDCTL_SEQ_OUTOFBAND) ARM: 8307/1: psci: move psci firmware calls out of line config: Enable NEED_DMA_MAP_STATE by default when SWIOTLB is selected staging, rtl8192e, LLVMLinux: Change extern inline to static inline kernel: use the gnu89 standard explicitly staging, rtl8192e, LLVMLinux: Remove unused inline prototype staging: wlags49_h2: fix extern inline functions staging: rtl8712, rtl8712: avoid lots of build warnings qla2xxx: remove redundant declaration in 'qla_gbl.h' ARM: mvebu: do not register custom DMA operations when coherency is disabled net: socket: Fix the wrong returns for recvmsg and sendmsg ALSA: hda - Add headphone quirk for Lifebook E752 ASoC: mc13783: Fix wrong mask value used in mc13xxx_reg_rmw() calls thermal: armada: Update Armada 380 thermal sensor coefficients mac80211: move WEP tailroom size check KVM: MMU: fix smap permission check KVM: MMU: fix CR4.SMEP=1, CR0.WP=0 with shadow pages KVM: MMU: fix SMAP virtualization storvsc: Set the SRB flags correctly when no data transfer is needed ASoC: wm8960: fix RINPUT3 audio route error ASoC: wm8994: correct BCLK DIV 348 to 384 Input: elantech - fix semi-mt protocol for v3 HW powerpc: Align TOC to 256 bytes ALSA: hda - Add Conexant codecs CX20721, CX20722, CX20723 and
[Kernel-packages] [Bug 1446239] Re: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- 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/1446239 Title: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid Status in bluez package in Ubuntu: Confirmed Bug description: At least in Beta 1 and Beta 2 of Xubuntu, bluetooth worked fine after installing the latest bluetooth driver from LWfinger (https://github.com/lwfinger/). After the latest kernel release I'm not able to get bluetooth to work anymore. With Kubuntu (vivid) there was and is no way to get rtl8723au_bt running. lsusb: Bus 004 Device 005: ID 5986:053d Acer, Inc Bus 004 Device 004: ID 0bda:1724 Realtek Semiconductor Corp. Bus 004 Device 003: ID 2047:0855 Texas Instruments Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 004: ID 03eb:8814 Atmel Corp. Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rfkill list: 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no Hardware Lenovo Yoga 11, WiFi = RTL8723 works without any problem but rtl8723au_bt means no external mouse. In addition to Xubuntu (vivid) the TLP repository with TLP is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1446239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I'm running into this problem (keys don't get automatically renewed and are expired after 10 minutes) on a precise server running the trusty lts kernel. I've just rebooted into the latest version (3.13.0.53.46), and the problem is still present. #33 mentions that installing keyutils fixes this. It fixes it by making the keys permanent (and thus increasing the likelihood of running out of space in the cache), and only with the trusty version of keyutils. With the precise version of keyutils, keys still expire and do not get renewed. Still, for people affected by the lack of renewal issue, you can install the trusty version of keyutils + libkeyutils1 + libnfsidmap2 (the trusty packages install cleanly on precise), and your keys will become permanent (beware of cache filling 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: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in nfs-utils package in Debian: Fix Released Status in Fedora: Unknown Bug description: [Impact] * This bug is likely to cause an incorrect UID/GID mapping for NFS shares in case of large numbers of differend UIDs/GIDs or in case of expired UID/GID mappings (stored as keys in the kernel). [Test Case] 1. Setup a nfs4 server exporting /home with a large number of different users and ldap-based authentication. 2. Mount the share on a ldap-connected client machine. 3. List the mounted /home directory. 4. Wait more than 10 minutes (the default key expiration time) and list it again with ls -l. Expected result - all directories are listed with correct UIDs/GIDs. Actual result - some of the directories may be listed with incorrect UID/GID of 4294967294. [Regression Potential] * This issue has been merged upstream in the 3.18 kernel and is also present in Debian's 3.16 kernel. [Other Info] * Original 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.
[Kernel-packages] [Bug 1446239] Re: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid
the bluetooth driver rtl8723au_bt-master from git-hub works fine, wlan driver rtl8723au too. Wlan driver I inserted into dkms Unfortunately I didn't managed to integrate bluetooth driver rtl8723au_bt into dkms. After every kernel update it has to be reinstalled. So could you please insert driver rtl8723au_bt and rtl8723au into kernel? So far I know all lenovo yoga notebooks like yoga 11 and 13 are affected by this issue. best from Stefan -- 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/1446239 Title: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid Status in bluez package in Ubuntu: Confirmed Bug description: At least in Beta 1 and Beta 2 of Xubuntu, bluetooth worked fine after installing the latest bluetooth driver from LWfinger (https://github.com/lwfinger/). After the latest kernel release I'm not able to get bluetooth to work anymore. With Kubuntu (vivid) there was and is no way to get rtl8723au_bt running. lsusb: Bus 004 Device 005: ID 5986:053d Acer, Inc Bus 004 Device 004: ID 0bda:1724 Realtek Semiconductor Corp. Bus 004 Device 003: ID 2047:0855 Texas Instruments Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 004: ID 03eb:8814 Atmel Corp. Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rfkill list: 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no Hardware Lenovo Yoga 11, WiFi = RTL8723 works without any problem but rtl8723au_bt means no external mouse. In addition to Xubuntu (vivid) the TLP repository with TLP is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1446239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] rukbah (amd64) - tests ran: 152, failed: 74
tests ran: 152, failed: 74; http://kernel.ubuntu.com/testing/rukbah__3.19.0-20.20__2015-06-16_11-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 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:Monday, 15. June 2015 22:16 UTC kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True kernel-Package-testing-start:Tuesday, 16. June 2015 11:00 UTC kernel-phase:Testing kernel-phase-changed:Tuesday, 16. June 2015 11:00 UTC kernel-Prepare-package-end:Tuesday, 16. June 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457672] Re: Wireless stops working when upgrading from -16 to -18 kernel on macbook air 2013
I updated the bug status. Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released ** Changed in: bcmwl (Ubuntu) Status: Confirmed = Invalid -- 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/1457672 Title: Wireless stops working when upgrading from -16 to -18 kernel on macbook air 2013 Status in bcmwl package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Today's upgrade from the -16 to the -18 kernel completely disables wireless on my 15.04 ubuntu install on a macbook air 2013. Reverting to the -16 kernel fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic:amd64 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roland 1630 F pulseaudio CurrentDesktop: Unity Date: Thu May 21 14:33:31 2015 HibernationDevice: RESUME=UUID=9e12a810-bfd8-43e5-a06f-c236be42f8b9 InstallationDate: Installed on 2014-11-09 (193 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=58091989-ee9b-4c99-afa8-fffa56a1f3af ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-23 (27 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1457672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464723 Title: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0 Status in linux package in Ubuntu: Incomplete Bug description: On my Asus X93SV-YZ225V laptop my mouse as well as all other 'human interface devices' (I tried it with a second mouse and a keyboard) stop working at a random time after boot, when attached to a USB 2.0 port. Other USB-devices (I tried it with several USB Flash drives) continue to work on the USB 2.0 ports. The USB 3.0 port on the laptop does not show this behavior, i.e. a human interface device never stops working. Unplugging and replugging the mouse does not reactivate it. The mouse works again for a random amount of time after a reboot or a wake-up from suspend to RAM. When the mouse stops working the respective /dev/input/mouseX device does not produce any output either. The touchpad, that is connected via PS/2, does not show this bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 12 14:50:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] InstallationDate: Installed on 2015-05-16 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K93SV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=4f453054-6eeb-4f48-ba87-b529b2fcd617 ro nosplash SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SV 209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK93SV209:bd11/22/2011:svnASUSTeKComputerInc.:pnK93SV:pvr1.0:rvnASUSTeKComputerInc.:rnK93SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Jun 12 13:08:49 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6152 vendor CMO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465364] Re: Laptop freeze with panic error
muka, as per http://support.lenovo.com/us/en/products/laptops-and- netbooks/lenovo-y-series-laptops/y50-70-notebook-lenovo an update to your computer's buggy and outdated BIOS is available (9ECN37WW). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-9ecn37ww ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: Incomplete Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: l 1422 F pulseaudio /dev/snd/controlC0: l 1422 F pulseaudio CurrentDesktop: LXDE Date: Mon Jun 15 20:09:15 2015 HibernationDevice: RESUME=UUID=5bb9993a-20aa-42b9-b775-d2508ba91475 InstallationDate: Installed on 2015-04-16 (59 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=949b66c8-bdcd-4186-980e-b873d5da5906 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-24 (22 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465613] Re: Utopic update to 3.16.7-ckt12 stable release
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed ** 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/1465613 Title: Utopic update to 3.16.7-ckt12 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.16.7-ckt12 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.16.7-ckt12 stable release: mlx4: Fix tx ring affinity_mask creation net/mlx4_en: Schedule napi when RX buffers allocation fails efi/reboot: Add generic wrapper around EfiResetSystem() efi/reboot: Allow powering off machines using EFI x86/reboot: Add EFI reboot quirk for ACPI Hardware Reduced flag ARC: signal handling robustify UBI: fix soft lockup in ubi_check_volume() mnt: Fail collect_mounts when applied to unmounted mounts ASoC: dapm: Enable autodisable on SOC_DAPM_SINGLE_TLV_AUTODISABLE ASoC: rt5677: add register patch for PLL btrfs: unlock i_mutex after attempting to delete subvolume during send ALSA: hda - Fix mute-LED fixed mode ALSA: hda - Add mute-LED mode control to Thinkpad arm64: dma-mapping: always clear allocated buffers ALSA: emu10k1: Fix card shortname string buffer overflow ALSA: emux: Fix mutex deadlock at unloading drm/radeon: add SI DPM quirk for Sapphire R9 270 Dual-X 2G GDDR5 SCSI: add 1024 max sectors black list flag 3w-sas: fix command completion race 3w-: fix command completion race 3w-9xxx: fix command completion race uas: Allow uas_use_uas_driver to return usb-storage flags uas: Add US_FL_MAX_SECTORS_240 flag uas: Set max_sectors_240 quirk for ASM1053 devices usb: chipidea: otg: remove mutex unlock and lock while stop and start role serial: xilinx: Use platform_get_irq to get irq description structure serial: of-serial: Remove device_type = serial registration tty/serial: at91: maxburst was missing for dma transfers ALSA: emux: Fix mutex deadlock in OSS emulation ALSA: emu10k1: Emu10k2 32 bit DMA mode rbd: end I/O the entire obj_request on error ext4: fix data corruption caused by unwritten and delayed extents ext4: move check under lock scope to close a race. bridge/mdb: remove wrong use of NLM_F_MULTI mlx4_en: Use correct loop cursor in error path. powerpc/pseries: Correct cpu affinity for dlpar added cpus Revert i2c: Mark adapter devices with pm_runtime_no_callbacks Revert mm/hugetlb: use pmd_page() in follow_huge_pmd() arm/arm64: KVM: Fix and refactor unmap_range ARM: KVM: Unmap IPA on memslot delete/move ARM: KVM: user_mem_abort: support stage 2 MMIO page mapping arm64: KVM: export demux regids as KVM_REG_ARM64 ARM: virt: fix wrong HSCTLR.EE bit setting ARM64: KVM: store kvm_vcpu_fault_info est_el2 as word KVM: ARM/arm64: fix non-const declaration of function returning const KVM: ARM/arm64: fix broken __percpu annotation KVM: ARM/arm64: avoid returning negative error code as bool KVM: vgic: return int instead of bool when checking I/O ranges ARM/arm64: KVM: fix use of WnR bit in kvm_is_write_fault() KVM: ARM: vgic: plug irq injection race arm/arm64: KVM: Fix set_clear_sgi_pend_reg offset arm/arm64: KVM: Fix VTTBR_BADDR_MASK and pgd alloc arm: kvm: fix CPU hotplug arm/arm64: KVM: fix potential NULL dereference in user_mem_abort() arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE arm: kvm: STRICT_MM_TYPECHECKS fix for user_mem_abort arm64: KVM: fix unmapping with 48-bit VAs arm/arm64: KVM: vgic: Fix error code in kvm_vgic_create() arm64/kvm: Fix assembler compatibility of macros arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() arm/arm64: KVM: Don't clear the VCPU_POWER_OFF flag arm/arm64: KVM: Correct KVM_ARM_VCPU_INIT power off option arm/arm64: KVM: Reset the HCR on each vcpu when resetting the vcpu arm/arm64: KVM: Introduce stage2_unmap_vm arm/arm64: KVM: Don't allow creating VCPUs after vgic_initialized arm/arm64: KVM: Require in-kernel vgic for the arch timers arm64: KVM: Fix TLB invalidation by IPA/VMID arm64: KVM: Fix HCR setting for 32bit guests arm64: KVM: Do not use pgd_index to index stage-2 pgd net: make skb_gso_segment error handling more robust efivarfs: Ensure VariableName is NUL-terminated x86/efi: Store upper bits of command line
[Kernel-packages] [Bug 1463445] Re: CVE-2015-4003
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463445 Title: CVE-2015-4003 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal
[Kernel-packages] [Bug 1416503] Re: CVE-2015-1420
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1416503 Title: CVE-2015-1420 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in
[Kernel-packages] [Bug 1463442] Re: CVE-2015-4001
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463442 Title: CVE-2015-4001 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal
[Kernel-packages] [Bug 1454656] Re: Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724
** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1454656 Title: Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724 Status in HWE Next Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: These codecs can be trivially supported by adding the relevant id:s to the right tables. X-HWE-Bug: Bug #1446932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463444] Re: CVE-2015-4002
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463444 Title: CVE-2015-4002 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
@Rob: Thanks to your advice I could avoid the errors according to #162, but I am ending up at the same problem as you described in #166! Has somebody any idea to solve this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Triaged Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.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 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C 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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 888828] Re: 0a5c:217f [ThinkPad X201s] sysfs: cannot create duplicate filename '/class/bluetooth/hci0:1 2'
Have this bug with my Bluetooth mouse, aftere resume-wake and mouse activity. Workaround: before mouse activity turn off bluetooth connection via GUI, so bluetooth status icon does not have small padlock in it. I tested issue with trusty and vivid kernels. $ uname -a Linux ilya-vaio 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:38:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [ 2158.421830] [ cut here ] [ 2158.421850] WARNING: CPU: 0 PID: 449 at /build/buildd/linux-lts-vivid-3.19.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() [ 2158.421854] sysfs: cannot create duplicate filename '/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/bluetooth/hci0/hci0: 21' [ 2158.421857] Modules linked in: hid_generic(E) hidp(E) hid xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_na t nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs(E) ctr ccm rfcomm(E) bnep(E) nls_iso8859_1 snd_hda_codec_hdmi(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) snd_hda_intel(E) snd_hda_controller(E) snd_hda_codec(E) snd_hwdep acer_wmi(E) sparse_keymap(E) snd_pcm intel_rapl(E) snd_seq_midi iosf_mbi snd_seq_midi_event x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel arc4 kvm crct10dif_pclmul ath9k(E) crc32_pclmul ath9k_common(E) snd_rawmidi ghash_clmulni_intel uvcvideo(E) ath9k_hw(E) cryptd videobuf2_vmalloc(E) videobuf2_memops(E) ath(E) videobuf2_core(E) v4l2_common(E) videodev(E) media(E) joydev mac80211(E) rtsx_pci_ms(E) serio_raw ath3k(E) snd_seq memstick(E) btusb(E) bluetooth(E) cfg80211(E) snd_seq_device lpc_ich(E) snd_timer wmi(E) snd sony_laptop(E) soundcore shpchp(E) mac_hid(E) i915(E) video drm_kms_helper(E) drm(E) mei_me(E) i2c_algo_bit(E) mei(E) parport_pc ppdev lp parport rtsx_pci_ sdmmc(E) psmouse ahci libahci r8169(E) mii rtsx_pci(E) [ 2158.422000] CPU: 0 PID: 449 Comm: kworker/u17:2 Tainted: GE 3.19.0-18-generic #18~14.04.1-Ubuntu [ 2158.422003] Hardware name: Sony Corporation SVT1312L1RS/VAIO, BIOS R0140D4 08/23/2012 [ 2158.422039] Workqueue: hci0 hci_rx_work [bluetooth] [ 2158.422044] 81ab6080 8802427aba58 817adfa3 [ 2158.422050] 8802427abaa8 8802427aba98 81074c2a 0206 [ 2158.422056] 880244b13000 88024482df48 8800a6c2a870 88024416cae8 [ 2158.422063] Call Trace: [ 2158.422077] [817adfa3] dump_stack+0x45/0x57 [ 2158.422085] [81074c2a] warn_slowpath_common+0x8a/0xc0 [ 2158.422091] [81074ca6] warn_slowpath_fmt+0x46/0x50 [ 2158.422098] [81260ee8] ? kernfs_path+0x48/0x60 [ 2158.422105] [81264858] sysfs_warn_dup+0x68/0x80 [ 2158.422111] [812648fe] sysfs_create_dir_ns+0x8e/0xa0 [ 2158.422123] [813a8afe] kobject_add_internal+0xce/0x3f0 [ 2158.422130] [813a9010] kobject_add+0x60/0xb0 [ 2158.422146] [814f1925] device_add+0x125/0x650 [ 2158.422152] [814f0041] ? dev_set_name+0x41/0x50 [ 2158.422191] [c069b7f1] hci_conn_add_sysfs+0x51/0xd0 [bluetooth] [ 2158.44] [c0689392] hci_event_packet+0x1962/0x2f70 [bluetooth] [ 2158.422234] [810aa6d2] ? dequeue_entity+0x142/0x5c0 [ 2158.422240] [810da643] ? internal_add_timer+0x63/0x80 [ 2158.422247] [810aaf9e] ? dequeue_task_fair+0x44e/0x660 [ 2158.422275] [c0674a78] hci_rx_work+0x1b8/0x3d0 [bluetooth] [ 2158.422283] [810ac0df] ? put_prev_task_fair+0x2f/0x50 [ 2158.422291] [8108d94f] process_one_work+0x14f/0x400 [ 2158.422296] [8108e0e8] worker_thread+0x118/0x510 [ 2158.422303] [8108dfd0] ? rescuer_thread+0x3d0/0x3d0 [ 2158.422310] [810935e2] kthread+0xd2/0xf0 [ 2158.422317] [81093510] ? kthread_create_on_node+0x1c0/0x1c0 [ 2158.422325] [817b58d8] ret_from_fork+0x58/0x90 [ 2158.422332] [81093510] ? kthread_create_on_node+0x1c0/0x1c0 [ 2158.422336] ---[ end trace 2a7dfc7ee14f5ccc ]--- [ 2158.422341] [ cut here ] [ 2158.422349] WARNING: CPU: 0 PID: 449 at /build/buildd/linux-lts-vivid-3.19.0/lib/kobject.c:240 kobject_add_internal+0x284/0x3f0() [ 2158.422353] kobject_add_internal failed for hci0:21 with -EEXIST, don't try to register things with the same name in the same directory. [ 2158.422355] Modules linked in: hid_generic(E) hidp(E) hid xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp llc aufs(E) ctr ccm rfcomm(E) bnep(E) nls_iso8859_1 snd_hda_codec_hdmi(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) snd_hda_intel(E) snd_hda_controller(E) snd_hda_codec(E) snd_hwdep acer_wmi(E) sparse_keymap(E) snd_pcm intel_rapl(E) snd_seq_midi iosf_mbi snd_seq_midi_event x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel arc4 kvm
[Kernel-packages] [Bug 1462530] Re: multipath errors on vivid and wily kernel?
related bug in redhat https://bugzilla.redhat.com/show_bug.cgi?id=630911 ** Bug watch added: Red Hat Bugzilla #630911 https://bugzilla.redhat.com/show_bug.cgi?id=630911 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1462530 Title: multipath errors on vivid and wily kernel? Status in linux package in Ubuntu: Confirmed Bug description: Oleg and I got changes into curtin to fix bug 1371634. So that now we can boot into multipath iscsi devices on power. It seems to go well enough with trusty+hwe-u, but when trying vivid, I am seeing errors. Boot was failing in one case --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 8 16:05 seq crw-rw 1 root audio 116, 33 Jun 8 16:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.17.3-0ubuntu4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 15.10 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=962acf9e-cd1c-49b0-9264-801271cd510f ro console=hvc0 ProcLoadAvg: 0.08 0.12 0.10 1/1126 3818 ProcLocks: 1: FLOCK ADVISORY WRITE 2951 00:12:14557 0 EOF 2: POSIX ADVISORY WRITE 2952 00:12:43306 0 EOF 3: POSIX ADVISORY WRITE 2905 00:12:22701 0 EOF 4: POSIX ADVISORY WRITE 2965 00:12:18505 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.19.0-20-generic (buildd@fisher03) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #20-Ubuntu SMP Fri May 29 10:03:56 UTC 2015 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.144 RfKill: Error: [Errno 2] No such file or directory Tags: wily uec-images UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.693 GHz (cpu 72) max: 3.695 GHz (cpu 87) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10 and 15.04
** Tags removed: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1400319 Title: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10 and 15.04 Status in kexec-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in kexec-tools source package in Utopic: Confirmed Status in linux source package in Utopic: Confirmed Status in kexec-tools source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: While testing the final build of 14.10 32bit we found that kernel panic cannot be activated for an installation on a Hyper-V VM. Repro rate: 100% Repro details: Hyper-V: Server 2012 R2 VM: Ubuntu 14.10 32bit Kdump is enabled in the config file at /etc/default/kdump-tools Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m | 384M-:256M VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this in combination with the values for crashkernel. Trying to start the kdump service: root@ubuntu1410i386:~# /etc/init.d/kdump-tools start Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes... locate_hole failed * failed to load kdump kernel --- root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded 0 If the conversion from hex to dec is right, the mentioned memory mapping of 0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then related to the RAM allocation nor the crashkernel value used. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6 InstallationDate: Installed on 2014-10-31 (37 days ago) InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release i386 (20141022.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory Tags: utopic Uname: Linux 3.16.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: Dec 8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3) Dec 8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 10.184.232.100 Dec 8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal in 13914 seconds. Dec 8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main process ended, respawning _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1400319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465696] [NEW] Vivid update to 3.19.8-ckt1 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.19.8-ckt1 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.19.8-ckt1 stable release: ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** 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/1465696 Title: Vivid update to 3.19.8-ckt1 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.19.8-ckt1 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.19.8-ckt1 stable release: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465696] Re: Vivid update to 3.19.8-ckt1 stable release
** Changed in: linux (Ubuntu Vivid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465696 Title: Vivid update to 3.19.8-ckt1 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.19.8-ckt1 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.19.8-ckt1 stable release: ASoC: tfa9879: Fix return value check in tfa9879_i2c_probe() ASoC: samsung: s3c24xx-i2s: Fix return value check in s3c24xx_iis_dev_probe() ASoC: dapm: Enable autodisable on SOC_DAPM_SINGLE_TLV_AUTODISABLE ASoC: rt5677: add register patch for PLL btrfs: unlock i_mutex after attempting to delete subvolume during send ALSA: hda - Fix mute-LED fixed mode ALSA: hda - Add mute-LED mode control to Thinkpad arm64: dma-mapping: always clear allocated buffers ALSA: emu10k1: Fix card shortname string buffer overflow ALSA: emux: Fix mutex deadlock at unloading drm/radeon: Use drm_calloc_ab for CS relocs drm/radeon: adjust pll when audio is not enabled drm/radeon: add SI DPM quirk for Sapphire R9 270 Dual-X 2G GDDR5 drm/radeon: fix lockup when BOs aren't part of the VM on release drm/radeon: reset BOs address after clearing it. drm/radeon: check new address before removing old one SCSI: add 1024 max sectors black list flag 3w-sas: fix command completion race 3w-: fix command completion race 3w-9xxx: fix command completion race uas: Allow uas_use_uas_driver to return usb-storage flags uas: Add US_FL_MAX_SECTORS_240 flag uas: Set max_sectors_240 quirk for ASM1053 devices usb: chipidea: otg: remove mutex unlock and lock while stop and start role serial: xilinx: Use platform_get_irq to get irq description structure serial: of-serial: Remove device_type = serial registration tty/serial: at91: maxburst was missing for dma transfers ALSA: emux: Fix mutex deadlock in OSS emulation ACPI / SBS: Enable battery manager when present ALSA: emu10k1: Emu10k2 32 bit DMA mode ASoC: rt5677: fixed wrong DMIC ref clock rbd: end I/O the entire obj_request on error ext4: fix data corruption caused by unwritten and delayed extents ext4: move check under lock scope to close a race. powerpc/pseries: Correct cpu affinity for dlpar added cpus powerpc/powernv: Restore non-volatile CRs after nap efivarfs: Ensure VariableName is NUL-terminated x86/efi: Store upper bits of command line buffer address in ext_cmd_line_ptr blk-mq: fix race between timeout and CPU hotplug blk-mq: fix CPU hotplug handling writeback: use |1 instead of +1 to protect against div by zero ARM: mvebu: armada-xp-openblocks-ax3-4: Disable internal RTC ARM: dts: imx23-olinuxino: Fix polarity of LED GPIO ARM: dts: imx23-olinuxino: Fix dr_mode of usb0 ARM: dts: imx6: phyFLEX: USB VBUS control is active-high ARM: dts: imx25: Add #pwm-cells to pwm4 ARM: dts: imx28: Fix AUART4 TX-DMA interrupt name [media] marvell-ccic: fix Y'CbCr ordering gpio: sysfs: fix memory leaks and device hotplug ACPI / SBS: Add 5 us delay to fix SBS hangs on MacBook ACPI / PNP: add two IDs to list for PNPACPI device enumeration ARM: OMAP2+: Fix omap off idle power consumption creeping up ARM: dts: OMAP3-N900: Add microphone bias voltages drm/radeon: disable semaphores for UVD V1 (v2) x86/spinlocks: Fix regression in spinlock contention detection RDMA/CMA: Canonize IPv4 on IPV6 sockets properly drm/i915: Assume dual channel LVDS if pixel clock necessitates it drm/i915: Add missing MacBook Pro models with dual channel LVDS efi: Fix error handling in add_sysfs_runtime_map_entry() Revert dm crypt: fix deadlock when async crypto algorithm returns -EBUSY xen/events: Clear cpu_evtchn_mask before resuming xen/xenbus: Update xenbus event channel on resume xen/console: Update console event channel on resume xen/events: Set irq_info-evtchn before binding the channel to CPU in __startup_pirq() mm/memory-failure: call shake_page() when error hits thp tail page mm: soft-offline: fix num_poisoned_pages counting on concurrent events nilfs2: fix sanity check of btree level in nilfs_btree_root_broken() ocfs2: dlm: fix race between purge and get lock resource drm/i915/dp: there is no audio on port A drm/amdkfd: allow unregister process with queues drm/radeon:
[Kernel-packages] [Bug 1463442] Re: CVE-2015-4001
** Changed in: linux (Ubuntu Vivid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463442 Title: CVE-2015-4001 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in
[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error
** Changed in: linux (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439780 Title: [Hyper-V] Fiber Channel critical target error Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: In Progress Bug description: System details: Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 (Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3) Ubuntu 3.19.0-11 Ubuntu Vivid 15.04 64bit custom kernel Platform: WS2012R2 Using a fiber channel disk partition ( dev/sde1 in this example) outputs the following error: [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0 [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0 [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0 Creating a partition works, reading too, but first time writing it hangs for around 20 seconds and after a couple more writes the partition goes into read-only mode: #echo test1 test1.txt *hangs for 30 seconds* blk_update_request: critical target error, dev sde, sector 0 # echo test2 test2.txt blk_update_request: critical target error, dev sde, sector 289671192 Aborting journal on device sde1-8. EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal EXT4-fs (sde1): Remounting filesystem read-only # echo test string sample.txt -bash: sample.txt: Read-only file system Dmesg log: [ 461.284362] blk_update_request: critical target error, dev sde, sector 0 [ 484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) [ 548.988377] blk_update_request: critical target error, dev sde, sector 0 [ 609.216340] blk_update_request: critical target error, dev sde, sector 289671192 [ 609.221812] Aborting journal on device sde1-8. [ 612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal [ 612.249529] EXT4-fs (sde1): Remounting filesystem read-only Additional info: cat /proc/version_signature Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416503] Re: CVE-2015-1420
** Changed in: linux (Ubuntu Vivid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1416503 Title: CVE-2015-1420 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in
[Kernel-packages] [Bug 1465714] [NEW] linux: 3.16.0-42.56 -proposed tracker
Public bug reported: This bug is for tracking the 3.16.0-42.56 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-stable-Prepare-package-start:Tuesday, 16. June 2015 15:08 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 15:08 UTC ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Tags: block-proposed-utopic kernel-release-tracking-bug utopic ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-utopic ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Tags added: utopic ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-signed
[Kernel-packages] [Bug 1465696] Re: Vivid update to 3.19.8-ckt1 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from Linus' tree or in a minimally + backported form of that patch. The 3.19.8-ckt1 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from Linus' tree or in a minimally -backported form of that patch. The 3.19.8-ckt1 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://kernel.ubuntu.com/ubuntu/linux.git -git://kernel.ubuntu.com/ubuntu/linux.git + TEST CASE: TBD - TEST CASE: TBD + The following patches are in the 3.19.8-ckt1 stable release: -The following patches are in the 3.19.8-ckt1 stable release: + ASoC: tfa9879: Fix return value check in tfa9879_i2c_probe() + ASoC: samsung: s3c24xx-i2s: Fix return value check in s3c24xx_iis_dev_probe() + ASoC: dapm: Enable autodisable on SOC_DAPM_SINGLE_TLV_AUTODISABLE + ASoC: rt5677: add register patch for PLL + btrfs: unlock i_mutex after attempting to delete subvolume during send + ALSA: hda - Fix mute-LED fixed mode + ALSA: hda - Add mute-LED mode control to Thinkpad + arm64: dma-mapping: always clear allocated buffers + ALSA: emu10k1: Fix card shortname string buffer overflow + ALSA: emux: Fix mutex deadlock at unloading + drm/radeon: Use drm_calloc_ab for CS relocs + drm/radeon: adjust pll when audio is not enabled + drm/radeon: add SI DPM quirk for Sapphire R9 270 Dual-X 2G GDDR5 + drm/radeon: fix lockup when BOs aren't part of the VM on release + drm/radeon: reset BOs address after clearing it. + drm/radeon: check new address before removing old one + SCSI: add 1024 max sectors black list flag + 3w-sas: fix command completion race + 3w-: fix command completion race + 3w-9xxx: fix command completion race + uas: Allow uas_use_uas_driver to return usb-storage flags + uas: Add US_FL_MAX_SECTORS_240 flag + uas: Set max_sectors_240 quirk for ASM1053 devices + usb: chipidea: otg: remove mutex unlock and lock while stop and start role + serial: xilinx: Use platform_get_irq to get irq description structure + serial: of-serial: Remove device_type = serial registration + tty/serial: at91: maxburst was missing for dma transfers + ALSA: emux: Fix mutex deadlock in OSS emulation + ACPI / SBS: Enable battery manager when present + ALSA: emu10k1: Emu10k2 32 bit DMA mode + ASoC: rt5677: fixed wrong DMIC ref clock + rbd: end I/O the entire obj_request on error + ext4: fix data corruption caused by unwritten and delayed extents + ext4: move check under lock scope to close a race. + powerpc/pseries: Correct cpu affinity for dlpar added cpus + powerpc/powernv: Restore non-volatile CRs after nap + efivarfs: Ensure VariableName is NUL-terminated + x86/efi: Store upper bits of command line buffer address in ext_cmd_line_ptr + blk-mq: fix race between timeout and CPU hotplug + blk-mq: fix CPU hotplug handling + writeback: use |1 instead of +1 to protect against div by zero + ARM: mvebu: armada-xp-openblocks-ax3-4: Disable internal RTC + ARM: dts: imx23-olinuxino: Fix polarity of LED GPIO + ARM: dts: imx23-olinuxino: Fix dr_mode of usb0 + ARM: dts: imx6: phyFLEX: USB VBUS control is active-high + ARM: dts: imx25: Add #pwm-cells to pwm4 + ARM: dts: imx28: Fix AUART4 TX-DMA interrupt name + [media] marvell-ccic: fix Y'CbCr ordering + gpio: sysfs: fix memory leaks and device hotplug + ACPI / SBS: Add 5 us delay to fix SBS hangs on MacBook + ACPI / PNP: add two IDs to list for PNPACPI device enumeration + ARM: OMAP2+: Fix omap off idle power consumption creeping up + ARM: dts: OMAP3-N900: Add microphone bias voltages + drm/radeon: disable semaphores for UVD V1 (v2) + x86/spinlocks: Fix regression in spinlock contention detection + RDMA/CMA: Canonize IPv4 on IPV6 sockets properly + drm/i915: Assume dual channel LVDS if pixel clock necessitates it + drm/i915: Add missing MacBook Pro models with dual channel LVDS + efi: Fix error handling in add_sysfs_runtime_map_entry() + Revert dm crypt: fix deadlock when async crypto algorithm returns -EBUSY + xen/events: Clear cpu_evtchn_mask before resuming + xen/xenbus: Update xenbus event channel on resume + xen/console: Update console event channel on resume + xen/events: Set irq_info-evtchn before binding the channel to CPU in __startup_pirq() + mm/memory-failure: call shake_page() when error hits thp tail page + mm: soft-offline: fix num_poisoned_pages counting
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
I built two more test kernels. One has commit df438af reverted and the other has df438af reverted. Can you test each of these kernels and see which one resolves the bug? The kernels can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1465322/df438af-reverted and http://kernel.ubuntu.com/~jsalisbury/lp1465322/7b0f287-reverted Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465755] [NEW] linux: 3.19.0-22.22 -proposed tracker
Public bug reported: This bug is for tracking the 3.19.0-22.22 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-stable-Prepare-package-start:Tuesday, 16. June 2015 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 16:18 UTC ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Medium Status: New ** Tags: block-proposed-vivid kernel-release-tracking-bug vivid ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-vivid ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Tags added: vivid ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee:
[Kernel-packages] [Bug 1463445] Re: CVE-2015-4003
** Changed in: linux (Ubuntu Vivid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463445 Title: CVE-2015-4003 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in
[Kernel-packages] [Bug 1463444] Re: CVE-2015-4002
** Changed in: linux (Ubuntu Vivid) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463444 Title: CVE-2015-4002 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
I can confirm that reverting df438afe2d93 (debugfs: leave freeing a symlink body until inode eviction) fixes the issue on an i386 VM. But it would be great to have the original bug reporter to test that too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid
** Tags removed: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1440103 Title: [Hyper-V] Kernel panic not functional on Vivid Status in linux package in Ubuntu: Confirmed Bug description: Issue description: Triggering a kernel panic will not produce a crash dump file. Steps to Reproduce: 1. install kdump related packages. 2. verify crashmem value - defaults to 384M-:129M 3. verify that the system is ready for crash: # cat /sys/kernel/kexec_crash_loaded 1 4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger 5. The system will freeze and no kernel dump will be generated, system is not rebooted automatically as configured in kdump-tools config. Versions details: Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter build 9600 Distribution name and release: Ubuntu Vivid Vervet Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 SMP Repro output with VM settings as follows: 2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M [ 149.328829] SysRq : Trigger a crash [ 149.342418] BUG: unable to handle kernel NULL pointer dereference at (null) [ 149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0 [ 149.346369] Oops: 0002 [#1] SMP [ 149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 8250_fintek hyperv_keyboard hv_balloon hyp erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy pata_acpi hv_vmbus [ 149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic #11lp14233432v201504021617 [ 149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 [ 149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 88007be7c000 [ 149.346369] RIP: 0010:[814ae776] [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP: 0018:88007be7fe68 EFLAGS: 00010292 [ 149.346369] RAX: 000f RBX: 0063 RCX: 000f [ 149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 0063 [ 149.346369] RBP: 88007be7fe68 R08: 0002 R09: 0275 [ 149.346369] R10: 0092 R11: 0275 R12: 0004 [ 149.346369] R13: R14: 81cb38e0 R15: 0008 [ 149.346369] FS: 7f0a2e22a700() GS:88007ce0() knlGS: [ 149.346369] CS: 0010 DS: ES: CR0: 8005003b [ 149.346369] CR2: CR3: 36047000 CR4: 06f0 [ 149.346369] Stack: [ 149.346369] 88007be7fe98 814aef96 0002 fffb [ 149.346369] 7ffc64e934b0 0002 88007be7feb8 814af443 [ 149.346369] 7ffc64e934b0 8800364f15c0 88007be7fed8 8125ad98 [ 149.346369] Call Trace: [ 149.346369] [814aef96] __handle_sysrq+0x106/0x170 [ 149.346369] [814af443] write_sysrq_trigger+0x33/0x40 [ 149.346369] [8125ad98] proc_reg_write+0x48/0x70 [ 149.346369] [811f33d7] vfs_write+0xb7/0x1f0 [ 149.346369] [811f3ece] ? vfs_read+0x11e/0x140 [ 149.346369] [811f3fe6] SyS_write+0x46/0xb0 [ 149.346369] [817c924d] system_call_fastpath+0x16/0x1b [ 149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00 01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 55 31 c0 48 89 e5 [ 149.346369] RIP [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP 88007be7fe68 [ 149.346369] CR2: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v 201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 3.19.0-11.11lp14233432v201504021617-generic 3.19.3) [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=867700K To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1446732] Re: Fujitsu Lifebook E544 touchpad doesn't work
Hello, I'm quite new here, so excuse if this is stupid question but would this https://github.com/torvalds/linux/commit/47c1ffb2b6b630894e9a16442611c056ab21c057 be backported to the 14.04 kernel? Looks like it is the cause of problems with E544 and E554 touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1446732 Title: Fujitsu Lifebook E544 touchpad doesn't work Status in linux package in Ubuntu: Incomplete Bug description: The touchpad does not work. The laptop is new and the touchpad works in Windows 7 Pro. 0.708960] mousedev: PS/2 mouse device common for all mice [ 2.325752] psmouse serio2: elantech: assuming hardware version 4 (with firmware version 0x470f00) [ 2.360739] psmouse serio2: elantech: Synaptics capabilities query result 0x50, 0x12, 0x09. [ 29.679419] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 a lot of lost sync at byte 6 in between [ 31.109895] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 31.109899] psmouse serio2: issuing reconnect request ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-34-generic 3.16.0-34.47 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lcf1837 F pulseaudio /dev/snd/controlC0: lcf1837 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 19.741240] systemd-logind[876]: Failed to start user service: Unknown unit: user@1000.service [ 19.744417] systemd-logind[876]: New session c1 of user lcf. [ 19.744434] systemd-logind[876]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 25.044453] init: anacron main process (1133) killed by TERM signal Date: Tue Apr 21 16:39:03 2015 HibernationDevice: RESUME=UUID=b8fdafe8-740b-4360-ad4e-e8dfb4eb2ab7 InstallationDate: Installed on 2015-04-17 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: FUJITSU LIFEBOOK E544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=bcf80a26-abb4-4054-81f6-c17bd7a84909 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-34-generic N/A linux-backports-modules-3.16.0-34-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.02 dmi.board.name: FJNB281 dmi.board.vendor: FUJITSU dmi.board.version: E2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E544 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.02:bd05/23/2014:svnFUJITSU:pnLIFEBOOKE544:pvr10601583220:rvnFUJITSU:rnFJNB281:rvrE2:cvnFUJITSU:ct10:cvrLIFEBOOKE544: dmi.product.name: LIFEBOOK E544 dmi.product.version: 10601583220 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465798] [NEW] linux: 3.13.0-56.93 -proposed tracker
Public bug reported: This bug is for tracking the 3.13.0-56.93 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-stable-Prepare-package-start:Tuesday, 16. June 2015 17:48 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 17:48 UTC ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Tags: block-proposed-trusty kernel-release-tracking-bug trusty ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-signed
[Kernel-packages] [Bug 1465808] Re: Hibernation fails due to a non-reachable cifs mount
** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465808/+attachment/4415784/+files/lspci-vnvn.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/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Incomplete Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465808] [NEW] Hibernation fails due to a non-reachable cifs mount
Public bug reported: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: version.log https://bugs.launchpad.net/bugs/1465808/+attachment/4415783/+files/version.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/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Incomplete Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2]
[Kernel-packages] [Bug 1465419] fozzie (i386) - tests ran: 167, failed: 27
tests ran: 167, failed: 27; http://kernel.ubuntu.com/testing/fozzie__3.19.0-20.20__2015-06-16_14-11-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 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:Monday, 15. June 2015 22:16 UTC kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True kernel-Package-testing-start:Tuesday, 16. June 2015 11:00 UTC kernel-phase:Testing kernel-phase-changed:Tuesday, 16. June 2015 11:00 UTC kernel-Prepare-package-end:Tuesday, 16. June 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458042 Title: [SRU] xgene-enet: add SGMII based 1GbE support for the second port Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: [Impact] APM's Mustang boards have a second SGMII based 1GbE interface that is currently unsupported by Ubuntu. [Test Case] Verify that the previously non-working SGMII based 1GbE interface now works. [Regression Risk] Since the changes touch the driver that supports the existing GbE and first SGMII support, it is possible that that support has become impacted. The changes also impact drivers/of/of_net.c, which could impact other users of the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
I just tested the linked upstream kernel. It does not change the behavior, I am observing the same bug on v4.1-rc8-unstable. I added the tag accordingly. Regarding the question whether this was happening after an upgrade. Well it's actually a little complicated. If my memory does not deceive me, I did not observe this problem when I installed Ubuntu 12.04 on this laptop in 2012. Some time afterwards, after an update this problem occurred. Unfortunately at the time I was otherwise occupied so I just attached the mouse to the USB 3.0 port and did not report the bug. And by the time my schedule had cleared up a bit I had forgotten all about the problem, until I recently switched USB ports with the mouse and stumbled upon it again. So it is probably a regression albeit only compared to a three year old kernel. I will try testing the 12.04.X releases and see if I can actually find a reliably good version, and then maybe start bisecting from there, though this may take some time. If some other debugging information would be useful let me know. ** 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/1464723 Title: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0 Status in linux package in Ubuntu: Confirmed Bug description: On my Asus X93SV-YZ225V laptop my mouse as well as all other 'human interface devices' (I tried it with a second mouse and a keyboard) stop working at a random time after boot, when attached to a USB 2.0 port. Other USB-devices (I tried it with several USB Flash drives) continue to work on the USB 2.0 ports. The USB 3.0 port on the laptop does not show this behavior, i.e. a human interface device never stops working. Unplugging and replugging the mouse does not reactivate it. The mouse works again for a random amount of time after a reboot or a wake-up from suspend to RAM. When the mouse stops working the respective /dev/input/mouseX device does not produce any output either. The touchpad, that is connected via PS/2, does not show this bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 12 14:50:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] InstallationDate: Installed on 2015-05-16 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K93SV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=4f453054-6eeb-4f48-ba87-b529b2fcd617 ro nosplash SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SV 209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK93SV209:bd11/22/2011:svnASUSTeKComputerInc.:pnK93SV:pvr1.0:rvnASUSTeKComputerInc.:rnK93SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
[Kernel-packages] [Bug 1462530] Re: multipath errors on vivid and wily kernel?
I filed debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=788841 about the race condition that I think exists. ** Bug watch added: Debian Bug tracker #788841 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788841 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1462530 Title: multipath errors on vivid and wily kernel? Status in linux package in Ubuntu: Confirmed Bug description: Oleg and I got changes into curtin to fix bug 1371634. So that now we can boot into multipath iscsi devices on power. It seems to go well enough with trusty+hwe-u, but when trying vivid, I am seeing errors. Boot was failing in one case --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 8 16:05 seq crw-rw 1 root audio 116, 33 Jun 8 16:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.17.3-0ubuntu4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 15.10 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=962acf9e-cd1c-49b0-9264-801271cd510f ro console=hvc0 ProcLoadAvg: 0.08 0.12 0.10 1/1126 3818 ProcLocks: 1: FLOCK ADVISORY WRITE 2951 00:12:14557 0 EOF 2: POSIX ADVISORY WRITE 2952 00:12:43306 0 EOF 3: POSIX ADVISORY WRITE 2905 00:12:22701 0 EOF 4: POSIX ADVISORY WRITE 2965 00:12:18505 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.19.0-20-generic (buildd@fisher03) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #20-Ubuntu SMP Fri May 29 10:03:56 UTC 2015 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.144 RfKill: Error: [Errno 2] No such file or directory Tags: wily uec-images UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.693 GHz (cpu 72) max: 3.695 GHz (cpu 87) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465808] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1465808 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/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Incomplete Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] onibi (i386) - tests ran: 167, failed: 27
tests ran: 167, failed: 27; http://kernel.ubuntu.com/testing/onibi__3.19.0-20.20__2015-06-16_14-21-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 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:Monday, 15. June 2015 22:16 UTC kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True kernel-Package-testing-start:Tuesday, 16. June 2015 11:00 UTC kernel-phase:Testing kernel-phase-changed:Tuesday, 16. June 2015 11:00 UTC kernel-Prepare-package-end:Tuesday, 16. June 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465808] Re: Hibernation fails due to a non-reachable cifs mount
Confirming manually as apport-collect is broken on Kubuntu, see #1439784 ** 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/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
I updated my ppa for vivid. Changed module version. But I get feedbacks that it worked without that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 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.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465796] [NEW] Trusty update to 3.13.11-ckt21 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.13.11-ckt21 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.13.11-ckt21 stable release: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Trusty) 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/1465796 Title: Trusty update to 3.13.11-ckt21 stable release Status in linux package in Ubuntu: New Status in linux source package in Trusty: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.13.11-ckt21 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.13.11-ckt21 stable release: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464490] Re: Elan new touchpad recognized as a mouse and doesn't work
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1464490 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. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Incomplete ** Changed in: linux (Ubuntu Trusty) Status: Incomplete = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1464490 Title: Elan new touchpad recognized as a mouse and doesn't work Status in HWE Next Project: New Status in linux package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: New Bug description: Elan new touchpad recognized as a mouse, here is the steps to reproduce the bug: Steps: 1. try scrolling with touchpad Expected results: Touchpad features such as scrolling should be supported Actual results: Touchpad features such as scrolling are not supported Actually we need add new icbody type to fix the bug, and mainline kernel has the fix, commit is: 692dd1916436164e228608803dfb6cb768d6355a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1464490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463442] Re: CVE-2015-4001
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463442 Title: CVE-2015-4001 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status
[Kernel-packages] [Bug 1465796] Re: Trusty update to 3.13.11-ckt21 stable release
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465796 Title: Trusty update to 3.13.11-ckt21 stable release Status in linux package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The 3.13.11-ckt21 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches are in the 3.13.11-ckt21 stable release: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463444] Re: CVE-2015-4002
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463444 Title: CVE-2015-4002 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status
[Kernel-packages] [Bug 1463445] Re: CVE-2015-4003
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1463445 Title: CVE-2015-4003 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status
[Kernel-packages] [Bug 1465755] Re: linux: 3.19.0-22.22 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465755 Title: linux: 3.19.0-22.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-22.22 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-stable-Prepare-package-start:Tuesday, 16. June 2015 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 16:18 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416503] Re: CVE-2015-1420
** Changed in: linux (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1416503 Title: CVE-2015-1420 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in
[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler
Both these test kernels for Trusty and Utopic worked as well. Thanks, Steve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463584 Title: [Hyper-V] Add support for VMBus panic notifier handler Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Please take these patches to our Hyper-V VMBus driver to enable kernel crash notification: Drivers: hv: vmbus: Add support for VMBus panic notifier handler https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81 Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13 In the event of a kernel panic, VMBus driver supports sending five 64-bit values to be recorded in the log. On Hyper-V this is recorded in the event log, and on Azure we can use this data to better detect failures like this in the guest VM and surface that as part of our diagnostics information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465714] Re: linux: 3.16.0-42.56 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465714 Title: linux: 3.16.0-42.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-42.56 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-stable-Prepare-package-start:Tuesday, 16. June 2015 15:08 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 15:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 Can anyone tell me if this bug affects kernel 3.10? I don't think this has the SATA 3.1 codes yet.. so I think it should be fine? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465755] Re: linux: 3.19.0-22.22 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465755 Title: linux: 3.19.0-22.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-22.22 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-stable-Prepare-package-start:Tuesday, 16. June 2015 16:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 16:18 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460674] Re: [i915_bpo] Rebase driver to 4.2~pre
** Changed in: linux (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460674 Title: [i915_bpo] Rebase driver to 4.2~pre Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Upstream i915 code has been feature-frozen for drm-next, and rebasing i915_bpo to it is fairly simple. We need all the drm_atomic* changes to date though, in order to avoid oopses loading the driver. Thankfully i915_bpo is the only driver that uses them (besides msm), so there's no chance of regressing other drivers that we care about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460661] Re: [i915, i915_bpo, snd-hda-intel] Switch to component support
** Changed in: linux (Ubuntu Vivid) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460661 Title: [i915, i915_bpo, snd-hda-intel] Switch to component support Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Migrate snd-hda-intel/i915/i915_bpo to use component support for the driver interface, instead of module symbol lookups. This has been upstream since 4.0, and lays the groundwork for proper HDMI/DP-audio support in i915_bpo. Patches cherry-pick cleanly. d7055bd653e00ef40a07065d1c94380240314c48 ALSA: hda: add component support 926981ae3325257d0bffcf7ff7ba359edb4fd7e8 ALSA: hda: pass intel_hda to all i915 interface functions 347de1f8625199d177caf7668cfa1c00717faedb ALSA: hda: export struct hda_intel 58fddc288b5cec192ad9eb9221da7ed14d974a27 drm/i915: add component support This is related to the power well in Haswell generation and newer, so regression testing on HSW/BDW is enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: linux-lts-trusty (Ubuntu Trusty) ** No longer affects: linux-lts-utopic (Ubuntu Precise) ** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu Precise) ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-trusty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-utopic (Ubuntu Utopic) Importance: Undecided Status: New ** No longer affects: linux-lts-utopic (Ubuntu Utopic) ** No longer affects: linux-lts-trusty (Ubuntu Utopic) ** No longer affects: linux-lts-trusty (Ubuntu) ** No longer affects: linux-lts-trusty (Ubuntu Precise) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Status in linux source package in Utopic: New Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458569] Re: System freezes randomly
** Description changed: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in - systems with the XPRESS 200M CPU chipset. + systems with the XPRESS 200M GPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: diskdoc1202 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor - Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f4a074bf-eb4a-4cda-8a5a-561f66420476 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.19.0-18-generic N/A - linux-backports-modules-3.19.0-18-generic N/A - linux-firmware 1.143.1 + linux-restricted-modules-3.19.0-18-generic N/A + linux-backports-modules-3.19.0-18-generic N/A + linux-firmware 1.143.1 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTT Ver. F.07 dmi.board.name: 308B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 45.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTTVer.F.07:bd07/01/2005:svnHewlett-Packard:pnHPCompaqnx6125(PY416EA#AK8):pvrF.07:rvnHewlett-Packard:rn308B:rvrKBCVersion45.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6125 (PY416EA#AK8) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard ** Tags removed: kernel-bug-exists-upstream-4.1-rc5 ** Tags added: kernel-bug-exists-upstream-4.1-rc6 ** 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/1458569 Title: System freezes randomly Status in linux package in Ubuntu: Confirmed Bug description: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in systems with the XPRESS 200M GPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Here's some more detail: running 'strace df' shows the following: statfs64(/sys/kernel/debug, 84, 0xbfddc6bc) = -1 ENOSYS (Function not implemented) A quick test shows that adding '.statfs = simple_statfs' in the debugfs_super_operations struct fixes the problem, but I'm not sure that's the right thing to do. (This has been reported upstream: http://thread.gmane.org/gmane.linux.kernel.stable/134708/focus=134588) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465714] Re: linux: 3.16.0-42.56 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465714 Title: linux: 3.16.0-42.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: New Bug description: This bug is for tracking the 3.16.0-42.56 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-stable-Prepare-package-start:Tuesday, 16. June 2015 15:08 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 15:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
I emailed Killer Network Support, the answered: Thank you for your email. We have worked with Qualcomm to verify linux drivers for teh Killer 1525. We have seen it work, and are awaiting the open source/linux community to accept the 6174 2.x ath10k firmware so that it is posted and available for everyone. Once the ath10k firmware has been updated, there should be no issue loading the ath10k drivers. ath10k drivers are here: https://github.com/kvalo/ath ath10k firmware is here: https://github.com/kvalo/ath10k-firmware Regards, Thomas Killer Networking -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Triaged Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.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 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C 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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
** Changed in: linux (Ubuntu Vivid) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458569] Re: System freezes randomly
Tested! System still freezes as before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458569 Title: System freezes randomly Status in linux package in Ubuntu: Confirmed Bug description: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in systems with the XPRESS 200M GPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f4a074bf-eb4a-4cda-8a5a-561f66420476 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTT Ver. F.07 dmi.board.name: 308B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 45.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTTVer.F.07:bd07/01/2005:svnHewlett-Packard:pnHPCompaqnx6125(PY416EA#AK8):pvrF.07:rvnHewlett-Packard:rn308B:rvrKBCVersion45.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6125 (PY416EA#AK8) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Reverting df438af seems to have fixed it. $ cat /proc/version_signature Ubuntu 3.2.0-86.123~lp1465322Commitdf438afReverted-generic 3.2.69 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4735296 2366480 67% / udev 371924 4371920 1% /dev -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
** Changed in: linux (Ubuntu Utopic) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Status in linux source package in Utopic: Fix Committed Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465808] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415843/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415847/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415840/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415841/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415836/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415845/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415849/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1404409] Re: [regression] Intel 10Gb NIC Crashes
** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404409 Title: [regression] Intel 10Gb NIC Crashes Status in linux package in Ubuntu: Triaged Bug description: I posted this to net...@vger.kernel.org as well: http://www.spinics.net/lists/netdev/msg309110.html I think the next step is to try to bisect this down to a specific commit. I'm starting to look at the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection - Previous history of this thread: http://thread.gmane.org/gmane.linux.network/326672 On 2014-11-04 22:57:19, Tom Herbert wrote: Using vlan and bonding? vlan_dev_hard_start_xmit called. A possible cause is that bonding interface is out of sync with slave interface w.r.t. GSO features. Do we know if this worked in 3.14, 3.15? I'm seeing the same sort of crash/warning (skb_war_bad_offload). It's happening on Intel 10 Gig NICs using the ixgbe driver. I'm using bridges (for virtual machines) on top of VLANs on top of 802.3ad bonding. I'm using an MTU of 9000 on the bond0 interface, but 1500 everywhere else. I'm always bonding two ports: one one system, I'm bonding two ports on identical one-port NICs; on another system, I'm bonding two ports on a single two-port NIC. Both systems exhibit the same behavior. Everything has worked fine for a couple years on Ubuntu 12.04 Precise (Linux 3.2.0). It immediately broke when I upgraded to Ubuntu 14.04 Trusty (Linux 3.13.0). I can also reproduce this using the packaged version of Linux 3.16.0 on Trusty. In contrast to other reports of this bug, disabling scatter gather on the physical interfaces (e.g. eth0) does *not* stop the crashes (assuming I disabled it correctly). I currently have two systems (one with Precise, one with Trusty) available to do any testing that you'd find helpful. Here's a first pass at getting some debugging data. The broken system (Ubuntu 14.04 Trusty): rlaager@BROKEN:~$ uname -a Linux BROKEN 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux rlaager@BROKEN:~$ ethtool -k p6p1 Features for p6p1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: on tx-checksum-fcoe-crc: on [fixed] tx-checksum-sctp: on scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: on udp-fragmentation-offload: off [fixed] generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off rx-vlan-offload: on tx-vlan-offload: on ntuple-filters: off receive-hashing: on highdma: on [fixed] rx-vlan-filter: on vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: on [fixed] tx-gre-segmentation: off [fixed] tx-ipip-segmentation: off [fixed] tx-sit-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] tx-mpls-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: on loopback: off [fixed] rx-fcs: off [fixed] rx-all: off tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off rlaager@BROKEN:~$ ethtool -k bond0 Features for bond0: rx-checksumming: off [fixed] tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [requested on] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: on tx-tcp6-segmentation: on udp-fragmentation-offload: off [fixed] generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off rx-vlan-offload: on tx-vlan-offload: on ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: on rx-vlan-filter: on vlan-challenged: off [fixed] tx-lockless: on [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-ipip-segmentation: off [fixed] tx-sit-segmentation: off [fixed] tx-udp_tnl-segmentation: on tx-mpls-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off [requested on] loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed]
[Kernel-packages] [Bug 1465808] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415846/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415839/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415838/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] Re: Hibernation fails due to a non-reachable cifs mount
apport information ** Tags added: apport-collected vivid ** Description changed: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b - The task in question is hanging and can't be killed by -KILL or -TERM. I - also couldn't umount the mount using 'umount -f'. + The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. + --- + ApportVersion: 2.17.2-0ubuntu1.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: packi 2227 F pulseaudio + /dev/snd/controlC0: packi 2227 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 + InstallationDate: Installed on 2015-05-07 (40 days ago) + InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) + MachineType: LENOVO 20EFCTO1WW + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-21-generic N/A + linux-backports-modules-3.19.0-21-generic N/A + linux-firmware 1.143.1 + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/26/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: GNET72WW (2.20 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20EFCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0E50510 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrGNET72WW(2.20):bd02/26/2015:svnLENOVO:pn20EFCTO1WW:pvrThinkPadW541:rvnLENOVO:rn20EFCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 20EFCTO1WW + dmi.product.version: ThinkPad W541 + dmi.sys.vendor: LENOVO ** Attachment added: AlsaInfo.txt
[Kernel-packages] [Bug 1465808] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415844/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415837/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1465808] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1465808/+attachment/4415842/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465808 Title: Hibernation fails due to a non-reachable cifs mount Status in linux package in Ubuntu: Confirmed Bug description: This happened twice during the last weeks with different kernel versions on Kubuntu 15.04 (latest kernel images released). Steps taken: 1) Mount cifs: sudo mount -t cifs -ouser=admin //x.y.z.a/video /home/packi/video/ 2) Watch movies (VLC startet using dolphin) 3) Hibernate 4) Wake-up at work (server no longer reachable) 5) Try to hibernate at work after 9 hours Output of dmesg: [224051.133206] PM: Syncing filesystems ... done. [224051.174400] PM: Preparing system for freeze sleep [224051.174567] Freezing user space processes ... [224071.207476] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [224071.207529] dolphin D 880320a0b968 0 31153 1787 0x0004 [224071.207532] 880320a0b968 8802799a93a0 00014200 880320a0bfd8 [224071.207534] 00014200 88046c2d93a0 8802799a93a0 20a0b948 [224071.207536] 8800648c79b8 8800648c79bc 8802799a93a0 [224071.207538] Call Trace: [224071.207545] [817c54e9] schedule_preempt_disabled+0x29/0x70 [224071.207548] [817c73a5] __mutex_lock_slowpath+0x95/0x100 [224071.207550] [817c7433] mutex_lock+0x23/0x40 [224071.207566] [c0b89f90] SendReceive+0x90/0x310 [cifs] [224071.207570] [c0b637f5] ? smb_init+0x45/0x60 [cifs] [224071.207575] [c0b63a54] CIFSSMBNegotiate+0x114/0x6c0 [cifs] [224071.207583] [c0b92f33] cifs_negotiate+0x43/0x60 [cifs] [224071.207589] [c0b73e9f] cifs_negotiate_protocol+0x7f/0xe0 [cifs] [224071.207593] [c0b634c2] cifs_reconnect_tcon+0xb2/0x320 [cifs] [224071.207598] [c0b637de] smb_init+0x2e/0x60 [cifs] [224071.207603] [c0b6a51a] CIFSSMBUnixQPathInfo+0x7a/0x300 [cifs] [224071.207609] [c0b82446] cifs_get_inode_info_unix+0x86/0x200 [cifs] [224071.207614] [811fd8e1] ? complete_walk+0x51/0x100 [224071.207616] [81203180] ? path_lookupat+0x60/0xc90 [224071.207619] [811d68c9] ? __kmalloc+0x1c9/0x280 [224071.207624] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207629] [c0b76156] ? build_path_from_dentry+0xb6/0x2c0 [cifs] [224071.207635] [c0b84abc] cifs_revalidate_dentry_attr+0xbc/0x200 [cifs] [224071.207641] [c0b84cb5] cifs_getattr+0x55/0x130 [cifs] [224071.207643] [811f85bc] vfs_getattr_nosec+0x2c/0x40 [224071.207644] [811f867d] vfs_getattr+0x2d/0x40 [224071.207646] [811f8754] vfs_fstatat+0x64/0xa0 [224071.207647] [811f8c22] SYSC_newlstat+0x22/0x40 [224071.207649] [811f8e6e] SyS_newlstat+0xe/0x10 [224071.207652] [817c990d] system_call_fastpath+0x16/0x1b The task in question is hanging and can't be killed by -KILL or -TERM. I also couldn't umount the mount using 'umount -f'. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: packi 2227 F pulseaudio /dev/snd/controlC0: packi 2227 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=21b20ba3-e090-4787-a27a-ccffdd11dd21 InstallationDate: Installed on 2015-05-07 (40 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20EFCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
@chiluk: yes, i did before adding libata.force=noncq to my kernel
command line.
another article on SSDs from this manufacturer has further information:
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode (err_mask=0x40) on upstream kernels = 3.12
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Utopic:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Invalid
Bug description:
[Impact]
* Users with Samsung 8** SSD drives see miscellaneous errors and
warning messages in the logs depending on the firmware level of the
drive while booting or after running trim.
[Test Case]
* Run this script, and then check logs for errors.
#!/bin/bash
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
for i in {0..10} ; do
cp -r linux linux$i
done
rm -rf linux*
echo sudo fstrim requires your password
sudo fstrim ./
[Regression Potential]
* There is very little regression potential as this change simply
prevents NCQ trim from being used on Samsung 8** drives.
[Other Info]
* Commit is upstream.
* Greatly increasing the timeout for the drives seems to relieve the timeout
errors. This may be due to trimming large numbers of sectors with single
commands. It may be prudent for future upstream to break up large trims into
multiple requests on smaller regions.
===Original Bug description ==
Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.55
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 2131 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 7 20:01:28 2014
HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
InstallationDate: Installed on 2014-06-22 (14 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-30-generic N/A
linux-backports-modules-3.13.0-30-generic N/A
linux-firmware 1.127.4
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-EM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
Just a comment, as it is right now, attempt to install trusty with hwe-v will fail due to this bug. In order to make that work, we need a released (or daily) image and specifically the related boot-initrd 20150609. That should happen in due course, the cloud-image daily builds had not succeeded since 20150609 and maas ephemeral are derived from those. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: Fix Released Status in linux source package in Trusty: Invalid Status in cloud-initramfs-tools source package in Utopic: Fix Released Status in linux source package in Utopic: New Bug description: [Impact] overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). [Test Case] Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. [Regression Potential] If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
I am manually hand-holding a build through for the latest kernel CVE. Image builds and promotion are in the works. ETA tomorrow morning. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: Fix Released Status in linux source package in Trusty: Invalid Status in cloud-initramfs-tools source package in Utopic: Fix Released Status in linux source package in Utopic: New Bug description: [Impact] overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). [Test Case] Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. [Regression Potential] If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1465364] Re: Laptop freeze with panic error
I've spent hours trying to sort this out. I've found no sane way to do a BIOS upgrade with the current utilty provided by Lenovo FreeDOS seems the best way but files name get rewritten to 8 char and I would avoid to brik the pc (maybe just an ignorant fear?) Need to spend more time on this. I experienced again the behaviour, while the pc load I get a bunch of messages and the pc freeze as usual Jun 15 19:50:35 echo kernel: [ 23.281213] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.282274] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.283335] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.284396] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.285457] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.286518] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.287579] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.288640] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.289700] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.290761] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.291822] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.292884] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.293945] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Jun 15 19:50:35 echo kernel: [ 23.295006] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] Will report soon hopefully after BIOS upgrade, thanks 2015-06-16 13:46 GMT+02:00 Christopher M. Penalver christopher.m.penal...@gmail.com: muka, as per http://support.lenovo.com/us/en/products/laptops-and- netbooks/lenovo-y-series-laptops/y50-70-notebook-lenovo an update to your computer's buggy and outdated BIOS is available (9ECN37WW). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-9ecn37ww ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: Incomplete Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS
[Kernel-packages] [Bug 1465798] Re: linux: 3.13.0-56.93 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465798 Title: linux: 3.13.0-56.93 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-56.93 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-stable-Prepare-package-start:Tuesday, 16. June 2015 17:48 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 17:48 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465798] Re: linux: 3.13.0-56.93 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed 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/1465798 Title: linux: 3.13.0-56.93 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-56.93 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-stable-Prepare-package-start:Tuesday, 16. June 2015 17:48 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 16. June 2015 17:48 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1376120] Re: Touch-pad dosen't work after installing Ubuntu 14.04 [Dual boot with Windows 8]
Can I reopen this somehow? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1376120 Title: Touch-pad dosen't work after installing Ubuntu 14.04 [Dual boot with Windows 8] Status in linux package in Ubuntu: Expired Bug description: Hi I just bought a new Acer Aspire V 15 Nitro computer with a pre-installed Windows 8. I installed Ubuntu so I can run dual-boot. Everything works fine now except my touch-pad that isn't working in Ubuntu but works fine when i boot into Windows. And when i'm in Ubuntu my USB mouse works fine aswell. cat /proc/bus/input/devices cat /proc/bus/input/devices This command does not show any SynPS/2 or anything. When i run xinput --list Under the Virtual core pointer there is only one Virtual core XTEST pointer Logitec USB-PS/2 Optical Mouse and then there is a empty slot where I think my touch-pad should be. In my system settings I can see the touch-pad and turn it on/off but nothing happens. I also installed Touch-pad indicator but nothing happens aswell. When I run cat /var/log/Xorg.0.log | grep -i synaptics [ 4.362] (**): Applying InputClass enable synaptics SHMConfig [ 4.362] (II) LoadModule: synaptics [ 4.362] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so [ 4.362] (II) Module synaptics: vendor=X.Org Foundation [ 4.362] (II) Using input driver 'synaptics' for ' ' [ 4.388] (--) synaptics:: x-axis range 0 - 1236 (res 12) [ 4.388] (--) synaptics:: y-axis range 0 - 898 (res 12) [ 4.388] (II) synaptics:: device does not report pressure, will use touch data. [ 4.388] (II) synaptics:: device does not report finger width. [ 4.388] (--) synaptics:: buttons: left double triple [ 4.388] (--) synaptics:: Vendor 0x6cb Product 0x2970 [ 4.388] (--) synaptics:: invalid pressure range. defaulting to 0 - 255 [ 4.388] (--) synaptics:: invalid finger width range. defaulting to 0 - 15 [ 4.388] (--) synaptics:: touchpad found [ 4.404] (**) synaptics:: (accel) MinSpeed is now constant deceleration 2.5 [ 4.404] (**) synaptics:: (accel) MaxSpeed is now 1.75 [ 4.404] (**) synaptics:: (accel) AccelFactor is now 0.131 [ 4.404] (--) synaptics:: touchpad found After running grep -i touchpad /var/log/Xorg.0.log the output is [ 4.362] (**): Applying InputClass evdev touchpad catchall [ 4.362] (**): Applying InputClass touchpad catchall [ 4.388] (--) synaptics:: touchpad found [ 4.404] (II) XINPUT: Adding extended input device (type: TOUCHPAD, id 12) [ 4.404] (--) synaptics:: touchpad found [ 4.404] (**): Ignoring device from InputClass touchpad ignore duplicates but when i run xinput -list there is nothing with id 12 ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB-PS/2 Optical Mouse id=11 [slave pointer (2)] ⎜ ↳ id=12 [slave pointer (2)] I'm running Ubuntu 14.04.1 LTS, Release: 14.04 From cat /proc/version_signature version.log: Ubuntu 3.13.0-36.63-generic 3.13.11.6 --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 2183 F pulseaudio /dev/snd/controlC0: eric 2183 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire VN7-591G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=b973e8ad-55d3-4d12-a642-9cbec54417db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 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 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/30/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G dmi.board.vendor: Acer
[Kernel-packages] [Bug 1454253] Re: external usb breaks suspend
Is there way to disable this useless brad-fagg bot somehow? It keeps complaining over logs which are already attached. ** Changed in: linux (Ubuntu) Status: Incomplete = New ** 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/1454253 Title: external usb breaks suspend Status in linux package in Ubuntu: Confirmed Bug description: After booting xubuntu 15.04 it's possible to suspend it the normal way BUT - only until you've plugged external usb hard drive. After that (even if it was unmounted and removed) it becomes impossible: the system goes to suspend briefly (for bout 1 second) but immediately wakes up for no apparent reason. I suspect there's some weird bug in xfce power management - is there a way to disable it alltogether and rely on systemd directly instead? --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes Package: linux (not installed) Tags: vivid Uname: Linux 4.1.0-040100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse kismet libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video wireshark _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes Package: linux (not installed) Tags: vivid Uname: Linux 4.1.0-040100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse kismet libvirtd lpadmin netdev plugdev sambashare scanner sudo tape video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452165] Re: currupted btrfs breaks both recovery and boot
** 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/1452165 Title: currupted btrfs breaks both recovery and boot Status in linux package in Ubuntu: Confirmed Bug description: If btrfs volume is corrupted (separate /home partition, not even / !!!) than not only booting ubuntu in normal AND recovery mode is impossible but even liveusb fails as well. The recovery drops to shell but it's impossible to fix btrfs - there's unkillable mount -t btrfs... process hanging and kernel regularly pukes with btrfs- transacti blocked for 120 seconds message. This is beyond horrible - the whole purpose of recovery mode is to fix errors like that, errors on partition which is not used to boot from (e. g. /home) should never ever break it. Alternatively you could add new mode to grub menu - smth like recovery which actually works or something like that. The workaround is to add 'break=premount' to grub command line and fix btrfs with 'btrfs check --repair /dev/dm-' from initramfs. Found on xubuntu 15.04 x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
