[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
to make my case once more: - Debian is more modular, what is the reason we don't follow what upstream does here? - the size of the package leads to problems as evidenced in bug 1951422 and bug 1951423 - it should be possible to carve out the larger bits into a separate package without making life hard for people who need those bits -> everybody happy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957790] Re: NVIDIA CVE-2022-{21813|21814}
It appears that this change might have introduced a regression. Please have a look at bug 1960499 and bug 1960621. +--[ https://askubuntu.com/questions/1392037/ ] | | From Ubuntu package list for nvidia-driver-*, any | nvidia driver in the major versions on the left will | be effectively upgraded to the major version on the | right: | | 495, 510 -> 510 | 460, 465, 470 -> 470 | 455 -> 460 | | This breaks compatibility if something relies on 495 | but is not compatible with 510. An example is A100 | GPUs on GCP, which can take 495 but not 510. | +-- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1957790 Title: NVIDIA CVE-2022-{21813|21814} Status in fabric-manager-450 package in Ubuntu: New Status in fabric-manager-470 package in Ubuntu: New Status in libnvidia-nscq-450 package in Ubuntu: New Status in libnvidia-nscq-470 package in Ubuntu: New Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Status in nvidia-graphics-drivers-495 package in Ubuntu: New Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: New Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-495 source package in Bionic: New Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: New Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-495 source package in Focal: New Status in fabric-manager-450 source package in Impish: Fix Released Status in fabric-manager-470 source package in Impish: Fix Released Status in libnvidia-nscq-450 source package in Impish: Fix Released Status in libnvidia-nscq-470 source package in Impish: Fix Released Status in linux-restricted-modules source package in Impish: New Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-495 source package in Impish: New Bug description: As per the subject, the update includes fixes for the following CVEs: CVE-2022-21813 CVE-2022-21814 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1957790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
The linux-firmware package in jammy grew considerably and is now almost 1GB in size. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
Juerg, thank you for picking this up and my apologies for the late response. You are of course right that there is no scientific answer or approach to this question. I'd simply look at the biggest directories with ncdu and make a decision if I thought that hardware was common when going down the list from top towards the bottom (first few entries only, of course). Let's be clear that this is not about stopping to support anything, upsetting anybody or break things or make things harder for people. Anybody who has the default of installing recommends by default will not be affected by this at all. It is about choice, for people in a scenario with limited ressources who'd like to trim some fat. Those people would need to make a conscious choice to remove the unnecessary (for them) packages. I certainly won't need support for netronome on any of my machines and would not install the package that contains it if it were optional. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515497] Re: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/br
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1515497 Title: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied Status in linux-firmware package in Ubuntu: Invalid Bug description: Daily update cannot complete for three days already because of: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-firmware 1.149 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 12 09:28:40 2015 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.149.2_all.deb ... Unpacking linux-firmware (1.149.2) over (1.149) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.149.2_all.deb (--unpack): unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied DuplicateSignature: package:linux-firmware:1.149:unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied ErrorMessage: unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied InstallationDate: Installed on 2015-09-30 (42 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: linux-firmware Title: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/brcmfmac43241b4-sdio.bin.dpkg-new' (while processing './lib/firmware/brcm/brcmfmac43241b4-sdio.bin'): Permission denied UpgradeStatus: Upgraded to wily on 2015-10-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1515497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735271] Re: Update firmware for netronome SmartNICs
** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1735271 Title: Update firmware for netronome SmartNICs Status in linux-firmware package in Ubuntu: Fix Released Bug description: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1171248] Re: package linux-firmware 1.79.2 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package amd64-micr
This was fixed in vivid linux-firmware (1.139) vivid; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 8ac569dd3ca3ca685bd47ee86c1eeb6050864db3 linux-firmware: Update AMD microcode patch firmware files linux-firmware: Add firmware files for Siano DTV devices linux-firmware: add sst audio firmware for baytrail platforms IntcSST2: Add firmware for Intel Broadwell SST DSP iwlwifi: add new firmware for 3160 / 7260 / 7265 / 7265D iwlwifi: update firmware for 3160 / 7260 / 7265 * Updated "UBUNTU: Remove amd64-microcode" during rebase to remove files introduced by "linux-firmware: Update AMD microcode patch firmware files." -- Seth Forshee Mon, 01 Dec 2014 12:45:33 -0600 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1171248 Title: package linux-firmware 1.79.2 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package amd64-microcode 1.20120910-2 Status in linux-firmware package in Ubuntu: Fix Released Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79.2 ProcVersionSignature: Ubuntu 3.2.0-41.65-generic-pae 3.2.42 Uname: Linux 3.2.0-41-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 Date: Sun Apr 21 23:49:25 2013 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package amd64-microcode 1.20120910-2 InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120908-22:17 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.2 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package amd64-microcode 1.20120910-2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1171248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1279893] Re: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x31010000_40.dfu', que está también en el paquete bt-dw17
*** This bug is a duplicate of bug 1358025 *** https://bugs.launchpad.net/bugs/1358025 ** This bug has been marked a duplicate of bug 1358025 package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1279893 Title: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I have no wifi ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: amd64 Date: Thu Feb 13 13:52:41 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgTerminalLog: Preparando para reemplazar linux-firmware 1.79 (usando .../linux-firmware_1.79.9_all.deb) ... Desempaquetando el reemplazo de linux-firmware ... dpkg: error al procesar /var/cache/apt/archives/linux-firmware_1.79.9_all.deb (--unpack): intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 DuplicateSignature: package:linux-firmware:1.79:intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 ErrorMessage: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1279893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440317] Re: Debian packaging issues
I believe this has been addressed in the meantime, please confirm. https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- firmware/tree/debian?h=jammy ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1440317 Title: Debian packaging issues Status in linux-firmware package in Ubuntu: Incomplete Bug description: Lintian reports many packaging issues. The following issues can easily be fixed with small updates inside debian/*: W: linux-firmware source: debhelper-but-no-misc-depends linux-firmware E: linux-firmware source: declares-possibly-conflicting-debhelper-compat-versions rules=5 compat=5 E: linux-firmware source: depends-on-build-essential-package-without-using-version gcc [build-depends: gcc] W: linux-firmware source: debian-rules-sets-DH_COMPAT line 12 W: linux-firmware source: ancient-standards-version 3.6.1 (current is 3.9.5) W: linux-firmware: copyright-without-copyright-notice W: linux-firmware: extra-license-file lib/firmware/GPL-3 W: linux-firmware: extra-license-file lib/firmware/carl9170fw/GPL W: linux-firmware: script-not-executable lib/firmware/configure W: linux-firmware: executable-not-elf-or-script lib/firmware/ath10k/QCA988X/hw2.0/firmware.bin W: linux-firmware: executable-not-elf-or-script lib/firmware/ath10k/QCA988X/hw2.0/board.bin W: linux-firmware: executable-not-elf-or-script lib/firmware/ath10k/QCA988X/hw2.0/otp.bin W: linux-firmware: executable-not-elf-or-script lib/firmware/qat_895xcc.bin W: linux-firmware: executable-not-elf-or-script lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq W: linux-firmware: executable-not-elf-or-script lib/firmware/brcm/brcmfmac43143-sdio.bin The remaining ones should be overridden: W: linux-firmware: windows-devel-file-in-package lib/firmware/korg/k1212.dsp << false positive W: linux-firmware: extra-license-file usr/share/doc/linux-firmware/licenses/LICENSE.* << W: linux-firmware: extra-license-file usr/share/doc/linux-firmware/licenses/LICENCE.* << practical reasons (in my opinion) I'm running Ubuntu 14.04. Fixed packaging files are attached. Additionally here's a diff: --- a/compat +++ b/compat @@ -1 +1 @@ -5 +9 --- a/control +++ b/control @@ -2,14 +2,15 @@ Section: misc Priority: optional Maintainer: Ubuntu Kernel Team -Standards-Version: 3.6.1 -Build-Depends: debhelper (>= 4.0.0), rsync, gcc +Standards-Version: 3.9.5 +Build-Depends: debhelper (>= 9), rsync Vcs-Git: git://kernel.ubuntu.com/ubuntu/linux-firmware.git Package: linux-firmware Architecture: all Multi-Arch: foreign Priority: optional +Depends: ${misc:Depends} Provides: atmel-firmware Conflicts: atmel-firmware Replaces: atmel-firmware, linux-restricted-common @@ -20,6 +21,7 @@ XC-Package-Type: udeb Architecture: all Section: debian-installer +Depends: ${misc:Depends} Description: Firmware for NICs This package contains firmware needed by some network controllers. @@ -27,5 +29,6 @@ XC-Package-Type: udeb Architecture: all Section: debian-installer +Depends: ${misc:Depends} Description: Firmware for SCSI controllers This package contains firmware needed by some scsi controllers. --- a/copyright +++ b/copyright @@ -6,6 +6,9 @@ This package is currently maintained by the Ubuntu Kernel Team +Copyright (c) 2008-2015 Ubuntu Kernel Team + + FIRMWARE: TERMS AND CONDITIONS --- /dev/null +++ b/linux-firmware.links @@ -0,0 +1,2 @@ +/usr/share/common-licenses/GPL-3 /lib/firmware/GPL-3 +/usr/share/common-licenses/GPL-2 /lib/firmware/carl9170fw/GPL --- /dev/null +++ b/linux-firmware.lintian-overrides @@ -0,0 +1,8 @@ +# False positive. This is actually a firmware binary. +linux-firmware: windows-devel-file-in-package lib/firmware/korg/k1212.dsp + +# This is probably better then creating an unreadable wall of text +# in a single file. +linux-firmware: extra-license-file usr/share/doc/linux-firmware/licenses/LICENCE.* +linux-firmware: extra-license-file usr/share/doc/linux-firmware/licenses/LICENSE.* + --- a/rules +++ b/rules @@ -8,38 +8,40 @@ # # -# This is the debhelper compatability version to use. -export DH_COMPAT=5 -export LC_ALL=C -export SHELL=/bin/bash -e - # # A list of the directories created by makefiles under fw_source. # GENERATED_DIRS=ea -binary-arch: - -build-arch: - $(MAKE) -C fw_source update - -build-indep: - firm_dir = $(CURDIR)/debian/linux-firmware/lib/firmware doc_dir = $(CURDIR)/debian/linux-firmware/usr/share/doc/linux-firmware license_dir = $(doc_dir)/licenses nic_firm_dir = $(CURDIR)/debian/nic-firmware/lib/firmware scsi_firm_dir = $(CURDIR)/debian/scsi-firmware/
[Kernel-packages] [Bug 1467456] Re: package linux-firmware 1.79.11 failed to install/upgrade: trying to overwrite `/lib/firmware/rtlwifi/rtl8723befw.bin', which is the diverted version of `/lib/firmwa
My apologies for the less-than-ideal experience. This isn't something that Ubuntu can fix, but I believe it would be up to one of the OEM groups to add breaks/replaces/conflict-information to the oem-wireless- skyray-rtl8723be-1265442-dkms package Reassigning (wild guess) ** Package changed: linux-firmware (Ubuntu) => oem-sru-workflow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1467456 Title: package linux-firmware 1.79.11 failed to install/upgrade: trying to overwrite `/lib/firmware/rtlwifi/rtl8723befw.bin', which is the diverted version of `/lib/firmware/rtlwifi/rtl8723befw.bin.diverted' (package: oem-wireless-skyray-rtl8723be-1265442-dkms) Status in OEM SRU Workflow: Confirmed Bug description: This is a borked Update Manager upgrade from Ubuntu 12.04 LTS to 14.04.2 LTS on an HP 455 G2 that came with factory-installed Ubuntu 12.04, we did not expect it to be seamless, but it reports a wide variety of problems that may revolve around linux-firmware install failure. It failed to reboot after the upgrade announced its completion, locking up after ~27 seconds and reporting: kernel panic - not syncing, fatal exception in interrupt. The upgrade had been messy and complained about both memtest86+ and linux-firmware package problems, but offered no remedies that were visible. It was hard to capture detailed information on this due to the (fixed) tiny terminal window on the upgrade box. We have a lot of screenshots but they don't help much. Rebooting in recovery mode and doing fsck and then dpkg options reported a clean file system and the need to upgrade memtest86+ and linux-firmware. These dpkg upgrades would fail with a slew of information that was resistant to capture. By experimentation, it was found possible to boot using the older kernel from 12.04 in the GRUB menu. This reported itself as Ubuntu 14.04 whilst booting and it was possible to log in successfully, but 1) No touchpad response and 2) doing a successful apt-get update followed by apt-get dist-upgrade resulted in a long list of complaints relating to an inability to successfully upgrade the packages: memtest86+ and linux-firmware ...which both downloaded satisfactorily but generated a slew of installation reportage to the effect that all was not well. Re-running the dist-upgrade just restarts the download/install/fail cycle. Also getting complaints in little popups (whose contents cannot be copied and pasted) about kerneloops, apport-gtk, and you-name it. Unfortunately, this is the third time this brand new factory-installed system has fallen over in a couple of pretty busy days. Normally we would not be upgrading like this, but the regular update process using Update Manager in 12.04 also failed - once fully updated the system would spit out complaints that HWE was not up to date, hinting at possible dark consequences. When the option to fix this was chosen in the Update Manager it too managed to bork the system in a remarkably similar way to the present situation. No touchpad, and all kinds of nasties being reported intermittently. Couldn't believe that a factory-installed Ubuntu would fail this way, so we did the Factory Restore and tried again. Same thing, pretty much, hence the upgrade to 14.04.2. Can't update, can't upgrade. Help, please! Ben PS Apologies for the paucity of detail - Unity is a hard system to operate without touchpad on a laptop, and right now I lack a mouse to try. Will try to dig one out of the attic, see if that works. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.79.11 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: fglrx AptOrdering: memtest86+: Install linux-firmware: Install memtest86+: Configure linux-firmware: Configure Architecture: amd64 Date: Mon Jun 22 10:13:37 2015 Dependencies: ErrorMessage: trying to overwrite `/lib/firmware/rtlwifi/rtl8723befw.bin', which is the diverted version of `/lib/firmware/rtlwifi/rtl8723befw.bin.diverted' (package: oem-wireless-skyray-rtl8723be-1265442-dkms) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20140918-03:14 LiveMediaBuild: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20140918-03:14 PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.11 failed to install/upgrade: trying to overwrite `/lib/firmware/rtlwifi/rtl8723befw.bin', which is the diverted version of `/lib/firmware/rtlwifi/rtl8723befw.bin.diverted' (package: oem-wireless-skyray-rtl8723be-1265442-dkms) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-sru-workflow/+bug/1467456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1268625] Re: package linux-firmware 1.79.7 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x31010000_40.dfu', que está también en el paquete bt-dw
*** This bug is a duplicate of bug 1358025 *** https://bugs.launchpad.net/bugs/1358025 ** This bug has been marked a duplicate of bug 1358025 package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1268625 Title: package linux-firmware 1.79.7 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 Status in linux-firmware package in Ubuntu: New Bug description: No tengo idea de lo que pasa ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79.7 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Jan 13 08:58:14 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DuplicateSignature: package:linux-firmware:1.79.7:intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 ErrorMessage: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.7 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1268625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493829] Re: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x31010000_40.dfu', que também está no pacote bt-dw1705-f
*** This bug is a duplicate of bug 1358025 *** https://bugs.launchpad.net/bugs/1358025 ** Package changed: linux-firmware (Ubuntu) => dell ** Changed in: dell Status: Invalid => New ** This bug has been marked a duplicate of bug 1358025 package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1493829 Title: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 Status in Dell Ubuntu Project: New Bug description: I was upgrading. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.79.1 ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Sep 8 22:57:31 2015 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 ErrorMessage: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 UpgradeStatus: Upgraded to trusty on 2015-09-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/1493829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270915] Re: package linux-firmware 1.79 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x31010000_40.dfu', which is also in package bt-dw1705-firmware
*** This bug is a duplicate of bug 1358025 *** https://bugs.launchpad.net/bugs/1358025 ** This bug has been marked a duplicate of bug 1358025 package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1270915 Title: package linux-firmware 1.79 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.1 Status in linux-firmware package in Ubuntu: New Bug description: it constantly detects a system problem. I am a new ubuntu user and when I have tried to update and upgrade via terminal it led me here. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: amd64 Date: Mon Jan 20 19:28:18 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgTerminalLog: Preparing to replace linux-firmware 1.79 (using .../linux-firmware_1.79.9_all.deb) ... Unpacking replacement linux-firmware ... dpkg: error processing /var/cache/apt/archives/linux-firmware_1.79.9_all.deb (--unpack): trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.1 ErrorMessage: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.1 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1270915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358025] Re: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x31010000_40.dfu', which is also in package bt-dw1705-firmwa
reassign to the dell project, they need to specify a Replaces- relationship for their bt-dw1705-firmware package with the official linux-firmware package from Ubuntu. ** Package changed: linux-firmware (Ubuntu) => dell -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1358025 Title: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 Status in Dell Ubuntu Project: Confirmed Bug description: I don't know what do 'cause it's caused when I'm trying to install a automatica atualization. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79.1 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: amd64 Date: Sun Aug 17 17:50:43 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DpkgTerminalLog: Preparing to replace linux-firmware 1.79.1 (using .../linux-firmware_1.79.16_all.deb) ... Unpacking replacement linux-firmware ... dpkg: error processing /var/cache/apt/archives/linux-firmware_1.79.16_all.deb (--unpack): trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 ErrorMessage: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/1358025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1279893] Re: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x31010000_40.dfu', que está también en el paquete bt-dw17
bt-dw1705-firmware is a third-party package and apparently it conflicts with the official Ubuntu packages It is not a good idea to install random software off the internet. In case you insist to do, you are on your own. Marking ticket as invalid. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1279893 Title: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I have no wifi ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: amd64 Date: Thu Feb 13 13:52:41 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgTerminalLog: Preparando para reemplazar linux-firmware 1.79 (usando .../linux-firmware_1.79.9_all.deb) ... Desempaquetando el reemplazo de linux-firmware ... dpkg: error al procesar /var/cache/apt/archives/linux-firmware_1.79.9_all.deb (--unpack): intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 DuplicateSignature: package:linux-firmware:1.79:intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 ErrorMessage: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79 failed to install/upgrade: intentando sobreescribir `/lib/firmware/ar3k/ramps_0x3101_40.dfu', que está también en el paquete bt-dw1705-firmware 0.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1279893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493829] Re: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x31010000_40.dfu', que também está no pacote bt-dw1705-f
bt-dw1705-firmware is a third-party package and apparently it conflicts with the official Ubuntu packages It is not a good idea to install random software off the internet. In case you insist to do, you are on your own. Marking ticket as invalid. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1493829 Title: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 Status in linux-firmware package in Ubuntu: Invalid Bug description: I was upgrading. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.79.1 ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Sep 8 22:57:31 2015 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 ErrorMessage: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.1 failed to install/upgrade: a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 UpgradeStatus: Upgraded to trusty on 2015-09-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1493829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] [NEW] split some large, lesser-used firmware files into -extra package
Public bug reported: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488758] Re: GPU crash on NUC with i915
upstream is closed WFM time to close here, 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/1488758 Title: GPU crash on NUC with i915 Status in linux package in Ubuntu: Triaged Bug description: Setup: Intel NUC, i915 graphics, two monitors, one connected with miniHDMI->HDMI cable, second with miniDP->HDMI cable. Screen goes black, flickers back on, goes black again. Only resolution is to ssh into the machine and reboot. Before rebooting, I got lots of these (about 106k lines) in syslog: kernel: [404964.521324] [drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.[drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. ...then, kernel: [406333.381029] [drm] stuck on render ring kernel: [406333.381945] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [406333.381947] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. kernel: [406333.381947] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel kernel: [406333.381948] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. kernel: [406333.381949] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. kernel: [406333.381951] [drm] GPU crash dump saved to /sys/class/drm/card0/error kernel: [406333.389006] drm/i915: Resetting chip after gpu hang kernel: [406339.379515] [drm] stuck on render ring kernel: [406339.380430] [drm] GPU HANG: ecode 8:0:0x85db, in webapp-containe [14994], reason: Ring hung, action: reset kernel: [406339.380583] drm/i915: Resetting chip after gpu hang kernel: [406417.336790] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [406417.343850] drm/i915: Resetting chip after gpu hang kernel: [407944.976072] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [407944.983106] drm/i915: Resetting chip after gpu hang kernel: [409258.618636] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [409258.625733] drm/i915: Resetting chip after gpu hang kernel: [409264.604180] [drm] stuck on render ring kernel: [409264.605059] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], reason: Ring hung, action: reset kernel: [409264.605153] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! kernel: [409264.612163] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 12:31:15 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872398] Re: [TGL] turbostat support
I'm sorry, but I dont' understand this bug report. Maybe you can explain what you did, what you expected to happen and what happened instead. FWIW, turbostat exists just fine in focal. $ dpkg -S /usr/bin/turbostat linux-tools-common: /usr/bin/turbostat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872398 Title: [TGL] turbostat support Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Description: Turbostat is a Linux tool to observe proper operation of Intel(R) Turbo Boost Technology. Turbostat displays actual processor frequency and idle power state on modern x86 processors supporting invariant TSC, plus APERF and MPERF MSRs. Upstream in Linux-5.6 author Chen Yu 2020-01-14 12:04:55 +0800 committer Len Brown 2020-03-20 00:32:27 -0400 commit 4bf7132a0ace398af8cec6485ee4c6db5ea8 (patch) tree c2e7dc88595f9f01bb1d1d36bec46fdac7e30147 /tools/power/x86/turbostat/turbostat.c parent d8d005ba6afa502ca37ced5782f672c4d2fc1515 (diff) download linux-4bf7132a0ace398af8cec6485ee4c6db5ea8.tar.gz tools/power turbostat: Support Tiger Lake From a turbostat point of view, Tiger Lake looks like Ice Lake. Signed-off-by: Chen Yu Signed-off-by: Len Brown Target Release: 20.10 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1872398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
Here is my status. The hidd binary seems to be gone. The bluetooth-wizard binary worked fine for me in bionic just now. -- 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/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 884549] Re: old linux-backports-* packages cannot be purged when corresponding linux-image is no longer available
lucid is EOL closing as obsolete ** Changed in: linux (Ubuntu) Status: Confirmed => 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/884549 Title: old linux-backports-* packages cannot be purged when corresponding linux-image is no longer available Status in linux package in Ubuntu: Invalid Bug description: it's impossible to purge some older linux-backports-* packages on my lucid system $ aptitude search ~c|grep linux c linux-backports-modules-nouveau - Ubuntu supplied Linux modules for version c linux-backports-modules-wireles - compat-wireless Linux modules for version $ sudo aptitude purge linux-backports-modules-wireless-2.6.32-19-generic Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done The following packages will be REMOVED: linux-backports-modules-wireless-2.6.32-19-generic{p} 0 packages upgraded, 0 newly installed, 1 to remove and 2 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Do you want to continue? [Y/n/?] Writing extended state information... Done (Reading database ... 345225 files and directories currently installed.) Removing linux-backports-modules-wireless-2.6.32-19-generic ... Purging configuration files for linux-backports-modules-wireless-2.6.32-19-generic ... FATAL: Could not open '/boot/System.map-2.6.32-19-generic': No such file or directory update-initramfs: Generating /boot/initrd.img-2.6.32-19-generic Cannot find /lib/modules/2.6.32-19-generic update-initramfs: failed for /boot/initrd.img-2.6.32-19-generic dpkg: error processing linux-backports-modules-wireless-2.6.32-19-generic (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-backports-modules-wireless-2.6.32-19-generic E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1529917] Re: mainline kernel fails to install in trusty
Trusty is no longer supported. Closing as obsolete ** Changed in: linux (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1529917 Title: mainline kernel fails to install in trusty Status in linux package in Ubuntu: Opinion Bug description: Today's mainline kernel fails to install in Ubuntu Trusty. $ sudo dpkg -i linux-headers-4.4.0-999-generic_4.4.0-999.201512282100_i386.deb linux-headers-4.4.0-999_4.4.0-999.201512282100_all.deb linux-image-4.4.0-999-generic_4.4.0-999.201512282100_i386.deb [...] update-initramfs: deferring update (hook will be called later) Failed to symbolic-link boot/initrd.img-4.4.0-999-generic to initrd.img:File exists at /var/lib/dpkg/info/linux-image-4.4.0-999-generic.postinst line 629. dpkg: error processing package linux-image-4.4.0-999-generic (--install): subprocess installed post-installation script returned error exit status 17 Setting up linux-headers-4.4.0-999-generic (4.4.0-999.201512282100) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.4.0-999-generic /boot/vmlinuz-4.4.0-999-generic ERROR (dkms apport): kernel package linux-headers-4.4.0-999-generic is not supported Error! Bad return status for module build on kernel: 4.4.0-999-generic (i686) Consult /var/lib/dkms/tp-smapi/0.41/build/make.log for more information. Errors were encountered while processing: linux-image-4.4.0-999-generic $ cat /var/lib/dkms/tp-smapi/0.41/build/make.log DKMS make.log for tp-smapi-0.41 for kernel 4.4.0-999-generic (i686) Wed Dec 30 01:45:40 PHT 2015 make: Entering directory `/usr/src/linux-headers-4.4.0-999-generic' Makefile:660: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler LD /var/lib/dkms/tp-smapi/0.41/build/built-in.o CC [M] /var/lib/dkms/tp-smapi/0.41/build/thinkpad_ec.o gcc: error: unrecognized command line option ‘-fstack-protector-strong’ make[1]: *** [/var/lib/dkms/tp-smapi/0.41/build/thinkpad_ec.o] Error 1 make: *** [_module_/var/lib/dkms/tp-smapi/0.41/build] Error 2 make: Leaving directory `/usr/src/linux-headers-4.4.0-999-generic' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 513921] Re: [ASUS 1005p] keys for adjusting display brightness don't work as expected
This hardware has long since bitten the dust over here. Closing ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/513921 Title: [ASUS 1005p] keys for adjusting display brightness don't work as expected Status in Linux: Expired Status in linux package in Ubuntu: Invalid Bug description: While trying out yesterday's lucid UNR live CD, I found out that the keys for adjusting display brightness (Fn+F5, Fn+F6) don't work as expected on the ASUS 1005p and 1001p pinetrail netbooks. While generally pushing Fn+F6 will increase the screen brightness, it can happen that it will go down (!) or even shut off the backlight when pushing that key combo. I always think maximum screen brightness is never reached. I only got this computer a few days ago and cannot tell whether this is a regression from karmic or not. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/513921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 641027] Re: Screen flickers after 2.6.32-24.42 update (drm/i915 changes)
closing as obsolete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/641027 Title: Screen flickers after 2.6.32-24.42 update (drm/i915 changes) Status in linux package in Ubuntu: Invalid Bug description: The display flickers several times per minute after the 2.6.32-24.42 kernel update. This is extremely tirying for the user. linux (2.6.32-24.42) lucid-proposed; urgency=low [ Upstream Kernel Changes ] * (pre-stable) drm/i915: add PANEL_UNLOCK_REGS definition - LP: #561802, #578673 * (pre-stable) drm/i915: make sure eDP panel is turned on - LP: #578673 * (pre-stable) drm/i915: make sure we shut off the panel in eDP configs - LP: #578673 These package changes correspond to our hardware, an Intel graphics chipset. 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) Subsystem: Dell Device 0410 Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 60b0 [size=8] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCIe advanced features Kernel driver in use: i915 Kernel modules: i915 I'll try to test with the latest mainline kernel as soon as I get time. Booting on 2.6.32-23 (still installed) instead makes the problem go away. Cheers, Michael. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.42 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 1645 F xfce4-mixer-plu maria 1653 F pulseaudio maria 1691 F xfce4-volumed CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf546 irq 22' Mixer name : 'Intel G45 DEVIBX' Components : 'HDA:111d7605,10280410,00100104 HDA:80862804,80860101,0010' Controls : 22 Simple ctrls : 13 Date: Fri Sep 17 06:25:56 2010 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4a94078b-e73f-4688-a8ab-849aef1171c9 InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429) MachineType: Dell Inc. Latitude E4310 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=0174c8f4-9dd1-4825-be0d-497de72aba62 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 SourcePackage: linux dmi.bios.date: 05/28/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd05/28/2010:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1320851] Re: WARNING: CPU: 0 PID: 74 at drivers/gpu/drm/i915/intel_pm.c:5817 i915_request_power_well+0x77/0x80 [i915]()
Is this still an issue? ** 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/1320851 Title: WARNING: CPU: 0 PID: 74 at drivers/gpu/drm/i915/intel_pm.c:5817 i915_request_power_well+0x77/0x80 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot my haswell machine in 14.04 unless I use 'recovery' mode. I get the following backtrace: [ 10.770854] WARNING: CPU: 0 PID: 74 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_pm.c:5817 i915_request_power_well+0x77/0x80 [i915]() [ 10.772266] Modules linked in: arc4 i915 iwldvm intel_ips mac80211 snd_hda_codec_realtek microread_mei microread mei_phy crc_ccitt x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel hci drm_kms_helper kvm_intel nfc drm kvm snd_hda_codec iwlwifi snd_hwdep snd_pcm snd_page_alloc snd_timer crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel snd psmouse i2c_algo_bit aes_x86_64 lrw mei_me gf128mul glue_helper serio_raw mac_hid soundcore cfg80211 ablk_helper lpc_ich cryptd mei video hid_generic usbhid hid e1000e ahci ptp libahci pata_acpi pps_core [ 10.776993] CPU: 0 PID: 74 Comm: kworker/0:1 Not tainted 3.13.0-24-generic #46-Ubuntu [ 10.99] Hardware name: [ 10.779442] Workqueue: events azx_probe_work [snd_hda_intel] [ 10.780273] 0009 880242365d50 81715a64 [ 10.781118] 880242365d88 810676bd [ 10.781962] 8802420ac000 880241a1f800 880242365d98 [ 10.782826] Call Trace: [ 10.783662] [] dump_stack+0x45/0x56 [ 10.784512] [] warn_slowpath_common+0x7d/0xa0 [ 10.784836] cfg80211: World regulatory domain updated: [ 10.784836] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 10.784838] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.784839] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.784840] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.784840] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.784841] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.791446] [] warn_slowpath_null+0x1a/0x20 [ 10.792296] [] i915_request_power_well+0x77/0x80 [i915] [ 10.793134] [] hda_display_power+0x32/0x40 [snd_hda_intel] [ 10.793970] [] azx_probe_continue+0x41/0x960 [snd_hda_intel] [ 10.794795] [] azx_probe_work+0x15/0x20 [snd_hda_intel] [ 10.795628] [] process_one_work+0x182/0x450 [ 10.796467] [] worker_thread+0x121/0x410 [ 10.797297] [] ? rescuer_thread+0x3e0/0x3e0 [ 10.798117] [] kthread+0xd2/0xf0 [ 10.798920] [] ? kthread_create_on_node+0x1d0/0x1d0 [ 10.799718] [] ret_from_fork+0x7c/0xb0 [ 10.800508] [] ? kthread_create_on_node+0x1d0/0x1d0 WORKAROUND: Use kernel boot parameter: nomodeset Related issues: http://wyldeplayground.net/kernel-problem-in-14-04-on-hold/ https://bugzilla.redhat.com/show_bug.cgi?id=1044764 https://bugzilla.kernel.org/show_bug.cgi?id=73971 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Mon May 19 07:12:25 2014 HibernationDevice: RESUME=UUID=6618bc54-5603-45c0-afd3-090398b48f59 InstallationDate: Installed on 2014-05-18 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Intel Corporation Shark Bay Client platform ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKe
[Kernel-packages] [Bug 1331149] Re: Bluetooth: hci0 failed to open Intel firmware file
How about bionic and later? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331149 Title: Bluetooth: hci0 failed to open Intel firmware file Status in linux package in Ubuntu: Confirmed Bug description: Loading the Bluetooth firmware doesn't always work after resume. There are examples of both success and failure in the dmesg. $ ls -l /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq -rw-r--r-- 1 root root 17917 jan 30 14:13 /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [44897.486087] Bluetooth: hci0: read Intel version: 370710018002030d00 [44897.486095] [ cut here ] [44897.486102] WARNING: CPU: 0 PID: 381 at /build/buildd/linux-3.13.0/drivers/base/firmware_class.c:1089 _request_firmware+0x5d9/0xb10() [44897.473636] Restarting tasks ... [44897.486104] Modules linked in: ctr ccm arc4 iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_realtek kvm_intel bnep rfcomm snd_hda_intel kvm snd_hda_codec snd_hwdep joydev snd_pcm serio_raw snd_page_alloc iwlwifi snd_seq_midi thinkpad_acpi snd_seq_midi_event nvram lpc_ich snd_rawmidi cfg80211 btusb snd_seq snd_seq_device rtsx_pci_ms snd_timer intel_smartconnect mac_hid memstick bluetooth snd soundcore parport_pc ppdev nls_iso8859_1 lp parport dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw i915 gf128mul glue_helper ablk_helper cryptd psmouse i2c_algo_bit e1000e drm_kms_helper ahci drm libahci ptp rtsx_pci pps_core wmi video [44897.486160] CPU: 0 PID: 381 Comm: kworker/u17:1 Not tainted 3.13.0-29-generic #53-Ubuntu [44897.486162] Hardware name: LENOVO 20AM009DMS/20AM009DMS, BIOS GIET74WW (2.24 ) 05/13/2014 [44897.486176] Workqueue: hci0 hci_power_on [bluetooth] [44897.486179] 0009 880232315bc8 8171a214 [44897.486183] 880232315c00 810676bd 880232315d28 880231408b80 [44897.486187] 880168b1ee40 fff5 880232315d20 880232315c10 [44897.486190] Call Trace: [44897.486197] [] dump_stack+0x45/0x56 [44897.486201] [] warn_slowpath_common+0x7d/0xa0 [44897.486204] [] warn_slowpath_null+0x1a/0x20 [44897.486208] [] _request_firmware+0x5d9/0xb10 [44897.486212] [] request_firmware+0x34/0x50 [44897.486217] [] btusb_setup_intel+0x1b4/0x7f0 [btusb] [44897.486229] [] hci_dev_do_open+0x275/0x760 [bluetooth] [44897.486239] [] hci_power_on+0x40/0x180 [bluetooth] [44897.486243] [] process_one_work+0x182/0x450 [44897.486246] [] worker_thread+0x121/0x410 [44897.486250] [] ? rescuer_thread+0x3e0/0x3e0 [44897.486253] [] kthread+0xd2/0xf0 [44897.486256] [] ? kthread_create_on_node+0x1d0/0x1d0 [44897.486260] [] ret_from_fork+0x7c/0xb0 [44897.486263] [] ? kthread_create_on_node+0x1d0/0x1d0 [44897.486266] ---[ end trace dc2cb2f3b632ce87 ]--- [44897.486270] bluetooth hci0: firmware: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq will not be loaded [44897.486274] Bluetooth: hci0 failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq(-11) [44897.486277] [ cut here ] [44897.486280] WARNING: CPU: 0 PID: 381 at /build/buildd/linux-3.13.0/drivers/base/firmware_class.c:1089 _request_firmware+0x5d9/0xb10() [44897.486282] Modules linked in: ctr ccm arc4 iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_realtek kvm_intel bnep rfcomm snd_hda_intel kvm snd_hda_codec snd_hwdep joydev snd_pcm serio_raw snd_page_alloc iwlwifi snd_seq_midi thinkpad_acpi snd_seq_midi_event nvram lpc_ich snd_rawmidi cfg80211 btusb snd_seq snd_seq_device rtsx_pci_ms snd_timer intel_smartconnect mac_hid memstick bluetooth snd soundcore parport_pc ppdev nls_iso8859_1 lp parport dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw i915 gf128mul glue_helper ablk_helper cryptd psmouse i2c_algo_bit e1000e drm_kms_helper ahci drm libahci ptp rtsx_pci pps_core wmi video [44897.486322] CPU: 0 PID: 381 Comm: kworker/u17:1 Tainted: GW 3.13.0-29-generic #53-Ubuntu [44897.486323] Hardware name: LENOVO 20AM009DMS/20AM009DMS, BIOS GIET74WW (2.24 ) 05/13/2014 [44897.486337] Workqueue: hci0 hci_power_on [bluetooth] [44897.486339] 0009 880232315bc8 8171a214 [44897.486343] 880232315c00 810676bd 880232315d28 880231408b80 [44897.486346] 880168b1ee40 fff5 880232315d20 880232315c10 [44897.486350] Call Trace: [44897.486354] [] dump_stack+0x45/0x56 [44897.486358] [] warn_slowpath_common+0x7d/0xa0 [44897.486361] [] warn_slowpath_null+0x1a/0x20 [44897.486365] [] _request_firmware+0x5d9/0xb10 [44897.486368] [] request_firmware+0x
[Kernel-packages] [Bug 568655] Re: [Sony Corporation VGN-NS130FE] hibernate/resume failure
old bug marked as fixed upstream ** Changed in: linux (Ubuntu) Status: Incomplete => 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/568655 Title: [Sony Corporation VGN-NS130FE] hibernate/resume failure Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: ~$ dpkg -l | grep linux-image ii linux-image-2.6.32-21-generic 2.6.32-21.32 Linux kernel image for version 2.6.32 on x86 ii linux-image-2.6.34-rc5-20100421 2.6.34-rc5-20100421-10.00.Custom [ 382.500096] [ cut here ] [ 382.500103] WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90() [ 382.500105] Hardware name: VGN-NS130FE [ 382.500112] Modules linked in: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs aes_i586 aes_generic joydev snd_hda_codec_realtek arc4 fbcon tileblit font bitblit softcursor vga16fb vgastate snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device ath9k snd mac80211 ath i915 drm_kms_helper soundcore sdhci_pci sony_laptop sdhci cfg80211 led_class psmouse serio_raw drm i2c_algo_bit video output uvcvideo snd_page_alloc videodev v4l1_compat intel_agp agpgart lp parport usbhid hid ohci1394 ieee1394 ahci sky2 [ 382.500179] Pid: 748, comm: phy0 Not tainted 2.6.32-21-generic #32-Ubuntu [ 382.500182] Call Trace: [ 382.500187] [] warn_slowpath_common+0x72/0xa0 [ 382.500190] [] ? local_bh_enable_ip+0x61/0x90 [ 382.500193] [] ? local_bh_enable_ip+0x61/0x90 [ 382.500197] [] warn_slowpath_null+0x1a/0x20 [ 382.500200] [] local_bh_enable_ip+0x61/0x90 [ 382.500204] [] _spin_unlock_bh+0x16/0x20 [ 382.500215] [] ath_tx_node_cleanup+0x14f/0x170 [ath9k] [ 382.500223] [] ath9k_sta_notify+0x4e/0xb0 [ath9k] [ 382.500238] [] __sta_info_unlink+0x127/0x1b0 [mac80211] [ 382.500246] [] ? ath9k_sta_notify+0x0/0xb0 [ath9k] [ 382.500254] [] sta_info_unlink+0x33/0x50 [mac80211] [ 382.500264] [] ieee80211_set_disassoc+0x17a/0x1d0 [mac80211] [ 382.500273] [] ieee80211_sta_work+0x427/0x460 [mac80211] [ 382.500278] [] ? finish_task_switch+0x43/0xc0 [ 382.500282] [] run_workqueue+0x8e/0x150 [ 382.500290] [] ? ieee80211_sta_work+0x0/0x460 [mac80211] [ 382.500294] [] worker_thread+0x84/0xe0 [ 382.500298] [] ? autoremove_wake_function+0x0/0x50 [ 382.500301] [] ? worker_thread+0x0/0xe0 [ 382.500304] [] kthread+0x74/0x80 [ 382.500307] [] ? kthread+0x0/0x80 [ 382.500311] [] kernel_thread_helper+0x7/0x10 [ 382.500313] ---[ end trace ae9cfb68556162e7 ]--- ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-21-generic 2.6.32-21.32 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1384 F pulseaudio CRDA: Error: [Errno 2] No existe el fichero ó directorio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd420 irq 22' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,104d3700,00100302 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 11 Date: Thu Apr 22 16:25:31 2010 Frequency: Once a day. HibernationDevice: RESUME=UUID=61e37874-09f4-4e5f-85d9-2f588d2f19d6 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1) MachineType: Sony Corporation VGN-NS130FE ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=7c374b03-1455-4547-80c4-d0b762953c15 ro quiet splash ProcEnviron: LANG=es_CL.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34 SourcePackage: linux dmi.bios.date: 08/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0200Y3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0200Y3:bd08/27/2009:svnSonyCorporation:pnVGN-NS130FE:pvr
[Kernel-packages] [Bug 594129] Re: 8086:27a2 X crashs on Intel 945 video (GPU hung: render error detected/task i915: blocked for more than 120 seconds)
closing as no-response, obsolete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/594129 Title: 8086:27a2 X crashs on Intel 945 video (GPU hung: render error detected/task i915: blocked for more than 120 seconds) Status in xf86-video-intel: New Status in linux package in Ubuntu: Invalid Bug description: X was hanging/crashing. SysRq did work. I'm running a DELL Inspiron 6400 with Intel graphics and had never problems with hanging/crashing X since using Ubuntu. Standby/Resume works. It's getting slowly annoying - things that worked just stop working in newer releases (sorry for the rant but...) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-22-generic 2.6.32-22.36 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peer 2218 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 12 Simple ctrls : 7 CheckboxSubmission: 27774017cc2538f163c801a2a9afdb5a CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Mon Jun 14 15:19:01 2010 Frequency: This has only happened once. HibernationDevice: RESUME=UUID=018bdd59-a71d-4c23-98c3-21871c5d7d6d MachineType: Dell Inc. MM061 ProcCmdLine: root=UUID=50ce24c3-8349-4b27-8c69-27211736429a ro quiet splash ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34 RfKill: 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux WpaSupplicantLog: dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KD882 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. Also see attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/594129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834222] [NEW] [i915] flickering after waking up from screensaver (fixed in mainline)
Public bug reported: I have an X220 connected to a dock and via HDMI to an external monitor running bionic. I noticed that anytime that I came back to the machine from a screensaver both displays would flicker hard in certain areas of the screen. The "fix" is to click the affected areas and then the flickering goes away. I believe the X230 I also have is not affected in the same dock but my memory might be wrong here. Most importantly, I was able to verify that this problem is not present in mainline kernel "5.2.0-999-generic #201905312204 SMP Sat Jun 1 02:07:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux" $ sudo lshw -c display *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:34 memory:f000-f03f memory:e000-efff ioport:5000(size=64) memory:c-d ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic kernel-fixed-upstream ** Tags added: kernel-fixed-upstream ** 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/1834222 Title: [i915] flickering after waking up from screensaver (fixed in mainline) Status in linux package in Ubuntu: Confirmed Bug description: I have an X220 connected to a dock and via HDMI to an external monitor running bionic. I noticed that anytime that I came back to the machine from a screensaver both displays would flicker hard in certain areas of the screen. The "fix" is to click the affected areas and then the flickering goes away. I believe the X230 I also have is not affected in the same dock but my memory might be wrong here. Most importantly, I was able to verify that this problem is not present in mainline kernel "5.2.0-999-generic #201905312204 SMP Sat Jun 1 02:07:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux" $ sudo lshw -c display *-display description: VGA compatible controller product: 2nd Generation Core Processor Family Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:34 memory:f000-f03f memory:e000-efff ioport:5000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1023174] Re: "ip -6 addr flush" flushes much more than just the addresses
still an issue? ** Changed in: linux (Ubuntu) Status: Triaged => 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/1023174 Title: "ip -6 addr flush" flushes much more than just the addresses Status in linux package in Ubuntu: Incomplete Bug description: root@testv6-tester:~# ls /proc/sys/net/ipv*/conf/ /proc/sys/net/ipv4/conf/: all default eth0 lo sit0 /proc/sys/net/ipv6/conf/: all default eth0 lo sit0 root@testv6-tester:~# ip addr flush dev eth0 root@testv6-tester:~# ls /proc/sys/net/ipv*/conf/ /proc/sys/net/ipv4/conf/: all default eth0 lo sit0 /proc/sys/net/ipv6/conf/: all default lo sit0 This results in no IPv6 connectivity on the interface and no obvious way to get it back to working condition other than destroying and recreating the interface (usually by rebooting). I reproduced this on the stable 12.04 kernel (3.2.0-26-generic) as well as 12.10 (3.5.0-3-generic). This is currently breaking ipv6 connectivity for some dual-stack setups in debian-installer though only for Ubuntu 12.10 (because the flush call was ipv4-specific in 12.04). I'll workaround the issue in d-i, but this bug should really be looked into. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1023174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 698120] Re: [gm45] Dual head corruption on 2.6.37 lucid backport
closing as obsolete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/698120 Title: [gm45] Dual head corruption on 2.6.37 lucid backport Status in linux package in Ubuntu: Invalid Bug description: Lenovo X301 laptop, 4G ram, Intel(R) Core(TM)2 Duo CPU U9400 @ 1.40GHz. Intel GM45 Express graphic chipset, Kubuntu 10.4.1 LTS Lucid 32 bits, Xorg driver "intel" # uname -a Linux wall-e 2.6.37-12-generic-pae #26~lucid1-Ubuntu SMP Wed Jan 5 22:54:38 UTC 2011 i686 GNU/Linux # version.log Ubuntu 2.6.37-12.26~lucid1-generic-pae 2.6.37 Symptoms: When starting X with the external screen attached to the VGA connector, I can't type anything in the login/password at the kdm greeter dialog. I can switch to VT1. Then I can kill kdm. Restarting kdm gives fatal error with technical messages about gem. Starting without the external screen is okay. If I plug the external screen and start using it (xrandr), the cursor becomes corrupted when it is inside a konsole window on the laptop screen, but gets back to normal outside this window. Then X freezes after a while. Working single-headed without plugging the external screen at all is fine so far. Previous versions 2.6.35 and 2.6.32 did not do this Previous version 2.6.37-11 already had the problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image (not installed) Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.37-12.26~lucid1-generic-pae 2.6.37 Uname: Linux 2.6.37-12-generic-pae i686 Architecture: i386 Date: Thu Jan 6 14:52:34 2011 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Lenovo Device [17aa:20e0] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Lenovo Device [17aa:20e4] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/698120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396291] Re: Maximum CPU frequency incorrect and there is no CPU scaling
Can this be closed or is this still an issue? ** Changed in: linux (Ubuntu) Status: Triaged => 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/1396291 Title: Maximum CPU frequency incorrect and there is no CPU scaling Status in linux package in Ubuntu: Incomplete Bug description: I have an Acer Aspire 5720 and it is set up to dual boot Vista and ubuntu 14.04 LTS. From new the laptop came with an Intel T7300 2.00 Ghz CPU and 1 GB DDR2 RAM. A few weeks ago I upgraded to 4 GB RAM, which works perfectly, and a few days ago I upgraded to an Intel T9300 2.5 Ghz CPU. The BIOS (up to date), Vista and ubuntu all recognise the CPU correctly as: "Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50 GHz". Vista allows the CPU to run correctly at up to 2.5 Ghz and will step the CPU speed lower when not needed, depending on which power settings are chosen. The problem is that ubuntu will only allow the CPU to run at a fixed frequency of 2.4 Ghz, which is incorrect as it's a 2.5Ghz CPU, and there is no stepping to lower the CPU frequency when max frequency is not needed. "cpupower frequency-info" in a terminal returns: analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 2.40 GHz - 2.40 GHz available frequency steps: 2.40 GHz, 2.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 2.40 GHz and 2.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.40 GHz. cpufreq stats: 2.40 GHz:10.47%, 2.40 GHz:89.53% (12799) boost state support: Supported: yes Active: yes I have tried using ondemand, performance and powersave - nothing makes any difference. I have also installed CPU Frequency Scaling Indicator (which shows only 2.4 Ghz and 2.4 Ghz (turbo mode) as available frequencies) and I have also tried TLP but nothing makes any difference. According to this website: http://www.phoronix.com/scan.php?page=article&item=mobile_penryn&num=3 the T9300 CPU should have the following frequency steps: 2.50 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz and 800 MHz. I have spent days trawling the internet for a solution but to no avail. Hence filing this bug report in the hope a solution might be found. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0c4e3b98-0d40-4db3-9f4d-d1c53eb96355 InstallationDate: Installed on 2014-04-23 (216 days ago) InstallationMedia: It MachineType: Acer Aspire 5720 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=9675b492-c55a-4c72-991b-263a27d74d5e ro quiet splash processor.ignore_ppc=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 RelatedPackageVersions: linux-restricted-modules-3.13.0-40-generic N/A linux-backports-modules-3.13.0-40-generic N/A linux-firmware 1.127.8 Tags: trusty Uname: Linux 3.13.0-40-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: eMachine dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rneMachine:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.name: Aspire 5720 dmi.product.version: V1.45 dmi.sys.vendor: Acer --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0c4e3b98-0d40-4db3-9f4d-d1c53eb96355 InstallationDate: Installed on 2014-04-23 (216 days ago) InstallationMedia: It MachineType: Acer Aspire 5720 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=9675b492-c55a-4c72-991b-263a27d74d5e ro quiet splash processor.ignore_ppc=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 RelatedPackageVersions: linux-restricted-modules-3.13.0-40-generic N/A linux-backports-modules-3.13.0-40-generi
[Kernel-packages] [Bug 1744330] Re: Bionic update to v4.14.14 stable release
4.15 is in bionic. Setting to fixed, assuming this was just forgotten. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744330 Title: Bionic update to v4.14.14 stable release Status in linux package in Ubuntu: Fix Released 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 a mainline/stable Linux tree or a minimally backported form of that patch. The v4.14.14 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.14.14 stable release shall be applied: dm bufio: fix shrinker scans when (nr_to_scan < retain_target) KVM: Fix stack-out-of-bounds read in write_mmio can: vxcan: improve handling of missing peer name attribute can: gs_usb: fix return value of the "set_bittiming" callback IB/srpt: Disable RDMA access by the initiator IB/srpt: Fix ACL lookup during login MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task MIPS: Factor out NT_PRFPREG regset access helpers MIPS: Guard against any partial write attempt with PTRACE_SETREGSET MIPS: Consistently handle buffer counter with PTRACE_SETREGSET MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses cgroup: fix css_task_iter crash on CSS_TASK_ITER_PROC kvm: vmx: Scrub hardware GPRs at VM-exit platform/x86: wmi: Call acpi_wmi_init() later iw_cxgb4: only call the cq comp_handler when the cq is armed iw_cxgb4: atomically flush the qp iw_cxgb4: only clear the ARMED bit if a notification is needed iw_cxgb4: reflect the original WR opcode in drain cqes iw_cxgb4: when flushing, complete all wrs in a chain x86/acpi: Handle SCI interrupts above legacy space gracefully ALSA: pcm: Remove incorrect snd_BUG_ON() usages ALSA: pcm: Workaround for weird PulseAudio behavior on rewind error ALSA: pcm: Add missing error checks in OSS emulation plugin builder ALSA: pcm: Abort properly at pending signal in OSS read/write loops ALSA: pcm: Allow aborting mutex lock at OSS read/write loops ALSA: aloop: Release cable upon open error path ALSA: aloop: Fix inconsistent format due to incomplete rule ALSA: aloop: Fix racy hw constraints adjustment x86/acpi: Reduce code duplication in mp_override_legacy_irq() 8021q: fix a memory leak for VLAN 0 device ip6_tunnel: disable dst caching if tunnel is dual-stack net: core: fix module type in sock_diag_bind phylink: ensure we report link down when LOS asserted RDS: Heap OOB write in rds_message_alloc_sgs() RDS: null pointer dereference in rds_atomic_free_op net: fec: restore dev_id in the cases of probe error net: fec: defer probe if regulator is not ready net: fec: free/restore resource in related probe error pathes sctp: do not retransmit upon FragNeeded if PMTU discovery is disabled sctp: fix the handling of ICMP Frag Needed for too small MTUs sh_eth: fix TSU resource handling net: stmmac: enable EEE in MII, GMII or RGMII only sh_eth: fix SH7757 GEther initialization ipv6: fix possible mem leaks in ipv6_make_skb() ethtool: do not print warning for applications using legacy API mlxsw: spectrum_router: Fix NULL pointer deref net/sched: Fix update of lastuse in act modules implementing stats_update ipv6: sr: fix TLVs not being copied using setsockopt mlxsw: spectrum: Relax sanity checks during enslavement sfp: fix sfp-bus oops when removing socket/upstream membarrier: Disable preemption when calling smp_call_function_many() crypto: algapi - fix NULL dereference in crypto_remove_spawns() mmc: renesas_sdhi: Add MODULE_LICENSE rbd: reacquire lock should update lock owner client id rbd: set max_segments to USHRT_MAX iwlwifi: pcie: fix DMA memory mapping / unmapping x86/microcode/intel: Extend BDW late-loading with a revision check KVM: x86: Add memory barrier on vmcs field lookup KVM: PPC: Book3S PR: Fix WIMG handling under pHyp KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt KVM: PPC: Book3S HV: Fix use after free in case of multiple resize requests KVM: PPC: Book3S HV: Always flush TLB in kvmppc_alloc_reset_hpt() drm/vmwgfx: Don't cache framebuffer maps drm/vmwgfx: Potential off by one in vmw_view_add() drm/i915/gvt: Clear the shadow page table entry after post-sync drm/i915: Whitelist SLICE_COMMON_ECO_CHICKEN1 on Geminilake. drm/i9
[Kernel-packages] [Bug 1711148] Re: Lage samba file transfers block btrfs to hung task
Nothing you say in your rant rules out an upstream bug. But maybe you are not so interested in getting this analysed and fixed? Anyhow, most likely time has moved on. Are you still affected by this problem? ** 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/1711148 Title: Lage samba file transfers block btrfs to hung task Status in samba: New Status in linux package in Ubuntu: Incomplete Bug description: I have this Bug since 15.10. It was confirmed but never fixed. This is a KVM guest with 17.04 (upgraded from 15.04->15.10->16.04->16.10). Its just am samba file server attached to a AD. When lage files get transfered (e.g. AD profile) samba gets stuck and prioduces a kernel hang. I install a Debain Stech (Kernel 4.9 and samba 4.2.14) for dual boot for testing, copied the smb.conf and attached it to the AD. I never get any errors like this for month, so this IS a Ubuntu related bug! I guess this is a samba related problem after samba 4.3.x [87236.886634] INFO: task btrfs-cleaner:245 blocked for more than 120 seconds. [87236.891185] Not tainted 4.10.0-32-generic #36-Ubuntu [87236.891781] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [87236.892270] btrfs-cleaner D0 245 2 0x [87236.892274] Call Trace: [87236.892320] __schedule+0x233/0x6f0 [87236.892342] ? __queue_work+0x171/0x470 [87236.892343] schedule+0x36/0x80 [87236.892525] wait_current_trans+0xc2/0x100 [btrfs] [87236.892532] ? wake_atomic_t_function+0x60/0x60 [87236.892546] start_transaction+0x2d4/0x460 [btrfs] [87236.892560] btrfs_start_transaction+0x18/0x20 [btrfs] [87236.892571] btrfs_drop_snapshot+0x454/0x8f0 [btrfs] [87236.892585] btrfs_clean_one_deleted_snapshot+0xb7/0x100 [btrfs] [87236.892597] cleaner_kthread+0x133/0x180 [btrfs] [87236.892600] kthread+0x109/0x140 [87236.892613] ? __btree_submit_bio_start+0x20/0x20 [btrfs] [87236.892614] ? kthread_create_on_node+0x60/0x60 [87236.892619] ret_from_fork+0x2c/0x40 [87357.711653] INFO: task btrfs-cleaner:245 blocked for more than 120 seconds. [87357.712727] Not tainted 4.10.0-32-generic #36-Ubuntu [87357.713035] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [87357.713348] btrfs-cleaner D0 245 2 0x [87357.713356] Call Trace: [87357.713366] __schedule+0x233/0x6f0 [87357.713369] ? __queue_work+0x171/0x470 [87357.713371] schedule+0x36/0x80 [87357.713429] wait_current_trans+0xc2/0x100 [btrfs] [87357.713432] ? wake_atomic_t_function+0x60/0x60 [87357.713446] start_transaction+0x2d4/0x460 [btrfs] [87357.713460] btrfs_start_transaction+0x18/0x20 [btrfs] [87357.713473] btrfs_drop_snapshot+0x454/0x8f0 [btrfs] [87357.713487] btrfs_clean_one_deleted_snapshot+0xb7/0x100 [btrfs] [87357.713501] cleaner_kthread+0x133/0x180 [btrfs] [87357.713503] kthread+0x109/0x140 [87357.713516] ? __btree_submit_bio_start+0x20/0x20 [btrfs] [87357.713517] ? kthread_create_on_node+0x60/0x60 [87357.713523] ret_from_fork+0x2c/0x40 [87357.713548] INFO: task nmbd:1434 blocked for more than 120 seconds. [87357.713846] Not tainted 4.10.0-32-generic #36-Ubuntu [87357.714103] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [87357.714350] nmbdD0 1434 1 0x [87357.714351] Call Trace: [87357.714353] __schedule+0x233/0x6f0 [87357.714354] schedule+0x36/0x80 [87357.714372] lock_extent_bits+0x190/0x1e0 [btrfs] [87357.714374] ? wake_atomic_t_function+0x60/0x60 [87357.714389] lock_and_cleanup_extent_if_need+0xff/0x280 [btrfs] [87357.714403] __btrfs_buffered_write+0x1e4/0x740 [btrfs] [87357.714448] btrfs_file_write_iter+0x182/0x4e0 [btrfs] [87357.714464] ? _copy_to_user+0x54/0x60 [87357.714470] new_sync_write+0xd5/0x130 [87357.714471] __vfs_write+0x26/0x40 [87357.714472] vfs_write+0xb5/0x1a0 [87357.714473] SyS_write+0x55/0xc0 [87357.714475] entry_SYSCALL_64_fastpath+0x1e/0xad [87357.714477] RIP: 0033:0x7f223143e670 [87357.714478] RSP: 002b:7ffce24e0398 EFLAGS: 0246 ORIG_RAX: 0001 [87357.714479] RAX: ffda RBX: 559d2a0eef60 RCX: 7f223143e670 [87357.714480] RDX: 004d RSI: 7ffce24e0900 RDI: 0009 [87357.714480] RBP: 7f222dc38b00 R08: c1c0 R09: 7362696c2f336563 [87357.714481] R10: 696c626d6e2f626d R11: 0246 R12: 0020 [87357.714482] R13: 0008 R14: 7ffce24e0c48 R15: 0001 [87357.714485] INFO: task miniserv.pl:1535 blocked for more than 120 seconds. [87357.714743] Not tainted 4.10.0-32-generic #36-Ubuntu [87357.714992] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
[Kernel-packages] [Bug 1643566] Re: [i915_bpo] Intermittent display outage with external monitor
Anybody who can still reproduce this particular problem? ** Changed in: linux (Ubuntu Xenial) 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/1643566 Title: [i915_bpo] Intermittent display outage with external monitor Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Bug description: Filing on behalf of Claire Newman... I seem to be tickling a bug in the i915 stack, when I use a desktop monitor. The symptom is that the screen blanks for a few seconds then comes back . This happens every few minutes. I am using a Lenovo Thinkpad T460s (new this weekend) but last week I was using a Thinkpad W550s - same issue with the blank screen on both laptops. Happens every 20 mins or so and there is no identifiable reproducer (eg. I cam just be sitting there doing something else on my phone and the screen goes black). Here is lspci output for the video card: 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics Flags: bus master, fast devsel, latency 0, IRQ 123 Memory at e000 (64-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=512M] I/O ports at e000 [size=64] Expansion ROM at [disabled] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] #1b Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] #13 Kernel driver in use: i915_bpo Kernel modules: i915_bpo And in dmesg I see the below text: [161321.406860] i915_bpo :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment [161528.013954] [ cut here ] [161528.013996] WARNING: CPU: 3 PID: 31178 at /build/linux-xHzv4a/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() [161528.013998] WARN_ON(!wm_changed) [161528.014047] Modules linked in: hid_logitech_hidpp hid_generic hid_logitech_dj usbhid hid snd_usb_audio snd_usbmidi_lib cpuid drbg ansi_cprng ctr ccm rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel bluetooth arc4 joydev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp nls_iso8859_1 kvm snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core irqbypass crct10dif_pclmul crc32_pclmul aesni_intel snd_compress ac97_bus aes_x86_64 snd_pcm_dmaengine dw_dmac_core iwlmvm lrw snd_hda_intel gf128mul glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm input_leds serio_raw iwlwifi rtsx_pci_ms [161528.014074] cfg80211 memstick snd_seq_midi thinkpad_acpi snd_seq_midi_event snd_rawmidi nvram mei_me mei shpchp snd_seq snd_seq_device snd_timer snd soundcore tpm_crb mac_hid parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect sysimgblt ptp fb_sys_fops pps_core drm nvme rtsx_pci wmi video fjes [161528.014079] CPU: 3 PID: 31178 Comm: Xorg Not tainted 4.4.0-47-generic #68-Ubuntu [161528.014080] Hardware name: LENOVO 20F9CTO1WW/20F9CTO1WW, BIOS N1CET47W (1.15 ) 08/08/2016 [161528.014085] 0286 b170f762 88027b36f600 813f5aa3 [161528.014088] 88027b36f648 c02a39a0 88027b36f638 81081262 [161528.014091] 880522e26000 88003f96a148 880522e27000 880523193b78 [161528.014092] Call Trace: [161528.014102] [] dump_stack+0x63/0x90 [161528.014108] [] warn_slowpath_common+0x82/0xc0 [161528.014112] [] warn_slowpath_fmt+0x5c/0x80 [161528.014144] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] [161528.014175] [] skl_update_wm+0x185/0x610 [i915_bpo] [161528.014224] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] [161528.014273] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [161528.014326] [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo] [161528.014378] [] ? intel_finish_crtc_commit+0xe/0x10 [i915_bpo] [161528.014395] [] ? drm_atomic_helper_commit_planes_on_crtc+0x154/0x270 [drm_kms_helper] [161528.014449] [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo] [161528.014488] [] ? drm_atomic_check_only+0x18e/0x590 [drm] [161528.014521] [] drm_atomic_commit+0x37/0x60 [drm] [161528.014538] [] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] [161528.014571] [] ? drm_modeset_loc
[Kernel-packages] [Bug 1674763] Re: Warnings then GPF originating from nouveau under zesty
I experience this, too, in bionic. Possibly related to bug 1730458. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674763 Title: Warnings then GPF originating from nouveau under zesty Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: unity-settings-[4857]: failed to turn the kbd backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UPower.KbdBacklight' on object at path /org/freedesktop/UPower/KbdBacklight polkit-gnome-au[7926]: cannot open display: :0 kernel: [ 2607.528731] [ cut here ] kernel: [ 2607.528802] WARNING: CPU: 6 PID: 4317 at /build/linux-ZNEhaM/linux-4.10.0/drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau] kernel: [ 2607.528803] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache snd_hda_codec_hdmi gpio_ich snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_hwdep kvm_intel snd_rawmidi snd_pcm kvm snd_seq irqbypass joydev input_leds intel_cstate snd_seq_device i7core_edac snd_timer serio_raw snd edac_core lpc_ich soundcore mei_me mei shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper kernel: [ 2607.528863] syscopyarea sysfillrect psmouse sysimgblt ahci e1000e fb_sys_fops libahci drm ptp pps_core pata_acpi fjes video kernel: [ 2607.528876] CPU: 6 PID: 4317 Comm: Xorg Not tainted 4.10.0-13-generic #15-Ubuntu kernel: [ 2607.528877] Hardware name: /DQ57TM, BIOS TMIBX10H.86A.0050.2011.1207.1134 12/07/2011 kernel: [ 2607.528878] Call Trace: kernel: [ 2607.528887] dump_stack+0x63/0x81 kernel: [ 2607.528890] __warn+0xcb/0xf0 kernel: [ 2607.528892] warn_slowpath_null+0x1d/0x20 kernel: [ 2607.528950] nouveau_bo_del_ttm+0x7f/0x90 [nouveau] kernel: [ 2607.528958] ttm_bo_release_list+0xcb/0x210 [ttm] kernel: [ 2607.528965] ttm_bo_release+0x19d/0x230 [ttm] kernel: [ 2607.528972] ttm_bo_unref+0x24/0x30 [ttm] kernel: [ 2607.529029] nouveau_gem_object_del+0x94/0xf0 [nouveau] kernel: [ 2607.529047] drm_gem_object_free+0x29/0x70 [drm] kernel: [ 2607.529062] drm_gem_object_unreference_unlocked+0x3a/0xa0 [drm] kernel: [ 2607.529077] drm_gem_object_handle_unreference_unlocked+0x65/0xb0 [drm] kernel: [ 2607.529093] drm_gem_object_release_handle+0x53/0x90 [drm] kernel: [ 2607.529095] idr_for_each+0xb0/0x110 kernel: [ 2607.529110] ? drm_gem_object_handle_unreference_unlocked+0xb0/0xb0 [drm] kernel: [ 2607.529168] ? nouveau_abi16_fini+0x50/0x70 [nouveau] kernel: [ 2607.529184] drm_gem_release+0x20/0x30 [drm] kernel: [ 2607.529199] drm_release+0x316/0x370 [drm] kernel: [ 2607.529202] __fput+0xe7/0x220 kernel: [ 2607.529205] fput+0xe/0x10 kernel: [ 2607.529207] task_work_run+0x80/0xa0 kernel: [ 2607.529210] do_exit+0x2ce/0xb10 kernel: [ 2607.529214] ? __do_page_fault+0x266/0x4e0 kernel: [ 2607.529216] do_group_exit+0x43/0xb0 kernel: [ 2607.529219] SyS_exit_group+0x14/0x20 kernel: [ 2607.529223] entry_SYSCALL_64_fastpath+0x1e/0xad kernel: [ 2607.529225] RIP: 0033:0x7f671d698b48 kernel: [ 2607.529226] RSP: 002b:7fff74c8cba8 EFLAGS: 0246 ORIG_RAX: 00e7 kernel: [ 2607.529229] RAX: ffda RBX: 55a1dc69e3b0 RCX: 7f671d698b48 kernel: [ 2607.529230] RDX: RSI: 003c RDI: kernel: [ 2607.529232] RBP: 7fff74c8cba0 R08: 00e7 R09: fc90 kernel: [ 2607.529233] R10: 7f671210a148 R11: 0246 R12: 7f6712109d90 kernel: [ 2607.529234] R13: 0044 R14: R15: 7fff74c8c8c0 kernel: [ 2607.529237] ---[ end trace 886311290d3f1a12 ]--- kernel: [ 2607.529322] [ cut here ] kernel: [ 2607.529322] [ cut here ] kernel: [ 2607.529383] WARNING: CPU: 6 PID: 4317 at /build/linux-ZNEhaM/linux-4.10.0/drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau] kernel: [ 2607.529383] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache snd_hda_codec_hdmi gpio_ich snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_hwdep kvm_intel snd_rawmidi snd_pcm kvm snd_seq irqbypass joydev input_leds intel_cstate snd_seq_device i7core_edac snd_timer serio_raw snd e
[Kernel-packages] [Bug 1747273] Re: Can not control brightness on Thinkpad P51
ping Michael and Urschl ** 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/1747273 Title: Can not control brightness on Thinkpad P51 Status in linux package in Ubuntu: Incomplete Bug description: I can not modify the screen brightness in Ubuntu 17.10. Controls aside, the classes in `proc` are either not available or non- functional depending on what arguments I provide in GRUB_CMDLINE_LINUX_DEFAULT. On a parallel installation (Ubuntu 16.04.3), brightness control works flawlessly. System Information -- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Device a171 (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux thinkpad-acpi.brightness_enable=1": $ grep . -R /sys/class/backlight/thinkpad_screen/* /sys/class/backlight/thinkpad_screen/actual_brightness:0 /sys/class/backlight/thinkpad_screen/bl_power:0 /sys/class/backlight/thinkpad_screen/brightness:11 /sys/class/backlight/thinkpad_screen/max_brightness:15 /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported grep: warning: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: recursive directory loop /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/max_brightness:15 /sys/class/back
[Kernel-packages] [Bug 1658352] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1.
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1658352 Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Status in linux-firmware package in Ubuntu: Invalid Bug description: whenever i try to upgrade my operating system from ubuntu 14.04 to 16.04 error show "could not install initramfs-tools", "could not install linux-firmware" and "could not install linux- image-4.4.0-59-generic" and te upgrade is failed show could not install upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Sat Jan 21 23:52:45 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-14 (7 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1658352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678645] Re: "btrfs send" returns "Inappropriate ioctl for device"
FWIW, this affects for example the latest www.system-rescue-cd.org as well dated 2nd of April. It boots by default into an amd64 kernel but the btrfs tools are i386. Very much looks like an upstream issue to me and possibly more relevant than one might be tempted to think initially. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678645 Title: "btrfs send" returns "Inappropriate ioctl for device" Status in linux package in Ubuntu: Triaged Bug description: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658352] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1.
Asif, did Steve's instructions help you to resolve the issue? ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1658352 Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Status in linux-firmware package in Ubuntu: Incomplete Bug description: whenever i try to upgrade my operating system from ubuntu 14.04 to 16.04 error show "could not install initramfs-tools", "could not install linux-firmware" and "could not install linux- image-4.4.0-59-generic" and te upgrade is failed show could not install upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Sat Jan 21 23:52:45 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-14 (7 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1658352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 374105] Re: linux-image-$ver packages leave cruft behind
found this on the console when removing a kernel package: dpkg: warning: while removing linux-image-4.4.0-81-generic, directory '/lib/modules/4.4.0-81-generic' not empty so not removed $ find /lib/modules/4.4.0-81-generic/ /lib/modules/4.4.0-81-generic/ /lib/modules/4.4.0-81-generic/modules.dep /lib/modules/4.4.0-81-generic/modules.dep.bin /lib/modules/4.4.0-81-generic/modules.alias /lib/modules/4.4.0-81-generic/modules.alias.bin /lib/modules/4.4.0-81-generic/modules.softdep /lib/modules/4.4.0-81-generic/modules.symbols /lib/modules/4.4.0-81-generic/modules.symbols.bin /lib/modules/4.4.0-81-generic/modules.builtin.bin /lib/modules/4.4.0-81-generic/modules.devname -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/374105 Title: linux-image-$ver packages leave cruft behind Status in linux package in Ubuntu: Confirmed Status in tp-smapi package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: New Bug description: $ ll /lib/modules/ total 6,0K drwxr-xr-x 8 root root 1,0K 2009-03-10 02:41 2.6.24-23-386 drwxr-xr-x 2 root root 1,0K 2009-03-23 05:13 2.6.28-10-generic drwxr-xr-x 5 root root 1,0K 2009-04-20 08:55 2.6.28-11-generic drwxr-xr-x 2 root root 1,0K 2009-03-17 05:54 2.6.28-4-386 drwxr-xr-x 3 root root 1,0K 2009-03-15 04:12 2.6.28-8-generic drwxr-xr-x 3 root root 1,0K 2009-03-12 02:18 2.6.28-9-generic $ dpkg -l linux-image*|grep ii ii linux-image2.6.28.11.15 Generic Linux kernel image. ii linux-image-2.6.24-23-386 2.6.24-23.48 Linux kernel image for version 2.6.24 on i38 ii linux-image-2.6.28-11-generic 2.6.28-11.42 Linux kernel image for version 2.6.28 on x86 ii linux-image-generic2.6.28.11.15 Generic Linux kernel image $ dpkg -S /lib/modules/*/modules.seriomap linux-image-2.6.24-23-386: /lib/modules/2.6.24-23-386/modules.seriomap dpkg: /lib/modules/2.6.28-10-generic/modules.seriomap not found. dpkg: /lib/modules/2.6.28-11-generic/modules.seriomap not found. 2.6.28-10-generic looks like a superseded package that did not properly clean up after itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/374105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
@Daniel, have you even bothered to actually read this ticket? Comment #11, for example? Who gives a hoot about Quantal EOL in this case? Since you are paid you ought to do a lot better. ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => 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/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678645] Re: "btrfs send" returns "Inappropriate ioctl for device"
** 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/1678645 Title: "btrfs send" returns "Inappropriate ioctl for device" Status in linux package in Ubuntu: Incomplete Bug description: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678645] Re: "btrfs send" returns "Inappropriate ioctl for device"
** 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/1678645 Title: "btrfs send" returns "Inappropriate ioctl for device" Status in linux package in Ubuntu: Confirmed Bug description: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678645] Re: "btrfs send" returns "Inappropriate ioctl for device"
There's nothing missing, all necessary information is there. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1678645 Title: "btrfs send" returns "Inappropriate ioctl for device" Status in linux package in Ubuntu: New Bug description: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1211976] Re: [ 11.063330] WARNING: CPU: 2 PID: 1455 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x58f/0x9c0 [i915]()
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1211976 Title: [ 11.063330] WARNING: CPU: 2 PID: 1455 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x58f/0x9c0 [i915]() Status in Linux: Fix Released Status in Linux Mint: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [ 10.847450] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 0, found 1) [ 10.847454] [ cut here ] [ 10.847478] WARNING: CPU: 1 PID: 1455 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x58f/0x9c0 [i915]() [ 10.847479] pipe state doesn't match! [ 10.847481] Modules linked in: md4(F) parport_pc(F) ppdev(F) x86_pkg_temp_thermal intel_powerclamp bnep rfcomm coretemp kvm_intel(F) kvm(F) crc32_pclmul(F) snd_hda_codec_hdmi ghash_clmulni_intel(F) snd_hda_codec_conexant aesni_intel(F) aes_x86_64(F) lrw(F) gf128mul(F) glue_helper(F) ablk_helper(F) cryptd(F) joydev(F) arc4(F) iwldvm dell_laptop dcdbas dell_wmi sparse_keymap mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev iwlwifi snd_hda_intel snd_hda_codec btusb snd_hwdep(F) i915 snd_pcm(F) bluetooth snd_page_alloc(F) microcode(F) psmouse(F) snd_seq_midi(F) snd_seq_midi_event(F) cfg80211 snd_rawmidi(F) serio_raw(F) drm_kms_helper snd_seq(F) drm snd_seq_device(F) wmi snd_timer(F) mei_me mei snd(F) i2c_algo_bit soundcore(F) lpc_ich mac_hid video(F) nls_utf8 cifs(F) fscache(F) lp(F) parport(F) hid_generic usbhid hid r8169 ahci(F) libahci(F) mii(F) [ 10.847537] CPU: 1 PID: 1455 Comm: Xorg Tainted: GF 3.11.0-2-generic #5-Ubuntu [ 10.847539] Hardware name: Dell Inc. Vostro V131/0P0TH6, BIOS A02 08/31/2011 [ 10.847541] 0009 880211b81898 816f1668 880211b818e0 [ 10.847544] 880211b818d0 81061cdd 8802126db6d0 0001 [ 10.847547] 8802117b6800 8802126db000 8802117b6c78 880211b81930 [ 10.847550] Call Trace: [ 10.847556] [] dump_stack+0x45/0x56 [ 10.847561] [] warn_slowpath_common+0x7d/0xa0 [ 10.847564] [] warn_slowpath_fmt+0x4c/0x50 [ 10.847576] [] check_crtc_state+0x58f/0x9c0 [i915] [ 10.847589] [] intel_modeset_check_state+0x2c3/0x770 [i915] [ 10.847599] [] intel_set_mode+0x25/0x30 [i915] [ 10.847610] [] intel_crtc_set_config+0x742/0x910 [i915] [ 10.847623] [] drm_mode_set_config_internal+0x5d/0xe0 [drm] [ 10.847632] [] drm_mode_setcrtc+0xf7/0x650 [drm] [ 10.847643] [] ? intel_crtc_load_lut+0xd2/0x170 [i915] [ 10.847651] [] drm_ioctl+0x532/0x660 [drm] [ 10.847657] [] do_vfs_ioctl+0x2e5/0x4d0 [ 10.847659] [] ? vtime_account_user+0x69/0x80 [ 10.847662] [] SyS_ioctl+0x81/0xa0 [ 10.847667] [] tracesys+0xe1/0xe6 [ 10.847669] ---[ end trace 3d81ce9006d37418 ]--- [ 11.063302] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 0, found 1) [ 11.063306] [ cut here ] [ 11.063330] WARNING: CPU: 2 PID: 1455 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x58f/0x9c0 [i915]() [ 11.063332] pipe state doesn't match! [ 11.06] Modules linked in: md4(F) parport_pc(F) ppdev(F) x86_pkg_temp_thermal intel_powerclamp bnep rfcomm coretemp kvm_intel(F) kvm(F) crc32_pclmul(F) snd_hda_codec_hdmi ghash_clmulni_intel(F) snd_hda_codec_conexant aesni_intel(F) aes_x86_64(F) lrw(F) gf128mul(F) glue_helper(F) ablk_helper(F) cryptd(F) joydev(F) arc4(F) iwldvm dell_laptop dcdbas dell_wmi sparse_keymap mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev iwlwifi snd_hda_intel snd_hda_codec btusb snd_hwdep(F) i915 snd_pcm(F) bluetooth snd_page_alloc(F) microcode(F) psmouse(F) snd_seq_midi(F) snd_seq_midi_event(F) cfg80211 snd_rawmidi(F) serio_raw(F) drm_kms_helper snd_seq(F) drm snd_seq_device(F) wmi snd_timer(F) mei_me mei snd(F) i2c_algo_bit soundcore(F) lpc_ich mac_hid video(F) nls_utf8 cifs(F) fscache(F) lp(F) parport(F) hid_generic usbhid hid r8169 ahci(F) libahci(F) mii(F) [ 11.063389] CPU: 2 PID: 1455 Comm: Xorg Tainted: GF W 3.11.0-2-generic #5-Ubuntu [ 11.063391] Hardware name: Dell Inc. Vostro V131/0P0TH6, BIOS A02 08/31/2011 [ 11.063393] 0009 880211b81898 816f1668 880211b818e0 [ 11.063396] 880211b818d0 81061cdd 8802126db6d0 0001 [ 11.063399] 8802117b6800 8802126db000 8802117b6c78 880211b81930 [ 11.063402] Call Trace: [ 11.063409] [] dump_stack+0x45/0x56 [ 11.063414] [] warn_slowpath_common+0x7d/0xa0 [ 11.063418] [] warn_slowpath_fmt+0x4c/0x50
[Kernel-packages] [Bug 557224] Re: resume broken on ATI radeon RV250
setting to fix released as per the latest comments ** Changed in: linux (Ubuntu) Status: Incomplete => 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/557224 Title: resume broken on ATI radeon RV250 Status in linux package in Ubuntu: Fix Released Bug description: I installed Lucid on my IBM T41 laptop with a Radeon RV250 chipset. After resuming from a suspend, I only see the mouse cursor on a black background. Switching VTs and coming back to X doesn't change anything. The dmesg log shows lots of ioctl errors in the radeon driver. WORKAROUND: Booting with "nomodeset" in the kernel cmdline fixes suspend/resume. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-19-generic 2.6.32-19.28 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amit 1245 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 26 Simple ctrls : 18 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1RHT71WW-3.04' Mixer name : 'ThinkPad EC 1RHT71WW-3.04' Components : '' Controls : 2 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 14 Mono: Playback 6 [43%] [on] Date: Wed Apr 7 12:53:41 2010 HibernationDevice: RESUME=UUID=3172ad6d-4dfb-43d6-898a-d3d54933400a InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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 MachineType: IBM 2373NG9 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=3af12628-6785-4f0a-bc58-c892037abaeb ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.33 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux dmi.bios.date: 10/29/2004 dmi.bios.vendor: IBM dmi.bios.version: 1RETDHWW (3.13 ) dmi.board.name: 2373NG9 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: 99Y15L3 dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDHWW(3.13):bd10/29/2004:svnIBM:pn2373NG9:pvrThinkPadT41:rvnIBM:rn2373NG9:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373NG9 dmi.product.version: ThinkPad T41 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/557224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1088053] Re: Kernel needs to provide FIFREEZE/FITHAW ioctl so that open-vm-dkms can build
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1088053 Title: Kernel needs to provide FIFREEZE/FITHAW ioctl so that open-vm-dkms can build Status in VMWare tools: Unknown Status in linux package in Ubuntu: Invalid Status in open-vm-tools package in Ubuntu: Fix Released Bug description: Hello, My name is Nate, and I'm responsible for keeping the open-vm-tools package up to date. I am requesting that ioctl (specifically FIFREEZE/FITHAW ioctl) please be compiled into the kernel (if it hasn't already) because vmsync doesn't compile since newer kernel (namely 3.6 and greater). Yes, I know it's depreciated but it need to be done. I'm reporting this now because I've known about this for a month or so because I have a scratch machine and both that and Ubuntu are different environments, and I just installed Raring for the first time. And since Ubuntu's kernel has more stuff that the normal kernel, I wanted to know if the module would compile. Here's part of the info I got: Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in import apport ImportError: No module named apport Error! Build of vmsync.ko failed for: 3.7.0-5-generic (i686) This is coming directly from upstream (http://sourceforge.net/tracker/?func=detail&aid=3579185&group_id=204462&atid=989708). I can do some of the work from my end (taking out mentions of the vmsync module for dkms from the debian folder, and upload the new config to bzr and wait for approval). But in order for me to upload and mark (my packaging) for approval, I need this to be done please. Obviously, I'm posting this so I also get a bug report number, that I can put in my packaging's changelog --- ApportVersion: 2.6.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 1948 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.753946] end_request: I/O error, dev fd0, sector 0 DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=1d10b04b-de23-4217-9fcd-cfc637bbfaf8 InstallationDate: Installed on 2012-12-08 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121207) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True Package: open-vm-tools-dkms PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-5-generic root=UUID=eed1e65f-5c0e-4f1e-9c82-c2425504c600 ro quiet splash ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 RelatedPackageVersions: linux-restricted-modules-3.7.0-5-generic N/A linux-backports-modules-3.7.0-5-generic N/A linux-firmware 1.98 RfKill: Tags: raring running-unity raring running-unity Uname: Linux 3.7.0-5-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/20/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.vmware.tools.tools.conf: mtime.conffile..etc.vmware.tools.tools.conf: 2012-12-07T19:24:35.065678 To manage notifications about this bug go to: https://bugs.launchpad.net/open-vm-tools/+bug/1088053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1131331] Re: CVE-2012-4542
** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Vivid) ** No longer affects: linux (Ubuntu Wily) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Yakkety) -- 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/1131331 Title: CVE-2012-4542 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: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Invalid 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: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid 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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid 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: New Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: New Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid 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-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty
[Kernel-packages] [Bug 1063791] Re: ubuntu kernels < 3.7 do not include DISCARD/TRIM (FITRIM ioctl) for JFS filesystem
The fix is in trusty and later, so setting status to 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/1063791 Title: ubuntu kernels < 3.7 do not include DISCARD/TRIM (FITRIM ioctl) for JFS filesystem Status in linux package in Ubuntu: Fix Released Bug description: I backported the (now uptream since linux 3.7) patch to add DISCARD/TRIM to JFS filesystem from https://lkml.org/lkml/2012/10/3/250 to ubuntu kernel < 3.7. It contains two other minor fixes, too. It's quite straightforward, the only change is to exclude one line (a call to dquot_writeback_dquots() in fs/jfs/super.c) that otherwise would pull in endless dependencies to newly added blkdev and quota functions and macros. The patched 3.2 kernel (ubuntu generic 3.2.0-31.50, +JFS TRIM + LZO instead of GZIP, no other changes) is up and running on a SSD, 'fstrim' command works and also mount option 'discard'. With the stock ubuntu 3.2 generic kernel on a SSD and JFS, I had two crashes, both inside JFS kernel code, one was catched (AppArmor?) leaving me with r/o filesystem and the other could not recover. Other than that, I experienced bad interactive performance since I installed the SSD. These have become slightly better with the patch added, but interactivity is still worse than with a rotational HD, e.g. when opening a menu. Will now investigate if running a low latency kernel fixes that. The patch is appended, the Ubuntu KernelGitGuide says clone stock linux from kernel.ubuntu.com, but https://wiki.ubuntu.com/Kernel/Dev/KernelPatches says clone stock linux-2.6 from kernel.org, that's all too confusing. Decide what you want and adjust the docs, please... Now the patch is against ubuntu-3.2. With kind regards, =|o) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.28 x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2554 F pulseaudio CRDA: country AM: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (N/A, 18) (5250 - 5330 @ 20), (N/A, 18), DFS Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf064 irq 44' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,10cf,0012 HDA:11c11040,11c10001,00100200' Controls : 29 Simple ctrls : 16 Date: Mon Oct 8 14:45:44 2012 HibernationDevice: RESUME=UUID=42c86022-ee03-45af-bd1e-58be6d2aa822 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS LIFEBOOK S7110 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE TERM=xterm-color PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.28 root=UUID=10e6b6ad-159a-41a1-8efe-04c1504aa075 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.28 N/A linux-backports-modules-3.2.28 N/A linux-firmware 1.79.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.35 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279611-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279611-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1063791] Re: ubuntu kernels < 3.7 do not include DISCARD/TRIM (FITRIM ioctl) for JFS filesystem
Thanks, guys, for your work. The only release still affected by this bug is precise which will be EOL by the end of this month. It's time to move on. Closing as obsolete. ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => 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/1063791 Title: ubuntu kernels < 3.7 do not include DISCARD/TRIM (FITRIM ioctl) for JFS filesystem Status in linux package in Ubuntu: Fix Released Bug description: I backported the (now uptream since linux 3.7) patch to add DISCARD/TRIM to JFS filesystem from https://lkml.org/lkml/2012/10/3/250 to ubuntu kernel < 3.7. It contains two other minor fixes, too. It's quite straightforward, the only change is to exclude one line (a call to dquot_writeback_dquots() in fs/jfs/super.c) that otherwise would pull in endless dependencies to newly added blkdev and quota functions and macros. The patched 3.2 kernel (ubuntu generic 3.2.0-31.50, +JFS TRIM + LZO instead of GZIP, no other changes) is up and running on a SSD, 'fstrim' command works and also mount option 'discard'. With the stock ubuntu 3.2 generic kernel on a SSD and JFS, I had two crashes, both inside JFS kernel code, one was catched (AppArmor?) leaving me with r/o filesystem and the other could not recover. Other than that, I experienced bad interactive performance since I installed the SSD. These have become slightly better with the patch added, but interactivity is still worse than with a rotational HD, e.g. when opening a menu. Will now investigate if running a low latency kernel fixes that. The patch is appended, the Ubuntu KernelGitGuide says clone stock linux from kernel.ubuntu.com, but https://wiki.ubuntu.com/Kernel/Dev/KernelPatches says clone stock linux-2.6 from kernel.org, that's all too confusing. Decide what you want and adjust the docs, please... Now the patch is against ubuntu-3.2. With kind regards, =|o) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.28 x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2554 F pulseaudio CRDA: country AM: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (N/A, 18) (5250 - 5330 @ 20), (N/A, 18), DFS Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf064 irq 44' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,10cf,0012 HDA:11c11040,11c10001,00100200' Controls : 29 Simple ctrls : 16 Date: Mon Oct 8 14:45:44 2012 HibernationDevice: RESUME=UUID=42c86022-ee03-45af-bd1e-58be6d2aa822 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS LIFEBOOK S7110 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE TERM=xterm-color PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.28 root=UUID=10e6b6ad-159a-41a1-8efe-04c1504aa075 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.28 N/A linux-backports-modules-3.2.28 N/A linux-firmware 1.79.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.35 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279611-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279611-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
found another similar bug 1678645 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678645] [NEW] "btrfs send" returns "Inappropriate ioctl for device"
Public bug reported: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678645 Title: "btrfs send" returns "Inappropriate ioctl for device" Status in linux package in Ubuntu: New Bug description: It seems I discovered another "Inappropriate ioctl for device" bug when running an amd64 kernel on an i386 system (the first one was bug 1619918). My system is trusty, but I assume later versions and even upstream are affected. Steps to reproduce: - run an amd64 kernel via multi-arch on an i386 system - Try to "btrfs send" or "btrfs receive" a subvolume Result: $ sudo btrfs send /mnt/LTS/snapshots/home-daily-2017-03-16/ -f /tmp/home-daily-2017-03-16.btrfs At subvol /mnt/LTS/snapshots/home-daily-2017-03-16/ ERROR: send ioctl failed with -25: Inappropriate ioctl for device This occurs with 3.13.0-96-generic as well as 3.13.0-114-generic (which fixes bug 1619918). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
Can this ticket be closed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
@Po-Hsu So, I did the work, yet you didn't act on it in time. Great! Just confirms the impression of the Ubuntu kernel team I've had for a while. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I'm happy to report that with kernel linux- image-3.13.0-114-generic:amd64 and e2fsprogs:i386 on trusty the original issue with lsattr is fixed and there are no regressions with "btrfs fi show" or "btrfs sub snapshot". For verification of the other kernels, is it sufficient for me to install those kernels on my trusty system and do the tests? ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Po-Hsu Lin, I understand the kernel team is busy, but frankly, I don't understand why I should be doing all the work when it wasn't me introducing the regression. There are clear steps provided in how to verify the problem and the fix. I don't think it should be beyond those who get paid for this kind of stuff and who no doubt will have more powerful resources and connectivity than me to do at least a test of their own from time to time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Thank you for releasing the test kernels. I will likely need a bit more time for testing than the allotted five days as the internet in this part of the world is inadequate. Please confirm the extension. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I'm happy to report that with the latest kernel from http://kernel.ubuntu.com/~jsalisbury/lp1619918/ the original issue with lsattr is fixed and there are no regressions with "btrfs fi show" or "btrfs sub snapshot". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 374105] Re: linux-image-$ver packages leave cruft behind
still not fixed. $ sudo find /lib/modules/4.4.0-53-generic/ /lib/modules/4.4.0-53-generic/ /lib/modules/4.4.0-53-generic/build $ file /lib/modules/4.4.0-53-generic/build /lib/modules/4.4.0-53-generic/ /lib/modules/4.4.0-53-generic/build: symbolic link to `/usr/src/linux-headers-4.4.0-53-generic' /lib/modules/4.4.0-53-generic/: directory -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/374105 Title: linux-image-$ver packages leave cruft behind Status in linux package in Ubuntu: Confirmed Status in tp-smapi package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: New Bug description: $ ll /lib/modules/ total 6,0K drwxr-xr-x 8 root root 1,0K 2009-03-10 02:41 2.6.24-23-386 drwxr-xr-x 2 root root 1,0K 2009-03-23 05:13 2.6.28-10-generic drwxr-xr-x 5 root root 1,0K 2009-04-20 08:55 2.6.28-11-generic drwxr-xr-x 2 root root 1,0K 2009-03-17 05:54 2.6.28-4-386 drwxr-xr-x 3 root root 1,0K 2009-03-15 04:12 2.6.28-8-generic drwxr-xr-x 3 root root 1,0K 2009-03-12 02:18 2.6.28-9-generic $ dpkg -l linux-image*|grep ii ii linux-image2.6.28.11.15 Generic Linux kernel image. ii linux-image-2.6.24-23-386 2.6.24-23.48 Linux kernel image for version 2.6.24 on i38 ii linux-image-2.6.28-11-generic 2.6.28-11.42 Linux kernel image for version 2.6.28 on x86 ii linux-image-generic2.6.28.11.15 Generic Linux kernel image $ dpkg -S /lib/modules/*/modules.seriomap linux-image-2.6.24-23-386: /lib/modules/2.6.24-23-386/modules.seriomap dpkg: /lib/modules/2.6.28-10-generic/modules.seriomap not found. dpkg: /lib/modules/2.6.28-11-generic/modules.seriomap not found. 2.6.28-10-generic looks like a superseded package that did not properly clean up after itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/374105/+subscriptions -- Mailing list: https://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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
On 08.02.2017 04:29, Joseph Salisbury wrote: > There should be a fix coming from upstream shortly: > https://lkml.org/lkml/2017/2/6/969 Great! Thanks. ** No longer affects: linux (Ubuntu Vivid) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
How many more times will I have to do silly tests with predictable results before this regression is finally fixed, Joseph? Just asking. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
On 07.01.2017 01:38, Luke-Jr wrote: > On Friday, January 06, 2017 5:22:34 PM Joseph Salisbury wrote: >> btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in >> btrfs_ioctl >> >> However, this commit introduced a new regression. With this commit >> applied, "btrfs fi show" no longer works and the btrfs snapshot >> functionality breaks. > I don't see how this is even possibly related. Furthermore, > "btrfs fi show" as well as snapshots seem to work just fine > for me. Maybe the relation isn't immediately obvious from code inspection alone, nonetheless it demonstrably is there. That commit is what introduced the described regression. Apparently, it's only present with an amd64 kernel and 32-bit userspace. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Thank you for providing the kernel. Here are the (as expected results) results: - lsattr bug is back - "btrfs fi show" works - snapshotting works $ uname -a Linux 1001P 4.4.0-53-generic #74~lp1619918Commit4c63c2454eReverted SMP Tue Dec 13 18:27:31 UT x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Bug watch added: Linux Kernel Bug Tracker #190221 http://bugzilla.kernel.org/show_bug.cgi?id=190221 ** Also affects: kernel via http://bugzilla.kernel.org/show_bug.cgi?id=190221 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
adding to comment #36: mainline kernel 4.9.0-040900rc7-generic #201611271731 does - not have the problem with lsattr - not have the problem with "btrfs fi show" - INDEED have the problem with snapshotting -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
The original bug is just an annoyance in my opinion and a cornercase as well. From what I can tell it makes it impossible to get extended attributes for any file, but only if you have a mixed i386/amd64 environment, run the amd64 kernel while having i386 e2fsprogs. The impact of that should be pretty low. Not being able to take a snapshot on the other hand is a pretty hefty problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
IOW, I think backing out the patch and reintroducing the original problem is better than keeping the regression the fix introduced to stick around. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
mainline amd64 kernel 4.9.0-040900rc7-generic #201611271731 does not have the problem with lsattr "btrfs fi show". It DOES have the problem with creating a btrfs snapshot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1015010] Re: Cannot connect to Samsung Galaxy S III
** Changed in: libmtp (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1015010 Title: Cannot connect to Samsung Galaxy S III Status in libmtp package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: libmtp can detect a Samsung Galaxy S III (GT-I9300, also known as the Galaxy S3) but cannot connect to it: $ mtp-detect libmtp version: 1.1.3 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. Found 1 device(s): Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 21 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. $ lsusb -vv -d 04e8:6860 Bus 002 Device 021: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x6860 GT-I9100 Phone [Galaxy S II] bcdDevice4.00 iManufacturer 2 SAMSUNG iProduct3 SAMSUNG_Android iSerial 4 4df1bc903e874f25 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 96mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 5 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 14 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 105 bNumInterfaces 3 bConfigurationValue 2 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 96mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 5 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
You know, it's getting to be somewhat annoying. I have very limited bandwidth here. Why don't you back out the patch already until a proper solution is found? I will happily continue to test but as you can see it does take me some time. The test case is pretty clear, why can you not be bothered to test yourself? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251960] Re: Btrfs crash during defrag after enabling skinny extents
Ubuntu has not shipped a btrfs package for a long time, moving to kernel bugs for triage. This bug is pretty old. Did anyone affected by this experience it with xenial or later? ** Package changed: btrfs (Ubuntu) => linux (Ubuntu) ** 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/1251960 Title: Btrfs crash during defrag after enabling skinny extents Status in linux package in Ubuntu: Incomplete Bug description: uname -a Linux thecus 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 i686 i686 i686 GNU/Linux cat /etc/issue Ubuntu 13.10 \n \l Unmounted file system ran btrfstune -x /dev/sdf2 remount file system successfully. Dmessage noted that skinny extents were enabled. Ran find -xdev \( -type f -o -type d \) -exec btrfs filesystem defragment -- {} + on the volume. After about 3 minutes, kernel panic and crash. [ 575.289734] BUG: unable to handle kernel paging request at 4839 [ 575.293639] IP: [] i915_gem_inactive_shrink+0xa8/0x150 [i915] [ 575.293639] *pdpt = 1bf56001 *pde = [ 575.293639] Oops: [#1] SMP [ 575.293639] Modules linked in: ppdev(F) microcode(F) serio_raw(F) lpc_ich bonding(F) i915 shpchp video(F) https://lkml.org/lkml/2013/5/9/404drm_kms_helper mac_hid parport_pc(F) drm i2c_algo_bit lp(F) parport(F) nfsd(F) auth_rpcgss(F) [ 575.293639] CPU: 0 PID: 25 Comm: kswapd0 Tainted: GF 3.11.0-13-generic #20-Ubuntu [ 575.293639] Hardware name:/i854GML-LPC47M182, BIOS 6.00 PG 06/21/2007 [ 575.293639] task: dd554d40 ti: da9d4000 task.ti: da9d4000 [ 575.293639] EIP: 0060:[] EFLAGS: 00010292 CPU: 0 [ 575.293639] EIP is at i915_gem_inactive_shrink+0xa8/0x150 [i915] [ 575.293639] EAX: 47b1 EBX: de73d6f0 ECX: de73d6b8 EDX: 4829 [ 575.293639] ESI: EDI: dbe8a000 EBP: da9d5e6c ESP: da9d5e54 [ 575.293639] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 575.293639] CR0: 8005003b CR2: 4839 CR3: 1bf54000 CR4: 07f0 [ 575.293639] Stack: [ 575.293639] dbe8a014 0100 0080 de73d6cc da9d5ed4 c11259a8 [ 575.293639] da9d5ea0 c115fda7 da9d5e7c 019d5e7c dd448800 da9d5ebc da9d5ea0 0080 [ 575.293639] 0001b56d dec99e38 0080 0001b56c 0020 [ 575.293639] Call Trace: [ 575.293639] [] shrink_slab+0x88/0x2c0 [ 575.293639] [] ? mem_cgroup_iter+0x147/0x2a0 [ 575.293639] [] kswapd+0x443/0x8b0 [ 575.293639] [] ? mem_cgroup_shrink_node_zone+0x100/0x100 [ 575.293639] [] kthread+0x94/0xa0 [ 575.293639] [] ? kthread_create_on_node+0x40/0xc0 [ 575.293639] [] ret_from_kernel_thread+0x1b/0x28 [ 575.293639] [] ? kthread_create_on_node+0xc0/0xc0 [ 575.293639] Code: 00 85 ff 75 08 8b 50 38 c1 ea 0c 01 d6 8b 50 68 39 d1 8d 42 98 75 e4 8b 53 24 83 c3 24 39 d3 8d 42 88 74 2f 8d b4 26 00 00 00 00 80 88 00 00 00 00 e0 01 00 75 12 8b 90 90 00 05 [ 575.293639] EIP: [] i915_gem_inactive_shrink+0xa8/0x150 [i915] SS:ESP 0068:da9d5e54 [ 575.293639] CR2: 4839 [ 575.513341] ---[ end trace 95a74918ec61aaea ]--- [ 581.148046] BUG: unable to handle kernel paging request at 000200da [ 581.152003] IP: [<000200da>] 0x200d9 [ 581.152003] *pdpt = 1d65e001 *pde = [ 581.152003] Oops: 0010 [#2] SMP [ 581.152003] Modules linked in: ppdev(F) microcode(F) serio_raw(F) lpc_ich bonding(F) i915 shpchp video(F) drm_kms_helper mac_hid parport_pc(F) drm i2c_algo_bit lp(F) parport(F) nfsd(F) auth_rpcgss(F) [ 581.152003] CPU: 0 PID: 765 Comm: rpcbind Tainted: GF D 3.11.0-13-generic #20-Ubuntu [ 581.152003] Hardware name:/i854GML-LPC47M182, BIOS 6.00 PG 06/21/2007 [ 581.152003] task: de7f8000 ti: dcc9 task.ti: dcc9 [ 581.152003] EIP: 0060:[<000200da>] EFLAGS: 00010206 CPU: 0 [ 581.152003] EIP is at 0x200da [ 581.152003] EAX: dc7329d0 EBX: dcc91c40 ECX: 000200da EDX: dcc91d28 [ 581.152003] ESI: dc7329d0 EDI: EBP: dcc91f90 ESP: dcc91be0 [ 581.152003] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 581.152003] CR0: 80050033 CR2: 000200da CR3: 1cce4000 CR4: 07f0 [ 581.152003] Stack: [ 581.152003] c117be66 01c9c37e de7f8000 01ff dcc91f98 01c9c37e dcc91c20 [ 581.152003] 0001 bfc3c21c dcc91c28 0002 0001 dcc91c68 0001 [ 581.152003] 4d5a8e4c 0087 0007 0005 002000c3 0006 002000c3 [ 581.152003] Call Trace: [ 581.152003] [] ? do_sys_poll+0x2d6/0x530 [ 581.152003] [] ? try_to_wake_up+0x14b/0x240 [ 581.152003] [] ? default_wake_function+0x10/0x20 [ 581.152003] [] ? autoremove_wake_function+0x1c/0x40 [ 581.152003] [] ? wake_bit_function+0x4e/0x50 [ 581.152003] [] ? __wake_up_common+0x47/0x70 [ 581.152
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I've downloaded the kernel from http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/ and https://launchpad.net/~canonical-kernel-security- team/+archive/ubuntu/ppa/+build/11038082 now. Both kernels have the same problem/regression (verified with "sudo btrfs fi show /") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I apologize for the delayed response, I was travelling. Yes, the error message is the same as for the original report. Then it was triggered by a call to lsattr, now by calling btrfs to create a snapshot. The released kernels do not have the originally reported problem with lsattr but regressed with the call to create a snapshot. I originally found a regression when calling "btrfs fi show" which one only emit a one-liner with the program version but not the requested version with information about the btrfs partitions. I have not yet had the chance to test the xenial or yakkety kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Thank you for providing the test kernel. Unfortunately, it does not fix the regression. I installed the trusty kernel. I did not install the linux-tools-* packages as it would have uninstalled the trusty version of linux-tools-generic. I have the i386 version of that package installed but I run an amd64 kernel. Could that lead to problems? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
The "I don't give a sh.."-attitude displayed here towards a regression is shocking. Why do I even bother to test? The regression is apparently much more severe to obot. I can no longer take a snapshot of my btrfs filesystem. $ sudo btrfs sub snapshot -r /mnt/LTS/@home/ /mnt/LTS/snapshots/home-daily-$(date +%F) Create a readonly snapshot of '/mnt/LTS/@home/' in '/mnt/LTS/snapshots/home-daily-2016-10-31' ERROR: cannot snapshot '/mnt/LTS/@home/' - Inappropriate ioctl for device ** Changed in: linux (Ubuntu) Status: Fix Released => Triaged ** Changed in: linux (Ubuntu Trusty) Status: Fix Released => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Triaged Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Released Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Triaged Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Brad, how can you set this to verified and release when that introduces a pretty severe regression? OMG!! ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Released Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Released Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Yes, regression from -96 to -97 verified on trusty. ** Tags removed: verification-done-trusty ** Tags added: regression-proposed verification-needed-trusty ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Triaged Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I think there might be a regression with this kernel. "sudo btrfs fi show" no longer works and only puts out "Btrfs v3.12" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Thanks. This works well in trusty. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1015010] Re: Cannot connect to Samsung Galaxy S III
Alistair, can you confirm the fix as reported by John in #43? ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1015010 Title: Cannot connect to Samsung Galaxy S III Status in libmtp package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: libmtp can detect a Samsung Galaxy S III (GT-I9300, also known as the Galaxy S3) but cannot connect to it: $ mtp-detect libmtp version: 1.1.3 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. Found 1 device(s): Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 21 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. $ lsusb -vv -d 04e8:6860 Bus 002 Device 021: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x6860 GT-I9100 Phone [Galaxy S II] bcdDevice4.00 iManufacturer 2 SAMSUNG iProduct3 SAMSUNG_Android iSerial 4 4df1bc903e874f25 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 96mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 5 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 14 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 105 bNumInterfaces 3 bConfigurationValue 2 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 96mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 5 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 E
[Kernel-packages] [Bug 374105] Re: linux-image-$ver packages leave cruft behind
Still present on trusty and it seems to be a problem with tp-smapi-dkms. $ find /lib/modules/3.13.0-65-generic/ /lib/modules/3.13.0-65-generic/ /lib/modules/3.13.0-65-generic/updates /lib/modules/3.13.0-65-generic/updates/dkms /lib/modules/3.13.0-65-generic/updates/dkms/thinkpad_ec.ko /lib/modules/3.13.0-65-generic/updates/dkms/tp_smapi.ko /lib/modules/3.13.0-65-generic/updates/dkms/hdaps.ko /lib/modules/3.13.0-65-generic/updates/dkms/vboxdrv.ko /lib/modules/3.13.0-65-generic/updates/dkms/vboxnetadp.ko /lib/modules/3.13.0-65-generic/updates/dkms/vboxnetflt.ko /lib/modules/3.13.0-65-generic/updates/dkms/vboxpci.ko /lib/modules/3.13.0-65-generic/modules.dep /lib/modules/3.13.0-65-generic/modules.dep.bin /lib/modules/3.13.0-65-generic/modules.alias /lib/modules/3.13.0-65-generic/modules.alias.bin /lib/modules/3.13.0-65-generic/modules.softdep /lib/modules/3.13.0-65-generic/modules.symbols /lib/modules/3.13.0-65-generic/modules.symbols.bin /lib/modules/3.13.0-65-generic/modules.builtin.bin /lib/modules/3.13.0-65-generic/modules.devname $ ll /boot/*65* ls: cannot access /boot/*65*: No such file or directory ** Also affects: tp-smapi (Ubuntu) Importance: Undecided Status: New ** Changed in: tp-smapi (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/374105 Title: linux-image-$ver packages leave cruft behind Status in linux package in Ubuntu: Confirmed Status in tp-smapi package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: New Bug description: $ ll /lib/modules/ total 6,0K drwxr-xr-x 8 root root 1,0K 2009-03-10 02:41 2.6.24-23-386 drwxr-xr-x 2 root root 1,0K 2009-03-23 05:13 2.6.28-10-generic drwxr-xr-x 5 root root 1,0K 2009-04-20 08:55 2.6.28-11-generic drwxr-xr-x 2 root root 1,0K 2009-03-17 05:54 2.6.28-4-386 drwxr-xr-x 3 root root 1,0K 2009-03-15 04:12 2.6.28-8-generic drwxr-xr-x 3 root root 1,0K 2009-03-12 02:18 2.6.28-9-generic $ dpkg -l linux-image*|grep ii ii linux-image2.6.28.11.15 Generic Linux kernel image. ii linux-image-2.6.24-23-386 2.6.24-23.48 Linux kernel image for version 2.6.24 on i38 ii linux-image-2.6.28-11-generic 2.6.28-11.42 Linux kernel image for version 2.6.28 on x86 ii linux-image-generic2.6.28.11.15 Generic Linux kernel image $ dpkg -S /lib/modules/*/modules.seriomap linux-image-2.6.24-23-386: /lib/modules/2.6.24-23-386/modules.seriomap dpkg: /lib/modules/2.6.28-10-generic/modules.seriomap not found. dpkg: /lib/modules/2.6.28-11-generic/modules.seriomap not found. 2.6.28-10-generic looks like a superseded package that did not properly clean up after itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/374105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
@All, please let us know what your current status with regards to this ticket. Are you still affected? -- 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/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
Konrad, that's premature. This problem was reported for example against trusty which until very recently was the latest LTS. Please stop closing tickets just because they are old. You can always ask if people are still affected by this problem and then close the ticket if there is no response. ** Changed in: bluez (Ubuntu) Status: Invalid => 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/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462169] Re: CVE-2014-9731
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1462169 Title: CVE-2014-9731 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Stat
[Kernel-packages] [Bug 1462173] Re: CVE-2015-4167
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1462173 Title: CVE-2015-4167 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Stat
[Kernel-packages] [Bug 1453256] Re: CVE-2015-3636
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1453256 Title: CVE-2015-3636 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Fix Released 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: In
[Kernel-packages] [Bug 1260616] Re: CVE-2013-6432
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1260616 Title: CVE-2013-6432 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix 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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Won't Fix Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Statu
[Kernel-packages] [Bug 1465400] Re: CVE-2015-1328
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1465400 Title: CVE-2015-1328 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Invalid 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Fix Released 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: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Sta
[Kernel-packages] [Bug 1462175] Re: CVE-2015-4170
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1462175 Title: CVE-2015-4170 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid 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: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1285053] Re: CVE-2014-2038
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1285053 Title: CVE-2014-2038 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix 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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in
[Kernel-packages] [Bug 1453216] Re: CVE-2014-3534
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1453216 Title: CVE-2014-3534 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid 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: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-ti-omap4 sourc
[Kernel-packages] [Bug 1462165] Re: CVE-2014-9729
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1462165 Title: CVE-2014-9729 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Stat
[Kernel-packages] [Bug 1260619] Re: CVE-2013-7026
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1260619 Title: CVE-2013-7026 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix 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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Won't Fix Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Sta
[Kernel-packages] [Bug 1293721] Re: CVE-2014-0102
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1293721 Title: CVE-2014-0102 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix 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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in Viv
[Kernel-packages] [Bug 1274684] Re: CVE-2014-1690
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1274684 Title: CVE-2014-1690 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: 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: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux source package in Trusty: Invalid 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: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid St
[Kernel-packages] [Bug 1453207] Re: CVE-2014-2889
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1453207 Title: CVE-2014-2889 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid 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: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1260615] Re: CVE-2013-6431
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1260615 Title: CVE-2013-6431 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix 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-lts-wily package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix 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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Won't Fix Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix 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: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Statu
[Kernel-packages] [Bug 1477026] Re: CVE-2015-3290
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New => Won't Fix -- 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/1477026 Title: CVE-2015-3290 Status in linux package in Ubuntu: Invalid 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-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released 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: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed 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-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: Fix Released 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 source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1364035] Re: armhf: dtb movement from /lib/firmware/$(uname -r) to /boot/$(uname -r)
** Changed in: linux-hammerhead (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-raspi2 (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: linux-meta (Ubuntu Utopic) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1364035 Title: armhf: dtb movement from /lib/firmware/$(uname -r) to /boot/$(uname -r) Status in kernel-wedge package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in kernel-wedge source package in Utopic: Won't Fix Status in linux source package in Utopic: Won't Fix Status in linux-hammerhead source package in Utopic: Won't Fix Status in linux-meta source package in Utopic: Won't Fix Status in linux-raspi2 source package in Utopic: Won't Fix Bug description: This is a placeholder to coordinate all the efforts required to move the DTB files from the previous location /lib/firmware/$(uname -r) to /boot/$(uname -r) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-wedge/+bug/1364035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp