[Kernel-packages] [Bug 1571786] Re: Broadcom 43602 requires module to be reloaded to work
seems like rather a driver issue, though it would be interesting to see if the n-m SRU candidate in xenial-proposed makes a difference for you ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571786 Title: Broadcom 43602 requires module to be reloaded to work Status in linux package in Ubuntu: Confirmed Bug description: Running 16.04, and a recent update (last week?) introduced the following issue. I have a Broadcom wireless card: 02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Upon startup the network will connect fine. Then after about a minute it will drop out. Possibly related to the following in dmesg: [ 163.870916] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 If I rmmod and re-insert brcmfmac it works until the next reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581332] [NEW] Test for request mirror, please ignore
Public bug reported: == Comment: #0 - bugproxy bugproxy - 2016-05-12 02:33:58 == ---Problem Description--- Test for request mirroring Contact Information = test for request mirroring ---uname output--- test for request mirroring Machine Type = test for request mirroring ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for test for request mirroring: -Attach sysctl -a output output to the bug. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-all bugnameltc-141346 severity-low targetmilestone-inin--- ** Tags added: architecture-all bugnameltc-141346 severity-low targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581332 Title: Test for request mirror, please ignore Status in linux package in Ubuntu: New Bug description: == Comment: #0 - bugproxy bugproxy - 2016-05-12 02:33:58 == ---Problem Description--- Test for request mirroring Contact Information = test for request mirroring ---uname output--- test for request mirroring Machine Type = test for request mirroring ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for test for request mirroring: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571786] [NEW] Broadcom 43602 requires module to be reloaded to work
You have been subscribed to a public bug: Running 16.04, and a recent update (last week?) introduced the following issue. I have a Broadcom wireless card: 02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Upon startup the network will connect fine. Then after about a minute it will drop out. Possibly related to the following in dmesg: [ 163.870916] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 If I rmmod and re-insert brcmfmac it works until the next reboot. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- Broadcom 43602 requires module to be reloaded to work https://bugs.launchpad.net/bugs/1571786 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 1581332] [NEW] Test for request mirror, please ignore
You have been subscribed to a public bug: == Comment: #0 - bugproxy bugproxy - 2016-05-12 02:33:58 == ---Problem Description--- Test for request mirroring Contact Information = test for request mirroring ---uname output--- test for request mirroring Machine Type = test for request mirroring ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for test for request mirroring: -Attach sysctl -a output output to the bug. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-all bugnameltc-141346 severity-low targetmilestone-inin--- -- Test for request mirror, please ignore https://bugs.launchpad.net/bugs/1581332 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 1581326] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1581326 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/1581326 Title: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS. Status in linux package in Ubuntu: Incomplete Bug description: Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00, Successfully discovered HBA and the devices connected to HBA. >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). volume successfully created and listed from SAS3IRCU utility. >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU utility. Kernel crashed here while creating second volume. >>tried with all possible combinations of RAID volumes. Please find the attached kernel crash logs. >>cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 HBA used : LSI SAS3(Fury) Issue : Kernel gets crashed , when tried creating 2nd RAID volume. Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1121699] Re: aufs CONFIG_AUFS_EXPORT build option should be enabled
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) 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/1121699 Title: aufs CONFIG_AUFS_EXPORT build option should be enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This is needed to export aufs filesystems via nfs. This was set in a previous version (in Debian - http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=490079), and released in Ubuntu build for aufs 0+20080719-4 (https://launchpad.net/ubuntu/+source/aufs/0+20080719-4), so this could perhaps be considered a regression (although to be fair aufs and its packaging has undergone significant rewriting since then). Regardless considering aufs is a popular method of supporting large storage systems (among other things) and nfs is a popular method of exporting large storage systems, it would be great if this could be enabled in a future build, unless there is some known contraindication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1121699] Re: aufs CONFIG_AUFS_EXPORT build option should be enabled
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1121699 Title: aufs CONFIG_AUFS_EXPORT build option should be enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This is needed to export aufs filesystems via nfs. This was set in a previous version (in Debian - http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=490079), and released in Ubuntu build for aufs 0+20080719-4 (https://launchpad.net/ubuntu/+source/aufs/0+20080719-4), so this could perhaps be considered a regression (although to be fair aufs and its packaging has undergone significant rewriting since then). Regardless considering aufs is a popular method of supporting large storage systems (among other things) and nfs is a popular method of exporting large storage systems, it would be great if this could be enabled in a future build, unless there is some known contraindication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
8321521 is good after 40 hours, moving to 586fbce -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581326] [NEW] Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.
Public bug reported: Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00, Successfully discovered HBA and the devices connected to HBA. >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). >>volume successfully created and listed from SAS3IRCU utility. >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU >>utility. Kernel crashed here while creating second volume. >>tried with all possible combinations of RAID volumes. Please find the attached kernel crash logs. >>cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 HBA used : LSI SAS3(Fury) Issue : Kernel gets crashed , when tried creating 2nd RAID volume. Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel crash logs." https://bugs.launchpad.net/bugs/1581326/+attachment/4661776/+files/ubuntu_kernal_crash_raidvolume.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581326 Title: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS. Status in linux package in Ubuntu: New Bug description: Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00, Successfully discovered HBA and the devices connected to HBA. >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). volume successfully created and listed from SAS3IRCU utility. >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU utility. Kernel crashed here while creating second volume. >>tried with all possible combinations of RAID volumes. Please find the attached kernel crash logs. >>cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 HBA used : LSI SAS3(Fury) Issue : Kernel gets crashed , when tried creating 2nd RAID volume. Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1121699] Re: aufs CONFIG_AUFS_EXPORT build option should be enabled
This has regressed again in 16.04 but it is still needed sarvatt@sarvatt-ThinkPad-X1-Carbon{~/}:grep CONFIG_AUFS_EXPORT /boot/config-4.4.0-22-generic # CONFIG_AUFS_EXPORT is not set -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1121699 Title: aufs CONFIG_AUFS_EXPORT build option should be enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Wily: Fix Released Bug description: This is needed to export aufs filesystems via nfs. This was set in a previous version (in Debian - http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=490079), and released in Ubuntu build for aufs 0+20080719-4 (https://launchpad.net/ubuntu/+source/aufs/0+20080719-4), so this could perhaps be considered a regression (although to be fair aufs and its packaging has undergone significant rewriting since then). Regardless considering aufs is a popular method of supporting large storage systems (among other things) and nfs is a popular method of exporting large storage systems, it would be great if this could be enabled in a future build, unless there is some known contraindication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577957] Re: Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation)
OK, after 3 days, even the most recent firmware still has this bug: /lib/firmware/iwlwifi-7265D-21.ucode I'm switching back to the 15.10 firmware which did NOT have this bug and we'll see if it still crashes: /lib/firmware/iwlwifi-7265D-12.ucode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577957 Title: Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation) Status in linux package in Ubuntu: Confirmed Bug description: The stock firmware for this device /lib/firmware/iwlwifi- 7265D-16.ucode is crashing. Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode) isn't supported by the existing iwlwifi driver, and so the driver likely needs to be upgraded (or downgraded as well (https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport- iwlwifi.git/?h=release/LinuxCore18). I can also confirm that wifi *did* work successfully on 15.10 before upgrading to 16.04, although the kernel module required frequent restarts due to this bug: https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595 A detailed message about the firmware crash is located in the attachment from dmesg output. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: mrhines2419 F...m pulseaudio /dev/snd/controlC1: mrhines2419 F pulseaudio /dev/snd/controlC0: mrhines2419 F pulseaudio CurrentDesktop: KDE Date: Tue May 3 16:50:50 2016 HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42 InstallationDate: Installed on 2016-01-05 (119 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (12 days ago) dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
I have bisected the source of the bug, then took a brief attempt at a fix, unfortunately the quickie fix failed (bad CONST definitions in an .h file). I thought perhaps it was some kind of memory region locking error causing corruption, but it appears to be more complicated than that. The bad commit is b836439 - 4KB Sector Support. The previous good commit is 2f5d1f7. I'm having difficulty integrating this compiled kernel into my PXE environment, hence the week long delay in posting this, unfortunately I lowered my priority for the whole issue once I figured it was too late to get anything into the new LTS release first run and it's been marked as expired. christopher.m.penalver said to mark as Confirmed, but I don't know if I can do that myself, or if I can do anything at all at this point other than post this info here for anyone who's interested. If I do ever get time to look at the (significant) code changes for the 4K support, I'll post changes here as well? Dan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION Status in linux package in Ubuntu: Confirmed Bug description: The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 seconds until reset. The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 7419]. The Dell Poweredge 1800 has newest BIOS (A07). All hardware has been tested thoroughly OK except possibly the APIC component (Serverset Northbridge?). The 14.04LTS with all updates (or not) works fine with a perfectly consistent throughput of 77MB/s (slowest HD=66MB/s), RAID5. 15.10 has the hangs of 10-60 seconds, AND with newest updates as of 26-FEB-2016. I have changed PCI interrupts around and moved card slots to minimize sharing and removed cards - repeatedly. All hard drives and cables have been thoroughly tested, but the drives are mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s. The drives not only work perfectly in 14.04LTS, but all Windows versions and DOS/BIOS-INT 19 as well (0x13). I have tried all combinations of card RAID options Read ahead, Write cache, and other BIOS options. Relevant dmesg lines (these were consecutive): [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0) [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ? [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0) [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.365 CurrentDesktop: Unity Date: Thu Mar 3 05:08:57 2016 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi file=u15.10-64/preseed/username.seed boot=casper netboot=nfs nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz ipv6.disable=1 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0P8611 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A04 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lis
[Kernel-packages] [Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
** Changed in: linux (Ubuntu) Status: Expired => 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/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION Status in linux package in Ubuntu: Confirmed Bug description: The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 seconds until reset. The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 7419]. The Dell Poweredge 1800 has newest BIOS (A07). All hardware has been tested thoroughly OK except possibly the APIC component (Serverset Northbridge?). The 14.04LTS with all updates (or not) works fine with a perfectly consistent throughput of 77MB/s (slowest HD=66MB/s), RAID5. 15.10 has the hangs of 10-60 seconds, AND with newest updates as of 26-FEB-2016. I have changed PCI interrupts around and moved card slots to minimize sharing and removed cards - repeatedly. All hard drives and cables have been thoroughly tested, but the drives are mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s. The drives not only work perfectly in 14.04LTS, but all Windows versions and DOS/BIOS-INT 19 as well (0x13). I have tried all combinations of card RAID options Read ahead, Write cache, and other BIOS options. Relevant dmesg lines (these were consecutive): [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0) [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ? [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0) [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.365 CurrentDesktop: Unity Date: Thu Mar 3 05:08:57 2016 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi file=u15.10-64/preseed/username.seed boot=casper netboot=nfs nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz ipv6.disable=1 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0P8611 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A04 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555898] Re: BUG: Bad page map in process JS Helper pte:8000000406bfd825 pmd:1c7bff067
[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/1555898 Title: BUG: Bad page map in process JS Helper pte:800406bfd825 pmd:1c7bff067 Status in linux package in Ubuntu: Expired Bug description: Reported on bootup ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oldrocker99 1897 F pulseaudio /dev/snd/controlC1: oldrocker99 1897 F pulseaudio /dev/snd/controlC0: oldrocker99 1897 F pulseaudio Date: Thu Mar 10 20:34:18 2016 Failure: oops HibernationDevice: RESUME=UUID=d8ddc656-a82b-4779-9bdc-260ad608faa2 InstallationDate: Installed on 2016-03-03 (7 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) MachineType: MSI MS-7693 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic.efi.signed root=UUID=6a4393d9-946d-459e-8118-33ea7b9f499f ro iommu=soft 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: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: Bad page map in process JS Helper pte:800406bfd825 pmd:1c7bff067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.2:bd12/16/2014:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.name: MS-7693 dmi.product.version: 4.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1537209] Re: Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10)
[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/1537209 Title: Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10) Status in linux package in Ubuntu: Expired Bug description: After updrade my laptop Lenovo T430u from Kubuntu Vivid to Wily), I can not load the kernel 4.2.0-23 or 4.2.0-25 (not tested other versions). The only kernel I can use is 3.19.0-43 (from Kubuntu Vivid). If I choose 4.2.0-xx kernel, I just can see a black screen. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-25-generic 4.2.0-25.30 ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamane 1879 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 22 19:13:09 2016 HibernationDevice: RESUME=UUID=f11f0511-b75c-4a11-a486-9119d10ee8d7 InstallationDate: Installed on 2014-03-08 (685 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308) MachineType: LENOVO 33525SP ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic root=UUID=0575faf0-2a03-4d14-8eff-4e45024318f0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-43-generic N/A linux-backports-modules-3.19.0-43-generic N/A linux-firmware 1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to wily on 2016-01-15 (6 days ago) dmi.bios.date: 01/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H6ET90WW (2.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 33525SP dmi.board.vendor: LENOVO dmi.board.version: Win8 STD EM DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ET90WW(2.08):bd01/11/2013:svnLENOVO:pn33525SP:pvrThinkPadT430u:rvnLENOVO:rn33525SP:rvrWin8STDEMDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33525SP dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
[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/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION Status in linux package in Ubuntu: Expired Bug description: The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 seconds until reset. The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 7419]. The Dell Poweredge 1800 has newest BIOS (A07). All hardware has been tested thoroughly OK except possibly the APIC component (Serverset Northbridge?). The 14.04LTS with all updates (or not) works fine with a perfectly consistent throughput of 77MB/s (slowest HD=66MB/s), RAID5. 15.10 has the hangs of 10-60 seconds, AND with newest updates as of 26-FEB-2016. I have changed PCI interrupts around and moved card slots to minimize sharing and removed cards - repeatedly. All hard drives and cables have been thoroughly tested, but the drives are mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s. The drives not only work perfectly in 14.04LTS, but all Windows versions and DOS/BIOS-INT 19 as well (0x13). I have tried all combinations of card RAID options Read ahead, Write cache, and other BIOS options. Relevant dmesg lines (these were consecutive): [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0) [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ? [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0) [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.365 CurrentDesktop: Unity Date: Thu Mar 3 05:08:57 2016 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi file=u15.10-64/preseed/username.seed boot=casper netboot=nfs nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz ipv6.disable=1 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0P8611 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A04 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556569] Re: ubuntu-bug linux
[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/1556569 Title: ubuntu-bug linux Status in linux package in Ubuntu: Expired Bug description: ubuntu-bug linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-12-generic 4.4.0-12.28 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: filipp 3080 F pulseaudio /dev/snd/controlC0: filipp 3080 F pulseaudio Date: Sun Mar 13 11:18:46 2016 HibernationDevice: RESUME=UUID=9cda1080-5b7b-4ccf-8e08-ea61dde382d1 InstallationDate: Installed on 2014-09-26 (533 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic root=UUID=1c4ee869-1f68-4ce2-8cf6-ca934c3cb03c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-12-generic N/A linux-backports-modules-4.4.0-12-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN48WW(V3.11) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo M30-70 dmi.modalias: dmi:bvnLENOVO:bvr8BCN48WW(V3.11):bd07/20/2015:svnLENOVO:pn20446:pvrLenovoM30-70:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrLenovoM30-70: dmi.product.name: 20446 dmi.product.version: Lenovo M30-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549840] Re: Skip music tracks via car bluetoorh
Hello, THe same for me on Maco - Rc-proposed up to date. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1549840 Title: Skip music tracks via car bluetoorh Status in bluez package in Ubuntu: Confirmed Bug description: When the phobe is connected to my cars bluetooth. I can play music tracks with the built in music approval on the phone but cannot skip tracks with the controls in the car. I am using bq Aquaris 5 hd with oat 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1549840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549840] Re: Skip music tracks via car bluetoorh
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1549840 Title: Skip music tracks via car bluetoorh Status in bluez package in Ubuntu: Confirmed Bug description: When the phobe is connected to my cars bluetooth. I can play music tracks with the built in music approval on the phone but cannot skip tracks with the controls in the car. I am using bq Aquaris 5 hd with oat 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1549840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working
linux- image-4.1.0-040100rc1-generic_4.1.0-040100rc1.201605121447_amd64.deb - WWW -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498667 Title: [Toshiba P50W-B00F] Touchscreen no longer working Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Sometime in the last month or so my touchscreen stopped working on my Toshiba P50W. The dmesg log shows it constantly reconnecting to it: [ 556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd [ 556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.538349] usb 1-4: Product: Touchscreen [ 556.538351] usb 1-4: Manufacturer: ELAN [ 556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 556.547788] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374 [ 556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 556.600584] usb 1-4: USB disconnect, device number 119 [ 556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd [ 556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.990503] usb 1-4: Product: Touchscreen [ 556.990506] usb 1-4: Manufacturer: ELAN [ 556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 557.001248] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376 [ 557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 557.013831] usb 1-4: USB disconnect, device number 120 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-11-generic 4.2.0-11.13 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob2041 F pulseaudio /dev/snd/controlC0: bob2041 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 09:46:25 2015 HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12 InstallationDate: Installed on 2013-12-26 (635 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: TOSHIBA Satellite P50W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-11-generic N/A linux-backports-modules-4.2.0-11-generic N/A linux-firmware1.148 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago) dmi.bios.date: 08/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite P50W-B dmi.product.version: PSVP2A-00F002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581005] Re: Dell XPS 15 9550 Freezes when HDMI is plugged in
Looks like the fix was in rc4. RC4 works fine, all prior release candidates freeze. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581005 Title: Dell XPS 15 9550 Freezes when HDMI is plugged in Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This is fixed upstream in the 4.6.0 series. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2087 F pulseaudio CurrentDesktop: Unity Date: Thu May 12 07:25:29 2016 HibernationDevice: RESUME=UUID=20adf9e8-41f0-4bf8-8075-dcff091511d4 InstallationDate: Installed on 2016-03-12 (60 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=ea2a2622-df89-4bf1-8f58-99f313ed3908 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580816] Re: linux-armadaxp: 3.2.0-1666.91 -proposed tracker
** Tags added: qa-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1580816 Title: linux-armadaxp: 3.2.0-1666.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1666.91 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 -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1580658 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1580816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1534440] Re: CVE-2015-7566
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1534440 Title: CVE-2015-7566 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid so
[Kernel-packages] [Bug 1555865] Re: CVE-2015-7515
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1555865 Title: CVE-2015-7515 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status
[Kernel-packages] [Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
** Changed in: xorg (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable Status in shim: New Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.04 since at least four months, always with the nvidia proprietary drivers (installed from the repository). I used nvidia-361 for a while with no issues (and i need it for steam gaming). However, an update installed on my machine yesterday breaks the nvidia drivers. I tried purging the driver, rebooting and reinstalling and i tried a newer version for the ubuntu-drivers ppa. Nothing helps: With the nvidia driver installed, i get a low- resolution login screen, but cannot login due to missing 3d acceleration. Running on nouveau works fine. This seems very strange to since everything worked until this afternoon. Yesterday, i was happily playing games on steam, installed some updates and now, my graphics are broken. $ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 Date: Mon Apr 25 17:45:12 2016 DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381] InstallationDate: Installed on 2016-01-05 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 17:44:29 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574069] Re: zfs-dkms 0.6.5.6-0ubuntu8: zfs kernel module failed to build
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1574069 Title: zfs-dkms 0.6.5.6-0ubuntu8: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: I'm already using ZFS (since 15.10) so I'm re-submitting in case this provides more data to debug the issue. Otherwise looks like a duplicate of #1568721 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-21-generic (x86_64) Sat 23 Apr 18:29:18 BST 2016 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.4.0-21-generic Date: Sat Apr 23 18:29:22 2016 InstallationDate: Installed on 2013-07-04 (1024 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageVersion: 0.6.5.6-0ubuntu8 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu8: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1537886] Re: CVE-2013-4312
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1537886 Title: CVE-2013-4312 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vi
[Kernel-packages] [Bug 1581249] Re: resume on dell xps 15 9550 fails
@arges I am also experiencing suspend issues on my XPS13 but before opening a separate bug report I would like to check if our systems are affected by the same bug. Please check/confirm the following: 1. Is your system fails to resume or stuck during suspend? Please suspend the system using system menu (instead of closing the LID) and describe power-button light behavior. Is it turned off after 5-10 seconds? 2. Is there an external monitor? What happens if it's disconnected? (In my case connecting/reconnecting the monitor after the system is booted triggers the issues). 3. Is it a persistent behavior? 4. Is http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.10-xenial/ still broken? (It solved the problem on my system). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581249 Title: resume on dell xps 15 9550 fails Status in linux package in Ubuntu: Confirmed Bug description: 4.4.0-22 fails to resume after suspend. 4.6 mainline from 20160508 works. To reproduce: 1) suspend machine by closing lid 2) open lid -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware 1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
** Changed in: gnome-settings-daemon Status: Unknown => Fix Released ** Changed in: gnome-settings-daemon Importance: Unknown => 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/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Fix Released Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
I used ftrace to do some duration measuring of the timer function fb_flashcursor(). I noticed several places where this timer takes around 98 ms to complete. This time seems to be due to multiple calls to __memcpy_toio() in ast_dirty_update(): for (i = y; i <= y2; i++) { /* assume equal stride for now */ src_offset = dst_offset = i * afbdev->afb.base.pitches[0] + (x * bpp); memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram + src_offset, (x2 - x + 1) * bpp); My theory is that this is causing mod_timer() to block on the other CPU, resulting in the soft lockup. Also - I built a custom d-i using pristine 4.6-rc7, and I am able to easily reproduce this. I think the next step here is to report this to 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/1574814 Title: ThunderX: soft lockup in cursor_timer_handler() Edit Status in linux package in Ubuntu: Confirmed Bug description: I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via virtual media: http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso During boot I observed the following lockup on the serial console: [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! [swapper/14:0] [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E) [ 84.922749] [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic #37-Ubuntu [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT) [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 801f6c9e8000 [ 84.922771] PC is at cursor_timer_handler+0x30/0x58 [ 84.922775] LR is at cursor_timer_handler+0x30/0x58 [ 84.922778] pc : [] lr : [] pstate: 00400145 [ 84.922781] sp : 801f6c9ebc20 [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8 [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8 [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00 [ 84.922798] x23: 801f667d9800 x22: 804ec4c0 [ 84.922802] x21: 0100 x20: 8000f94398d8 [ 84.922807] x19: 8000f9439800 x18: c76a5358 [ 84.922811] x17: 97bbd2a8 x16: 802a5040 [ 84.922816] x15: 3e4cf1e0 x14: 0008 [ 84.922820] x13: x12: 003d0900 [ 84.922824] x11: 003d0900 x10: 8090f200 [ 84.922829] x9 : 3d09 x8 : 000e [ 84.922833] x7 : 801f7b3c5008 x6 : [ 84.922837] x5 : x4 : 0001 [ 84.922842] x3 : x2 : 801f6c899e05 [ 84.922846] x1 : 801f667d99e0 x0 : [ 84.922850] [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd [ 101.342677] random: nonblocking pool is initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580272] Re: i915-bpo crashes on external hdmi input
** Description changed: - This crash happens when plugging in an external HDMI projector in + This issue happens when plugging in an external HDMI projector in mirrored mode. + + To reproduce this issue: + 1) Plug in external HDMI monitor + 2) Set mirrored displays + 3) Unplug HDMI + 4) check dmesg for warnings + + -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580272 Title: i915-bpo crashes on external hdmi input Status in linux package in Ubuntu: Confirmed Bug description: This issue happens when plugging in an external HDMI projector in mirrored mode. To reproduce this issue: 1) Plug in external HDMI monitor 2) Set mirrored displays 3) Unplug HDMI 4) check dmesg for warnings -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.s
[Kernel-packages] [Bug 1581249] [NEW] resume on dell xps 15 9550 fails
Public bug reported: 4.4.0-22 fails to resume after suspend. 4.6 mainline from 20160508 works. To reproduce: 1) suspend machine by closing lid 2) open lid -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware 1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Critical Status: Confirmed ** Description changed: 4.4.0-22 fails to resume after suspend. 4.6 mainline from 20160508 works. + + To reproduce: + 1) suspend machine by closing lid + 2) open lid -- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: mark 4296 F pulseaudio + USER PID ACCESS COMMAND + /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. - Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. - Bus 001 Device 004: ID 0c45:6713 Microdia - 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 04f3:21d4 Elan Microelectronics Corp. + Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. + Bus 001 Device 004: ID 0c45:6713 Microdia + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: - LANGUAGE=en_GB:en - TERM=linux - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=linux + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + 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-4.4.0-22-generic N/A - linux-backports-modules-4.4.0-22-generic N/A - linux-firmware 1.157 + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware 1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1580272] Re: i915-bpo crashes on external hdmi input
I've also tested this on 4.4.0-22 with i915 patches here: http://koti.kapsi.fi/~tjaalton/skl/mst/ And the problem persists. In addition I've tested a 4.6 mainline from 5/8 and the problem persists there as well. Here is the warning from the mainline kernel: [ 44.871672] [ cut here ] [ 44.871687] WARNING: CPU: 1 PID: 871 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3586 skl_update_other_pipe_wm+0x16c/0x180 [i915] [ 44.871688] WARN_ON(!wm_changed) [ 44.871688] Modules linked in: [ 44.871689] rfcomm bnep snd_hda_codec_hdmi dell_led brcmfmac snd_hda_codec_realtek intel_rapl snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp brcmutil coretemp uvcvideo cfg80211 i2c_designware_platform i2c_designware_core kvm_intel videobuf2_vmalloc kvm snd_hda_intel videobuf2_memops snd_hda_codec videobuf2_v4l2 dell_wmi dell_laptop videobuf2_core dell_smbios snd_hda_core videodev dcdbas rtsx_pci_ms irqbypass snd_hwdep media memstick snd_pcm hid_multitouch crct10dif_pclmul snd_seq_midi crc32_pclmul btusb btrtl ghash_clmulni_intel snd_seq_midi_event snd_rawmidi aesni_intel snd_seq snd_seq_device aes_x86_64 lrw snd_timer gf128mul glue_helper snd ablk_helper cryptd soundcore hci_uart btbcm btqca idma64 joydev input_leds shpchp btintel virt_dma mei_me serio_raw bluetooth mei processor_thermal_device [ 44.871711] intel_lpss_pci intel_soc_dts_iosf acpi_als kfifo_buf industrialio intel_lpss_acpi intel_hid dell_smo8800 int3403_thermal int3400_thermal int3402_thermal intel_lpss acpi_pad sparse_keymap int340x_thermal_zone acpi_thermal_rel mac_hid parport_pc ppdev lp parport autofs4 usbhid rtsx_pci_sdmmc nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt nvme fb_sys_fops uas nvme_core ahci drm usb_storage rtsx_pci libahci i2c_hid hid wmi pinctrl_sunrisepoint video pinctrl_intel fjes [ 44.871727] CPU: 1 PID: 871 Comm: Xorg Not tainted 4.6.0-999-generic #201605082200 [ 44.871728] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016 [ 44.871729] 0286 52e51aba 8808985bf918 813f2ea3 [ 44.871731] 8808985bf968 8808985bf958 8108294b [ 44.871732] 0e02 880891b41000 8800219d9da4 880891b42000 [ 44.871733] Call Trace: [ 44.871736] [] dump_stack+0x63/0x90 [ 44.871739] [] __warn+0xcb/0xf0 [ 44.871740] [] warn_slowpath_fmt+0x5f/0x80 [ 44.871749] [] skl_update_other_pipe_wm+0x16c/0x180 [i915] [ 44.871758] [] skl_update_wm+0x185/0x640 [i915] [ 44.871769] [] ? gen9_write32+0x235/0x370 [i915] [ 44.871782] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915] [ 44.871790] [] intel_update_watermarks+0x1e/0x30 [i915] [ 44.871802] [] haswell_crtc_enable+0x321/0x8c0 [i915] [ 44.871813] [] intel_atomic_commit+0x5fb/0xdd0 [i915] [ 44.871825] [] ? drm_atomic_check_only+0x181/0x600 [drm] [ 44.871832] [] drm_atomic_commit+0x37/0x60 [drm] [ 44.871837] [] drm_atomic_helper_set_config+0x7a/0xb0 [drm_kms_helper] [ 44.871844] [] drm_mode_set_config_internal+0x62/0x100 [drm] [ 44.871851] [] drm_mode_setcrtc+0x3e0/0x500 [drm] [ 44.871856] [] drm_ioctl+0x152/0x540 [drm] [ 44.871862] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 44.871864] [] do_vfs_ioctl+0xa1/0x5b0 [ 44.871866] [] ? __set_task_blocked+0x41/0xa0 [ 44.871867] [] ? __set_current_blocked+0x36/0x60 [ 44.871868] [] SyS_ioctl+0x79/0x90 [ 44.871869] [] ? SyS_rt_sigprocmask+0x8e/0xc0 [ 44.871872] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 44.871873] ---[ end trace 12f151afa4c9e462 ]--- [ 53.708328] dell_wmi: Unknown WMI event type 0x12 ** Description changed: - This crash happens when plugging in an external HDMI projector. + This crash happens when plugging in an external HDMI projector in + mirrored mode. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 4296 F pulseaudio Date: Tue May 10 10:25:07 2016 InstallationDate: Installed on 2016-05-02 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/
[Kernel-packages] [Bug 1581243] Re: [Hyper-V] PCI Passthrough kernel hang and explicit barriers
No log files required, upstream commits cited. ** 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/1581243 Title: [Hyper-V] PCI Passthrough kernel hang and explicit barriers Status in linux package in Ubuntu: Confirmed Bug description: Two upstream commits (right now in Bjorn Helgaas's PCI tree, and heading to Linus's tree) address potential hangs in PCI passthrough. Please consider these upstream items for 16.10 and 16.04 (and HWE kernels based on lts-xenial). https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=deb22e5c84c884a129d801cf3bfde7411536998d PCI: hv: Report resources release after stopping the bus Kernel hang is observed when pci-hyperv module is release with device drivers still attached. E.g., when I do 'rmmod pci_hyperv' with BCM5720 device pass-through-ed (tg3 module) I see the following: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [rmmod:2104] ... Call Trace: [] tg3_read_mem+0x87/0x100 [tg3] [] ? 0xa063f000 [] tg3_poll_fw+0x85/0x150 [tg3] [] tg3_chip_reset+0x357/0x8c0 [tg3] [] tg3_halt+0x3b/0x190 [tg3] [] tg3_stop+0x171/0x230 [tg3] ... [] tg3_remove_one+0x90/0x140 [tg3] [] pci_device_remove+0x39/0xc0 [] __device_release_driver+0xa1/0x160 [] device_release_driver+0x23/0x30 [] pci_stop_bus_device+0x8a/0xa0 [] pci_stop_root_bus+0x36/0x60 [] hv_pci_remove+0x238/0x260 [pci_hyperv] The problem seems to be that we report local resources release before stopping the bus and removing devices from it and device drivers may try to perform some operations with these resources on shutdown. Move resources release report after we do pci_stop_root_bus(). Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=bdd74440d9e887b1fa648eefa17421def5f5243c PCI: hv: Add explicit barriers to config space accesspci/host-hv I'm trying to pass-through Broadcom BCM5720 NIC (Dell device 1f5b) on a Dell R720 server. Everything works fine when the target VM has only one CPU, but SMP guests reboot when the NIC driver accesses PCI config space with hv_pcifront_read_config()/hv_pcifront_write_config(). The reboot appears to be induced by the hypervisor and no crash is observed. Windows event logs are not helpful at all ('Virtual machine ... has quit unexpectedly'). The particular access point is always different and putting debug between them (printk/mdelay/...) moves the issue further away. The server model affects the issue as well: on Dell R420 I'm able to pass-through BCM5720 NIC to SMP guests without issues. While I'm obviously failing to reveal the essence of the issue I was able to come up with a (possible) solution: if explicit barriers are added to hv_pcifront_read_config()/hv_pcifront_write_config() the issue goes away. The essential minimum is rmb() at the end on _hv_pcifront_read_config() and wmb() at the end of _hv_pcifront_write_config() but I'm not confident it will be sufficient for all hardware. I suggest the following barriers: 1) wmb()/mb() between choosing the function and writing to its space. 2) mb() before releasing the spinlock in both _hv_pcifront_read_config()/ _hv_pcifront_write_config() to ensure that consecutive reads/writes to the space won't get re-ordered as drivers may count on that. Config space access is not supposed to be performance-critical so these explicit barriers should not cause any slowdown. [bhelgaas: use Linux "barriers" terminology] Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581243] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1581243 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/1581243 Title: [Hyper-V] PCI Passthrough kernel hang and explicit barriers Status in linux package in Ubuntu: Incomplete Bug description: Two upstream commits (right now in Bjorn Helgaas's PCI tree, and heading to Linus's tree) address potential hangs in PCI passthrough. Please consider these upstream items for 16.10 and 16.04 (and HWE kernels based on lts-xenial). https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=deb22e5c84c884a129d801cf3bfde7411536998d PCI: hv: Report resources release after stopping the bus Kernel hang is observed when pci-hyperv module is release with device drivers still attached. E.g., when I do 'rmmod pci_hyperv' with BCM5720 device pass-through-ed (tg3 module) I see the following: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [rmmod:2104] ... Call Trace: [] tg3_read_mem+0x87/0x100 [tg3] [] ? 0xa063f000 [] tg3_poll_fw+0x85/0x150 [tg3] [] tg3_chip_reset+0x357/0x8c0 [tg3] [] tg3_halt+0x3b/0x190 [tg3] [] tg3_stop+0x171/0x230 [tg3] ... [] tg3_remove_one+0x90/0x140 [tg3] [] pci_device_remove+0x39/0xc0 [] __device_release_driver+0xa1/0x160 [] device_release_driver+0x23/0x30 [] pci_stop_bus_device+0x8a/0xa0 [] pci_stop_root_bus+0x36/0x60 [] hv_pci_remove+0x238/0x260 [pci_hyperv] The problem seems to be that we report local resources release before stopping the bus and removing devices from it and device drivers may try to perform some operations with these resources on shutdown. Move resources release report after we do pci_stop_root_bus(). Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=bdd74440d9e887b1fa648eefa17421def5f5243c PCI: hv: Add explicit barriers to config space accesspci/host-hv I'm trying to pass-through Broadcom BCM5720 NIC (Dell device 1f5b) on a Dell R720 server. Everything works fine when the target VM has only one CPU, but SMP guests reboot when the NIC driver accesses PCI config space with hv_pcifront_read_config()/hv_pcifront_write_config(). The reboot appears to be induced by the hypervisor and no crash is observed. Windows event logs are not helpful at all ('Virtual machine ... has quit unexpectedly'). The particular access point is always different and putting debug between them (printk/mdelay/...) moves the issue further away. The server model affects the issue as well: on Dell R420 I'm able to pass-through BCM5720 NIC to SMP guests without issues. While I'm obviously failing to reveal the essence of the issue I was able to come up with a (possible) solution: if explicit barriers are added to hv_pcifront_read_config()/hv_pcifront_write_config() the issue goes away. The essential minimum is rmb() at the end on _hv_pcifront_read_config() and wmb() at the end of _hv_pcifront_write_config() but I'm not confident it will be sufficient for all hardware. I suggest the following barriers: 1) wmb()/mb() between choosing the function and writing to its space. 2) mb() before releasing the spinlock in both _hv_pcifront_read_config()/ _hv_pcifront_write_config() to ensure that consecutive reads/writes to the space won't get re-ordered as drivers may count on that. Config space access is not supposed to be performance-critical so these explicit barriers should not cause any slowdown. [bhelgaas: use Linux "barriers" terminology] Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581243] [NEW] [Hyper-V] PCI Passthrough kernel hang and explicit barriers
Public bug reported: Two upstream commits (right now in Bjorn Helgaas's PCI tree, and heading to Linus's tree) address potential hangs in PCI passthrough. Please consider these upstream items for 16.10 and 16.04 (and HWE kernels based on lts-xenial). https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=deb22e5c84c884a129d801cf3bfde7411536998d PCI: hv: Report resources release after stopping the bus Kernel hang is observed when pci-hyperv module is release with device drivers still attached. E.g., when I do 'rmmod pci_hyperv' with BCM5720 device pass-through-ed (tg3 module) I see the following: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [rmmod:2104] ... Call Trace: [] tg3_read_mem+0x87/0x100 [tg3] [] ? 0xa063f000 [] tg3_poll_fw+0x85/0x150 [tg3] [] tg3_chip_reset+0x357/0x8c0 [tg3] [] tg3_halt+0x3b/0x190 [tg3] [] tg3_stop+0x171/0x230 [tg3] ... [] tg3_remove_one+0x90/0x140 [tg3] [] pci_device_remove+0x39/0xc0 [] __device_release_driver+0xa1/0x160 [] device_release_driver+0x23/0x30 [] pci_stop_bus_device+0x8a/0xa0 [] pci_stop_root_bus+0x36/0x60 [] hv_pci_remove+0x238/0x260 [pci_hyperv] The problem seems to be that we report local resources release before stopping the bus and removing devices from it and device drivers may try to perform some operations with these resources on shutdown. Move resources release report after we do pci_stop_root_bus(). Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=bdd74440d9e887b1fa648eefa17421def5f5243c PCI: hv: Add explicit barriers to config space accesspci/host-hv I'm trying to pass-through Broadcom BCM5720 NIC (Dell device 1f5b) on a Dell R720 server. Everything works fine when the target VM has only one CPU, but SMP guests reboot when the NIC driver accesses PCI config space with hv_pcifront_read_config()/hv_pcifront_write_config(). The reboot appears to be induced by the hypervisor and no crash is observed. Windows event logs are not helpful at all ('Virtual machine ... has quit unexpectedly'). The particular access point is always different and putting debug between them (printk/mdelay/...) moves the issue further away. The server model affects the issue as well: on Dell R420 I'm able to pass-through BCM5720 NIC to SMP guests without issues. While I'm obviously failing to reveal the essence of the issue I was able to come up with a (possible) solution: if explicit barriers are added to hv_pcifront_read_config()/hv_pcifront_write_config() the issue goes away. The essential minimum is rmb() at the end on _hv_pcifront_read_config() and wmb() at the end of _hv_pcifront_write_config() but I'm not confident it will be sufficient for all hardware. I suggest the following barriers: 1) wmb()/mb() between choosing the function and writing to its space. 2) mb() before releasing the spinlock in both _hv_pcifront_read_config()/ _hv_pcifront_write_config() to ensure that consecutive reads/writes to the space won't get re-ordered as drivers may count on that. Config space access is not supposed to be performance-critical so these explicit barriers should not cause any slowdown. [bhelgaas: use Linux "barriers" terminology] Signed-off-by: Vitaly Kuznetsov Signed-off-by: Bjorn Helgaas Acked-by: Jake Oshins ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581243 Title: [Hyper-V] PCI Passthrough kernel hang and explicit barriers Status in linux package in Ubuntu: New Bug description: Two upstream commits (right now in Bjorn Helgaas's PCI tree, and heading to Linus's tree) address potential hangs in PCI passthrough. Please consider these upstream items for 16.10 and 16.04 (and HWE kernels based on lts-xenial). https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=deb22e5c84c884a129d801cf3bfde7411536998d PCI: hv: Report resources release after stopping the bus Kernel hang is observed when pci-hyperv module is release with device drivers still attached. E.g., when I do 'rmmod pci_hyperv' with BCM5720 device pass-through-ed (tg3 module) I see the following: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [rmmod:2104] ... Call Trace: [] tg3_read_mem+0x87/0x100 [tg3] [] ? 0xa063f000 [] tg3_poll_fw+0x85/0x150 [tg3] [] tg3_chip_reset+0x357/0x8c0 [tg3] [] tg3_halt+0x3b/0x190 [tg3] [] tg3_stop+0x171/0x230 [tg3] ... [] tg3_remove_one+0x90/0x140 [tg3] [] pci_device_remove+0x39/0xc0 [] __device_release_driver+0xa1/0x160 [] device_release_driver+0x23/0x30 [] pci_stop_bus_device+0x8a/0xa0 [] pci_stop_root_bus+0x36/0x60 [] hv_pci_remove+0x238/0x260 [pci_
[Kernel-packages] [Bug 1581241] [NEW] bluetooth headset doesn't automatically configure for a2dp correctly (regression)
Public bug reported: I have a bluetooth headset capable of several modes of connection (headset, handsfree, and a2dp). In 15.10, once I had correctly configured it for a2dp once, applications using pulseaudio could use it freely each time it was connected to the machine. In 16.04, upon connection, applications that attempt to use it appear to hang waiting for something. I have to fiddle with its settings (and sorry I can't be more specific, but it's not clear to me exactly what sequence fixes it; I change it to/from headset and A2DP in blueman a few times, do the same in pavucontrol, etc., and at some point it starts working) for several minutes to get it working in a2dp mode. It appears that after connection I can put it in headset mode and start playing to it immediately, but of course the audio quality is horrible. Once I've fiddled it into working, it works until disconnected, and upon reconnect it behaves the same as before I fiddled it into submission: a2dp connection, but clients accessing it hang. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 12 18:38:16 2016 InstallationDate: Installed on 2015-06-04 (342 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-04-22 (20 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/07/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 5C:51:4F:7C:03:11 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1391 acl:0 sco:0 events:164 errors:0 TX bytes:27517 acl:0 sco:0 commands:163 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1581241 Title: bluetooth headset doesn't automatically configure for a2dp correctly (regression) Status in bluez package in Ubuntu: New Bug description: I have a bluetooth headset capable of several modes of connection (headset, handsfree, and a2dp). In 15.10, once I had correctly configured it for a2dp once, applications using pulseaudio could use it freely each time it was connected to the machine. In 16.04, upon connection, applications that attempt to use it appear to hang waiting for something. I have to fiddle with its settings (and sorry I can't be more specific, but it's not clear to me exactly what sequence fixes it; I change it to/from headset and A2DP in blueman a few times, do the same in pavucontrol, etc., and at some point it starts working) for several minutes to get it working in a2dp mode. It appears that after connection I can put it in headset mode and start playing to it immediately, but of course the audio quality is horrible. Once I've fiddled it into working, it works until disconnected, and upon reconnect it behaves the same as before I fiddled it into submission: a2dp connection, but clients accessing it hang. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 12 18:38:16 2016 InstallationDate: Installed on 2015-06-04 (342 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-04-22 (20 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/07/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:7C:03:11 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING P
[Kernel-packages] [Bug 1581236] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1581236 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/1581236 Title: Power state does not drop lower than pc03 for package (Haswell i7-4500U) Status in linux package in Ubuntu: Incomplete Bug description: So similarly to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917, I am also not able to get into pc10, as described there. I am using a sata drive, and after setting min_power to /sys/class/scsi_host/*/link_power_management_policy still does not get me into any states lower than pc03. Following these links -- without testing the patched kernel (Setting min_power gets me to pc03, but not any further) https://mjg59.dreamwidth.org/42156.html https://mjg59.dreamwidth.org/41713.html Attaching the powertop screencap: http://pastebin.ubuntu.com/16382692/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581236] [NEW] Power state does not drop lower than pc03 for package (Haswell i7-4500U)
Public bug reported: So similarly to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917, I am also not able to get into pc10, as described there. I am using a sata drive, and after setting min_power to /sys/class/scsi_host/*/link_power_management_policy still does not get me into any states lower than pc03. Following these links -- without testing the patched kernel (Setting min_power gets me to pc03, but not any further) https://mjg59.dreamwidth.org/42156.html https://mjg59.dreamwidth.org/41713.html Attaching the powertop screencap: http://pastebin.ubuntu.com/16382692/ ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1581236 Title: Power state does not drop lower than pc03 for package (Haswell i7-4500U) Status in linux package in Ubuntu: Incomplete Bug description: So similarly to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917, I am also not able to get into pc10, as described there. I am using a sata drive, and after setting min_power to /sys/class/scsi_host/*/link_power_management_policy still does not get me into any states lower than pc03. Following these links -- without testing the patched kernel (Setting min_power gets me to pc03, but not any further) https://mjg59.dreamwidth.org/42156.html https://mjg59.dreamwidth.org/41713.html Attaching the powertop screencap: http://pastebin.ubuntu.com/16382692/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580311] Re: Regression: drm / modesetting failure for i915
Another observation: booting with 4.4.0-22-generic is successful if I have an external HDMI display connected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580311 Title: Regression: drm / modesetting failure for i915 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since updating to 16.04 with kernel vmlinuz-4.4.0-22-generic my laptop no longer completes the boot sequence under a normal boot scenario - the "loading initrd..." message is displayed, then, when the VGA modesetting usually kicks the display into a higher resolution, the screen blanks and the startup apparently halts. This is a regression from 4.2 series kernels. I can successfully bring up the system if I revert to 4.2.0-35, and also if I boot 4.4 with the failsafe setting (but then X is painfully slow, as its using software) Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 May 10 20:29:56 2016 DistUpgraded: 2016-05-04 00:10:55,503 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06ac] InstallationDate: Installed on 2015-05-12 (364 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 15-3552 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/ubuntu--15--vg-root ro plymouth:debug i8042.nopnp=1 vesafb.invalid=1 drm.debug=0xe SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-05-03 (6 days ago) dmi.bios.date: 11/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.3 dmi.board.name: 0CP33T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.3:bd11/17/2015:svnDellInc.:pnInspiron15-3552:pvr4.0.3:rvnDellInc.:rn0CP33T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 10 12:26:45 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5578 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580776] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at 0000000000000002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0
Being the tired and daft bugger that I am, I failed to convert minutes and seconds to frames properly resulting in trying to consume several hours worth of PCM data per track. Not my brightest moment and I would like to apologise for wasting your time... /Dave ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580776 Title: Kernel Oops - unable to handle kernel NULL pointer dereference at 0002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0 Status in linux package in Ubuntu: Invalid Bug description: While playing around with the CDROM API found in linux/cdrom.h I encountered a kernel oops when my program stalls. My code can be found at https://github.com/bigdavedev/audiorip. My program simply examines the ToC and then begins reading the PCM data track-by-track. I would expect it to complete without any major issue At first I assumed it was the CD, but after switching CDs several times I noticed that the oops happens at around frame 170925, reading CD_FRAMES (75) per ioctl. At this point, the disc is spinning at full speed. I have not yet tried reading fewer frames, nor have I tried setting the speed to something not max to see if I still receive a kernel oops. This would not be problematic to try. I have attached the output from `ubuntu-bug linux` to this issue. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dabr 2430 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-29 (102 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ASUSTeK COMPUTER INC. K55VD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/primary_lvm_volume-root ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-19 (22 days ago) UserGroups: adm audio bumblebee cdrom dialout dip kvm lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD 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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD 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/1580776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1511525] Re: Can't transfer file using bluetooth OBEX
@mpt any news on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1511525 Title: Can't transfer file using bluetooth OBEX Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in bluez package in Ubuntu: Invalid Bug description: Hi all On my BQ E4.5 I can't send or recive files using bluetooth. It looks strange for me that nobody reported this before so I decided to open this question. Thanks all To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578022] Re: dmidecode fails to output smibios 3.0 info
The following two upstream patches is needed to fix this (on my system): Let read_file return the actual data size http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=de9a74e1c60210bee229fcf55b1678a99d1b44dd dmidecode: Use read_file() to read the DMI table from sysfs http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=364055211b1956539c6a6268e111e244e1292c8c There's also a couple other SMBIOS 3.0 related fixes that is listed as recomended for 3.0 on http://dmidecode.nongnu.org/ Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=bf7bad24ce141dab5b5acc3ffb98ce5fe4a8e0f9 Use DWORD for Structure table maximum size in SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=ab02b117511230e46bbef7febbd854b9c832c13c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1578022 Title: dmidecode fails to output smibios 3.0 info Status in dmidecode package in Ubuntu: Confirmed Bug description: Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios 3.0. Rhel 7.2 can display smibios 3.0 on the same system without a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
the log doesn't seem to have useful clue ... could you "stop unity- settings-daemon" and lock/unlock the screen, just to see if that's also doing it without usd? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Unknown Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568830] Re: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124
> 3.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ This one works. I've got to say that it's really annoying that every time I reboot my system comes back with a degraded array: # cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid0 sdc[1] sdb[0] 1953524736 blocks super 1.2 512k chunks md0 : active raid1 sdd[0] 1953514496 blocks [2/1] [U_] unused devices: Before reboot it looked like this: # cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid0 sdb[0] sdc[1] 1953524736 blocks super 1.2 512k chunks md0 : active raid1 md1[1] sdd[0] 1953514496 blocks [2/2] [UU] unused devices: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568830 Title: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124 Status in linux package in Ubuntu: Triaged Bug description: I have a couple of RAID arrays with the following configuration: /dev/md1: Version : 1.2 Creation Time : Sat Dec 26 19:49:41 2015 Raid Level : raid0 Array Size : 1953524736 (1863.03 GiB 2000.41 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sat Dec 26 19:49:41 2015 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Chunk Size : 512K Name : linux.interlinx.bc.ca:1 (local to host linux.interlinx.bc.ca) UUID : f27ae74d:e2997e50:9df158ee:c5ed3cbb Events : 0 Number Major Minor RaidDevice State 0 8 160 active sync /dev/sdb 1 8 321 active sync /dev/sdc /dev/md0: Version : 0.90 Creation Time : Mon Jan 26 19:51:38 2009 Raid Level : raid1 Array Size : 1953514496 (1863.02 GiB 2000.40 GB) Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Fri Apr 8 00:00:42 2016 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 1 Spare Devices : 0 UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21 Events : 0.5031387 Number Major Minor RaidDevice State 0 8 480 active sync /dev/sdd 1 001 removed 2 91- faulty spare /dev/md1 This configuration has worked for a number of years but has all of a sudden started breaking with: [37722.335880] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124 [37722.335887] md/raid1:md0: md1: rescheduling sector 2554601336 [37722.376776] md/raid1:md0: redirecting sector 2554601336 to other mirror: md1 [37722.386455] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124 [37722.386461] md/raid1:md0: md1: rescheduling sector 2554601336 [37722.412059] md/raid1:md0: redirecting sector 2554601336 to other mirror: sdd [37722.735049] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554608496 124 [37722.735056] md/raid1:md0: md1: rescheduling sector 2554608496 [37722.789926] md/raid1:md0: redirecting sector 2554608496 to other mirror: md1 [37722.798689] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554608496 124 [37722.798696] md/raid1:md0: md1: rescheduling sector 2554608496 [37722.859314] md/raid1:md0: redirecting sector 2554608496 to other mirror: sdd [37724.819090] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554606584 12 [37724.819096] md/raid1:md0: md1: rescheduling sector 2554606584 [37727.455279] md/raid1:md0: redirecting sector 2554606584 to other mirror: sdd [37752.406865] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1748150224 124 [37752.521219] md/raid1:md0: Disk failure on md1, disabling device. [37752.521222] md/raid1:md0: Operation continuing on 1 devices. [37752.580186] RAID1 conf printout: [37752.580190] --- wd:1 rd:2 [37752.580194] disk 0, wo:0, o:1, dev:sdd [37752.580197] disk 1, wo:1, o:0, dev:md1 [37752.580199] RAID1 conf printout: [37752.580201] --- wd:1 rd:2 [37752.580203] disk 0, wo:0, o:1, dev:sdd [37752.580228] BUG: unable to handle kernel paging request at 1dff2107 [37752.584011] IP: [] close_write+0x6a/0xa0 [raid1] [37752.584011] PGD 20f667067 PUD 20f669067 PMD 0 [37752.584011] Oops: [#1] SMP
[Kernel-packages] [Bug 1574238] Re: Stand-by/sleep mode 16.04
The bug is fixed.Thank you very much for your help! ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1574238 Title: Stand-by/sleep mode 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Problems with Stand-by/sleep mode after upgrading to 16.04. Driver ventilation still running, but the screen stays black. No reaction at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: 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: Sun Apr 24 13:46:01 2016 DistUpgraded: 2016-04-22 21:07:47,908 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea] InstallationDate: Installed on 2015-06-04 (324 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7af49af0-d45a-4a2b-82e8-78cce2243823 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RKNTK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0RKNTK:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 24 13:05:15 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
Sure. Here you go. ** Attachment added: "usd.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510344/+attachment/4661498/+files/usd.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/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Unknown Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581202] [NEW] CVE-2016-0758
*** This bug is a security vulnerability *** Private security bug reported: Placeholder ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Undecided Status: New ** Tags: kernel-cve-tracking-bug ** Information type changed from Public to Private ** Summary changed: - CVE-- + CVE-2016-0758 ** Tags added: kernel-cve-tracking-bug ** Information type changed from Private to Private Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0758 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581202 Title: CVE-2016-0758 Status in linux package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux source package in Precise: New Status in linux-raspi2 source package in Precise: New Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-raspi2 source package in Trusty: New Status in linux-ti-omap4 source package in Trusty: New Status in linux source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: New Status in linux source package in Xenial: New Status in linux-raspi2 source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: New Status in linux source package in Yakkety: New Status in linux-raspi2 source package in Yakkety: New Status in linux-ti-omap4 source package in Yakkety: New Bug description: Placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang
I still need test results from my kernel build, since that has what is going to be in the next SRU kernel and if it's still broken then there's something to be backported to core-drm (from v4.4..v4.6) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 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) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
@Mario, thanks for testing the fix! I'm going to upload/SRU that one to start then. Could you run unity-settings-daemon with --debug and share the log? it might give an hint on what is happening with the other issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Unknown Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581201] [NEW] CVE-2016-3713
*** This bug is a security vulnerability *** Private security bug reported: Placeholder ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Undecided Status: New ** Tags: kernel-cve-tracking-bug ** Information type changed from Public to Private ** Summary changed: - CVE-- + CVE-2016-3713 ** Tags added: kernel-cve-tracking-bug ** Information type changed from Private to Private Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-3713 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581201 Title: CVE-2016-3713 Status in linux package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux source package in Precise: New Status in linux-raspi2 source package in Precise: New Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-raspi2 source package in Trusty: New Status in linux-ti-omap4 source package in Trusty: New Status in linux source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: New Status in linux source package in Xenial: New Status in linux-raspi2 source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: New Status in linux source package in Yakkety: New Status in linux-raspi2 source package in Yakkety: New Status in linux-ti-omap4 source package in Yakkety: New Bug description: Placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
Well there are really two problems here as I understand it. I can however confirm that that the first problem (backlight turns on on it's own at boot) is fixed by this patch. So that's a definite improvement. The second problem (backlight turns on on it's own after unlock) I can still reproduce. Here is my reproduce scenario. 1) Install patched u-s-d from patch in #55. 2) Turn on backlight with hotkey. 3) Shutdown machine. 4) Turn on machine. 5) Log in. 6) Turn off backlight with hotkey. 7) Lock machine (ctrl-alt-l), wait for screensaver to kick in. 8) unlock machine 9) Notice that backlight turned back on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Unknown Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580776] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at 0000000000000002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0
Alas, the exact same result on the exact same frame in the upstream mainline kernel... ** 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/1580776 Title: Kernel Oops - unable to handle kernel NULL pointer dereference at 0002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0 Status in linux package in Ubuntu: Confirmed Bug description: While playing around with the CDROM API found in linux/cdrom.h I encountered a kernel oops when my program stalls. My code can be found at https://github.com/bigdavedev/audiorip. My program simply examines the ToC and then begins reading the PCM data track-by-track. I would expect it to complete without any major issue At first I assumed it was the CD, but after switching CDs several times I noticed that the oops happens at around frame 170925, reading CD_FRAMES (75) per ioctl. At this point, the disc is spinning at full speed. I have not yet tried reading fewer frames, nor have I tried setting the speed to something not max to see if I still receive a kernel oops. This would not be problematic to try. I have attached the output from `ubuntu-bug linux` to this issue. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dabr 2430 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-29 (102 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ASUSTeK COMPUTER INC. K55VD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/primary_lvm_volume-root ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-19 (22 days ago) UserGroups: adm audio bumblebee cdrom dialout dip kvm lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD 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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD 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/1580776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577099] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Same here, didn't occured before with 14.04, started immediatly with Xenial 16.04 fresh install >From the syslog : May 11 18:29:10 hecatonchires kernel: [1.130925] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A May 11 18:29:10 hecatonchires kernel: [1.130974] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" $ uname -r -v -s Linux 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 $ sudo lspci -v -s 02.0 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. P8 series motherboard Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577099 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Incomplete Bug description: Graphical glitches in Firefox. Gere is dmesg log when it happens. [97970.020983] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [97970.021023] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun Description: Ubuntu 16.04 LTS Release: 16.04 linux-image-generic: Установлен: 4.4.0.21.22 Кандидат: 4.4.0.21.22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: sam2091 F...m pulseaudio /dev/snd/controlC0: sam2091 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 12:23:21 2016 HibernationDevice: RESUME=UUID=478fdfc2-ea5f-4e80-a404-cf3230067630 InstallationDate: Installed on 2016-04-16 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415) MachineType: LENOVO 25372A2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=b5bacb2b-487f-4164-ba6f-e8d22ab6c97e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET80WW (1.40 ) dmi.board.name: 25372A2 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET80WW(1.40):bd12/01/2011:svnLENOVO:pn25372A2:pvrThinkPadT410:rvnLENOVO:rn25372A2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 25372A2 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
It looks like the break happened in the initial release candidate. 3.18rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571798 Title: Broadwell ECRC Support missing in Ubuntu Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Here is the problem statement from the Dell team: When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick Assist Card, the memory location that corresponds to ECRC is set to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot. This causes the card to not function unless we implement the following workaround using setpci. “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the Intel Quick Assit Card. We’ve verified the memory location is correct when booting to other OSes, such as RHEL 7.2 and Windows Server 2012 R2. If there is any information you can give as to why this may be occurring in Ubuntu or where we may start to debug when the memory is changed, we would appreciate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580776] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at 0000000000000002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0
I have tested against both 4.4.0-21.37 and 4.4.0-22.39 on two laptops with the same results. I will test with an upstream kernel and get back to you. /Dave -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580776 Title: Kernel Oops - unable to handle kernel NULL pointer dereference at 0002; IP is at mmc_ioctl_cdrom_read_audio+0x212/0x3b0 Status in linux package in Ubuntu: Incomplete Bug description: While playing around with the CDROM API found in linux/cdrom.h I encountered a kernel oops when my program stalls. My code can be found at https://github.com/bigdavedev/audiorip. My program simply examines the ToC and then begins reading the PCM data track-by-track. I would expect it to complete without any major issue At first I assumed it was the CD, but after switching CDs several times I noticed that the oops happens at around frame 170925, reading CD_FRAMES (75) per ioctl. At this point, the disc is spinning at full speed. I have not yet tried reading fewer frames, nor have I tried setting the speed to something not max to see if I still receive a kernel oops. This would not be problematic to try. I have attached the output from `ubuntu-bug linux` to this issue. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dabr 2430 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-29 (102 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ASUSTeK COMPUTER INC. K55VD Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/primary_lvm_volume-root ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-19 (22 days ago) UserGroups: adm audio bumblebee cdrom dialout dip kvm lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD 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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD 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/1580776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580659] Re: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build [wlc_hybrid.o_shipped_x86_64: No such file or directory]
after -f install i managed to start wifi but it keeps dropping it every few minutes and generally works very poorly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1580659 Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build [wlc_hybrid.o_shipped_x86_64: No such file or directory] Status in bcmwl package in Ubuntu: New Bug description: trying to iinstall drivers ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.4.0-21-generic Date: Wed May 11 19:37:07 2016 InstallationDate: Installed on 2016-05-11 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: (not installed) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1580659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
Hi Brad, I do have a vmcore + dmesg, but this is very large (total: ~16GB). I will provide the test kernel based on Ubuntu-lts-4.2.0-36.41_14.04.1 including commit "fb53c43" and ask my contact to test it and confirm if it mitigate the issue on their affected systems where they can reproduce the panic on demand using the "udevadm" command. Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: Incomplete Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Re: LG 22V240 all in one PC with ACPI problems
Do I need to run apport-collect with the upstream 4.6 kernel? I suspect this is a CPU or ACPI table parsing code issue because just with acpi=ht the system is not usable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG 22V240 all in one PC with ACPI problems Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Re: LG 22V240 all in one PC with ACPI problems
Sorry for the delay, this was not my computer but Marta's one. This computer was bought recently and installed directly with Ubuntu 16.04 in dual boot with Windows. So no previous kernel version was tested. Even Ubuntu 16.04 CD install media needed kernel parameter acpi=off to boot. I just tried kernel 4.6 rc7 and problem persist. I had also tried upstream kernel version 4.5 with the same results. Only with acpi=off the system is usable. Any other option: Lot of NMI watchdog: Watchdog detected Hard LOCKUP on cpu 0 other CPU numbers also seen. System present LightDM after more than 15min. Desktop not usable due to constant lock-up (detected because mouse pointer and user name input stop blinking) Does not had the patience to try to log in after waiting more than 20 minutes. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG 22V240 all in one PC with ACPI problems Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port
This issue still exists in kernel 4.5.3 FWIW. dmesg snippet: [35001.978557] usb 3-1: USB disconnect, device number 5 [35001.978714] ax88179_178a 3-1:1.0 eth0: unregister 'ax88179_178a' usb-:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet [35001.978725] ax88179_178a 3-1:1.0 eth0: Failed to read reg index 0x0002: -19 [35001.978727] ax88179_178a 3-1:1.0 eth0: Failed to write reg index 0x0002: -19 [35001.998616] ax88179_178a 3-1:1.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 [35001.998620] ax88179_178a 3-1:1.0 eth0 (unregistered): Failed to write reg index 0x0001: -19 [35001.998623] ax88179_178a 3-1:1.0 eth0 (unregistered): Failed to write reg index 0x0002: -19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1269883 Title: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in USB3 port yields slow performance, dmesg flooded with errors. Plugging on USB2 port, exact same situation otherwise, works well. This is reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the left, 2 USB2 ports on the right. ### When working (USB2 port) * ethernet auto-negociation is fast * mii-tool is fast (typical 0.05s) * few lines in dmesg * good performance ### When failing : * ethernet auto-negociation fails, then sometimes eventually works * mii-tool is slow (10s of seconds instead of 0.05s) time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m40.014s user 0m0.013s sys 0m0.006s time sudo mii-tool eth0: no link eth1: 10 Mbit, half duplex, no link real 0m50.015s user 0m0.011s sys 0m0.011s time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m10.051s user 0m0.000s sys 0m0.012s But on some attempts mii-tool is fast... time sudo mii-tool eth0: no link eth1: negotiated 100baseTx-FD, link ok real 0m0.057s user 0m0.011s sys 0m0.012s * DHCP eventually completes (after about 30 seconds) then ethernet works. * whole system behaviour feels a little sluggish (not very clear, though) * mii-tool still slow (10s of seconds instead of 0.05s) ## dmesg when failing Full dmesg attached. Specific lines with occurrence count at random point (obtained with "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ). 50 ei_me :00:16.0: reset: wrong host start response 51 ei_me :00:16.0: reset: unexpected enumeration response hbm. 60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING 141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Another attempt 11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110 6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110 6 net_ratelimit: 31 callbacks suppressed 9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready 10 net_ratelimit: 30 callbacks suppressed 14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110 14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110 209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped 232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. 232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr 610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of current TD 809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1 Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
hum, we should backport that commit https://git.gnome.org/browse/gnome- settings-daemon/commit/?id=c311de7 ... it might be enough to fix the issue, could somebody try to build unity-settings-daemon with that simple change and see if it's enough to resolve the issue? ** Changed in: unity-settings-daemon (Ubuntu) Importance: Undecided => High ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => In Progress ** Bug watch added: GNOME Bug Tracker #734074 https://bugzilla.gnome.org/show_bug.cgi?id=734074 ** Also affects: unity-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=734074 Importance: Unknown Status: Unknown ** Project changed: unity-settings-daemon => gnome-settings-daemon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Unknown Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Re: LG 22V240 all in one PC with ACPI problems
** Summary changed: - LG V220 all in one PC with ACPI problems + LG 22V240 all in one PC with ACPI problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG 22V240 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working
I built the next test kernel, up to the following commit: c0d96af2e0427cc90b1f0d3c6a5294d90f93fcf4 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1498667 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498667 Title: [Toshiba P50W-B00F] Touchscreen no longer working Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Sometime in the last month or so my touchscreen stopped working on my Toshiba P50W. The dmesg log shows it constantly reconnecting to it: [ 556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd [ 556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.538349] usb 1-4: Product: Touchscreen [ 556.538351] usb 1-4: Manufacturer: ELAN [ 556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 556.547788] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374 [ 556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 556.600584] usb 1-4: USB disconnect, device number 119 [ 556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd [ 556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.990503] usb 1-4: Product: Touchscreen [ 556.990506] usb 1-4: Manufacturer: ELAN [ 556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 557.001248] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376 [ 557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 557.013831] usb 1-4: USB disconnect, device number 120 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-11-generic 4.2.0-11.13 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob2041 F pulseaudio /dev/snd/controlC0: bob2041 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 09:46:25 2015 HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12 InstallationDate: Installed on 2013-12-26 (635 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: TOSHIBA Satellite P50W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-11-generic N/A linux-backports-modules-4.2.0-11-generic N/A linux-firmware1.148 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago) dmi.bios.date: 08/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite P50W-B dmi.product.version: PSVP2A-00F002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1544978] Re: PCI Call Traces hw csum failure in dmesg with 4.4.0-2-generic
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Milestone: None => ubuntu-16.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1544978 Title: PCI Call Traces hw csum failure in dmesg with 4.4.0-2-generic Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Helmut Grauer - 2016-02-12 03:00:03 == Hi getting the following Call Traces when PCI interfaces will be configured [ 246.051566] enp0s0: hw csum failure [ 246.051571] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GE 4.4.0-2-generic #16-Ubuntu [ 246.051573]f9793778 f9793808 0002 f97938a8 f9793820 f9793820 00114182 0166 0091e9ca 000a 000a f9793868 f9793808 f9d38000 00114182 f9793808 f9793868 [ 246.051581] Call Trace: [ 246.051589] ([<001140b8>] show_trace+0x140/0x148) [ 246.051590] [<00114136>] show_stack+0x76/0xe8 [ 246.051595] [<005172d6>] dump_stack+0x6e/0x90 [ 246.051599] [<00673500>] __skb_checksum_complete+0xd0/0xd8 [ 246.051605] [<0076ae24>] icmpv6_rcv+0x124/0x500 [ 246.051608] [<00746e60>] ip6_input_finish+0x170/0x4e0 [ 246.051610] [<0074775c>] ip6_input+0x4c/0xd0 [ 246.051611] [<007478ee>] ip6_mc_input+0x10e/0x280 [ 246.051612] [<00747538>] ipv6_rcv+0x368/0x540 [ 246.051616] [<0067e5d4>] __netif_receive_skb_core+0x6fc/0xaf8 [ 246.051618] [<00681a56>] netif_receive_skb_internal+0x3e/0xd8 [ 246.051619] [<00682314>] napi_gro_frags+0x17c/0x208 [ 246.051627] [<03ff805f3a2c>] mlx4_en_process_rx_cq+0x8b4/0xbd0 [mlx4_en] [ 246.051630] [<03ff805f3e62>] mlx4_en_poll_rx_cq+0xc2/0x1a0 [mlx4_en] [ 246.051631] [<006839e2>] net_rx_action+0x2a2/0x418 [ 246.051635] [<00162726>] __do_softirq+0x156/0x300 [ 246.051637] [<00162ace>] irq_exit+0xd6/0xf8 [ 246.051641] [<0010cc5a>] do_IRQ+0x6a/0x88 [ 246.051644] [<007a99c2>] io_int_handler+0x112/0x220 [ 246.051646] [<00104856>] enabled_wait+0x56/0xa8 [ 246.051649] ([<00ccb888>] cpu_dead_idle+0x0/0x8) [ 246.051651] [<00104b5a>] arch_cpu_idle+0x32/0x48 [ 246.051669] [<001a8198>] cpu_startup_entry+0x200/0x278 [ 246.051674] [<001156ba>] smp_start_secondary+0xea/0xf8 [ 246.051679] [<007a9f42>] restart_int_handler+0x62/0x78 [ 246.051680] [<>] (null) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1544978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
** Package changed: linux-lts-trusty (Ubuntu) => linux-lts-wily (Ubuntu) ** Changed in: linux-lts-wily (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu) Status: New => In Progress ** Changed in: linux-lts-wily (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Package changed: linux-lts-wily (Ubuntu Precise) => linux-lts-trusty (Ubuntu Precise) ** Package changed: linux-lts-trusty (Ubuntu) => linux-lts-wily (Ubuntu) ** No longer affects: linux-lts-wily (Ubuntu Precise) ** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu) Status: New => In Progress ** Changed in: linux-lts-trusty (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-lts-wily (Ubuntu) Status: In Progress => Fix Released ** 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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-wily package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Wily: Fix Released Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) 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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-wily package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Wily: Fix Released Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
According to the vmcore[1], the crash seems to occur while performing the "udevadm"[2] command which is part of the sosreport under the block plugin. [1] - vmcore KERNEL: /usr/lib/debug/boot/vmlinux-4.2.0-30-generic DUMPFILE: dump.201605101421 [PARTIAL DUMP] CPUS: 40 DATE: Wed Dec 31 19:00:00 1969 UPTIME: 12:56:48 LOAD AVERAGE: 4.66, 5.51, 4.64 TASKS: 37318 NODENAME: XX RELEASE: 4.2.0-30-generic VERSION: #36~14.04.1-Ubuntu SMP Fri Feb 26 18:49:23 UTC 2016 MACHINE: x86_64 (2992 Mhz) MEMORY: 256 GB PANIC: "" PID: 53367 COMMAND: "udevadm" TASK: 88038624 [THREAD_INFO: 880130fac000] CPU: 24 STATE: TASK_RUNNING (PANIC) [2] - sosreport - block plugin sosreport-3.1/sos/plugins/block.py: self.add_cmd_output("udevadm info -ap /sys/block/%s" % (disk)) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: Incomplete Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574697] Re: WARNING: at /build/linux-aWXT0l/linux-4.4.0/drivers/pci/pci.c:1595 [travis3EN]
** Changed in: linux (Ubuntu Wily) Importance: Undecided => Low ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Low ** Changed in: linux (Ubuntu Xenial) Milestone: None => ubuntu-16.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574697 Title: WARNING: at /build/linux-aWXT0l/linux-4.4.0/drivers/pci/pci.c:1595 [travis3EN] Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: ---Problem Description--- WARNING: at /build/linux-aWXT0l/linux-4.4.0/drivers/pci/pci.c:1595 [travis3EN] ---uname output--- Linux ltciofvtr-s822l2-lp3 4.4.0-4-generic #19-Ubuntu SMP Fri Feb 5 17:36:21 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = s822l ---Steps to Reproduce--- triggering EEH causes the warning messages in syslog Note: its just the warning messages, card recovers after EEH 1. from peer: run some load linux-xqxs:~ # ping -f 22.22.22.22 2. from pKVM host run the EEH for the travis3EN card [root@ltciofvtr-s822l2-lp1 ~]# echo 0x8000 > /sys/kernel/debug/powerpc/PCI0003/err_injct_inboundA; sleep 1; echo 0x0 > /sys/kernel/debug/powerpc/PCI0003/err_injct_inboundA 3. on client's sysfs you can see the warning messages "WARNING: at /build/linux-aWXT0l/linux-4.4.0/drivers/pci/pci.c:1595" [ 940.382507] EEH: Frozen PHB#0-PE#1 detected [ 940.382594] EEH: PE location: N/A, PHB location: N/A [ 940.382828] mlx4_core :00:04.0: mlx4_pci_err_detected was called [ 940.382891] mlx4_core :00:04.0: device is going to be reset [ 940.382953] mlx4_core :00:04.0: device was reset successfully [ 940.383014] mlx4_en :00:04.0: Internal error detected, restarting device Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382507] EEH: Frozen PHB#0-PE#1 detected Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382594] EEH: PE location: N/A, PHB location: N/A Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382647] CPU: 1 PID: 176 Comm: kworker/u16:2 Not tainted 4.4.0-4-generic #19-Ubuntu Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382671] Workqueue: mlx4_en mlx4_en_do_get_stats [mlx4_en] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382673] Call Trace: Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382714] [c487b7c0] [c0ad8aa0] dump_stack+0x90/0xbc (unreliable) Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382725] [c487b7f0] [c00378f4] eeh_dev_check_failure+0x534/0x580 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382728] [c487b890] [c00379c4] eeh_check_failure+0x84/0xd0 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382743] [c487b8d0] [d2112fc0] cmd_pending+0xb0/0xe0 [mlx4_core] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382749] [c487b900] [d21130b0] mlx4_cmd_post+0xc0/0x250 [mlx4_core] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382756] [c487b9b0] [d211592c] __mlx4_cmd+0x1dc/0x9b0 [mlx4_core] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382766] [c487ba70] [d24eb030] mlx4_en_DUMP_ETH_STATS+0xc0/0x830 [mlx4_en] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382770] [c487bb70] [d24ef150] mlx4_en_do_get_stats+0x160/0x340 [mlx4_en] Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382780] [c487bc50] [c00dc920] process_one_work+0x1e0/0x560 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382783] [c487bce0] [c00dce34] worker_thread+0x194/0x680 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382785] [c487bd80] [c00e58d0] kthread+0x110/0x130 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382788] [c487be30] [c0009538] ret_from_kernel_thread+0x5c/0xa4 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382814] mlx4_core :00:04.0: Could not post command 0x49: ret=-5, in_param=0x0, in_mod=0x1, op_mod=0x0 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382821] EEH: Detected PCI bus error on PHB#0-PE#1 Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382823] EEH: This PCI device has failed 1 times in the last hour Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382824] EEH: Notify device drivers to shutdown Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382828] mlx4_core :00:04.0: mlx4_pci_err_detected was called Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382891] mlx4_core :00:04.0: device is going to be reset Feb 19 02:18:23 ltciofvtr-s822l2-lp3 kernel: [ 940.382953] mlx4_core :00
[Kernel-packages] [Bug 1581005] Re: Dell XPS 15 9550 Freezes when HDMI is plugged in
I'd like to test some of the 4.6 release candidates. The all can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/ We should first test v4.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/ If the bug still exists in -rc1, maybe try -rc4 and then newer versions until we find the last bad kernel and first good one. We can then bisect between those two versions: v4.6-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/ v4.6-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/ ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581005 Title: Dell XPS 15 9550 Freezes when HDMI is plugged in Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This is fixed upstream in the 4.6.0 series. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2087 F pulseaudio CurrentDesktop: Unity Date: Thu May 12 07:25:29 2016 HibernationDevice: RESUME=UUID=20adf9e8-41f0-4bf8-8075-dcff091511d4 InstallationDate: Installed on 2016-03-12 (60 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=ea2a2622-df89-4bf1-8f58-99f313ed3908 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] [NEW] kernel panic (General protection fault) on module hpsa (lockup_detected)
Public bug reported: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. ** Affects: linux (Ubuntu) Importance: Medium Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
Possible commit to fix the issue, found upstream: I'll create a testfix and will make it public shortly. $ git show fb53c43 commit fb53c439d84387621c53808a3957ffd9876e5094 Author: Tomas Henzl Date: Fri Nov 6 16:24:09 2015 +0100 hpsa: move lockup_detected attribute to host attr This patch fixes a 'general protection fault' issue by moving the attribute to where it was likely meant. Signed-off-by: Tomas Henzl Signed-off-by: Don Brace Signed-off-by: Martin K. Petersen diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c index 57166e6..6d44123 100644 --- a/drivers/scsi/hpsa.c +++ b/drivers/scsi/hpsa.c @@ -867,7 +867,6 @@ static struct device_attribute *hpsa_sdev_attrs[] = { &dev_attr_unique_id, &dev_attr_hp_ssd_smart_path_enabled, &dev_attr_path_info, - &dev_attr_lockup_detected, NULL, }; @@ -879,6 +878,7 @@ static struct device_attribute *hpsa_shost_attrs[] = { &dev_attr_resettable, &dev_attr_hp_ssd_smart_path_status, &dev_attr_raid_offload_debug, + &dev_attr_lockup_detected, NULL, }; ** 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/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1581169 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/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: Incomplete Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-wily (Ubuntu Precise) 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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-wily package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Wily: Fix Released Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
The problem is reproducible on demand : root@dob2-bfs-r5n09:~# udevadm --debug info -ap /sys/block/sdf calling: info device 0x154a300 has devpath '/devices/pci:00/:00:02.2/:02:00.0/host2/target2:0:0/2:0:0:5/block/sdf' Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/pci:00/:00:02.2/:02:00.0/host2/target2:0:0/2:0:0:5/block/sdf': KERNEL=="sdf" SUBSYSTEM=="block" DRIVER=="" ATTR{ro}=="0" ATTR{size}=="1562758832" ATTR{stat}==" 526 0 168573 232 11691 5205 2997588 3820 0 4016 4040" ATTR{range}=="16" ATTR{discard_alignment}=="0" ATTR{events}=="" ATTR{ext_range}=="256" ATTR{events_poll_msecs}=="-1" ATTR{alignment_offset}=="0" ATTR{inflight}==" 0 0" ATTR{removable}=="0" ATTR{capability}=="50" ATTR{events_async}=="" device 0x154b220 has devpath '/devices/pci:00/:00:02.2/:02:00.0/host2/target2:0:0/2:0:0:5' looking at parent device '/devices/pci:00/:00:02.2/:02:00.0/host2/target2:0:0/2:0:0:5': KERNELS=="2:0:0:5" SUBSYSTEMS=="scsi" DRIVERS=="sd" ATTRS{rev}=="7.02" ATTRS{type}=="0" ATTRS{scsi_level}=="6" ATTRS{lunid}=="0x0540" ATTRS{model}=="LOGICAL VOLUME " ATTRS{state}=="running" ATTRS{queue_type}=="simple" ATTRS{iodone_cnt}=="0x328b" ATTRS{iorequest_cnt}=="0x328b" ATTRS{unique_id}=="600508B1001C6ACDCAA167F467871EAB" ATTRS{queue_ramp_up_period}=="12" ATTRS{device_busy}=="0" ATTRS{evt_capacity_change_reported}=="0" ATTRS{timeout}=="30" ATTRS{evt_media_change}=="0" ATTRS{ioerr_cnt}=="0x2" ssh: Write failed: Broken pipe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-wily (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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-wily package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Wily: Fix Released Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
Stack Trace: [46586.194135] general protection fault: [#1] SMP [46586.194933] Modules linked in: ipmi_ssif x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw input_leds joydev sb_edac edac_core hpilo lpc_ich ioatdma dca shpchp wmi xfs ipmi_si 8250_fintek ipmi_msghandler tpm_infineon acpi_power_meter mac_hid libcrc32c bonding lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic psmouse raid6_pq sfc raid1 usbhid raid0 mtd hid tg3 pata_acpi i2c_algo_bit multipath ptp mdio hpsa pps_core linear [46586.206368] CPU: 24 PID: 53367 Comm: udevadm Not tainted 4.2.0-30-generic #36~14.04.1-Ubuntu [46586.207925] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [46586.208898] task: 88038624 ti: 880130fac000 task.ti: 880130fac000 [46586.210030] RIP: 0010:[] [] host_show_lockup_detected+0x2c/0x50 [hpsa] [46586.213065] RSP: 0018:880130fafd88 EFLAGS: 00010282 [46586.213882] RAX: 2030203020302030 RBX: c00422e0 RCX: 88274bb66000 [46586.215502] RDX: 881fbf98 RSI: c00422e0 RDI: 881fb1416968 [46586.216560] RBP: 880130fafd88 R08: 881fb1416978 R09: [46586.217616] R10: 1000 R11: 0246 R12: 818749b0 [46586.218674] R13: 0001 R14: 880130faff20 R15: 881fb1d46180 [46586.219969] FS: 7f060a57d880() GS:881fbf98() knlGS: [46586.221181] CS: 0010 DS: ES: CR0: 80050033 [46586.222000] CR2: 01748000 CR3: 000a6ad8f000 CR4: 001406e0 [46586.223039] Stack: [46586.223334] 880130fafdb8 814f0eb0 88274bb66000 817ba686 [46586.224518] 881fa016aa00 881fb1d46180 880130fafdd8 81263bc2 [46586.225716] 881fa016aa00 880130fafde8 81262413 [46586.227165] Call Trace: [46586.227539] [] dev_attr_show+0x20/0x50 [46586.228313] [] ? mutex_lock+0x16/0x37 [46586.229113] [] sysfs_kf_seq_show+0xc2/0x1a0 [46586.229957] [] kernfs_seq_show+0x23/0x30 [46586.231564] [] seq_read+0xe5/0x350 [46586.232303] [] kernfs_fop_read+0x10d/0x170 [46586.233180] [] __vfs_read+0x18/0x40 [46586.233947] [] vfs_read+0x86/0x130 [46586.235451] [] SyS_read+0x46/0xa0 [46586.236180] [] entry_SYSCALL_64_fastpath+0x16/0x75 [46586.237160] Code: 1f 44 00 00 55 48 89 d1 48 8b 87 e0 02 00 00 48 89 e5 65 8b 15 a6 93 fd 3f 48 63 d2 48 8b 80 b8 4b 00 00 48 8b 14 d5 80 c1 d2 81 <8b> 14 02 48 c7 c6 5c fb 03 c0 48 89 cf 31 c0 e8 50 0b 38 c1 5d [46586.242101] RIP [] host_show_lockup_detected+0x2c/0x50 [hpsa] [46586.243446] RSP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451233] Re: 10ec:b723 [Lenovo B5400] Realtek RTL8723BE drops connection until reboot
same problem with ubuntu 16.04. workaround works for me (options rtl8723be ips=0 fwlps=0). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451233 Title: 10ec:b723 [Lenovo B5400] Realtek RTL8723BE drops connection until reboot Status in linux package in Ubuntu: Triaged Bug description: I have a Lenovo B5400 laptop with RTL8723BE wireless module. Using 802.11n the internet connection constantly getting lost after a random duration (usually after 20-30 minutes). The NetworkManager applet does not recognize it (still looks like i have a connection), but when I try do disconnect and connect again, there is only one useful information I can find in dmesg: "wlan0: deauthenticating from [ap mac address] by local choice (Reason: 3=DEAUTH_LEAVING)" Reinserting the driver (modprobe -r rtl8723be and modprobe rtl8723) used to be my only workaround, but it does not work anymore and now I have to reboot. Router Manufacturer: EDIMAX Model: BR-6214K Firmware version: 1.40 2008/11/03 08:33:04 Switching to 802.11g (54Mb/s) shows a small performance improvement while browsing websites. However there are still random "ping jumps" and the connection still drops (maybe 1-2 minutes later than usual at least). The following improves performance, but I am still encountering some minor performance issues while playing online games (random lag spikes): sudo nano /etc/modprobe.d/rtl8723be.conf options rtl8723be ips=0 fwlps=0 --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pk 1907 F pulseaudio /dev/snd/controlC0: pk 1907 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=4ce160f4-029c-4fd5-ba3f-254c6e3e33dd InstallationDate: Installed on 2015-05-24 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20278 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=a9da170f-b86b-434f-910b-00929ceb8420 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 RelatedPackageVersions: linux-restricted-modules-3.16.0-38-generic N/A linux-backports-modules-3.16.0-38-generic N/A linux-firmware 1.127.12 Tags: trusty Uname: Linux 3.16.0-38-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/03/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J7ET61WW (2.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20278 QB0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ7ET61WW(2.06):bd03/03/2014:svnLENOVO:pn20278:pvrB5400:rvnLENOVO:rn20278QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20278 dmi.product.version: B5400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
According to the vmcore[1], the crash seems to occur while performing the "udevadm"[2] command which is part of the sosreport under the block plugin. [1] - vmcore KERNEL: /usr/lib/debug/boot/vmlinux-4.2.0-30-generic DUMPFILE: dump.201605101421 [PARTIAL DUMP] CPUS: 40 DATE: Wed Dec 31 19:00:00 1969 UPTIME: 12:56:48 LOAD AVERAGE: 4.66, 5.51, 4.64 TASKS: 37318 NODENAME: pob3-bach-r7n07 RELEASE: 4.2.0-30-generic VERSION: #36~14.04.1-Ubuntu SMP Fri Feb 26 18:49:23 UTC 2016 MACHINE: x86_64 (2992 Mhz) MEMORY: 256 GB PANIC: "" PID: 53367 COMMAND: "udevadm" TASK: 88038624 [THREAD_INFO: 880130fac000] CPU: 24 STATE: TASK_RUNNING (PANIC) [2] - sosreport - block plugin sosreport-3.1/sos/plugins/block.py: self.add_cmd_output("udevadm info -ap /sys/block/%s" % (disk)) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
Thanks for testing, John. To narrow it down further, can you test some of the 3.18 release candidates? They can all be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/ I'd suggest trying -rc1 first. If that version does not have the bug, try some of the newer candidates: v3.18-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ v3.18-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ v3.18-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc7-vivid/ Once we know the last good kernel version and the first bad one, we can bisect between them. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: Confirmed ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Wily) Importance: Undecided => High ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Vivid) 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/1571798 Title: Broadwell ECRC Support missing in Ubuntu Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Here is the problem statement from the Dell team: When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick Assist Card, the memory location that corresponds to ECRC is set to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot. This causes the card to not function unless we implement the following workaround using setpci. “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the Intel Quick Assit Card. We’ve verified the memory location is correct when booting to other OSes, such as RHEL 7.2 and Windows Server 2012 R2. If there is any information you can give as to why this may be occurring in Ubuntu or where we may start to debug when the memory is changed, we would appreciate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
We can confirm this is the last line we see regardless of the disk: ATTRS{ioerr_cnt}=="0x2" On a working disk the next line is : "ATTRS{lockup_detected}" It seems to stuck at the lockup_detected attribute. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581169 Title: kernel panic (General protection fault) on module hpsa (lockup_detected) Status in linux package in Ubuntu: New Bug description: it has been brought to my attention the following: Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu When running an sosreport on HP DL380 gen8 machines running this kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning block devices. These are machines with an onboard p420i and daughtercard p420 RAID controller, with each drive in a single raid0 configuration. (unideal, but the machines do not boot when the card is in HBA mode). This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using sosreport. The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable solution - I have yet to see a prior issue in which the p420 would lock up on this version. One issue wit h this is HP 99% of the time will require an sosreport when we raise any hardware issues. I can no longer produce that on kernel 4.2 machines because they kernel panic. I can reproduce this consistently with several other machines in our environment. - please let me know if you would like more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574238] Re: Stand-by/sleep mode 16.04
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 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'. 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.6-rc7-wily/ ** 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/1574238 Title: Stand-by/sleep mode 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Problems with Stand-by/sleep mode after upgrading to 16.04. Driver ventilation still running, but the screen stays black. No reaction at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: 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: Sun Apr 24 13:46:01 2016 DistUpgraded: 2016-04-22 21:07:47,908 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea] InstallationDate: Installed on 2015-06-04 (324 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7af49af0-d45a-4a2b-82e8-78cce2243823 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RKNTK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0RKNTK:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 24 13:05:15 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581132] Re: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Medium => Wishlist ** Changed in: linux (Ubuntu Xenial) Importance: Medium => Wishlist ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581132 Title: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Post 4.4, several changes landed upsteam to allow users to set interface speed for virtio_net backed devices. This feature is extremely useful for those doing large-scale networking simulations where Ubuntu-based VMs are used to simulate hosts. Not only does it allow hosts to report the same speed in simulations for monitoring tools, but it is required to simulate 802.3ad bonding where link-speed is reported to the peer device. Without proper speed setting there are cases where establishing LACP adjacency is not possible. After this patch setting the link speed and duplex now works just as one would expect. I'm running the kernel that contains this patch for these commands: $ sudo ethtool -s enp0s8 speed 10 duplex full $ sudo ethtool enp0s8 Settings for enp0s8: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes I've already submitted patches to the kernel-team mailing list. Those patches can be found in this thread: https://lists.ubuntu.com/archives /kernel-team/2016-May/077286.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581127] Re: zfs: disable module checks for zfs when cross-compiling
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Yakkety) 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/1581127 Title: zfs: disable module checks for zfs when cross-compiling Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: When cross-compiling we necessarily turn off zfs builds. This leaves us with missing modules for ZFS when doing a full package build in a cross-compilation environment. This failure prevents other modules from being checked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 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'. 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.6-rc7-wily/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1:
[Kernel-packages] [Bug 1578022] Re: dmidecode fails to output smibios 3.0 info
Recent BIOS upgrades from Asrock Rack is also hitting this, for example v2.10 for the dual socket Xeon EP2C612D16-2L2T board. For Asrock at least SMBIOS 3.0 seems to have arrived with Broadwell-EP CPU support (Xeon E5 v4). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1578022 Title: dmidecode fails to output smibios 3.0 info Status in dmidecode package in Ubuntu: Confirmed Bug description: Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios 3.0. Rhel 7.2 can display smibios 3.0 on the same system without a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580355] Re: promote *_diag modules from linux-image-extra to linux-image
** Also affects: linux (Ubuntu Yakkety) Importance: Wishlist Status: Triaged ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580355 Title: promote *_diag modules from linux-image-extra to linux-image Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Bug description: Hi, For checkpoint restore support via CRIU, we need to use the following modules: udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag some of which aren't included in linux-image, requiring users to install linux-image-extra. It would be handy if these were in the main kernel package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Re: LG V220 all in one PC with ACPI problems
Sorry for the delay, this was not my computer but Marta's one. I'm going to try now latest v4.6 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661415/+files/AlsaInfo.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/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661424/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661419/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661425/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661426/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661428/+files/UdevDb.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/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Re: LG V220 all in one PC with ACPI problems
ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magtae 1528 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a048eff8-4362-47eb-8a6b-7f0481ff986b InstallationDate: Installed on 2016-03-23 (49 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LG Electronics 22V240-L.AT2WB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=b594541d-97cc-4c45-b1b3-f3c110e62949 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' Uname: Linux 4.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 22V24FF4 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22V240 dmi.board.vendor: LG Electronics dmi.board.version: FAB3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr22V24FF4X64:bd05/20/2014:svnLGElectronics:pn22V240-L.AT2WB:pvr0.1:rvnLGElectronics:rn22V240:rvrFAB3:cvnLGElectronics:ct13:cvr0.1: dmi.product.name: 22V240-L.AT2WB dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Tags added: apport-collected wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661427/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661418/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661429/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661420/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580345] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1580345/+attachment/4661421/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580345 Title: LG V220 all in one PC with ACPI problems Status in linux package in Ubuntu: Incomplete Bug description: I have the following problem with a LG all in one PC V220. Ubuntu 16.04 does not boots unless ACPI is deactivated with acpi=off kernel option. Never see the X starting after waiting a lot of minutes. Removing the quiet kernel parameter we can see the kernel reporting a lot of errors and progressing very slowly. None of those parameters allowed a normal boot: acpi=ht pci=noacpi acpi=noirq pnpacpi=off noapic nolapic Only acpi=off allowed the system to boot. But with very poor performance and only one core CPU. Tested also latest vanilla linux kernel with same problem. Hardware information in attached files. Attached ACPI dump extracted from Windows. I have some experience with many GNU/Linux distros but no experience debugging ACPI. I am willing to help debug this issue. Tell what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp