[Kernel-packages] [Bug 1460674] Re: [i915_bpo] Rebase driver to 4.2~pre
Certification team has completed the testing for assigned platforms. No regression observed. For those bug that happen on stock kernel, please refer to bug 1464226 (180 rotation blackout) and bug 1465108 (Blink on VT switching) ** Tags removed: needs-cert-testing ** Tags added: cert-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460674 Title: [i915_bpo] Rebase driver to 4.2~pre Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: Upstream i915 code has been feature-frozen for drm-next, and rebasing i915_bpo to it is fairly simple. We need all the drm_atomic* changes to date though, in order to avoid oopses loading the driver. Thankfully i915_bpo is the only driver that uses them (besides msm), so there's no chance of regressing other drivers that we care about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/comments/1 . ** Tags added: cherry-pick ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: In Progress = Fix Released ** Tags added: kernel-fixed-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/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: Fix Released Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452293] Re: kernel crash when compiling linux-4.1-rc2 with make -j20
*** This bug is a duplicate of bug 1440536 *** https://bugs.launchpad.net/bugs/1440536 ** This bug has been marked a duplicate of bug 1440536 Oops __d_lookup+0x88/0x194 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452293 Title: kernel crash when compiling linux-4.1-rc2 with make -j20 Status in linux package in Ubuntu: Confirmed Bug description: Kernel crash whilst building new kernel: Steps to reproduce: wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz tar xf linux-4.1-rc2.tar.xz cd linux-4.1-rc2/ make mrproper make olddefconfig make -j20 I noticed that the output from the build had stopped then noticed the following messages (via dmesg): [ 15.285274] random: nonblocking pool is initialized [ 15.633718] xgene-enet 1702.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 2541.173142] Unable to handle kernel paging request at virtual address 1018 [ 2541.181062] pgd = ffc3ec61d000 [ 2541.184449] [1018] *pgd=, *pud= [ 2541.191476] Internal error: Oops: 9605 [#1] SMP [ 2541.196331] Modules linked in: rtc_xgene xgene_rng uio_pdrv_genirq uio autofs4 realtek ahci_xgene libahci_platform xgene_enet libahci aes_neon_blk ablk_ helper cryptd [ 2541.211214] CPU: 2 PID: 17206 Comm: sh Not tainted 3.19.0-15-generic #15-Ubuntu [ 2541.218488] Hardware name: APM X-Gene Mustang board (DT) [ 2541.223775] task: ffc3ec2d3d40 ti: ffc0fec1c000 task.ti: ffc0fec1c000 [ 2541.231236] PC is at __d_lookup+0x88/0x194 [ 2541.235324] LR is at d_lookup+0x3c/0x64 [ 2541.239148] pc : [ffc00022a120] lr : [ffc00022a268] pstate: 0145 [ 2541.246509] sp : ffc0fec1fb40 [ 2541.249807] x29: ffc0fec1fb40 x28: 00020241 [ 2541.255114] x27: 1b2865a6 x26: ffc0fec1fe88 [ 2541.260421] x25: x24: ffc0ff01d02d [ 2541.265728] x23: 000b x22: ffc0fec1fda0 [ 2541.271045] x21: ffc3b80ebd80 x20: 0ff8 [ 2541.276353] x19: 1000 x18: [ 2541.281659] x17: 002000118748 x16: ffc00020f430 [ 2541.286967] x15: 0008 x14: 636e692f8134366d [ 2541.292275] x13: 72612f8168637261 x12: 492d812069706175 [ 2541.297594] x11: x10: fefefefefefefeff [ 2541.302904] x9 : x8 : ffc3e9ed2f40 [ 2541.308221] x7 : x6 : 003f [ 2541.313532] x5 : ffc0ff01d000 x4 : 0015 [ 2541.318848] x3 : ffc000b64f60 x2 : 9e370001 [ 2541.324155] x1 : ffc3eec0 x0 : 001e7194 [ 2541.330959] Process sh (pid: 17206, stack limit = 0xffc0fec1c058) [ 2541.337367] Stack: (0xffc0fec1fb40 to 0xffc0fec2) [ 2541.343088] fb40: fec1fba0 ffc0 0022a268 ffc0 dd6e 00b5a000 ffc0 [ 2541.351235] fb60: fec1fda0 ffc0 b80ebd80 ffc3 0301 b80ebd80 ffc3 [ 2541.359378] fb80: 0001 fec1fe88 ffc0 fec1fd90 ffc0 00020241 [ 2541.367516] fba0: fec1fbd0 ffc0 0021b0e0 ffc0 fec1fd40 ffc0 b80ebd80 ffc3 [ 2541.375654] fbc0: fec1fda0 ffc0 fec1fca7 ffc0 fec1fc10 ffc0 0021d790 ffc0 [ 2541.383792] fbe0: fec1fd40 ffc0 b8113458 ffc3 b80ebd80 ffc3 ff01d000 ffc0 [ 2541.391930] fc00: fec1fd3c ffc0 fec1fd90 ffc0 fec1fcb0 ffc0 002204c8 ffc0 [ 2541.400066] fc20: fe52d000 ffc0 fec1fd90 ffc0 fec1fe88 ffc0 ff01d000 ffc0 [ 2541.408204] fc40: 0041 ff9c 011a 0038 [ 2541.416343] fc60: 00b6e000 ffc0 fec1fcb0 ffc0 002204a4 ffc0 [ 2541.424481] fc80: 0001 ff01d000 ffc0 fe52d000 ffc0 0022 (the rest is attached) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17.2-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed May 6 14:08:16 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron:
[Kernel-packages] [Bug 1465249] Re: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmodplug in Ubuntu. https://bugs.launchpad.net/bugs/1465249 Title: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1 Status in libmodplug package in Ubuntu: New Bug description: ubuntu技术人员，你好，我电脑每次开机都会显示有个错误提示，提示此软件安装有误。 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libmodplug1 1:0.8.8.4-4.1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Sun Jun 14 15:23:11 2015 DuplicateSignature: package:libmodplug1:1:0.8.8.4-4.1:您已经安装并配置了软件包 libmodplug1 ErrorMessage: 您已经安装并配置了软件包 libmodplug1 InstallationDate: Installed on 2015-06-13 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: libmodplug Title: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmodplug/+bug/1465249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465108] Re: [Dell Vostro 3458] System will start blinking after switch to virtual terminal
Po-Hsu Lin, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/vostro-14-3458-laptop/drivers an update to your computer's buggy and outdated BIOS is available (A01). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-a01 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465108 Title: [Dell Vostro 3458] System will start blinking after switch to virtual terminal Status in linux package in Ubuntu: Incomplete Bug description: On this I+N hybrid graphic system, when switching to Virtual Terminal with Ctrl + Alt + F1, the display will start blinking and Steps: 1. Install 14.04.2 + update 2. Switch to VT with Ctrl + Alt + F1 3. Switch back with Ctrl + Alt + F7 Expected result: Everything should work as expected. Actual result: It will start blinking, error message could be found in dmesg output, please find the attachment for the video. [ 3765.731436] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1205 F pulseaudio /dev/snd/controlC0: ubuntu 1205 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 14 22:48:50 2015 HibernationDevice: RESUME=UUID=e9508693-344c-4086-8491-70a51cabd161 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 3458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=ed5bbf8c-21d8-4bca-ae2b-d803cc0fc1ad ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: X13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX13:bd01/07/2015:svnDellInc.:pnVostro3458:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465178] Re: Microcode SW error detected. Restarting 0x2000000 on connecting to AC network with iwlwifi-7265-ucode-25.228.9.0
Updated to 3.16.0-39-generic #53~14.04.1-Ubuntu - no change in behaviour -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1465178 Title: Microcode SW error detected. Restarting 0x200 on connecting to AC network with iwlwifi-7265-ucode-25.228.9.0 Status in linux-lts-utopic package in Ubuntu: New Bug description: When trying to connect to an 802.11AC network using an Intel 7265 with firmware iwlwifi-7265-ucode-25.228.9.0 on kernel 3.16.0-38-generic #52~14.04.1-Ubuntu, the error Microcode SW error detected. Restarting 0x200. is received, the card crashes and can't connect to the network. The same card/driver/firmware combination performs well on 2.4GHz networks, and also 802.11a. Jun 15 14:02:38 nomad115 NetworkManager[911]: info NetworkManager state is now DISCONNECTED Jun 15 14:02:36 nomad115 wpa_supplicant[962]: wlan0: CTRL-EVENT-SCAN-STARTED Jun 15 14:02:38 nomad115 wpa_supplicant[962]: wlan0: Reject scan trigger since one is already pending Jun 15 14:02:38 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: inactive - disconnected Jun 15 14:02:39 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: disconnected - inactive Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) starting connection 'chocolateblock5 1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info NetworkManager state is now CONNECTING Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: prepare - config (reason 'none') [40 50 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0/wireless): connection 'chocolateblock5 1' has security, and secrets exist. No new secrets needed. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'ssid' value 'chocolateblock5' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'scan_ssid' value '1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'key_mgmt' value 'WPA-PSK' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'psk' value 'omitted' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: set interface ap_scan to 1 Jun 15 14:02:40 nomad115 wpa_supplicant[962]: wlan0: SME: Trying to authenticate with 30:b5:c2:84:95:0b (SSID='chocolateblock5' freq=5640 MHz) Jun 15 14:02:40 nomad115 kernel: [ 362.919913] wlan0: authenticate with 30:b5:c2:84:95:0b Jun 15 14:02:40 nomad115 kernel: [ 362.922550] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Jun 15 14:02:40 nomad115 kernel: [ 362.922554] iwlwifi :03:00.0: CSR values: Jun 15 14:02:40 nomad115 kernel: [ 362.922556] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Jun 15 14:02:40 nomad115 kernel: [ 362.922598] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489200 Jun 15 14:02:40 nomad115 kernel: [ 362.922653] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X0040 Jun 15 14:02:40 nomad115 kernel: [ 362.922708] iwlwifi :03:00.0: CSR_INT: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922763] iwlwifi :03:00.0: CSR_INT_MASK: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922818] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922874] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922929] iwlwifi :03:00.0: CSR_RESET: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922984] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403cd Jun 15 14:02:40 nomad115 kernel: [ 362.923039] iwlwifi :03:00.0: CSR_HW_REV: 0X0210 Jun 15 14:02:40 nomad115 kernel: [ 362.923094] iwlwifi :03:00.0: CSR_EEPROM_REG: 0Xd5d5 Jun 15 14:02:40 nomad115 kernel: [ 362.923150] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X Jun 15 14:02:40 nomad115
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
Michael Sharman, thank you for reporting this and helping make Ubuntu better. As per https://www.asus.com/Notebooks_Ultrabooks/N56VM/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (214). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-214 ** 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/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Incomplete Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session,
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
I do not have the hardware. Was there a warning about sanity check? I think the problem is in that same 0.7 btusb version in 3.16 and my module. Can you change it yourself to 0.7.1? I am out of my main computer now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458470] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1458470 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458470 Title: no uevent after ejecting CD-ROM Status in linux package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file /lib/udev/rules.d/10-test.rules with the content KERNEL==sr0, RUN+=/usr/bin/touch /tmp/test.txt does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
Yes linux-firmware has been installed from your PPA. But the log says that the board do not need the firmware to be uploaded in the board which is weird because in 3.13 the firmware was uploaded. Did it work on your side on 14.04.2 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465178] Re: Microcode SW error detected. Restarting 0x2000000 on connecting to AC network with iwlwifi-7265-ucode-25.228.9.0
sorry, mirror was out of date, now on 3.16.0-40-generic #54~14.04.1-Ubuntu - no change in behaviour -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1465178 Title: Microcode SW error detected. Restarting 0x200 on connecting to AC network with iwlwifi-7265-ucode-25.228.9.0 Status in linux-lts-utopic package in Ubuntu: New Bug description: When trying to connect to an 802.11AC network using an Intel 7265 with firmware iwlwifi-7265-ucode-25.228.9.0 on kernel 3.16.0-38-generic #52~14.04.1-Ubuntu, the error Microcode SW error detected. Restarting 0x200. is received, the card crashes and can't connect to the network. The same card/driver/firmware combination performs well on 2.4GHz networks, and also 802.11a. Jun 15 14:02:38 nomad115 NetworkManager[911]: info NetworkManager state is now DISCONNECTED Jun 15 14:02:36 nomad115 wpa_supplicant[962]: wlan0: CTRL-EVENT-SCAN-STARTED Jun 15 14:02:38 nomad115 wpa_supplicant[962]: wlan0: Reject scan trigger since one is already pending Jun 15 14:02:38 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: inactive - disconnected Jun 15 14:02:39 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: disconnected - inactive Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) starting connection 'chocolateblock5 1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info NetworkManager state is now CONNECTING Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: prepare - config (reason 'none') [40 50 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0/wireless): connection 'chocolateblock5 1' has security, and secrets exist. No new secrets needed. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'ssid' value 'chocolateblock5' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'scan_ssid' value '1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'key_mgmt' value 'WPA-PSK' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'psk' value 'omitted' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: set interface ap_scan to 1 Jun 15 14:02:40 nomad115 wpa_supplicant[962]: wlan0: SME: Trying to authenticate with 30:b5:c2:84:95:0b (SSID='chocolateblock5' freq=5640 MHz) Jun 15 14:02:40 nomad115 kernel: [ 362.919913] wlan0: authenticate with 30:b5:c2:84:95:0b Jun 15 14:02:40 nomad115 kernel: [ 362.922550] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Jun 15 14:02:40 nomad115 kernel: [ 362.922554] iwlwifi :03:00.0: CSR values: Jun 15 14:02:40 nomad115 kernel: [ 362.922556] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Jun 15 14:02:40 nomad115 kernel: [ 362.922598] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489200 Jun 15 14:02:40 nomad115 kernel: [ 362.922653] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X0040 Jun 15 14:02:40 nomad115 kernel: [ 362.922708] iwlwifi :03:00.0: CSR_INT: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922763] iwlwifi :03:00.0: CSR_INT_MASK: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922818] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922874] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922929] iwlwifi :03:00.0: CSR_RESET: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922984] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403cd Jun 15 14:02:40 nomad115 kernel: [ 362.923039] iwlwifi :03:00.0: CSR_HW_REV: 0X0210 Jun 15 14:02:40 nomad115 kernel: [ 362.923094] iwlwifi :03:00.0: CSR_EEPROM_REG: 0Xd5d5 Jun 15 14:02:40 nomad115 kernel: [ 362.923150] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
@Pilot6 : Tested your DKMS on Ubuntu 14.04.2 3.16 , still nothing discovered. It seems we really need to dig what's wrong with 3.16. I'm always surprised that realtek does not deliver DKMS for Ubuntu LTS directly, they would spare a lot of 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/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
Did you also install linux-firmware from my ppa. Firmware for bluetooth has been added to 1.144 that is in Ubuntu 15.10. Without the firmware it will not work. I made a separate package for bt-firmware but it will conflict with nwe linux-firmware, that has same files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458470] Re: no uevent after ejecting CD-ROM
In the past physically ejecting /dev/sr0 has worked for me. A recent apport-collect (while this report was already made) against linux (Ubuntu) was done here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463627 ** 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/1458470 Title: no uevent after ejecting CD-ROM Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file /lib/udev/rules.d/10-test.rules with the content KERNEL==sr0, RUN+=/usr/bin/touch /tmp/test.txt does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460674] Re: [i915_bpo] Rebase driver to 4.2~pre
** Changed in: linux (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460674 Title: [i915_bpo] Rebase driver to 4.2~pre Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Upstream i915 code has been feature-frozen for drm-next, and rebasing i915_bpo to it is fairly simple. We need all the drm_atomic* changes to date though, in order to avoid oopses loading the driver. Thankfully i915_bpo is the only driver that uses them (besides msm), so there's no chance of regressing other drivers that we care about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464561] Re: [Asus UX303LN] several hotkeys don't produce evdev event
gratefulfrog, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-input) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger- lists.html . It can take a day for the new e-mail to show up in the respective archive. Thank you for your understanding. ** Tags removed: kernel-bug-exists-upstream-4.1.0-040100rc8 ** Tags added: kernel-bug-exists-upstream-4.1-rc8 ** Summary changed: - [Asus UX303LN] several hotkeys don't produce evdev event + [Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event ** Description changed: - Running Xubuntu on an Asus UX303LN laptop. - The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random mouse movements, making it impossible to enter text in the right place. When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off. Also, if the bluetooth connection is lost, then I can do nothing and have to reboot! - - I have no idea how to debug this but would be happy to help. - - Another hotkey that does not work is F2 airplane mode. This one is of - no importance to me, but I mention it for completeness. - - I am really hoping for a fix! - - I am a Ubuntu beta-tester from long ago, and helped on the 1st 64bit - version! - - Let me know, please!, - Cheers, - Bob - - I have attached all the files specified on the hotkey bug reporting - page. I put them in an archive since that seems to be the only option - for attaching multiple files? - - udevadm info --export-db udev-db.txt - dmesg dmesg.log - sudo lsinput lsinput.log - xkbcomp -xkb :0 - xkbcomp.txt - setxkbmap -print xkbmap.txt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jun 12 10:05:56 2015 InstallationDate: Installed on 2015-05-11 (31 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2a Intel Corp. - Bus 001 Device 002: ID 064e:9700 Suyin Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 064e:9700 Suyin Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LNB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=eba1a0f5-161a-4061-99a4-b5598f7692c1 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LNB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LNB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.203:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LNB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464561 Title: [Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event Status in linux package in Ubuntu: Triaged Bug description: The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random mouse movements, making it impossible to enter text in the right place. When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off. Also, if the bluetooth connection is lost, then I can do nothing and have to reboot! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5
[Kernel-packages] [Bug 1465249] [NEW] package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1
Public bug reported: ubuntu技术人员，你好，我电脑每次开机都会显示有个错误提示，提示此软件安装有误。 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libmodplug1 1:0.8.8.4-4.1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Sun Jun 14 15:23:11 2015 DuplicateSignature: package:libmodplug1:1:0.8.8.4-4.1:您已经安装并配置了软件包 libmodplug1 ErrorMessage: 您已经安装并配置了软件包 libmodplug1 InstallationDate: Installed on 2015-06-13 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: libmodplug Title: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libmodplug (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmodplug in Ubuntu. https://bugs.launchpad.net/bugs/1465249 Title: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1 Status in libmodplug package in Ubuntu: New Bug description: ubuntu技术人员，你好，我电脑每次开机都会显示有个错误提示，提示此软件安装有误。 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libmodplug1 1:0.8.8.4-4.1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Sun Jun 14 15:23:11 2015 DuplicateSignature: package:libmodplug1:1:0.8.8.4-4.1:您已经安装并配置了软件包 libmodplug1 ErrorMessage: 您已经安装并配置了软件包 libmodplug1 InstallationDate: Installed on 2015-06-13 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: libmodplug Title: package libmodplug1 1:0.8.8.4-4.1 failed to install/upgrade: 您已经安装并配置了软件包 libmodplug1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmodplug/+bug/1465249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
So to install bt driver from my ppa run sudo apt-get install rtl8723au-bt-dkms linux-firmware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464983] Re: Black screen after after wake up from suspend
Dimon2242, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-1.27 ** Attachment removed: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+attachment/4414580/+files/lspci-vnvn.log ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464983 Title: Black screen after after wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: Notebook Acer Extensa 2510g When i change video on Intel HD, all is working! When i use NVidia 820m, after wake up i got black screen with console cursor in upper left corner. This problem on Proprietary and Nouveau. Version: Ubuntu 3.19.0-20.20-generic 3.19.8 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1404 F pulseaudio /dev/snd/controlC1: dmitry21 1404 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=85369393-b11e-4aa9-9876-f0fe071152a8 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Extensa 2510G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed root=UUID=62ba55e3-29b2-46df-a4a0-cdc272eafe4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462180] Re: Bad page map / bad pte
So far 4.1.0-040100rc7-generic has been running without a problem. Because this problem is intermittent I want to give it another week of running before marking it as fixed 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/1462180 Title: Bad page map / bad pte Status in linux package in Ubuntu: Incomplete Bug description: I have received very similar bugs on 3.13.0-53, 3.13-0.52, 3.13.0-51 and 3.13.0-49. I will be falling back to 3.13.0-45, which is the last kernel where I believe I didn't have this problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-49-generic 3.13.0-49.83 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 23:21:23 2015 HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002 InstallationDate: Installed on 2014-06-06 (363 days ago) InstallationMedia: Linux Mint 17 Qiana - Release amd64 20140530 IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-49-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-49-generic N/A linux-backports-modules-3.13.0-49-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459052] Re: CPU lockup
So far 4.1.0-040100rc7-generic has been running without a problem. Because this problem is intermittent I want to give it another week of running before marking it as fixed 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/1459052 Title: CPU lockup Status in linux package in Ubuntu: Incomplete Bug description: CPU lockup experienced. Appears to be a bad PTE? Left google-chrome running for hours, untouched. Went to use it again and chrome stopped responding. dmesg showed a CPU stuck. Farther up it showed a bad PTE. Machine passes memtest86. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 26 19:12:47 2015 HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002 InstallationDate: Installed on 2014-06-06 (354 days ago) InstallationMedia: Linux Mint 17 Qiana - Release amd64 20140530 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.utf8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1459052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463553] Re: accept() system call is inconsistent with bind(), connect()
Christopher, I did test the latest mainline kernel (4.0.5-040005-generic_4.0.5-040005.201506061639_amd64). Unless there's been another release over the last five days? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463553 Title: accept() system call is inconsistent with bind(), connect() Status in linux package in Ubuntu: Confirmed Bug description: Under kernel 3.2.0-54 and 3.9.3 (at least), the accept() system call in a PF_LOCAL, AF_LOCAL, SOCK_STREAM context returns an addrlen for the sockaddr_un structure that is too large by one. As the SUN_LEN macro of the sys/un.h header shows, the length of the structure is expected to be the strlen() of the sun_path member, plus that member's offset. This is the length used by bind() and connect(), in particular. But accept() consistently returns a length which includes the trailing null, and is thus too large by one. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-libc-dev 3.2.0-54.82 ProcVersionSignature: Ubuntu 3.2.0-54.82-virtual 3.2.50 Uname: Linux 3.2.0-54-virtual x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 May 26 09:41 seq crw-rw---T 1 root audio 116, 33 May 26 09:41 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Jun 9 16:14:40 2015 Dependencies: HibernationDevice: RESUME=UUID=476a0cd7-3578-49f2-b064-1d2151aa9f56 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet MachineType: innotek GmbH VirtualBox MarkForUpload: True PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-virtual root=UUID=c1c9d001-671e-44c6-8e7c-82f83d591195 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-54-virtual N/A linux-backports-modules-3.2.0-54-virtual N/A linux-firmware1.79.18 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462530] Re: multipath errors on vivid and wily kernel?
So, just to catch this bug up with where Oleg and I are. a.) curtin installs multipath-tools-boot into the target with /dev, /proc and /sys mounted. However, it has disabled services from starting through ChrootableTarget's allow_services=False [1]. That uses disable_services_in_root [2]. b.) the way /etc/multipath/bindings is normally created is through the multipath daemon running So, since we've blocked 'b', we dont get the file created and it doesn't get collected into the initramfs. To solve this, we'll need to run a blocking command with no other side effects in the chroot that creates /etc/multipath/bindings. Oleg found that that can be accomplished with /multipath -r'. sudo sh -c 'rm -Rf /etc/multipath multipath -r /dev/null ls -l /etc/multipath/bindings' Last thing, a minor point, there is a race condition in the normal install path that could lead to initramfs not collecting /etc/multipath/bindings. This is because the daemon is started in the background, and is not guaranteed to create /etc/multipath/bindings before update-initramfs is run by the trigger. -- [1] http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L289 [2] http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L257 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1462530 Title: multipath errors on vivid and wily kernel? Status in linux package in Ubuntu: Confirmed Bug description: Oleg and I got changes into curtin to fix bug 1371634. So that now we can boot into multipath iscsi devices on power. It seems to go well enough with trusty+hwe-u, but when trying vivid, I am seeing errors. Boot was failing in one case --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 8 16:05 seq crw-rw 1 root audio 116, 33 Jun 8 16:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.17.3-0ubuntu4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 15.10 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=962acf9e-cd1c-49b0-9264-801271cd510f ro console=hvc0 ProcLoadAvg: 0.08 0.12 0.10 1/1126 3818 ProcLocks: 1: FLOCK ADVISORY WRITE 2951 00:12:14557 0 EOF 2: POSIX ADVISORY WRITE 2952 00:12:43306 0 EOF 3: POSIX ADVISORY WRITE 2905 00:12:22701 0 EOF 4: POSIX ADVISORY WRITE 2965 00:12:18505 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.19.0-20-generic (buildd@fisher03) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #20-Ubuntu SMP Fri May 29 10:03:56 UTC 2015 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.144 RfKill: Error: [Errno 2] No such file or directory Tags: wily uec-images UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.693 GHz (cpu 72) max: 3.695 GHz (cpu 87) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No firmware implementation of function cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended
Hello Jan, Jan Rathmann [2015-06-15 14:06 -]: - If I run the ethtool command before 'systemctl suspend', the bug hasn't appeared so far - and it does not seem to matter if I run ethtool with the 'wol g' (enable WOL) or with the 'wol d' flag! That's indeed interesting -- After a clean boot, if you just do sudo ethtool eth0, it should show you the default WOL status; for me it is g. So running ethtool -s eth0 wol g *should* be a no-op, but maybe it actually isn't. - After I suspended my PC succesfull by running e.g. 'ethtool -s eth0 wol g ; systemctl suspend', the bug seems to stay away untill the next reboot even I simply use 'systemctl suspend' without ethtool on the next attempts to suspend. Yes, that's expected. The driver ought to remember the WOL status across suspends. Thus it seems that for proper suspend on my system it only matters that ethtool is poking the network card one-time after system startup, regardless if I use it to enable or disable WOL. I'll do further testing if it is indeed sufficient to put the ethtool command e.g. in /etc/rc.local to make the bug disappear without any additional steps. That'll be interesting indeed! It'll also show the kernel developers where to fix this. (Allthough it has no influence on the bug there is one relevant difference between running ethtool to disable or enable WOL before systemctl: If I disable WOL, my network is offline after resume, and I have do run 'ifdown eth0; ifup eth0' to make it work again. If I enable WOL instead, my network is up after suspend at least most of the time.) This could also explain bug 1270257, and its more recent duplicates like bug 1431582. Thanks for your investigations! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450396 Title: Gigabyte P35-DS3: does not stay suspended Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running cat /proc/acpi/wakeup | grep enabled if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like echo USB0 /proc/acpi/wakeup) had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as enabled. In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Marking as confirmed since I was able to reproduce on two different systems. ** Description changed: - $ cat /proc/version_signature + $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 - Filesystem 1K-blocks Used Available Use% Mounted on - /dev/md1 17444128 136371242927852 83% / - udev 950040 4 950036 1% /dev + Filesystem 1K-blocksUsed Available Use% Mounted on + /dev/vda17481832 4262872 2838904 61% / + udev 371920 4371916 1% /dev - $ cat /proc/version_signature + $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented - Filesystem 1K-blocks Used Available Use% Mounted on - /dev/md1 17444128 136382682926708 83% / - udev 950040 4 950036 1% /dev + Filesystem 1K-blocksUsed Available Use% Mounted on + /dev/vda17481832 4263012 2838764 61% / + udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. ** Description changed: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev - This is confirmed in an amd64 VM and on an amd64 system. + This is confirmed in an amd64 VM and on an amd64 system. It doesn't make + a difference if I use sudo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
This bug may be due to one of these commits: 7b0f287 kdb: fix incorrect counts in KDB summary command output df438af debugfs: leave freeing a symlink body until inode eviction I'll build a test kernel with these two commits reverted before starting the bisect process. I'll post a link to the test kernel shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended
Martin, I did check that and I think I can preliminary give results that are quite interesting: - If I run the ethtool command before 'systemctl suspend', the bug hasn't appeared so far - and it does not seem to matter if I run ethtool with the 'wol g' (enable WOL) or with the 'wol d' flag! - After I suspended my PC succesfull by running e.g. 'ethtool -s eth0 wol g ; systemctl suspend', the bug seems to stay away untill the next reboot even I simply use 'systemctl suspend' without ethtool on the next attempts to suspend. Thus it seems that for proper suspend on my system it only matters that ethtool is poking the network card one-time after system startup, regardless if I use it to enable or disable WOL. I'll do further testing if it is indeed sufficient to put the ethtool command e.g. in /etc/rc.local to make the bug disappear without any additional steps. (Allthough it has no influence on the bug there is one relevant difference between running ethtool to disable or enable WOL before systemctl: If I disable WOL, my network is offline after resume, and I have do run 'ifdown eth0; ifup eth0' to make it work again. If I enable WOL instead, my network is up after suspend at least most of the 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/1450396 Title: Gigabyte P35-DS3: does not stay suspended Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running cat /proc/acpi/wakeup | grep enabled if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like echo USB0 /proc/acpi/wakeup) had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as enabled. In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
** Tags added: performing-bisect ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] [NEW] regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Public bug reported: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1171550] Re: libftdi v1.0 is released
** Changed in: libftdi (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libftdi in Ubuntu. https://bugs.launchpad.net/bugs/1171550 Title: libftdi v1.0 is released Status in libftdi package in Ubuntu: Triaged Status in libftdi package in Debian: Fix Released Bug description: v1.0 of libftdi was released a few months ago. It would be great to resynchronize with this point release to take advantage of all of the bug fixes etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libftdi/+bug/1171550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461174] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi has an issue
Verified with the DKMS provided in comment #20, it looks good! tested with the mtr ubuntu.com command, with ~24500 packet sent, loss rate ~0.0% Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Realtek Wifi card rtl8723be [10ec:b723] WiFi has an issue Status in HWE Next Project: New Status in linux package in Ubuntu: Confirmed Bug description: My WiFi has an issue. --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1785 F pulseaudio /dev/snd/controlC0: u 1785 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c2a5715c-c92c-47fa-9aa2-c6f6e03f21bf InstallationDate: Installed on 2015-06-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP 455 G2 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=97d2645a-a2be-49ec-b1bd-37c43ab4eeb1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M75 Ver. 01.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2235 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 66.19 dmi.chassis.asset.tag: 73612P10CU dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM75Ver.01.06:bd07/25/2014:svnHewlett-Packard:pnHP455G2:pvrA3009CD10002:rvnHewlett-Packard:rn2235:rvrKBCVersion66.19:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 455 G2 dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1461174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Great, thanks, Jamie. I'll reproduce the bug and figure out which of these commits is the cause. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 77010] Re: Overuse of system beep without volume control
Here's the link I messed up in the previous post: https://www.debian- administration.org/article/110/Removing_annoying_console_beeps -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/77010 Title: Overuse of system beep without volume control Status in Ayatana: Invalid Status in One Hundred Papercuts: Fix Released Status in libgnome package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Status in module-init-tools package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Confirmed Status in libgnome source package in Karmic: Fix Released Status in linux source package in Karmic: Won't Fix Status in module-init-tools source package in Karmic: Fix Released Status in pulseaudio source package in Karmic: Won't Fix Bug description: System 'beeps' have become omnipresent in gnome. When I unplug my power cord, the notification system emits a system beep. When I try to do quick find in Firefox and I type a word that doesn't exist in the document, it beeps. When I tab-autocomplete in a gnome-terminal, it beeps if there are no completions. There are numerous other software packages that behave similarly. This is a problem for multiple reasons. First of all, there are some cases where the beep is used inappropriately -- I really *don't care* that my power cord is unplugged - in fact I unplugged it! I appreciate the technology advances that gnome-power-management has made in recent history, but I feel like I just want it to `go away' most of the time - I don't care about most of the things it informs me (besides low battery). Firefox has color feedback in the Find bar, why do I need auditory feedback too? Second of all, I can't control the volume of the beep, or disable it in all cases. In the case of the gnome-terminal I can disable the console bell, but that only solves a single instance of the problem. In most other cases, there is nothing I can do to prevent the beeps. This can be very obtrusive in quite environments, and simply annoying in other cases. On my laptop (recent Dell Latitude D620) the beep is incredibly loud - it is very noticeable. It would be great to have a toggle button in the system sound preferences, or better yet, a volume slider for the system bell. This is a large problem, affecting multiple packages and systems - I don't know the best way to fix it, but I do know that it is definitely an overall gnome UI issue. I've read that some programs literally just have the ASCII BEL coded into the source, so in some cases the problem may be unavoidable - I don't know enough of the technical details to recognize an appropriate solution. Any help dividing this into specific fixes for multiple projects or identifying the best place for an overall fix would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/dead-ayatana/+bug/77010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] Re: linux: 4.0.0-2.4 -proposed tracker
** Summary changed: - linux: 4.0.0-2.3 -proposed tracker + linux: 4.0.0-2.4 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 77010] Re: Overuse of system beep without volume control
Stumbled over this bug while unblacklisting 'pcspkr' in /etc/modprobe.d/blacklist.conf. There was a reference to this bug number. I hate the beeps for the most part, but unloading the kernel module means the `beep` utility doesn't work. I like to use it for notifications as I only have headphones on my desktop. This Debian post has a better fix in my opinion: https://www.debianadministration.org/article/110/Removing_annoying_console_beeps `beep` still works, but terminals and vim don't beep at me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/77010 Title: Overuse of system beep without volume control Status in Ayatana: Invalid Status in One Hundred Papercuts: Fix Released Status in libgnome package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Status in module-init-tools package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Confirmed Status in libgnome source package in Karmic: Fix Released Status in linux source package in Karmic: Won't Fix Status in module-init-tools source package in Karmic: Fix Released Status in pulseaudio source package in Karmic: Won't Fix Bug description: System 'beeps' have become omnipresent in gnome. When I unplug my power cord, the notification system emits a system beep. When I try to do quick find in Firefox and I type a word that doesn't exist in the document, it beeps. When I tab-autocomplete in a gnome-terminal, it beeps if there are no completions. There are numerous other software packages that behave similarly. This is a problem for multiple reasons. First of all, there are some cases where the beep is used inappropriately -- I really *don't care* that my power cord is unplugged - in fact I unplugged it! I appreciate the technology advances that gnome-power-management has made in recent history, but I feel like I just want it to `go away' most of the time - I don't care about most of the things it informs me (besides low battery). Firefox has color feedback in the Find bar, why do I need auditory feedback too? Second of all, I can't control the volume of the beep, or disable it in all cases. In the case of the gnome-terminal I can disable the console bell, but that only solves a single instance of the problem. In most other cases, there is nothing I can do to prevent the beeps. This can be very obtrusive in quite environments, and simply annoying in other cases. On my laptop (recent Dell Latitude D620) the beep is incredibly loud - it is very noticeable. It would be great to have a toggle button in the system sound preferences, or better yet, a volume slider for the system bell. This is a large problem, affecting multiple packages and systems - I don't know the best way to fix it, but I do know that it is definitely an overall gnome UI issue. I've read that some programs literally just have the ASCII BEL coded into the source, so in some cases the problem may be unavoidable - I don't know enough of the technical details to recognize an appropriate solution. Any help dividing this into specific fixes for multiple projects or identifying the best place for an overall fix would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/dead-ayatana/+bug/77010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1390223] Re: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel
An again:
zoolook@venkman:~$ sudo lxc-attach -n dana
root@dana:~# mailq
postqueue: warning: close: Permission denied
root@dana:~# uname -a
Linux dana 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
root@dana:~# dmesg | tail -n1
[ 3637.172284] audit: type=1400 audit(1434420248.087:2162): apparmor=DENIED
operation=file_perm profile=lxc-container-default name=public/showq
pid=29657 comm=postqueue requested_mask=r denied_mask=r fsuid=0 ouid=0
Seriously. Is anyone working on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix sockets on a candidate
3.16 backport kernel
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Utopic:
Confirmed
Status in linux source package in Vivid:
Fix Committed
Bug description:
I recently noticed a bunch of containers failing in a rather odd way
when running postfix.
The most visible example is when running mailq on an empty queue.
Without apparmor (unconfined container) I see that the queue is empty,
with apparmor, I get Permission denied.
That's all running as root so the permission denied looks a tiny bit
odd. Also, running the 3.13 kernel, I don't get any of that weirdness.
My guess is that it has to do with the work that went into the 3.16
kernel for socket mediation. In theory only systems that run the
utopic apparmor (which I DO NOT) should be seeing that kind of
behavior, but it looks like some code path isn't checking things
properly :)
== strace in unconfined container ==
chdir(/var/spool/postfix) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART,
0x7f8963a62c30}, {SIG_IGN, [], 0}, 8) = 0
getuid()= 0
socket(PF_LOCAL, SOCK_STREAM, 0)= 4
fcntl(4, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(4, F_SETFL, O_RDWR) = 0
connect(4, {sa_family=AF_LOCAL, sun_path=public/showq}, 110) = 0
poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4,
revents=POLLIN|POLLHUP}])
read(4, Mail queue is empty\n, 4096) = 20
poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4,
revents=POLLIN|POLLHUP}])
read(4, , 4096) = 0
write(1, Mail queue is empty\n, 20Mail queue is empty
) = 20
close(4)= 0
exit_group(0) = ?
+++ exited with 0 +++
== strace in confined container ==
chdir(/var/spool/postfix) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART,
0x7ffe62de4c30}, {SIG_IGN, [], 0}, 8) = 0
getuid()= 0
socket(PF_LOCAL, SOCK_STREAM, 0)= 4
fcntl(4, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(4, F_SETFL, O_RDWR) = 0
connect(4, {sa_family=AF_LOCAL, sun_path=public/showq}, 110) = 0
poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4,
revents=POLLIN|POLLHUP}])
read(4, 0x7ffe65b35c00, 4096) = -1 EACCES (Permission denied)
close(4)= 0
write(2, postqueue: warning: close: Permi..., 45postqueue: warning: close:
Permission denied
) = 45
sendto(3, 20Nov 6 20:40:42 postfix/post..., 78, MSG_NOSIGNAL, NULL, 0) =
78
exit_group(0) = ?
Kernel is a slightly outdated version of the kernel from the kernel team PPA:
Linux shell01 3.16.0-23-generic #31-Ubuntu SMP Thu Oct 23 20:13:35 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
If you think the latest build will improve this, I can test it, but
seeing how this is a production server, I can't just flip kernels
every 5 minutes (I'm running 3.16 to avoid a nasty btrfs bug on 3.13).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390223/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1431852] Re: Trackpad not working at all in Lenovo G570
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1431852 Title: Trackpad not working at all in Lenovo G570 Status in linux package in Ubuntu: Expired Bug description: After upgrading from Ubuntu 14.04 to 14.10 the trackpad doesn't work. I have tried installing the newest kernels 3.19, but doesn't make any difference. When typing xinput in command line, synaptic trackpad doesn't appear on list. Lenovo G570 Ubuntu 14.04 --- ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-06-19 (266 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: linux (not installed) Tags: utopic Uname: Linux 3.18.9-031809-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-06-19 (266 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: linux (not installed) Tags: utopic Uname: Linux 3.18.9-031809-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.14.7-0ubuntu8.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-06-19 (300 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: linux (not installed) Tags: utopic Uname: Linux 3.18.9-031809-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1431852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445279] Re: error adding kernel module usbserial
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445279 Title: error adding kernel module usbserial Status in linux package in Ubuntu: Expired Bug description: The error in dmesg is Request for unknown module key 'Magrathea: Glacier signing key: 6fca287c2573d09ca32c1980c0d763777a63d4f5' err -11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-49-generic 3.13.0-49.83 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charly 2899 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 16 20:17:33 2015 HibernationDevice: RESUME=UUID=b39b0154-7e07-417f-b4cc-e3de3e4d105e InstallationDate: Installed on 2014-01-06 (465 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Vostro 3550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=dbd79840-21e3-44ca-8676-642180bac2ab ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-49-generic N/A linux-backports-modules-3.13.0-49-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-06-01 (319 days ago) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0JGC48 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0JGC48:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445031] Re: package linux-image-3.16.0-34-generic 3.16.0-34.45 failed to install/upgrade: cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445031 Title: package linux-image-3.16.0-34-generic 3.16.0-34.45 failed to install/upgrade: cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic .dpkg-new': unexpected end of file or stream Status in linux package in Ubuntu: Expired Bug description: Boot = 0 MB ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-34-generic 3.16.0-34.45 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lambert2066 F pulseaudio /dev/snd/controlC0: lambert2066 F pulseaudio Date: Thu Apr 16 01:03:29 2015 DpkgTerminalLog: Preparing to unpack .../linux-image-3.16.0-34-generic_3.16.0-34.47_amd64.deb ... Done. Unpacking linux-image-3.16.0-34-generic (3.16.0-34.47) over (3.16.0-34.45) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.16.0-34-generic_3.16.0-34.47_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream DuplicateSignature: package:linux-image-3.16.0-34-generic:3.16.0-34.45:cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream HibernationDevice: RESUME=UUID=fe677f5d-fc91-456b-b28a-507c8e25999f InstallationDate: Installed on 2014-12-19 (118 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Acer Aspire M5810 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.16.0-34-generic 3.16.0-34.45 failed to install/upgrade: cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FMP55 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd08/29/2009:svnAcer:pnAspireM5810:pvr:rvnAcer:rnFMP55:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire M5810 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454975] Re: AMD Radeon HD 8570 / R7 240/340 OEM] [1002:6611] No DP audio with the open source driver
As the proprietary driver is available now, I will remove the blocker tag, for those who are affected by this, please install the proprietary fglrx driver in your Additional Drivers tool. Thanks ** Tags removed: blocks-hwcert -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1454975 Title: AMD Radeon HD 8570 / R7 240/340 OEM] [1002:6611] No DP audio with the open source driver Status in HWE Next Project: New Status in linux-lts-utopic package in Ubuntu: New Bug description: CID: 201302-12679 Dell OptiPlex 9020 There is no audio output available from the DisplayPort with the open source driver. There are two output options here in the Sound Settings: Analog Output and Speaker Non of them could make the DP audio device (the speaker on the monitor) work. Also, this is a desktop system, I can't hear anything with the Speaker option. Since we're unable to install the fglrx now, I will mark this one as a blocker. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-37-generic 3.16.0-37.51~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 23:52:37 2015 InstallationDate: Installed on 2015-05-13 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1697 F pulseaudio /dev/snd/controlC1: ubuntu 1697 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9201b911-af8a-4fe9-a8b1-544f1f394b6a InstallationDate: Installed on 2015-05-13 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 9020 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=9d6f549c-046c-4193-b58e-5ee4df6c0e0b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 RelatedPackageVersions: linux-restricted-modules-3.16.0-37-generic N/A linux-backports-modules-3.16.0-37-generic N/A linux-firmware 1.127.11 RfKill: Tags: trusty Uname: Linux 3.16.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
msharman@laptop-msharman:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date N56VM.214 08/28/2012 Thanks, for some reason it didn't occur to me to check for out dated BIOS. I've updated the BIOS to the 214 version which indeed has made a significant change. Ubuntu now attachs to the phone with the file manager when it is plugged in. Add if I eject the phone (to avoid the device can not be claimed error in Shotwell) then Shotwell is now able to read the previews of the photos and import the photos - which is much better. However, it isn't stable, I gave the mtp-detect process above a go after a reboot and the result is better but there were some errors I've attached the output as the file mtp-detect-out.txt and also there are still errors in the dmesg I've attached the complete dmesg output as dmesg-out.txt Interestingly after repeating the above mtp-detect hangs as it attempts to reset the device: msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ mtp-detect (output attached as mtp-detect-out.txt) dmesg output: [ 51.197549] usb 1-4: USB disconnect, device number 3 [ 54.520400] usb 1-4: new high-speed USB device number 4 using xhci_hcd [ 54.649665] usb 1-4: New USB device found, idVendor=04e8, idProduct=6860 [ 54.649672] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.649676] usb 1-4: Product: SAMSUNG_Android [ 54.649679] usb 1-4: Manufacturer: SAMSUNG [ 54.649682] usb 1-4: SerialNumber: 2410ba56 [ 131.389969] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.501544] usb 1-4: reset high-speed USB device number 4 using xhci_hcd [ 131.630174] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da48 [ 131.630180] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da00 [ 131.630184] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da90 [ 131.630628] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.630712] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630828] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630841] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630856] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630872] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630900] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.631012] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) Seems to hang here. For reference my list of steps is now: 1. Plug in device 2. Click Eject when notification about device attached appears (otherwise will get an error about device being claimed). 3. Kill gvfs processes because they stop mtp-detect from working. msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 5. Make sure phone is unlocked and then run mtp-detect Works but has errors. 5. Make sure phone is unlocked and then run mtp-detect a second time. This time it hangs. As before I tried updating to the most recent mainline kernel 4.1rc7 but the same symptoms were present the dmesg output was different again (I've attached this as dmesg-out-41.rc7.txt) ** Attachment added: dmesg output kernel 3.19.0-20 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415376/+files/dmesg-out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect,
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: dmesg output kernel 4.1rc7 for comparison https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415377/+files/dmesg-out-4.1rc7.txt ** 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/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [
[Kernel-packages] [Bug 1465419] onibi (amd64) - tests ran: 193, failed: 28
tests ran: 193, failed: 28; http://kernel.ubuntu.com/testing/onibi__3.19.0-20.20__2015-06-16_00-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: output when mtp-detect works after resetting device https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415375/+files/mtp-detect-out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Android [ 215.634196] usb
[Kernel-packages] [Bug 1300557] Re: Screen resolution no longer works
No Tried 4.1-rc7. No change. ** 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/1300557 Title: Screen resolution no longer works Status in linux package in Ubuntu: Confirmed Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] fozzie (i386) - tests ran: 167, failed: 27
tests ran: 167, failed: 27; http://kernel.ubuntu.com/testing/fozzie__3.19.0-20.20__2015-06-16_03-04-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.4 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1300557] Re: Screen resolution no longer works
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest resolution offered in the System Settings is 1920×1200. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in linux package in Ubuntu: Confirmed Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464983] Re: Black screen after after wake up from suspend
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1.0-040100rc8-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464983 Title: Black screen after after wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: Notebook Acer Extensa 2510g When i change video on Intel HD, all is working! When i use NVidia 820m, after wake up i got black screen with console cursor in upper left corner. This problem on Proprietary and Nouveau. Version: Ubuntu 3.19.0-20.20-generic 3.19.8 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1404 F pulseaudio /dev/snd/controlC1: dmitry21 1404 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=85369393-b11e-4aa9-9876-f0fe071152a8 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Extensa 2510G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic.efi.signed root=UUID=62ba55e3-29b2-46df-a4a0-cdc272eafe4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 Tags: vivid UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464300] Re: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: linux (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464300 Title: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: I wasn't aware of any bug until the reporter said it needed to send this to you. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-54-generic 3.13.0-54.91 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: camdin 2346 F pulseaudio Date: Thu Jun 11 07:47:52 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-06 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. usb0 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dx2300 Microtower ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-53-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.1 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 11/24/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: MS7336 1.14 dmi.board.name: 0A90 dmi.board.vendor: MSI dmi.chassis.asset.tag: MXL7260G73 dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrMS73361.14:bd11/24/2008:svnHewlett-Packard:pnHPCompaqdx2300Microtower:pvr:rvnMSI:rn0A90:rvr:cvnMSI:ct3:cvr: dmi.product.name: HP Compaq dx2300 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464624] Re: package linux-image-3.13.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package. If that does not resolve your issue, please mark the bug as Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464624 Title: package linux-image-3.13.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: no way, I tryed realy every thing, don't let me install linux- image-3.13.0-15-gneric !!! PLEASE HELP ! Thank's in front. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo1327 F pulseaudio Date: Thu Jun 11 12:42:30 2015 DpkgHistoryLog: Start-Date: 2015-06-11 12:42:23 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.60' Install: linux-image-3.13.0-53-generic:i386 (3.13.0-53.89, automatic), linux-headers-3.13.0-53-generic:i386 (3.13.0-53.89, automatic), linux-image-3.13.0-44-generic:i386 (3.13.0-44.73, automatic), linux-image-3.13.0-43-generic:i386 (3.13.0-43.72, automatic), linux-headers-3.13.0-53:i386 (3.13.0-53.89, automatic), linux-image-extra-3.13.0-53-generic:i386 (3.13.0-53.89, automatic) Upgrade: linux-generic:i386 (3.13.0.44.51, 3.13.0.53.60), linux-image-generic:i386 (3.13.0.44.51, 3.13.0.53.60), linux-headers-generic:i386 (3.13.0.44.51, 3.13.0.53.60) DpkgTerminalLog: Preparing to unpack .../linux-image-3.13.0-53-generic_3.13.0-53.89_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-53-generic_3.13.0-53.89_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 DuplicateSignature: package:linux-image-3.13.0-53-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=1d09eb21-0201-4383-a80d-7d075d21b6ef InstallationDate: Installed on 2015-01-06 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: Acer Extensa 3000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=6f5ddefa-7cab-49f7-927d-d8f63e9ce3b5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux StagingDrivers: r8712u Title: package linux-image-3.13.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2004 dmi.bios.vendor: ACER dmi.bios.version: 3A08 dmi.board.name: Extensa 3000 dmi.board.vendor: Acer dmi.board.version: Rev 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnACER:bvr3A08:bd09/09/2004:svnAcer:pnExtensa3000:pvrRev1:rvnAcer:rnExtensa3000:rvrRev1.0:cvnAcer:ct10:cvrRev.1: dmi.product.name: Extensa 3000 dmi.product.version: Rev 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/ ** Package changed: linux-lts-vivid (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Triaged ** 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/1464723 Title: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0 Status in linux package in Ubuntu: Incomplete Bug description: On my Asus X93SV-YZ225V laptop my mouse as well as all other 'human interface devices' (I tried it with a second mouse and a keyboard) stop working at a random time after boot, when attached to a USB 2.0 port. Other USB-devices (I tried it with several USB Flash drives) continue to work on the USB 2.0 ports. The USB 3.0 port on the laptop does not show this behavior, i.e. a human interface device never stops working. Unplugging and replugging the mouse does not reactivate it. The mouse works again for a random amount of time after a reboot or a wake-up from suspend to RAM. When the mouse stops working the respective /dev/input/mouseX device does not produce any output either. The touchpad, that is connected via PS/2, does not show this bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 12 14:50:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] InstallationDate: Installed on 2015-05-16 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K93SV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=4f453054-6eeb-4f48-ba87-b529b2fcd617 ro nosplash SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SV 209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK93SV209:bd11/22/2011:svnASUSTeKComputerInc.:pnK93SV:pvr1.0:rvnASUSTeKComputerInc.:rnK93SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
[Kernel-packages] [Bug 1458470] Re: no uevent after ejecting CD-ROM
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/ ** 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/1458470 Title: no uevent after ejecting CD-ROM Status in linux package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file /lib/udev/rules.d/10-test.rules with the content KERNEL==sr0, RUN+=/usr/bin/touch /tmp/test.txt does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465364] [NEW] Laptop freeze with panic error
Public bug reported: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: l 1422 F pulseaudio /dev/snd/controlC0: l 1422 F pulseaudio CurrentDesktop: LXDE Date: Mon Jun 15 20:09:15 2015 HibernationDevice: RESUME=UUID=5bb9993a-20aa-42b9-b775-d2508ba91475 InstallationDate: Installed on 2015-04-16 (59 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=949b66c8-bdcd-4186-980e-b873d5da5906 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-24 (22 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: New Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic
[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
I've succeeded to boot gparted from external usb. just press multiple times right after boot/reboot ESC. This should throw you to grub console. Then: ls set root=(hd1,msdos2) chailoader /efi/... (list the content of the drive and find *.efi) boot that's gonna load the gparted (or the one you've chosen before [made on Fujitsu AH532, Linux Mint Rebecca] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access Status in linux package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-7ubuntu11 Candidate: 2.00-7ubuntu11 Pheonix Secure Core Tiano bios version 1.09 New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All functions worked normally when running Win7. Ubuntu 12.10 installed using whole disk. Installation successful Ubuntu boots and runs normally, however all access to the bios has now been lost. Pressing the default key (f2) during boot up is acknowledged by bios beep, but ignored and Ubuntu continues booting. In addition the 'boot choices' menu (f12) contains nothing but Ubuntu making it impossible to boot from USB or CD/DVD. The latter (f12) problem was overcome by opening up the machine, removing the ram and shorting the cl1/cl2 posts with a screwdriver. This restores the ability to boot from USB/CD by pressing f12 but does not restore bios access. The following recovery actions have been tried. 1) Install Boot-Repair, run repair, no change occurred. Boot repair report here: http://paste.ubuntu.com/1375041/ 2) Restore Windows from Clonezilla disk image (factory settings) - result - bios access is no longer possible from windows either, f2 now launches the Windows boot menu. 3) Update all drivers using Fujitsu driver update tool from within windows (which included a bios update). Result - no change, no bios. 4) Restored Ubuntu from Clonezilla disk image - no change. 5) Added second distro to disk. Installed successfully (uefi mode as that is all I have) no change to bios access. So overall result I have lost all bios access even from a reinstalled Windows. I repeat that bios access was perfectly normal before installing Ubuntu. I strongly suggest you read the contents of this thread in addition to the information here: http://ubuntuforums.org/showthread.php?t=2086602 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: grub-efi 2.00-7ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 23 15:50:07 2012 InstallationDate: Installed on 2012-11-22 (1 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465364] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: Confirmed Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: l 1422 F pulseaudio /dev/snd/controlC0: l 1422 F pulseaudio CurrentDesktop: LXDE Date: Mon Jun 15 20:09:15 2015 HibernationDevice: RESUME=UUID=5bb9993a-20aa-42b9-b775-d2508ba91475 InstallationDate: Installed on 2015-04-16 (59 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=949b66c8-bdcd-4186-980e-b873d5da5906 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-24 (22 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465054] Re: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-54-generic/kernel/drivers/i
It appears the .deb file is corrupt. You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package. If that does not resolve your issue, please mark the bug as Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465054 Title: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko' to '/lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko .dpkg-new': unexpected end of file or stream Status in linux package in Ubuntu: Incomplete Bug description: System freezes after booting up, after last update. When booting in previous version and recover, the message still comes, but system is not freezing. Tried apt-get autoremove -f, and then apt-get update and upgrade and autoremove and rebooting just to see, and now I can boot again without the system freezes after starting up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-54-generic 3.13.0-54.91 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bjarke 1479 F pulseaudio /dev/snd/controlC1: bjarke 1479 F pulseaudio /dev/snd/controlC0: bjarke 1479 F pulseaudio Date: Thu Jun 11 08:10:19 2015 DuplicateSignature: package:linux-image-extra-3.13.0-54-generic:3.13.0-54.91:cannot copy extracted data for './lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko' to '/lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko' to '/lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko.dpkg-new': unexpected end of file or stream HibernationDevice: RESUME=UUID=94981dc1-2f27-459d-bbeb-f9045c381c76 InstallationDate: Installed on 2015-02-16 (118 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-54-generic root=UUID=f6972629-cb95-4110-bfd1-cf89a1deb3d0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.2 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko' to '/lib/modules/3.13.0-54-generic/kernel/drivers/isdn/hardware/eicon/divacapi.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: P45DE3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP45DE3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465364] Re: Laptop freeze with panic error
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: Confirmed Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: l 1422 F pulseaudio /dev/snd/controlC0: l 1422 F pulseaudio CurrentDesktop: LXDE Date: Mon Jun 15 20:09:15 2015 HibernationDevice: RESUME=UUID=5bb9993a-20aa-42b9-b775-d2508ba91475 InstallationDate: Installed on 2015-04-16 (59 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=949b66c8-bdcd-4186-980e-b873d5da5906 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-24 (22 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464723] [NEW] Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
You have been subscribed to a public bug: On my Asus X93SV-YZ225V laptop my mouse as well as all other 'human interface devices' (I tried it with a second mouse and a keyboard) stop working at a random time after boot, when attached to a USB 2.0 port. Other USB-devices (I tried it with several USB Flash drives) continue to work on the USB 2.0 ports. The USB 3.0 port on the laptop does not show this behavior, i.e. a human interface device never stops working. Unplugging and replugging the mouse does not reactivate it. The mouse works again for a random amount of time after a reboot or a wake-up from suspend to RAM. When the mouse stops working the respective /dev/input/mouseX device does not produce any output either. The touchpad, that is connected via PS/2, does not show this bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 12 14:50:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] InstallationDate: Installed on 2015-05-16 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K93SV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=4f453054-6eeb-4f48-ba87-b529b2fcd617 ro nosplash SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SV 209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK93SV209:bd11/22/2011:svnASUSTeKComputerInc.:pnK93SV:pvr1.0:rvnASUSTeKComputerInc.:rnK93SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Jun 12 13:08:49 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6152 vendor CMO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: linux (Ubuntu) Importance: Medium Status: Triaged ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0 https://bugs.launchpad.net/bugs/1464723 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463627] Re: Limiting the data size doesn't work
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1463627 Title: Limiting the data size doesn't work Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu 15.10 dev with libpam-modules 1.1.8-3.1ubuntu3 and if I'm limiting the data size with ulimit -d 8192 and executing for example the testcase from this ticket ( https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1462853 ) I'm noticing that the data size can still be more than 8 MiB (in this case ~2 GiB). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-20-generic. ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 36 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Tags: wily Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF4739C55 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
This bug was fixed in the package apparmor - 2.8.95~2430-0ubuntu5.2 --- apparmor (2.8.95~2430-0ubuntu5.2) trusty-proposed; urgency=medium * debian/patches/php5-Zend_semaphore-lp1401084.patch: allow php5 abstraction access to Zend opcache files (LP: #1401084) * debian/patches/dnsmasq-lxc_networking-lp1403468.patch: update profile for lxc support (LP: #1403468) * debian/patches/profiles-texlive_font_generation-lp1010909.patch: allow generation of texlive fonts by sanitized-helpers (LP: #1010909) * debian/apport/source_apparmor.py: fix the apparmor apport hook so it does not raise an exception if a non-unicode character is found in /var/log/kern.log or in /var/log/syslog. This should work under python3 or python2.7 (LP: #1304447) * debian/patches/profiles-dovecot-updates-lp1296667.patch: update dovecot profiles to address several missing permissions. (LP: #1296667) * debian/patches/profiles-adjust_X_for_lightdm-lp1339727.patch: adjust X abstraction for LightDM xauthority location (LP: #1339727) * debian/patches/libapparmor-fix_memory_leaks-lp1340927.patch; fix memory leaks in log parsing component of libapparmor (LP: #1340927) * debian/patches/libapparmor-another_audit_format-lp1399027.patch: add support for another log format style (LP: #1399027) * debian/patches/tests-workaround_for_unix_socket_change-lp1425398.patch: work around apparmor kernel behavioral change in regression tests (LP: #1425398) * debian/control: add breaks on python3-apparmor against older apparmor-utils that used to be where python bits lived (LP: #1373259) * debian/patches/utils-update_to_2.9.2.patch: update the python utilities to the upstream 2.9.2 (LP: #1449769, incorporating a large number of fixes and improvements, including: - fix aa-genprof traceback with apparmor 2.8.95 (LP: #1294797) - fix aa-genprof crashing when selecting scan on Ubuntu 14.04 server (LP: #1319829) - make aa-logprof read profile instead of program binary (LP: #1317176, LP: #1324154) - aa-complain: don't traceback when marking multiple profiles (LP: #1378095) - make python tools able to parse mounts with UTF-8 non-ascii characters (LP: #1310598) -- Steve Beattie sbeat...@ubuntu.com Thu, 30 Apr 2015 12:18:08 -0700 ** Changed in: apparmor (Ubuntu Trusty) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Fix Released Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Released Bug description: [apparmor impact] This bug generates false positives when using the apparmor regression tests on the HWE kernels (utopic and newer), which means the kernel team needs to examine test output to ensure that addiitional failures didn't occur when testing new kernels. [apparmor test case] 1) install hwe kernel libapparmor-dev libdbus-1-dev attr 2) apt-get source apparmor 3) cd apparmor-2.8.95~2430/tests/regression/apparmor/ 4) make USE_SYSTEM=1 5) sudo bash unix_socket_file.sh If the bug has not been addressed, this test script will fail with the following messages: Error: unix_socket_file failed. Test 'socket file (dgram); confined server / access (w)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied FAIL - poll timed out' Error: unix_socket_file failed. Test 'socket file (dgram); confined client w/ access (rw)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied FAIL - poll timed out' and a return code of 2 (echo $?). If it has been fixed it should return silently, with a return code of 0. [apparmor regression potential] The patch for this bug only affects the test suite for apparmor, which is a loosening of the policy used in the specific failing testcases. There should be no effect on the apparmor implementation proper from this fix. [apparmor additional info] This testsuite is run as part of the test-apparmor.py test script from lp:qa-regression-testing, and used as part of the kernel update process, but is useful for ensuring that apparmor is functioning properly. [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400
[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run
** Changed in: linux (Ubuntu Trusty) Status: Incomplete = Confirmed ** Summary changed: - ext4 turned read-only during logrotate daily run + ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I noticed that one of my VM had this dmesg -T output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [81720eb6] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [810677cd] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [810678aa] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [8126e862] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [81246a5a] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [81277086] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [810aacc5] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [812685b5] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [81267527] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [8126ad00] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [8126af5c] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [8126d300] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [81244eb9] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [81245a18] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [811d8f60] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [811d9775] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [811d4698] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [811d4795] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [811bf7e6] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [811bf91e] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [810882f7] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [81013ed7] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [81731c2a] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G W 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 task.ti: 880003a1 [Thu Feb 19 06:25:09 2015] RIP: 0010:[8125d4c1] [8125d4c1] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58 EFLAGS: 00010292 [Thu Feb 19 06:25:09 2015] RAX: RBX:
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
I built a Precise test kernel with a revert of 7b0f287 and df438af. Can you test this kernel and see if it still exhibits the bug? It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1465322/ ** Tags added: precise 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/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460674] Re: [i915_bpo] Rebase driver to 4.2~pre
Thanks for the testing. Moving back to in progress, since the code hasn't been merged yet. ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = In Progress ** Changed in: linux (Ubuntu Vivid) Assignee: Canonical Hardware Certification (canonical-hw-cert) = Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460674 Title: [i915_bpo] Rebase driver to 4.2~pre Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: Upstream i915 code has been feature-frozen for drm-next, and rebasing i915_bpo to it is fairly simple. We need all the drm_atomic* changes to date though, in order to avoid oopses loading the driver. Thankfully i915_bpo is the only driver that uses them (besides msm), so there's no chance of regressing other drivers that we care about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464560] Re: Backport request: include PRD support for OpenPower kernels
Jeremy, Which Ubuntu series kernels are you requesting this for specifically, 3.19? Wily will track upstream a bit, so if these make 4.1/4.2 they might just come in through a rebase. ** Changed in: linux (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464560 Title: Backport request: include PRD support for OpenPower kernels Status in linux package in Ubuntu: In Progress Bug description: Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. Patches have recently hit linux-next: 0d7cd85 powerpc/powernv: Add opal-prd channel 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 48c0615 powerpc/powernv: Merge common platform device initialisation Let me know if you need any info (or dependencies) for these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1465364] Re: Laptop freeze with panic error
Today I issued an apt-get dist-upgrade and the kernel has been upgraded to the above. I always had this issue but only when getting back from hibernation (I've installed only a couple of months ago) After the upgrade of today the issues become severe.. I cannot have a coffee without rebooting afterwards :) Today only I've seen the panic message on the console and more logging about nouveau I'm going to try 4.1-rc8-unstable from kernel-ppa/mainline and report back from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/linux-headers-4.1.0-040100rc8-generic_4.1.0-040100rc8.201506150335_amd64.deb Thank you Best Luca 2015-06-15 20:49 GMT+02:00 Joseph Salisbury joseph.salisb...@canonical.com : Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/ -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1465364 Title: Laptop freeze with panic error Status in linux package in Ubuntu: Confirmed Bug description: When getting back to the pc and the screen is turned off, the pc freeze and sometime show a message like (sorry do not have full message) drm_kms_helper: panic ... In dmesg I see a lot of noveau related error like [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] # thousand like this! [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001098] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001099] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001097] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,001096] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ UNK08 ] [ +0,000566] nouveau E[ PFIFO][:01:00.0] runlist 4 update timeout [ +0,000123] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 1 [ +1,260477] nouveau [ PGRAPH][:01:00.0] using external firmware [ +0,22] nouveau :01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2 [ +0,06] nouveau :01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2 [ +0,01] nouveau E[ PGRAPH][:01:00.0] failed to load fuc409c [giu15 20:06] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x573f (0x1c408200) [giu15 20:09] nouveau E[ PIBUS][:01:00.0] HUB0: 0x6013d4 0x (0x1b40822c) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: l 1422 F pulseaudio /dev/snd/controlC0: l 1422 F pulseaudio CurrentDesktop: LXDE Date: Mon Jun 15 20:09:15 2015 HibernationDevice: RESUME=UUID=5bb9993a-20aa-42b9-b775-d2508ba91475 InstallationDate: Installed on 2015-04-16 (59 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=949b66c8-bdcd-4186-980e-b873d5da5906 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-24 (22 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler
** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New = Confirmed ** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Vivid) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463584 Title: [Hyper-V] Add support for VMBus panic notifier handler Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: Please take these patches to our Hyper-V VMBus driver to enable kernel crash notification: Drivers: hv: vmbus: Add support for VMBus panic notifier handler https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81 Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13 In the event of a kernel panic, VMBus driver supports sending five 64-bit values to be recorded in the log. On Hyper-V this is recorded in the event log, and on Azure we can use this data to better detect failures like this in the guest VM and surface that as part of our diagnostics information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
And yet again: root@rproxy:~# dmesg -T | tail [Thu Jun 11 15:28:56 2015] type=1400 audit(1434050938.364:24): apparmor=STATUS operation=profile_replace profile=unconfined name=nc pid=658 comm=apparmor_parser [Thu Jun 11 15:28:59 2015] init: plymouth-upstart-bridge main process ended, respawning [Thu Jun 11 15:29:02 2015] init: console-font main process (757) terminated with status 71 [Thu Jun 11 15:29:03 2015] init: plymouth-splash main process (815) terminated with status 1 [Thu Jun 11 18:18:40 2015] random: nonblocking pool is initialized [Mon Jun 15 16:53:35 2015] EXT4-fs (vda1): pa 8800061e1000: logic 3293, phys. 469944, len 424 [Mon Jun 15 16:53:35 2015] EXT4-fs error (device vda1): ext4_mb_release_inode_pa:3753: group 14, free 13, pa_free 11 [Mon Jun 15 16:53:35 2015] Aborting journal on device vda1-8. [Mon Jun 15 16:53:36 2015] EXT4-fs (vda1): Remounting filesystem read-only [Mon Jun 15 16:53:36 2015] EXT4-fs error (device vda1): ext4_journal_check_start:56: Detected aborted journal root@rproxy:~# uname -a Linux rproxy.dmz.sdeziel.info 3.13.0-54-generic #91-Ubuntu SMP Tue May 26 19:15:08 UTC 2015 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/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I noticed that one of my VM had this dmesg -T output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [81720eb6] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [810677cd] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [810678aa] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [8126e862] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [81246a5a] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [81277086] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [810aacc5] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [812685b5] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [81267527] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [8126ad00] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [8126af5c] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [8126d300] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [81244eb9] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [81245a18] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [811d8f60] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [811d9775] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [811d4698] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [811d4795] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [811bf7e6] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [811bf91e] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [810882f7] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [81013ed7] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [81731c2a] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] __ext4_error_inode+0x31/0x160
[Kernel-packages] [Bug 1461620] Re: NUMA task migration race condition due to stop task not being checked when balancing happens
Just got an update from Peter: https://lkml.org/lkml/2015/6/15/531 asking for feedback on a patch: Subject: stop_machine: Fix deadlock between multiple stop_two_cpus() From: Peter Zijlstra pet...@infradead.org Date: Fri, 5 Jun 2015 17:30:23 +0200 Will try to test the latest builds + this patch with the NUMA migration test. Unfortunately it is REALLY hard to reproduce the issue so I cannot know if the patch fixed anything, just test if it looks good or not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461620 Title: NUMA task migration race condition due to stop task not being checked when balancing happens Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: It was brought to my attention the follow kernel panic: [3367068.076488] Code: 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 41 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 fa 66 0f 1f 44 00 00 eb d8 66 0f 1f [3367068.092735] BUG: soft lockup - CPU#16 stuck for 22s! [migration/16:153] [3367068.100368] Modules linked in: iptable_raw xt_nat xt_REDIRECT veth openvswitch(OF) gre vxlan ip_tunnel libcrc32c dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables ipmi_devintf 8021q garp stp mrp llc bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel gpio_ich joydev aes_x86_64 lrw gf128mul glue_helper ablk_helper ipmi_si cryptd sb_edac wmi lpc_ich edac_core mac_hid acpi_power_meter nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache lp parport hid_generic ixgbe fnic libfcoe dca ptp [3367068.100409] libfc megaraid_sas pps_core mdio usbhid scsi_transport_fc hid enic scsi_tgt [3367068.100415] CPU: 16 PID: 153 Comm: migration/16 Tainted: GF O 3.13.0-34-generic #60-Ubuntu [3367068.100417] Hardware name: Cisco Systems Inc UCSC-C220-M3S/UCSC-C220-M3S, BIOS C220M3.1.5.4f.0.111320130449 11/13/2013 [3367068.100419] task: 881fd2f517f0 ti: 881fd2f1c000 task.ti: 881fd2f1c000 [3367068.100420] RIP: 0010:[810f5944] [810f5944] multi_cpu_stop+0x64/0xf0 [3367068.100426] RSP: :881fd2f1dd98 EFLAGS: 0246 [3367068.100427] RAX: 8180af40 RBX: 0086 RCX: a402 [3367068.100428] RDX: 0001 RSI: RDI: 883e607edb48 [3367068.100430] RBP: 881fd2f1ddb8 R08: 0282 R09: 0001 [3367068.100431] R10: b6d8 R11: 881fc374dc80 R12: 00014440 [3367068.100432] R13: 881fd291ae00 R14: 881fd291ae08 R15: 00020010 [3367068.100433] FS: () GS:881fffd0() knlGS: [3367068.100434] CS: 0010 DS: ES: CR0: 80050033 [3367068.100435] CR2: 7f6202134b98 CR3: 01c0e000 CR4: 001407e0 [3367068.100437] Stack: [3367068.100438] 883e607edb70 881fffd0ede0 881fffd0ede8 883e607edb48 [3367068.100441] 881fd2f1de78 810f5b5e 8109dfc4 881fffd14440 [3367068.100443] 881fd2f1de08 81097508 881fffd14440 [3367068.100446] Call Trace: [3367068.100450] [810f5b5e] cpu_stopper_thread+0x7e/0x150 [3367068.100454] [8109dfc4] ? vtime_common_task_switch+0x24/0x40 [3367068.100458] [81097508] ? finish_task_switch+0x128/0x170 [3367068.100462] [8171fd41] ? __schedule+0x381/0x7d0 [3367068.100465] [810926af] smpboot_thread_fn+0xff/0x1b0 [3367068.100467] [810925b0] ? SyS_setgroups+0x1a0/0x1a0 [3367068.100470] [8108b3d2] kthread+0xd2/0xf0 [3367068.100473] [8108b300] ? kthread_create_on_node+0x1d0/0x1d0 [3367068.100477] [8172c6bc] ret_from_fork+0x7c/0xb0 [3367068.100479] [8108b300] ? kthread_create_on_node+0x1d0/0x1d0 [3367068.100480] Code: db 85 db 41 0f 95 c5 31 f6 31 d2 eb 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed 75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 41 8b 5c 24 20 39 d3 74 f0 83 fb 02 75 d7 I'm explaining WHY this is happening in the first comments and HOW to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465400] [NEW] CVE-2015-1328
*** This bug is a security vulnerability *** Public security bug reported: overlayfs privilege escalation ** Affects: linux (Ubuntu) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: High Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: High Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: High Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: High Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: High Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: High Status: New ** Affects: linux-manta (Ubuntu) Importance: High Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: High Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: High Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: High Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: High Status: New ** Affects: linux (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: High Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: High Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: High Status: New ** Affects: linux-armadaxp
[Kernel-packages] [Bug 1465400] Re: CVE-2015-1328
CVE-2015-1328 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New = Invalid **
[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler
I also built Utopic and Trusty test kernels with these patches applied. They can be downloaded from: Trusty: http://kernel.ubuntu.com/~jsalisbury/lp1463584/trusty Utopic: http://kernel.ubuntu.com/~jsalisbury/lp1463584/utopic Can these kernels also be tested? I'll send an SRU request for all the releases once these two are tested as well. Wily will get these patches when it is rebased to upstream 4.1. Thanks in advance! ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Wily) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Vivid) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Utopic) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463584 Title: [Hyper-V] Add support for VMBus panic notifier handler Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Please take these patches to our Hyper-V VMBus driver to enable kernel crash notification: Drivers: hv: vmbus: Add support for VMBus panic notifier handler https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81 Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13 In the event of a kernel panic, VMBus driver supports sending five 64-bit values to be recorded in the log. On Hyper-V this is recorded in the event log, and on Azure we can use this data to better detect failures like this in the guest VM and surface that as part of our diagnostics information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 Here's an edited summary of the reply I got from the please contact our firmware engineers at xxx@xxx address; turns out there's no engineers there either, but at least we finally have a sane non-formletter reply which *for the first time* states that Samsung is aware of the issue and is working on a fix at the firmware level. Good news for everyone: We are just the SSD tech support. We are not the FW engineers. They are in Korea and have been aware of the issue since it first started being reported online. The latest stable Linux Kernal 4.0.5 successfully blacklists the affected drive(s) from queued TRIM. Linux can still use Sequential TRIM, so you’re not losing out on anything. We see that you are well aware that Marc Carino and Martin K. Petersen are in contact with Samsung on how to resolve the issue since it started. All we can say to users at this moment is that Linux is the only operating system that has this issue with the Queued TRIM. Linux is open source and can be modified by anyone, as such we do not support the OS. We recommend updating to the new kernel, as we have seen that other users have done so and it alleviated their issue(s). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1464561] Re: [Asus UX303LN] several hotkeys don't produce evdev event
Hello, Thank you for your help. I sent the email following the instructions verbatim. However, I do not understand how to do this: Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger- lists.html . It can take a day for the new e-mail to show up in the respective archive. Sorry to have to ask you.. Cheers, Bob On Mon, Jun 15, 2015 at 1:12 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: gratefulfrog, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-input) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger- lists.html . It can take a day for the new e-mail to show up in the respective archive. Thank you for your understanding. ** Tags removed: kernel-bug-exists-upstream-4.1.0-040100rc8 ** Tags added: kernel-bug-exists-upstream-4.1-rc8 ** Summary changed: - [Asus UX303LN] several hotkeys don't produce evdev event + [Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event ** Description changed: - Running Xubuntu on an Asus UX303LN laptop. - The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random mouse movements, making it impossible to enter text in the right place. When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off. Also, if the bluetooth connection is lost, then I can do nothing and have to reboot! - - I have no idea how to debug this but would be happy to help. - - Another hotkey that does not work is F2 airplane mode. This one is of - no importance to me, but I mention it for completeness. - - I am really hoping for a fix! - - I am a Ubuntu beta-tester from long ago, and helped on the 1st 64bit - version! - - Let me know, please!, - Cheers, - Bob - - I have attached all the files specified on the hotkey bug reporting - page. I put them in an archive since that seems to be the only option - for attaching multiple files? - - udevadm info --export-db udev-db.txt - dmesg dmesg.log - sudo lsinput lsinput.log - xkbcomp -xkb :0 - xkbcomp.txt - setxkbmap -print xkbmap.txt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jun 12 10:05:56 2015 InstallationDate: Installed on 2015-05-11 (31 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2a Intel Corp. - Bus 001 Device 002: ID 064e:9700 Suyin Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 064e:9700 Suyin Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LNB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=eba1a0f5-161a-4061-99a4-b5598f7692c1 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LNB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LNB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.203:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LNB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1464561 Title: [Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464561/+subscriptions -- You received
[Kernel-packages] [Bug 1465178] [NEW] Microcode SW error detected. Restarting 0x2000000 on connecting to AC network with iwlwifi-7265-ucode-25.228.9.0
Public bug reported: When trying to connect to an 802.11AC network using an Intel 7265 with firmware iwlwifi-7265-ucode-25.228.9.0 on kernel 3.16.0-38-generic #52~14.04.1-Ubuntu, the error Microcode SW error detected. Restarting 0x200. is received, the card crashes and can't connect to the network. The same card/driver/firmware combination performs well on 2.4GHz networks, and also 802.11a. Jun 15 14:02:38 nomad115 NetworkManager[911]: info NetworkManager state is now DISCONNECTED Jun 15 14:02:36 nomad115 wpa_supplicant[962]: wlan0: CTRL-EVENT-SCAN-STARTED Jun 15 14:02:38 nomad115 wpa_supplicant[962]: wlan0: Reject scan trigger since one is already pending Jun 15 14:02:38 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: inactive - disconnected Jun 15 14:02:39 nomad115 NetworkManager[911]: info (wlan0): supplicant interface state: disconnected - inactive Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) starting connection 'chocolateblock5 1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info NetworkManager state is now CONNECTING Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 15 14:02:40 nomad115 NetworkManager[911]: info (wlan0): device state change: prepare - config (reason 'none') [40 50 0] Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0/wireless): connection 'chocolateblock5 1' has security, and secrets exist. No new secrets needed. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'ssid' value 'chocolateblock5' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'scan_ssid' value '1' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'key_mgmt' value 'WPA-PSK' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: added 'psk' value 'omitted' Jun 15 14:02:40 nomad115 NetworkManager[911]: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 15 14:02:40 nomad115 NetworkManager[911]: info Config: set interface ap_scan to 1 Jun 15 14:02:40 nomad115 wpa_supplicant[962]: wlan0: SME: Trying to authenticate with 30:b5:c2:84:95:0b (SSID='chocolateblock5' freq=5640 MHz) Jun 15 14:02:40 nomad115 kernel: [ 362.919913] wlan0: authenticate with 30:b5:c2:84:95:0b Jun 15 14:02:40 nomad115 kernel: [ 362.922550] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Jun 15 14:02:40 nomad115 kernel: [ 362.922554] iwlwifi :03:00.0: CSR values: Jun 15 14:02:40 nomad115 kernel: [ 362.922556] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) Jun 15 14:02:40 nomad115 kernel: [ 362.922598] iwlwifi :03:00.0: CSR_HW_IF_CONFIG_REG: 0X00489200 Jun 15 14:02:40 nomad115 kernel: [ 362.922653] iwlwifi :03:00.0: CSR_INT_COALESCING: 0X0040 Jun 15 14:02:40 nomad115 kernel: [ 362.922708] iwlwifi :03:00.0: CSR_INT: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922763] iwlwifi :03:00.0: CSR_INT_MASK: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922818] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922874] iwlwifi :03:00.0: CSR_GPIO_IN: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922929] iwlwifi :03:00.0: CSR_RESET: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.922984] iwlwifi :03:00.0: CSR_GP_CNTRL: 0X080403cd Jun 15 14:02:40 nomad115 kernel: [ 362.923039] iwlwifi :03:00.0: CSR_HW_REV: 0X0210 Jun 15 14:02:40 nomad115 kernel: [ 362.923094] iwlwifi :03:00.0: CSR_EEPROM_REG: 0Xd5d5 Jun 15 14:02:40 nomad115 kernel: [ 362.923150] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.923205] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0Xd5d5 Jun 15 14:02:40 nomad115 kernel: [ 362.923259] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 Jun 15 14:02:40 nomad115 kernel: [ 362.923310] iwlwifi :03:00.0: CSR_GP_UCODE_REG: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.923361] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X Jun 15 14:02:40 nomad115 kernel: [ 362.923412] iwlwifi :03:00.0:
[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
From dann's reports:
1) system1
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
2) system2
Code: 1412 f9400273 b4000213 d1002274 (b9402280)
And the upstem report in #15,
Code: 1403 f9400273 b4000213 d1002274 (b9402282)
The code snippet should be the following in __d_lookup(): fs/dcache.c
ffc0001aae68: 1403b ffc0001aae74
__d_lookup+0x84
*
* See Documentation/filesystems/path-lookup.txt for more details.
*/
rcu_read_lock();
hlist_bl_for_each_entry_rcu(dentry, node, b, d_hash) {
ffc0001aae6c: f9400273ldr x19, [x19]
ffc0001aae70: b40001f3cbz x19, ffc0001aaeac
__d_lookup+0xbc
if (dentry-d_name.hash != hash)
ffc0001aae74: d1002274sub x20, x19, #0x8
ffc0001aae78: b9402282ldr w2, [x20,#32]
#faulted instruction
Then the problem should be caused by bad pointer of dcache.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440536
Title:
Oops __d_lookup+0x88/0x194
Status in The Linux Kernel:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Vivid:
Triaged
Bug description:
This started happening on a Mustang board after upgrading to
3.19.0-9.9 and persists in 3.19.0-11.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-11-generic 3.19.0-11.11
ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
Uname: Linux 3.19.0-11-generic aarch64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Dec 31 1969 seq
crw-rw 1 root audio 116, 33 Dec 31 1969 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.17-0ubuntu1
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer',
'/dev/snd/seq'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Sun Apr 5 08:32:28 2015
HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,115200n8 ro
earlyprintk=uart8250-32bit,0x1c02
RelatedPackageVersions:
linux-restricted-modules-3.19.0-11-generic N/A
linux-backports-modules-3.19.0-11-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
SystemImageInfo:
current build number: 0
device name: ?
channel: daily
last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458470] [NEW] udev rules aren't executed anymore after booting
You have been subscribed to a public bug: I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file /lib/udev/rules.d/10-test.rules with the content KERNEL==sr0, RUN+=/usr/bin/touch /tmp/test.txt does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore. ** Affects: linux (Ubuntu) Importance: Low Status: New -- udev rules aren't executed anymore after booting https://bugs.launchpad.net/bugs/1458470 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
Yep, I am using kvalo's kernel. I've been following instructions from comment #150. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Triaged Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458470] Re: udev rules aren't executed anymore after booting
Right, so this is (at most) the kernel's fault. I'm not sure whether ejecting a CD is supposed to trigger an uevent, but maybe not in all cases? ** Package changed: udev (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Summary changed: - udev rules aren't executed anymore after booting + no uevent after ejecting CD-ROM -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458470 Title: no uevent after ejecting CD-ROM Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file /lib/udev/rules.d/10-test.rules with the content KERNEL==sr0, RUN+=/usr/bin/touch /tmp/test.txt does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] Re: linux: 4.0.0-2.3 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Leann Ogasawara (leannogasawara) ** Description changed: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare + kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.3 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465108] Re: [Dell Vostro 3458] System will start blinking after switch to virtual terminal
Attachment is the dmesg output after switching to VT ** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465108/+attachment/4414951/+files/log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465108 Title: [Dell Vostro 3458] System will start blinking after switch to virtual terminal Status in linux package in Ubuntu: Confirmed Bug description: On this I+N hybrid graphic system, when switching to Virtual Terminal with Ctrl + Alt + F1, the display will start blinking and Steps: 1. Install 14.04.2 + update 2. Switch to VT with Ctrl + Alt + F1 3. Switch back with Ctrl + Alt + F7 Expected result: Everything should work as expected. Actual result: It will start blinking, error message could be found in dmesg output, please find the attachment for the video. [ 3765.731436] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1205 F pulseaudio /dev/snd/controlC0: ubuntu 1205 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 14 22:48:50 2015 HibernationDevice: RESUME=UUID=e9508693-344c-4086-8491-70a51cabd161 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 3458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=ed5bbf8c-21d8-4bca-ae2b-d803cc0fc1ad ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: X13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX13:bd01/07/2015:svnDellInc.:pnVostro3458:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465108] Re: [Dell Vostro 3458] System will start blinking after switch to virtual terminal
ubuntu@ubuntu-Vostro-3458:~$ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) OpenGL version string: 3.0 Mesa 10.5.2 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: yes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465108 Title: [Dell Vostro 3458] System will start blinking after switch to virtual terminal Status in linux package in Ubuntu: Confirmed Bug description: On this I+N hybrid graphic system, when switching to Virtual Terminal with Ctrl + Alt + F1, the display will start blinking and Steps: 1. Install 14.04.2 + update 2. Switch to VT with Ctrl + Alt + F1 3. Switch back with Ctrl + Alt + F7 Expected result: Everything should work as expected. Actual result: It will start blinking, error message could be found in dmesg output, please find the attachment for the video. [ 3765.731436] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1205 F pulseaudio /dev/snd/controlC0: ubuntu 1205 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 14 22:48:50 2015 HibernationDevice: RESUME=UUID=e9508693-344c-4086-8491-70a51cabd161 InstallationDate: Installed on 2015-06-12 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 3458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=ed5bbf8c-21d8-4bca-ae2b-d803cc0fc1ad ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: X13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX13:bd01/07/2015:svnDellInc.:pnVostro3458:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] [NEW] NVMe shutdown and suspend delay time is too short
Public bug reported: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: In Progress ** Changed in: linux (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: In Progress Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465136] Re: NVMe shutdown and suspend delay time is too short
A patch in newer kernel (3.19 and later) has a fix for this as below: commit 2484f40780b97df1b5eb09e78ce4efaa78b21875 Author: Dan McLeran daniel.mcle...@intel.com Date: Tue Jul 1 09:33:32 2014 -0600 NVMe: Add shutdown timeout as module parameter. The current implementation hard-codes the shutdown timeout to 2 seconds. Some devices take longer than this to complete a normal shutdown. Changing the shutdown timeout to a module parameter with a default timeout of 5 seconds. Signed-off-by: Dan McLeran daniel.mcle...@intel.com Signed-off-by: Matthew Wilcox matthew.r.wil...@intel.com Signed-off-by: Jens Axboe ax...@fb.com However, this patch is not included in 3.13 or 3.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465136 Title: NVMe shutdown and suspend delay time is too short Status in linux package in Ubuntu: In Progress Bug description: A hardware vendor reported that NVMe didn't implement power management correctly during shutdown/restart and suspend/resume as below: = However, when it comes to shutdown/restart, the Power Management Events (PME) are not correctly implemented. When the host (Linux/Driver) sends the PME_TURN_OFF message it should wait for PME_TO_ACK from the device. Microsoft Windows versions typically wait for 5 seconds. The Linux OSes doesn't wait for the PME_TO_ACK from the device and simply turns off the system instantly immediately after the shutdown/restart. This is not the way to treat PCIe storage devices. The host should allow the device to properly shutdown. Otherwise the disk will go in to rebuild during next power on which takes a while resulting in OS finding the device not responding and disabling it and not loading the driver for it. = To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464576] Re: Realtek Bluetooth [0bda:b001] does not work at all on 14.04.2
With the DKMS provided in comment #42 of bug 1382404 it could make the Bluetooth work (tested with a Bluetooth headset) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1464576 Title: Realtek Bluetooth [0bda:b001] does not work at all on 14.04.2 Status in HWE Next Project: New Status in linux-lts-utopic package in Ubuntu: New Bug description: CID: 201403-14879 HP 355 G2 Notebook PC The Bluetooth device on this system does not work at all on 14.04.2 It can't see any other devices. Steps: 1. Install 14.04.2 + update (3.16.0-40) 2. Click Set Up New Device... from the Bluetooth applet 3. Try to pair with any other Bluetooth devices Expected result: It should be able to see and pair with other devices. Actual result: Nothing could be seen in the device list. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-40-generic 3.16.0-40.54~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-40.54~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 12 05:26:17 2015 InstallationDate: Installed on 2015-06-12 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1599 F pulseaudio /dev/snd/controlC0: ubuntu 1599 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=27046bba-cdf2-4475-873e-005fe871a3f0 InstallationDate: Installed on 2015-06-12 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard Presario CQ45 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-40-generic root=UUID=c7162180-a7e3-4d60-b741-af4696d2dd1b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-40.54~14.04.1-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-40-generic N/A linux-backports-modules-3.16.0-40-generic N/A linux-firmware 1.127.12 Tags: trusty Uname: Linux 3.16.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: B.0A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 86.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0A:bd04/03/2014:svnHewlett-Packard:pnPresarioCQ45NotebookPC:pvr05A920200:rvnHewlett-Packard:rn22C2:rvrKBCVersion86.08:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ45 Notebook PC dmi.product.version: 05A920200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1464576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
The Bluetooth device base on the lsusb output is: Bus 002 Device 005: ID 0bda:b002 Realtek Semiconductor Corp. Here is another bug for its sister model [0bda:b001] bug 1464576 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460674] Re: [i915_bpo] Rebase driver to 4.2~pre
Here is the call trace that I mentioned before, however, it can be reproduced in stock kernel with graphic-stress test as well. Therefore I think it's not a regression. Please refer for the attachment for the dmesg output for both stock kernel and this BPO kernel. [ 1748.393952] WARNING: CPU: 0 PID: 843 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:3625 intel_crtc_wait_for_pending_flips+0x19a/0x230 [i915]() [ 1748.393956] WARN_ON(wait_event_timeout(dev_priv-pending_flip_queue, !intel_crtc_has_pending_flip(crtc), 60*HZ) == 0) [ 1748.393959] Modules linked in: [ 1748.393963] cfg80211 toshiba_acpi toshiba_haps hp_accel lis3lv02d input_polldev rtsx_usb_ms memstick dell_wmi sparse_keymap uvcvideo intel_rapl iosf_mbi videobuf2_vmalloc x86_pkg_temp_thermal intel_powerclamp videobuf2_memops coretemp videobuf2_core v4l2_common videodev kvm_intel media kvm dell_led nouveau snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_soc_rt5640 dell_laptop crct10dif_pclmul dcdbas mxm_wmi crc32_pclmul snd_soc_rl6231 snd_hda_intel snd_hda_controller ttm snd_hda_codec snd_soc_core bcma ghash_clmulni_intel aesni_intel i8k aes_x86_64 lrw gf128mul glue_helper ablk_helper joydev cryptd serio_raw snd_compress snd_hwdep snd_pcm_dmaengine i915 snd_pcm i2c_hid snd_seq_midi hid snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer mei_me acpi_pad drm_kms_helper [ 1748.394035] drm snd mei video i2c_algo_bit dw_dmac spi_pxa2xx_platform dw_dmac_core i2c_designware_platform i2c_designware_core soundcore shpchp snd_soc_sst_acpi mac_hid 8250_dw lpc_ich wmi parport_pc ppdev lp parport autofs4 rtsx_usb_sdmmc rtsx_usb psmouse ahci r8169 libahci mii sdhci_acpi sdhci [ 1748.394076] CPU: 0 PID: 843 Comm: Xorg Tainted: GW OE 3.19.0-20-generic #20+bpo1-Ubuntu [ 1748.394079] Hardware name: Dell Inc. Vostro 3458/ , BIOS X13 01/07/2015 [ 1748.394082] c051aef8 88040dc879b8 817c3da8 0007 [ 1748.394089] 88040dc87a08 88040dc879f8 810769aa 88040dc87a18 [ 1748.394094] 8804190411a8 88041a3b84c8 8804193e2000 880419041000 [ 1748.394100] Call Trace: [ 1748.394115] [817c3da8] dump_stack+0x45/0x57 [ 1748.394123] [810769aa] warn_slowpath_common+0x8a/0xc0 [ 1748.394128] [81076a26] warn_slowpath_fmt+0x46/0x50 [ 1748.394138] [810b7319] ? finish_wait+0x59/0x70 [ 1748.394183] [c04bd9ca] intel_crtc_wait_for_pending_flips+0x19a/0x230 [i915] [ 1748.394189] [810b7510] ? wait_woken+0x90/0x90 [ 1748.394230] [c04bfba3] intel_crtc_disable_planes+0x33/0x140 [i915] [ 1748.394269] [c04c091f] haswell_crtc_disable+0x4f/0x3c0 [i915] [ 1748.394308] [c04c178c] __intel_set_mode+0x92c/0xc80 [i915] [ 1748.394317] [811d7b5e] ? __kmalloc+0x24e/0x280 [ 1748.394358] [c04c7918] ? intel_crtc_set_config+0x88/0xf70 [i915] [ 1748.394398] [c04c7999] ? intel_crtc_set_config+0x109/0xf70 [i915] [ 1748.394436] [c04c848b] intel_crtc_set_config+0xbfb/0xf70 [i915] [ 1748.394473] [c026eb16] drm_mode_set_config_internal+0x66/0x100 [drm] [ 1748.394506] [c02731c3] drm_mode_setcrtc+0x253/0x5a0 [drm] [ 1748.394529] [c0263a6f] drm_ioctl+0x1df/0x680 [drm] [ 1748.394541] [81209230] do_vfs_ioctl+0x2e0/0x4e0 [ 1748.394547] [811f7165] ? __sb_end_write+0x35/0x70 [ 1748.394554] [811f4bd2] ? vfs_write+0x1b2/0x1f0 [ 1748.394560] [812094b1] SyS_ioctl+0x81/0xa0 [ 1748.394566] [817caecd] system_call_fastpath+0x16/0x1b [ 1748.394570] ---[ end trace 7614d6cd5f75c668 ]--- ** Attachment added: dmesg.zip https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+attachment/4414964/+files/dmesg.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460674 Title: [i915_bpo] Rebase driver to 4.2~pre Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: Upstream i915 code has been feature-frozen for drm-next, and rebasing i915_bpo to it is fairly simple. We need all the drm_atomic* changes to date though, in order to avoid oopses loading the driver. Thankfully i915_bpo is the only driver that uses them (besides msm), so there's no chance of regressing other drivers that we care about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes
2 nights ago something happened. I have a 5th server which doesn't use LVM snapshots, but still it's backed up every night. I didn't install the mainline kernel on this machine, because we thought the problem was due to snapshots. And it crashed two nights ago, in the same way the other machines crashed, without using snapshots. It crashed after finishing the backup. I think the problem lies in the disconnection of the iscsi volume on which the machines do the backup. On the first reboot, I had the following in the kernel log: [ 209.312097] [ cut here ] [ 209.312106] WARNING: CPU: 0 PID: 1808 at /build/buildd/linux-3.13.0/drivers/pci/pci.c:1444 pci_disable_device+0x9c/0xb0() [ 209.312108] ipmi_si :01:04.6: disabling already-disabled device [ 209.312110] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sit tunnel4 ip_tunnel dm_crypt gpio_ich coretemp kvm joydev serio_raw hpilo lpc_ich ipmi_si(-) i3200_edac shpchp edac_core mac_hid lp parport reiserfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic radeon i2c_algo_bit ttm drm_kms_helper psmouse drm pata_acpi tg3 usbhid hid ptp pps_core [ 209.312151] CPU: 0 PID: 1808 Comm: modprobe Not tainted 3.13.0-53-generic #89-Ubuntu [ 209.312153] Hardware name: HP ProLiant DL320 G5p, BIOS W05 04/03/2008 [ 209.312154] 0009 88007abb3d40 81722e1e 88007abb3d88 [ 209.312158] 88007abb3d78 810677fd 88007c311000 88007c2c5580 [ 209.312161] 88007c311000 7f459c5473f0 7ffd2b319338 88007abb3dd8 [ 209.312164] Call Trace: [ 209.312170] [81722e1e] dump_stack+0x45/0x56 [ 209.312175] [810677fd] warn_slowpath_common+0x7d/0xa0 [ 209.312177] [8106786c] warn_slowpath_fmt+0x4c/0x50 [ 209.312182] [811a259d] ? kfree+0xfd/0x140 [ 209.312186] [813a9c7c] pci_disable_device+0x9c/0xb0 [ 209.312192] [a0398059] ipmi_pci_remove+0x29/0x30 [ipmi_si] [ 209.312195] [813ac68b] pci_device_remove+0x3b/0xb0 [ 209.312200] [81498c3f] __device_release_driver+0x7f/0xf0 [ 209.312203] [81499608] driver_detach+0xb8/0xc0 [ 209.312207] [81498875] bus_remove_driver+0x55/0xd0 [ 209.312210] [81499c7c] driver_unregister+0x2c/0x50 [ 209.312213] [813ab179] pci_unregister_driver+0x29/0x90 [ 209.312218] [a03984c4] cleanup_ipmi_si+0xd4/0xf0 [ipmi_si] [ 209.31] [810e05d2] SyS_delete_module+0x162/0x200 [ 209.312227] [81013ed7] ? do_notify_resume+0x97/0xb0 [ 209.312231] [8173391d] system_call_fastpath+0x1a/0x1f [ 209.312233] ---[ end trace f6143eeb3c0e8dba ]--- I don't know if this is related, anyway it happened only on this particular reboot. I now installed the mainline kernel also on this machine. I changed the title of this bug to reflect the additional information I got. ** Summary changed: - System hangs apparently randomly when creating LVM snapshots + System hangs apparently randomly when disconnecting iScsi volumes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449910 Title: System hangs apparently randomly when disconnecting iScsi volumes Status in linux package in Ubuntu: Triaged Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8
[Kernel-packages] [Bug 1464561] Re: [Asus UX303LN] several hotkeys don't produce evdev event
Hi, Again, thanks for your quick reply. I tested with the most recent kernel: linux-image-4.1.0-040100rc8-generic_4.1.0-040100rc8.201506150335_amd64 And the bug remains, exactly as my present kernel. I am available for further tests as needed. Thanks for this great support! Bob ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1.0-040100rc8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464561 Title: [Asus UX303LN] several hotkeys don't produce evdev event Status in linux package in Ubuntu: Incomplete Bug description: Running Xubuntu on an Asus UX303LN laptop. The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random mouse movements, making it impossible to enter text in the right place. When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off. Also, if the bluetooth connection is lost, then I can do nothing and have to reboot! I have no idea how to debug this but would be happy to help. Another hotkey that does not work is F2 airplane mode. This one is of no importance to me, but I mention it for completeness. I am really hoping for a fix! I am a Ubuntu beta-tester from long ago, and helped on the 1st 64bit version! Let me know, please!, Cheers, Bob I have attached all the files specified on the hotkey bug reporting page. I put them in an archive since that seems to be the only option for attaching multiple files? udevadm info --export-db udev-db.txt dmesg dmesg.log sudo lsinput lsinput.log xkbcomp -xkb :0 - xkbcomp.txt setxkbmap -print xkbmap.txt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jun 12 10:05:56 2015 InstallationDate: Installed on 2015-05-11 (31 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LNB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=eba1a0f5-161a-4061-99a4-b5598f7692c1 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LNB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LNB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.203:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LNB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
The Bluetooth device base on the lsusb output is: Bus 002 Device 005: ID 0bda:b002 Realtek Semiconductor Corp. Here is another bug for its sister model [0bda:b001] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working Status in linux package in Ubuntu: Confirmed Bug description: We need to support the realtek bluetooth part that comes with the Realtek Wifi MiniPCI Card ( 8723BE ) the info collect has been done a Clevo W310CZ Realtek has provided a driver which has been patched to work on trusty/3.13 here : https://github.com/lwfinger/rtl8723au_bt/tree/51a20d7c07861cbdd7219e54244bb3e38ba55058 This driver replace the current btusb driver and thus might cause different dehaviour with other bluetooth cards. --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2091 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3fc39459-32f3-45b1-9121-6b8d0f2b6765 InstallationDate: Installed on 2014-08-09 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Notebook W310CZ/CZ-T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=d43834ee-9abe-45da-acfd-3d522bff10c8 ro acpi_osi=Linux acpi_backlight=vendor ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W310CZ dmi.board.vendor: Notebook dmi.board.version: V2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/24/2013:svnNotebook:pnW310CZ/CZ-T:pvrNotApplicable:rvnNotebook:rnW310CZ:rvrV2.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W310CZ/CZ-T dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463627] Re: Limiting the data size doesn't work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? I don't know if this issue is a regression. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463627 Title: Limiting the data size doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.10 dev with libpam-modules 1.1.8-3.1ubuntu3 and if I'm limiting the data size with ulimit -d 8192 and executing for example the testcase from this ticket ( https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1462853 ) I'm noticing that the data size can still be more than 8 MiB (in this case ~2 GiB). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-20-generic. ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 36 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Tags: wily Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF4739C55 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
This works as advertised in an amd64 VM. $ cat /proc/version_signature Ubuntu 3.2.0-85.122~lp1465322-generic 3.2.69 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4264172 2837604 61% / udev 371924 4371920 1% /dev -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465322 Title: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122 Status in linux package in Ubuntu: In Progress Bug description: $ cat /proc/version_signature Ubuntu 3.2.0-84.121-generic 3.2.68 $ df | head -3 Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4262872 2838904 61% / udev 371920 4371916 1% /dev $ cat /proc/version_signature Ubuntu 3.2.0-85.122-generic 3.2.69 $ df | head -3 df: `/sys/kernel/debug': Function not implemented Filesystem 1K-blocksUsed Available Use% Mounted on /dev/vda17481832 4263012 2838764 61% / udev 371920 4371916 1% /dev This is confirmed in an amd64 VM and on an amd64 system. It doesn't make a difference if I use sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465424] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465424 Title: package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: /boot keeps filling up with deprecated packages. I don't know if I'm meant to report this bug over and over or just purge to fix it. Please advise. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-55-generic 3.13.0-55.92 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: shizoor2385 F pulseaudio /dev/snd/controlC0: shizoor2385 F pulseaudio /dev/snd/seq:timidity 1626 F timidity Date: Mon Jun 15 23:17:25 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=/dev/mapper/games--tower--vg-swap_1 IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: auto BOOT_IMAGE=Linux ro root=/dev/mapper/games--tower--vg-root PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 09/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465424] [NEW] package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: /boot keeps filling up with deprecated packages. I don't know if I'm meant to report this bug over and over or just purge to fix it. Please advise. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-55-generic 3.13.0-55.92 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: shizoor2385 F pulseaudio /dev/snd/controlC0: shizoor2385 F pulseaudio /dev/snd/seq:timidity 1626 F timidity Date: Mon Jun 15 23:17:25 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=/dev/mapper/games--tower--vg-swap_1 IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: auto BOOT_IMAGE=Linux ro root=/dev/mapper/games--tower--vg-root PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 09/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package 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/1465424 Title: package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: /boot keeps filling up with deprecated packages. I don't know if I'm meant to report this bug over and over or just purge to fix it. Please advise. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-55-generic 3.13.0-55.92 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: shizoor2385 F pulseaudio /dev/snd/controlC0: shizoor2385 F pulseaudio /dev/snd/seq:timidity 1626 F timidity Date: Mon Jun 15 23:17:25 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=/dev/mapper/games--tower--vg-swap_1 IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: auto BOOT_IMAGE=Linux ro root=/dev/mapper/games--tower--vg-root PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-55-generic 3.13.0-55.92 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 09/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name
[Kernel-packages] [Bug 1465419] [NEW] linux: 4.0.0-2.3 -proposed tracker
Public bug reported: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Wily) Importance: Medium Status: New ** Tags: block-proposed kernel-release-tracking-bug wily ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Tags added: wily ** Also affects: kernel-development-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New = In Progress ** Changed in: kernel-development-workflow Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-development-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided = Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) = Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu Wily) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.3 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description:
[Kernel-packages] [Bug 1465439] [NEW] Can't eject cd rom : Inappropriate ioctl for device
Public bug reported: Can't eject an empty CD-Rom tray. None of the things suggested here (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At best, working from a console, I get the message above. At worst, the CD drawer grunts as though trying to eject, but doesn't open. Using a paperclip to push the hidden manual release does work, and once the tray has a CD in it, it ejects every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1662 F pulseaudio geoff 1965 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Tue Jun 16 11:28:07 2015 HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 320 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0MH651 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 staging 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/1465439 Title: Can't eject cd rom : Inappropriate ioctl for device Status in linux package in Ubuntu: New Bug description: Can't eject an empty CD-Rom tray. None of the things suggested here (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At best, working from a console, I get the message above. At worst, the CD drawer grunts as though trying to eject, but doesn't open. Using a paperclip to push the hidden manual release does work, and once the tray has a CD in it, it ejects every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1662 F pulseaudio geoff 1965 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Tue Jun 16 11:28:07 2015 HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 320 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0MH651 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465439] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465439 Title: Can't eject cd rom : Inappropriate ioctl for device Status in linux package in Ubuntu: Confirmed Bug description: Can't eject an empty CD-Rom tray. None of the things suggested here (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At best, working from a console, I get the message above. At worst, the CD drawer grunts as though trying to eject, but doesn't open. Using a paperclip to push the hidden manual release does work, and once the tray has a CD in it, it ejects every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1662 F pulseaudio geoff 1965 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Tue Jun 16 11:28:07 2015 HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 320 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0MH651 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465419] Re: linux: 4.0.0-2.3 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-proposed Status: New = Fix Released ** Description changed: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC + proposed-announcement-sent:True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465419 Title: linux: 4.0.0-2.3 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.0.0-2.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Monday, 15. June 2015 22:16 UTC kernel-phase-changed:Monday, 15. June 2015 22:16 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Monday, 15. June 2015 23:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1465419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
