[Kernel-packages] [Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing
The kernel in comment #7 pass our SMEP/SMAP test and doesn't generate regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520427 Title: drm/fbdev: Return -EBUSY when oopsing Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Issue: Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access, the screen would be frozen and never come back,but the system does not hang. Generally, an SMEP/SMAP violation should cause the involved process killed, an oops from page fault exception generated to the syslog, and the system survived. Fix: One patch from 4.3 kernel fix this issue commit c50bfd08d60cefbe1714c4a53b1c325982858549 Author: Daniel Vetter Date: Tue Jul 28 13:18:40 2015 +0200 drm/fbdev: Return -EBUSY when oopsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1517942] Re: Backport upstream commit to Ubuntu 15.10 (Wily) SRU stream
** Tags removed: verification-needed-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/1517942 Title: Backport upstream commit to Ubuntu 15.10 (Wily) SRU stream 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 Released Bug description: == Comment: #0 - UMA KRISHNAN - 2015-11-18 16:27:06 == ---Problem Description--- When FC login times out, cxlflash resets the link. As part of reset, when the link comes back up, cxlflash driver calls scsi_scan_host() and in case previous scan is still running we get the message and stack dump on console/logs. scsi host2: scsi_prep_async_scan called twice CPU: 16 PID: 55 Comm: kworker/16:1 Not tainted 4.2.0-439-f9a408a+ #1 Workqueue: events cxlflash_worker_thread [cxlflash] Call Trace: [c0078bea7ae0] [c0a6e720] dump_stack+0x90/0xbc (unreliable) [c0078bea7b10] [c06f539c] scsi_scan_host+0x28c/0x2a0 [c0078bea7bb0] [d4085344] cxlflash_worker_thread+0x144/0x430 [cxlflash] [c0078bea7c50] [c00d8b64] process_one_work+0x1a4/0x4c0 [c0078bea7ce0] [c00d9014] worker_thread+0x194/0x5f0 [c0078bea7d80] [c00e1630] kthread+0x110/0x130 [c0078bea7e30] [c0009530] ret_from_kernel_thread+0x5c/0xac cxlflash 0009:00:00.0: cxlflash_async_err_irq: FC Port 1 -> login succeeded, fc_status 0x114001D8F This message is alarming to customers. Community has already fixed this. We would like to see the upstreamed commit a4cf30e15ccea82a07fa5870e8af787b9ea1a672 (scsi_scan: don't dump trace when scsi_prep_async_scan() is called twice) backported to Ubuntu 15.10 (Wily) SRU stream. ---uname output--- Linux tul83p1 4.2.0-444-5b49ef1+ #1 SMP Wed Nov 18 12:44:21 CST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Simply disconnecting the adapter and plugging it back in, triggers this scenario. Contact Information = ukri...@linux.vnet.ibm.com Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for ukri...@linux.vnet.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522958] kili (amd64) - tests ran: 87, failed: 36
tests ran: 87, failed: 36; http://kernel.ubuntu.com/testing/4.3.0-2.11/kili__4.3.0-2.11__2015-12-09_02-57-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522958 Title: linux: 4.3.0-2.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.3.0-2.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 04. December 2015 20:20 UTC kernel-phase-changed:Friday, 04. December 2015 20:20 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 04. December 2015 21:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1522958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504829] Re: [Lenovo ThinkPad SL510] Loud beep on resume from suspend
Bumping this 7 days before expiration. Hope to find some time during the holidays to investigate further. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504829 Title: [Lenovo ThinkPad SL510] Loud beep on resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from kernel 3.13.x, my Thinkpad SL510 beeps loudly for ~50ms when opening the lid to resume from suspend. No other issues occur. The beep when closing the lid is quiet and lasts ~130ms. This is reproducible in 15.10. --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uwer 2247 F pulseaudio uwer 7833 F audacity CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=449bf762-bd99-4fb4-9d33-f86c42cebc06 InstallationDate: Installed on 2015-01-03 (280 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 28477MG Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic root=UUID=5b1f663b-f520-4c03-8df5-b66bcf2a74e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16 RelatedPackageVersions: linux-restricted-modules-3.16.0-50-generic N/A linux-backports-modules-3.16.0-50-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.16.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET94WW (1.52 ) dmi.board.name: 28477MG 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:bvr6JET94WW(1.52):bd06/19/2012:svnLENOVO:pn28477MG:pvrThinkPadSL510:rvnLENOVO:rn28477MG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 28477MG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1263257] Re: "Disks" formatted mounted disk ext4->NTFS without unmount, resulting in kernel panic
[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/1263257 Title: "Disks" formatted mounted disk ext4->NTFS without unmount, resulting in kernel panic Status in linux package in Ubuntu: Expired Bug description: gnome-disk-utility "Disks", version 3.6.1-1ubuntu1 System in question: uname -a = 'Linux scorpio 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux' lsb_release -a = 'Distributor ID: LinuxMint Description: Linux Mint 15 Olivia Release: 15 Codename:olivia' (This is Linux Mint 15 MATE edition) lsblk = 'NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 298.1G 0 disk ├─sda18:10 15.3G 0 part / ├─sda28:20 2.8G 0 part [SWAP] ├─sda38:30 15.6G 0 part ├─sda48:40 7.9M 0 part └─sda58:50 264.5G 0 part /home sdb 8:16 0 465.8G 0 disk └─sdb18:17 0 465.8G 0 part └─md0 9:00 465.7G 0 raid1 sdc 8:32 0 698.7G 0 disk ├─sdc18:33 0 465.8G 0 part │ └─md0 9:00 465.7G 0 raid1 └─sdc28:34 0 232.9G 0 part /media/ed/Spare sdd 8:48 1 7.9G 0 disk └─sdd18:49 1 7.9G 0 part /media/ed/MEMSTICK Attempted to format partition in question (/dev/sdc2, /dev/sdb2 before reboot) from ext4 to NTFS, failed to unmount partition beforehand. Admittably a failure in proper user policy; but a frontend graphical program like "Disks" should know better than to have actually tried to preform said operation without doing an unmount first. Result was a partition which read 16EB (exabyte) ext3/ext4 in caja shell properties window. Attempt to unmount via caja shell resulted in kernel panic :( Clearly this is a very serious issue; anybody working on disk partioning could potentially make this mistake. Terminal format utilites would actually complain about mounted partitions-- the fact the "Disks" was able to format an in-use, mounted partition is very worrying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503931] Re: BUG: unable to handle kernel paging request at fffffffffffffff8
[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/1503931 Title: BUG: unable to handle kernel paging request at fff8 Status in linux package in Ubuntu: Expired Bug description: unexpected crash ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-15-generic 4.2.0-15.17 ProcVersionSignature: Ubuntu 4.2.0-15.17-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Oct 8 13:54:09 2015 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location eventpoll_release_file+0x3f/0xa0 Failure: oops HibernationDevice: RESUME=UUID=3d6e9da2-58d0-4e57-ac19-f6e414aea827 InstallationDate: Installed on 2015-10-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150909) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic root=UUID=fce078d6-ffe0-4f17-9c76-572dab4aa1a0 ro quiet splash 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-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: unable to handle kernel paging request at fff8 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503640] Re: Asus Laptop X450JB Can't enable Wifi
[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/1503640 Title: Asus Laptop X450JB Can't enable Wifi Status in linux package in Ubuntu: Expired Bug description: I can't get my asus laptop Wifi working. I asked on askubuntu.com and a good guy suggest me to disable acer_wmi driver. He said it could be a bug that wrongly detect and setup acer_wmi driver. I got it working by blacklisting acer_wmi driver in /etc/modprobe.d/blacklist.conf ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andy 1308 F pulseaudio /dev/snd/controlC0: andy 1308 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 7 17:08:28 2015 HibernationDevice: RESUME=UUID=272a6582-7e1b-482c-aa24-38b4034cbdba InstallationDate: Installed on 2015-10-07 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. X450JB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=cc0a48eb-97f5-4eaf-8112-a34bc09d1f18 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143.3 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: 03/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X450JB 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.:bvr202:bd03/13/2015:svnASUSTeKCOMPUTERINC.:pnX450JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X450JB 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/1503640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503821] Re: kernel BUG at /build/linux-r65iLe/linux-4.2.0/fs/dcache.c:847!
[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/1503821 Title: kernel BUG at /build/linux-r65iLe/linux-4.2.0/fs/dcache.c:847! Status in linux package in Ubuntu: Expired Bug description: ubuntu nvidia driver 304.128 doesn't work but 304.125 does on 15.04. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-15-generic 4.2.0-15.17 ProcVersionSignature: Ubuntu 4.2.0-15.17-generic 4.2.3 Uname: Linux 4.2.0-15-generic i686 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19.1-0ubuntu1 Architecture: i386 Date: Wed Oct 7 11:18:23 2015 Failure: oops InstallationDate: Installed on 2015-09-29 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150924) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic root=UUID=d48585e4-7ed2-4f16-9701-a50b539d7234 ro quiet splash SourcePackage: linux Title: kernel BUG at /build/linux-r65iLe/linux-4.2.0/fs/dcache.c:847! UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503568] Re: BUG: unable to handle kernel paging request at ffffebe000000000
[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/1503568 Title: BUG: unable to handle kernel paging request at ebe0 Status in linux package in Ubuntu: Expired Bug description: Not sure what happened. ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-15-generic 4.2.0-15.17 ProcVersionSignature: Ubuntu 4.2.0-15.17-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 NonfreeKernelModules: nvidia wl Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Oct 7 03:12:52 2015 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location kmem_cache_free+0x69/0x1e0 Failure: oops HibernationDevice: RESUME=UUID=e92dd984-60bd-4066-9aa2-4fbb662fbe90 InstallationDate: Installed on 2015-09-23 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK Computer INC. CM1630 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic root=UUID=93a7ab21-b1ea-4d11-85c6-c273e718d08b ro quiet splash 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-3ubuntu8 SourcePackage: linux Title: BUG: unable to handle kernel paging request at ebe0 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: CM1630 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd05/20/2010:svnASUSTeKComputerINC.:pnCM1630:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM1630:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM1630 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524167] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524167 Title: Computer freezes since 15.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Machine freezes randomly. No crash logs or anything in syslog. Not enough know-how to figure it out. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jd 2303 F pulseaudio Date: Tue Dec 8 22:23:17 2015 HibernationDevice: RESUME=UUID=97af6a20-8cf6-48bb-a4a4-20d55865a2e3 MachineType: Acer Aspire ES1-512 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=af5dae25-82ce-4518-83af-ee2f6e077b25 ro recovery nomodeset 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.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-01 (37 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/11/2014:svnAcer:pnAspireES1-512:pvrV1.07:rvnAcer:rnAspireES1-512:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524167] [NEW] Computer freezes since 15.10 upgrade
Public bug reported: Machine freezes randomly. No crash logs or anything in syslog. Not enough know-how to figure it out. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jd 2303 F pulseaudio Date: Tue Dec 8 22:23:17 2015 HibernationDevice: RESUME=UUID=97af6a20-8cf6-48bb-a4a4-20d55865a2e3 MachineType: Acer Aspire ES1-512 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=af5dae25-82ce-4518-83af-ee2f6e077b25 ro recovery nomodeset 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.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-01 (37 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/11/2014:svnAcer:pnAspireES1-512:pvrV1.07:rvnAcer:rnAspireES1-512:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed 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/1524167 Title: Computer freezes since 15.10 upgrade Status in linux package in Ubuntu: New Bug description: Machine freezes randomly. No crash logs or anything in syslog. Not enough know-how to figure it out. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jd 2303 F pulseaudio Date: Tue Dec 8 22:23:17 2015 HibernationDevice: RESUME=UUID=97af6a20-8cf6-48bb-a4a4-20d55865a2e3 MachineType: Acer Aspire ES1-512 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=af5dae25-82ce-4518-83af-ee2f6e077b25 ro recovery nomodeset 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.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-01 (37 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/11/2014:svnAcer:pnAspireES1-512:pvrV1.07:rvnAcer:rnAspireES1-512:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524157] [NEW] package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brc
Public bug reported: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied But I was sudo ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-firmware 1.149 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 8 10:27:23 2015 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.149.3_all.deb ... Unpacking linux-firmware (1.149.3) over (1.149) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.149.3_all.deb (--unpack): unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied DuplicateSignature: package:linux-firmware:1.149:unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied ErrorMessage: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied InstallationDate: Installed on 2015-09-30 (69 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: linux-firmware Title: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied UpgradeStatus: Upgraded to wily on 2015-10-28 (41 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1524157 Title: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied Status in linux-firmware package in Ubuntu: New Bug description: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied But I was sudo ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-firmware 1.149 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 8 10:27:23 2015 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.149.3_all.deb ... Unpacking linux-firmware (1.149.3) over (1.149) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.149.3_all.deb (--unpack): unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied DuplicateSignature: package:linux-firmware:1.149:unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied ErrorMessage: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied InstallationDate: Installed on 2015-09-30 (69 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: linux-firmware Title: package linux-firmware 1.149 failed to install/upgrade: unable to create '/lib/firmware/brcm/bcm4329-fullmac-4.bin.dpkg-new' (while processing './lib/firmware/brcm/bcm4329-fullmac-4.bin'): Permission denied UpgradeStatus: Upgraded to wily on 2015-10-28 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1524157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
> "BTW, Since Ubuntu 15.04's " typo.. 15.04 -> 15.10. -- You 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 Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: 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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
@f-bosch @jsalisbury I can reproduce the issue consistently within 5~6 hours with a Ubuntu 15.10 VM. In /var/log/syslog, several minutes before the file system is remounted as read-only, the hv_vss_daemon has stopped working: the daemon just always hangs on the poll() , not receiving freeze/thaw commands from the hv_utils driver at all. I guess there might be a race condition in the hv_utils.ko driver, so the commands from the host are not received properly, or not forwarded to the daemon properly, so the daemon isn't be woken up. Trying to track it down. BTW, Since Ubuntu 15.04's code of the hv_utils driver and the daemon is the same as the upstream Linux, I think the upstream should have the same issue. BTW, the below message looks like a benign warning -- I get this every time the backup begins, but I think it has nothing to do with the issue here: [ 967.339810] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention [current] [ 967.339891] sd 2:0:0:0: [storvsc] Add. Sense: Changed operating definition [ 967.340111] sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automa -- You 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 Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: 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 1524122] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1524122/+attachment/4531712/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524122 Title: XPS 15 (9550) Won't boot with 4.4 Status in linux package in Ubuntu: Confirmed Bug description: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-11-18 (20 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524122] Re: XPS 15 (9550) Won't boot with 4.4
apport information ** Tags added: apport-collected wily ** Description changed: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + InstallationDate: Installed on 2015-11-18 (20 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: linux (not installed) + Tags: wily + Uname: Linux 4.3.0-040300-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video wireshark + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1524122/+attachment/4531711/+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/1524122 Title: XPS 15 (9550) Won't boot with 4.4 Status in linux package in Ubuntu: Confirmed Bug description: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-11-18 (20 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UnreportableReason: The running k
[Kernel-packages] [Bug 1513886] Re: Decreased battery life after upgrade.
Daniel Holm, if you boot into a 3.19.x kernel is this still reproducible? ** Tags removed: bios-outdated-r1044v7 ** Tags added: latest-bios-r1044v7 regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1513886 Title: Decreased battery life after upgrade. Status in linux package in Ubuntu: Incomplete Bug description: Hi, In Ubuntu 15.04 I had around 7-8 hours of battery life but after upgrade I got half. Why? Maybe not the right package, but I don't know what else than the kernel. If wrong please change. I use lmt for increased battery life, and it is still installed (even reinstalled and I also tried ltp instead, but no change). Disabling intel p state turbo does no change. I dont really have any processes ruining it and it even says 4 hours after first boot. The battery ost 5% just while I submitted this bug report. 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-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 3401 F pulseaudio /dev/snd/pcmC1D0p: daniel 3401 F...m pulseaudio /dev/snd/controlC1: daniel 3401 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 6 16:46:52 2015 HibernationDevice: RESUME=UUID=45e6f377-dcab-4fc1-a57b-5b21563164a2 InstallationDate: Installed on 2014-11-02 (368 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Sony Corporation SVP1321M2EB ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149.1 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-25 (11 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1043V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1043V7:bd11/21/2013:svnSonyCorporation:pnSVP1321M2EB:pvrC60C0754:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321M2EB dmi.product.version: C60C0754 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524122] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1524122 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/1524122 Title: XPS 15 (9550) Won't boot with 4.4 Status in linux package in Ubuntu: Incomplete Bug description: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524122] [NEW] XPS 15 (9550) Won't boot with 4.4
Public bug reported: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! ** 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/1524122 Title: XPS 15 (9550) Won't boot with 4.4 Status in linux package in Ubuntu: New Bug description: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...' linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff echo'Loading initial ramdisk ...' initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 I have also reported this bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=108981 Please let me know what other info would be helpful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1524122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522949] Re: Bluetooth doesn't work on 0930:0225 Toshiba Corporation
Somehow I missed the step where I rename it, though I see it now with the word "Important" in front of it in your instructions. Working great now! Thanks so much! So can a script be made that grabs (wgets) the drivers from the broadcom website and extracts the right one? Would that be legal? Maybe something like some of the flash installers? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522949 Title: Bluetooth doesn't work on 0930:0225 Toshiba Corporation Status in linux package in Ubuntu: In Progress Bug description: I have not been able to get bluetooth running in Ubuntu 14.04, 14.10, or 15.10 on my Toshiba laptop. Bluetooth does work under Windows. There is no bluetooth icon. The bluetooth manager says "Bluetooth is disabled" whether I set it to On or Off. rfkill list: 0: Toshiba Bluetooth: Bluetooth Soft blocked: no Hard blocked: no [...] The modified kernel is because I installed btusb-lp1506615-dkms from https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth . No change in behavior. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josiah 1874 F pulseaudio /dev/snd/controlC1: josiah 1874 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 4 14:45:28 2015 HibernationDevice: RESUME=UUID=0bcbd4ab-9f94-44d7-857f-717f4e7c9481 InstallationDate: Installed on 2015-12-03 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: TOSHIBA Satellite L75-B ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-4.2.0-16-generic.efi.signed root=UUID=edea9167-ead7-4da4-81ac-fa65520b3e91 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-4.2.0-16-generic RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 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: 11/03/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.60 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP 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.60:bd11/03/2014:svnTOSHIBA:pnSatelliteL75-B:pvrPSKRLU-01400M:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L75-B dmi.product.version: PSKRLU-01400M dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1522949] Re: Bluetooth doesn't work on 0930:0225 Toshiba Corporation
See this? BCM: Patch brcm/BCM.hcd not found You need to convert the firmware and copy it as /lib/firmware/brcm/BCM.hcd 2015-12-09 1:00 GMT+03:00 Josiah Raiche : > I've just tried it with my wife's phone and it cannot see other devices > or be seen by them. > > I think you're right about the firmware. Do I need to rename the .hcd > file? > > $ dmesg | grep -i blue > [7.220345] toshiba_bluetooth: Toshiba ACPI Bluetooth device driver > [9.324633] Bluetooth: Core ver 2.20 > [9.324652] Bluetooth: HCI device and connection manager initialized > [9.324655] Bluetooth: HCI socket layer initialized > [9.324658] Bluetooth: L2CAP socket layer initialized > [9.324663] Bluetooth: SCO socket layer initialized > [ 10.102717] Bluetooth: hci0: BCM: chip id 70 > [ 10.102732] Bluetooth: hci0: BCM (001.001.011) build > [ 10.201305] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed > with error -2 > [ 10.201311] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found > [ 12.206876] Bluetooth: hci0 command 0x1003 tx timeout > [ 20.557296] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 20.557300] Bluetooth: BNEP filters: protocol multicast > [ 20.557304] Bluetooth: BNEP socket layer initialized > [ 27.343887] Bluetooth: RFCOMM TTY layer initialized > [ 27.343894] Bluetooth: RFCOMM socket layer initialized > [ 27.343899] Bluetooth: RFCOMM ver 1.11 > [ 975.436789] Bluetooth: hci0: BCM: chip id 70 > [ 975.436798] Bluetooth: hci0: BCM (001.001.011) build > [ 975.436823] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed > with error -2 > [ 975.436827] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found > [ 977.441211] Bluetooth: hci0 command 0x1003 tx timeout > [ 1052.412795] Bluetooth: hci0: BCM: chip id 70 > [ 1052.412803] Bluetooth: hci0: BCM (001.001.011) build > [ 1052.412827] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed > with error -2 > [ 1052.412831] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found > [ 3982.782368] Modules linked in: cmac rfcomm bnep pci_stub vboxpci(OE) > vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 btusb(OE) > uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops > videobuf2_core bluetooth snd_hda_codec_hdmi v4l2_common videodev media > intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp > snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel kvm_intel > snd_hda_codec kvm snd_hda_core snd_hwdep wl(POE) crct10dif_pclmul > crc32_pclmul ghash_clmulni_intel snd_seq_midi rtsx_pci_ms snd_seq_midi_event > snd_rawmidi memstick cryptd snd_seq snd_seq_device cfg80211 snd_soc_rt5640 > snd_soc_rl6231 toshiba_acpi snd_soc_core joydev input_leds snd_compress > ac97_bus serio_raw snd_pcm_dmaengine snd_pcm snd_timer sparse_keymap dw_dmac > i2c_designware_platform > [ 3982.782415] i2c_designware_core toshiba_bluetooth snd dw_dmac_core > soc_button_array soundcore snd_soc_sst_acpi 8250_dw shpchp > spi_pxa2xx_platform mei_me mei lpc_ich mac_hid parport_pc ppdev lp parport > autofs4 rtsx_pci_sdmmc i915 psmouse ahci i2c_algo_bit libahci drm_kms_helper > rtsx_pci drm r8169 mii wmi video i2c_hid hid sdhci_acpi sdhci > [ 4312.154947] Modules linked in: cmac rfcomm bnep pci_stub vboxpci(OE) > vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 btusb(OE) > uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops > videobuf2_core bluetooth snd_hda_codec_hdmi v4l2_common videodev media > intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp > snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel kvm_intel > snd_hda_codec kvm snd_hda_core snd_hwdep wl(POE) crct10dif_pclmul > crc32_pclmul ghash_clmulni_intel snd_seq_midi rtsx_pci_ms snd_seq_midi_event > snd_rawmidi memstick cryptd snd_seq snd_seq_device cfg80211 snd_soc_rt5640 > snd_soc_rl6231 toshiba_acpi snd_soc_core joydev input_leds snd_compress > ac97_bus serio_raw snd_pcm_dmaengine snd_pcm snd_timer sparse_keymap dw_dmac > i2c_designware_platform > [ 4312.155028] i2c_designware_core toshiba_bluetooth snd dw_dmac_core > soc_button_array soundcore snd_soc_sst_acpi 8250_dw shpchp > spi_pxa2xx_platform mei_me mei lpc_ich mac_hid parport_pc ppdev lp parport > autofs4 rtsx_pci_sdmmc i915 psmouse ahci i2c_algo_bit libahci drm_kms_helper > rtsx_pci drm r8169 mii wmi video i2c_hid hid sdhci_acpi sdhci > [ 4367.360223] Bluetooth: hci0 command 0x1001 tx timeout > [ 4375.359525] Bluetooth: hci0: BCM: Reading local version info failed (-110) > [ 4375.367118] Bluetooth: hci0: BCM: chip id 70 > [ 4375.367125] Bluetooth: hci0: BCM (001.001.011) build > [ 4375.367151] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed > with error -2 > [ 4375.367154] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found > [ 5659.942860] Bluetooth: hci0: BCM: chip id 70 > [ 5659.942866] Bluetooth: hci0: BCM (001.001.011) build > [ 5659.969593] bluetooth hci0: Direct firmw
[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in kvm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08: 0086 R09: 025f [ 522.963781] R10: R11: 88005dec79ae R12: 1000 [ 522.963785] R13: 880043a42000 R14: 880043a43000 R15: 0012 [ 522.963789] FS: 7fa330823740() GS:88007fd0() knlGS: [ 522.963793] CS: 0010
[Kernel-packages] [Bug 1522949] Re: Bluetooth doesn't work on 0930:0225 Toshiba Corporation
I've just tried it with my wife's phone and it cannot see other devices or be seen by them. I think you're right about the firmware. Do I need to rename the .hcd file? $ dmesg | grep -i blue [7.220345] toshiba_bluetooth: Toshiba ACPI Bluetooth device driver [9.324633] Bluetooth: Core ver 2.20 [9.324652] Bluetooth: HCI device and connection manager initialized [9.324655] Bluetooth: HCI socket layer initialized [9.324658] Bluetooth: L2CAP socket layer initialized [9.324663] Bluetooth: SCO socket layer initialized [ 10.102717] Bluetooth: hci0: BCM: chip id 70 [ 10.102732] Bluetooth: hci0: BCM (001.001.011) build [ 10.201305] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 10.201311] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 12.206876] Bluetooth: hci0 command 0x1003 tx timeout [ 20.557296] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.557300] Bluetooth: BNEP filters: protocol multicast [ 20.557304] Bluetooth: BNEP socket layer initialized [ 27.343887] Bluetooth: RFCOMM TTY layer initialized [ 27.343894] Bluetooth: RFCOMM socket layer initialized [ 27.343899] Bluetooth: RFCOMM ver 1.11 [ 975.436789] Bluetooth: hci0: BCM: chip id 70 [ 975.436798] Bluetooth: hci0: BCM (001.001.011) build [ 975.436823] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 975.436827] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 977.441211] Bluetooth: hci0 command 0x1003 tx timeout [ 1052.412795] Bluetooth: hci0: BCM: chip id 70 [ 1052.412803] Bluetooth: hci0: BCM (001.001.011) build [ 1052.412827] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 1052.412831] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 3982.782368] Modules linked in: cmac rfcomm bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 btusb(OE) uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops videobuf2_core bluetooth snd_hda_codec_hdmi v4l2_common videodev media intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel kvm_intel snd_hda_codec kvm snd_hda_core snd_hwdep wl(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi rtsx_pci_ms snd_seq_midi_event snd_rawmidi memstick cryptd snd_seq snd_seq_device cfg80211 snd_soc_rt5640 snd_soc_rl6231 toshiba_acpi snd_soc_core joydev input_leds snd_compress ac97_bus serio_raw snd_pcm_dmaengine snd_pcm snd_timer sparse_keymap dw_dmac i2c_designware_platform [ 3982.782415] i2c_designware_core toshiba_bluetooth snd dw_dmac_core soc_button_array soundcore snd_soc_sst_acpi 8250_dw shpchp spi_pxa2xx_platform mei_me mei lpc_ich mac_hid parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc i915 psmouse ahci i2c_algo_bit libahci drm_kms_helper rtsx_pci drm r8169 mii wmi video i2c_hid hid sdhci_acpi sdhci [ 4312.154947] Modules linked in: cmac rfcomm bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 btusb(OE) uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops videobuf2_core bluetooth snd_hda_codec_hdmi v4l2_common videodev media intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel kvm_intel snd_hda_codec kvm snd_hda_core snd_hwdep wl(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi rtsx_pci_ms snd_seq_midi_event snd_rawmidi memstick cryptd snd_seq snd_seq_device cfg80211 snd_soc_rt5640 snd_soc_rl6231 toshiba_acpi snd_soc_core joydev input_leds snd_compress ac97_bus serio_raw snd_pcm_dmaengine snd_pcm snd_timer sparse_keymap dw_dmac i2c_designware_platform [ 4312.155028] i2c_designware_core toshiba_bluetooth snd dw_dmac_core soc_button_array soundcore snd_soc_sst_acpi 8250_dw shpchp spi_pxa2xx_platform mei_me mei lpc_ich mac_hid parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc i915 psmouse ahci i2c_algo_bit libahci drm_kms_helper rtsx_pci drm r8169 mii wmi video i2c_hid hid sdhci_acpi sdhci [ 4367.360223] Bluetooth: hci0 command 0x1001 tx timeout [ 4375.359525] Bluetooth: hci0: BCM: Reading local version info failed (-110) [ 4375.367118] Bluetooth: hci0: BCM: chip id 70 [ 4375.367125] Bluetooth: hci0: BCM (001.001.011) build [ 4375.367151] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 4375.367154] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 5659.942860] Bluetooth: hci0: BCM: chip id 70 [ 5659.942866] Bluetooth: hci0: BCM (001.001.011) build [ 5659.969593] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 5659.969600] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 5661.974325] Bluetooth: hci0 command 0x1003 tx timeout [ 9561.882519] Modules linked in: cmac rfcomm bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 btusb(OE)
[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
I just tried again with two logical CPUs and the core set to "Westmere" (I think that was the default), and didn't see the bug. So this seems related specifically to "[x] Copy host CPU configuration" being checked. Here's the /proc/cpuinfo from the "virtual Westmere" where it works: http://paste.ubuntu.com/13836572/ ** Also affects: kvm (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/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in kvm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08:
[Kernel-packages] [Bug 1512482] Re: Keyboard and touchpad malfunctioning on Thinkpad Twist
Unfortunately, I don't have them anymore as I had to delete them to make space for upgrades. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1512482 Title: Keyboard and touchpad malfunctioning on Thinkpad Twist Status in linux package in Ubuntu: Incomplete Bug description: I don't know if this is really a kernel bug or if it's any other component, please help me know how I can diagnose the problem better. This is a bug I have been experiencing with both 15.04 and 15.10, while this was not a problem with earlier distributions -- unfortunately, I don't remember which one in particular was actually working. I have a Thinkpad Twist -- a hybrid laptop with touchscreen. The touchpad almost never works (even though sometimes, erratically, it does). The keyboard sometimes stops working, and works again after a suspend/resume cycle. Sometimes it behaves as if a key is stuck. When running xinput --list, I don't see the touchpad. The touchscreen and external input devices connected via USB, however, work fine. I was thinking this was a hardware problem, but on the same machine with Windows the problem does not appear to present itself. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-17-generic 4.2.0-17.21 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: della 1684 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 2 21:39:42 2015 HibernationDevice: RESUME=UUID=38d3eec5-87ea-4477-bd19-d975ac2fca22 InstallationDate: Installed on 2013-10-05 (758 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: LENOVO 33474HU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic root=UUID=907c2dfa-5b96-4857-a1e7-6b59406e9721 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-17-generic N/A linux-backports-modules-4.2.0-17-generic N/A linux-firmware1.149.1 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-01 (0 days ago) dmi.bios.date: 12/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GDETA9WW (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.vendor: LENOVO dmi.board.version: Win8 STD 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:bvrGDETA9WW(1.69):bd12/15/2014:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33474HU dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524069] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in linux package in Ubuntu: Confirmed Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08: 0086 R09: 025f [ 522.963781] R10: R11: 88005dec79ae R12: 1000 [ 522.963785] R13: 880043a42000 R14: 880043a43000 R15: 0012 [ 522.963789] FS: 7fa330823740() GS:88007fd0() knlGS: [ 522.963793] CS: 0010 DS:
[Kernel-packages] [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
I got this error on my HP Notebook 15-ac131ne (i3-5005U) with Ubuntu Gnome 15.10 freshly installed. Errors show just before login prompt. I can log in to my desktop after that. [26255.192670] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [26255.194650] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [26255.202474] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [26255.203480] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [26255.210467] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! [26255.211472] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On a recent intel NUC using i915 graphics, I get the following errors in dmesg: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! There are two monitors connected to this box, one with mini- HDMI->HDMI, one with mini-DP->HDMI cable. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=80896 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.26.25 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 10:07:31 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in linux package in Ubuntu: New Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08: 0086 R09: 025f [ 522.963781] R10: R11: 88005dec79ae R12: 1000 [ 522.963785] R13: 880043a42000 R14: 880043a43000 R15: 0012 [ 522.963789] FS: 7fa330823740() GS:88007fd0() knlGS: [ 522.963793] CS: 0010 DS: ES: CR0: 80050033 [ 522.963796] CR2: 7fa330623000 CR3
[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
For what it's worth, unchecking "[ ] Copy host CPU configuration" in virt-manager and selecting "Hypervisor default" for the CPU is a workaround. (/proc/cpuinfo reports "QEMU Virtual CPU version 2.4.0") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in linux package in Ubuntu: New Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08: 0086 R09: 025f [ 522.963781] R10: R11: 88005dec79ae R12: 1000 [ 522.963785] R13: 880043a42000 R14: 880043a43000 R15: 0012 [ 522.963789] FS: 7
[Kernel-packages] [Bug 1524069] Re: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
Also, the hypervisor's /proc/cpuinfo reports the following CPU configuration (8 cores of the same): processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz stepping: 3 microcode : 0x1e cpu MHz : 2500.097 cache size : 6144 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt bugs: bogomips: 4988.49 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: And the hypervisor's kernel is version 4.2.0-19-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524069 Title: Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception Status in linux package in Ubuntu: New Bug description: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_pag
[Kernel-packages] [Bug 1523161] Re: [Worked around]BCM43142 802.11b/g/n (rev 01) wifi adapter random freezes. Possibly affects more broadcom devices.
Also, I've found a final workaround that gives 0% losses and a stable connection. For me it was 3.13.0-37 kernel and a _downgraded_ driver with version 6.30.223.141+bdcom-0ubuntu2 ** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- 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/1523161 Title: [Worked around]BCM43142 802.11b/g/n (rev 01) wifi adapter random freezes. Possibly affects more broadcom devices. Status in Linux Mint: New Status in bcmwl package in Ubuntu: New Bug description: Hi, I've experienced random timeouts on BCM43142 802.11b/g/n (rev 01) adapter on Lenovo Z50-70 laptop. The flow is as follows: on startup I _always_ have a connection to my network. I use up some traffic, then suddenly packet loss rate climbs up, then maybe goes down, then up again and the connection becomes effectively unresponsive. The device is still connected to the network. Some packets, actually, even may slip through. After reconnection (rmmod wl -> modprobe wl), it stabilizes a bit, but then it occurs again. It seems that the probability of such an issue increases with the number of programs that are using connection. I have removed all drivers but bcmwl-kernel-sources and blacklisted their modules: (from /etc/modprobe.d/blacklist.conf) blacklist ideapad_laptop blacklist ssb blacklist bcma blacklist b43 blacklist brcmsmac blacklist b43legacy blacklist ndiswrapper I wasn't able to find a root cause of it, but it happens really often. Two times when I wrote this message, actually. I am running Mint 17.3 'Rosa' I have bcmwl-kernel-sources 6.30.223.248+bdcom-0ubuntu0.2~lp1415880~1 I tried other versions, but not succeeded. The issue makes the wifi adapter effectively unusable. uname -a Linux dsmdmini-mint 4.2.0-19-generic #23~14.04.1-Ubuntu SMP Thu Nov 12 12:33:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux lsmod Module Size Used by lib80211_crypt_tkip20480 0 lib80211 16384 1 lib80211_crypt_tkip wl 6365184 0 cfg80211 540672 1 wl bbswitch 16384 0 intel_rapl 20480 0 iosf_mbi 16384 1 intel_rapl x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 coretemp 16384 0 rfcomm 69632 0 bnep 20480 2 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo bluetooth 512000 10 bnep,rfcomm videobuf2_memops 16384 1 videobuf2_vmalloc rtsx_usb_ms20480 0 nvidia 8642560 33 kvm 507904 0 videobuf2_core 49152 1 uvcvideo v4l2_common16384 1 videobuf2_core videodev 172032 3 uvcvideo,v4l2_common,videobuf2_core media 24576 2 uvcvideo,videodev memstick 20480 1 rtsx_usb_ms crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel snd_soc_rt5640114688 0 lrw16384 1 aesni_intel snd_soc_rl6231 16384 1 snd_soc_rt5640 gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel snd_soc_core 200704 1 snd_soc_rt5640 ablk_helper16384 1 aesni_intel snd_hda_codec_hdmi 49152 1 cryptd 20480 2 aesni_intel,ablk_helper snd_compress 20480 1 snd_soc_core binfmt_misc20480 1 snd_hda_codec_conexant24576 1 ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core snd_hda_codec_generic73728 1 snd_hda_codec_conexant input_leds 16384 0 joydev 20480 0 snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_hda_intel 36864 5 serio_raw 16384 0 snd_hda_codec 135168 4 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel snd_hda_core 65536 5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_rawmidi32768 1 snd_seq_midi snd_hwdep 16384 1 snd_hda_codec mei_me 32768 0 lpc_ich24576 0 snd_pcm 102400 7 snd_soc_rt5640,snd_soc_core,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_pcm_dmaengine,snd_hda_core mei98304 1 mei_me shpchp 36864 0 snd_seq69632 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 32768 2 snd_pcm,snd_seq snd81920 23 snd_soc_core,snd_hwdep,snd_timer,snd_hda_codec_hdmi,sn
[Kernel-packages] [Bug 1524069] [NEW] Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel exception
Public bug reported: The symptom I saw was this (note the segfault, and apt-get upgrade hangs after this): Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic Segmentation fault done Setting up linux-firmware (1.127.19) ... Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-3.13.0-71-generic Found initrd image: /boot/initrd.img-3.13.0-71-generic Found linux image: /boot/vmlinuz-3.13.0-68-generic Found initrd image: /boot/initrd.img-3.13.0-68-generic In dmesg, I saw a corresponding kernel stack trace: [ 522.649091] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 522.654031] JFS: nTxBlock = 8192, nTxLock = 65536 [ 522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE]. [ 522.672519] QNX4 filesystem 0.2.3 registered. [ 522.677257] xor: measuring software checksum speed [ 522.715613]prefetch64-sse: 17306.000 MB/sec [ 522.755589]generic_sse: 16039.000 MB/sec [ 522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec) [ 522.823619] raid6: sse2x1 10481 MB/s [ 522.891614] raid6: sse2x2 13303 MB/s [ 522.959616] raid6: sse2x4 15209 MB/s [ 522.963634] invalid opcode: [#1] SMP [ 522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse [ 522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic #111-Ubuntu [ 522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 88005dec6000 [ 522.963759] RIP: 0010:[] [] raid6_avx21_gen_syndrome+0x4a/0x160 [raid6_pq] [ 522.963767] RSP: 0018:88005dec7c40 EFLAGS: 00010246 [ 522.963771] RAX: RBX: 88005dec7c88 RCX: 880059363000 [ 522.963774] RDX: RSI: 0080 RDI: 0012 [ 522.963778] RBP: 88005dec7c70 R08: 0086 R09: 025f [ 522.963781] R10: R11: 88005dec79ae R12: 1000 [ 522.963785] R13: 880043a42000 R14: 880043a43000 R15: 0012 [ 522.963789] FS: 7fa330823740() GS:88007fd0() knlGS: [ 522.963793] CS: 0010 DS: ES: CR0: 80050033 [ 522.963796] CR2: 7fa330623000 CR3: 36acf000 CR4: 001006e0 [ 522.963801] Stack: [ 522.963803] 0080 a049e238 a04b0720 880043a42000 [ 522.963810] 3cd7 0001d992 88005dec7d40 a00d20fb [ 522.963817] a04a0600 a04a1600 a04a2600 [ 522.963824] Call Trace: [ 522.963838] [] init_module+0xfb/0x1000 [raid6_pq] [ 522.963843] [] ? 0xa00d1fff [ 522.9638
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
Knowing that this bug is in progress, I want to share an interesting finding (at least for me). I am on rc-proposed (with bluez5, see details below). When SIM 1 is (randomly picked) used, the battery status is shown in the car display. When SIM 2 is used, the battery status shows 100% loading. system-image-cli -i: current build number: 196 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-05 18:28:01 version version: 196 version ubuntu: 20151204.1 version device: 20151028-869191d version custom: 2015–36-46-vivid -- 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/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Triaged Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Triaged Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509565] Re: CVE-2015-7885
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1509565 Title: CVE-2015-7885 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: 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 Committed 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivi
[Kernel-packages] [Bug 1520184] Re: CVE-2015-8104
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1520184 Title: CVE-2015-8104 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid 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-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid 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 source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid S
[Kernel-packages] [Bug 1508856] Re: CVE-2015-7872
** Description changed: The key_gc_unused_keys function in security/keys/gc.c in the Linux kernel through 4.2.6 allows local users to cause a denial of service (OOPS) via crafted keyctl commands. Break-Fix: - f05819df10d7b09f6d1eb6f8534a8f68e5a4fe61 - Break-Fix: - 911b79cde95c7da0ec02f48105358a36636b7a71 -- 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/1508856 Title: CVE-2015-7872 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
I see the same error message when I try the following: * laptop is in docking station, external monitor is connected * send laptop to sleep * undock laptop * wake laptop up The error message is present on the terminal, my KDE session is logged out. Nothing useful in .xsession-errors though. The laptop is a new T450s, running Kubuntu 15.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On a recent intel NUC using i915 graphics, I get the following errors in dmesg: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! There are two monitors connected to this box, one with mini- HDMI->HDMI, one with mini-DP->HDMI cable. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=80896 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.26.25 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 10:07:31 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1508329] Re: CVE-2015-7799
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1508329 Title: CVE-2015-7799 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: 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 Committed 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivi
[Kernel-packages] [Bug 1509564] Re: CVE-2015-7884
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1509564 Title: CVE-2015-7884 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in Vivid: Invalid Status in linux-ti-omap4 source packa
[Kernel-packages] [Bug 1522991] Re: linux-lts-trusty: 3.13.0-73.116~precise1 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-73.116~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 23:03 UTC kernel-stable-master-bug:1522858 kernel-stable-Prepare-package-end:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:27 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:03 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:03 UTC + kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1522991 Title: linux-lts-trusty: 3.13.0-73.116~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-73.116~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 23:03 UTC kernel-stable-master-bug:1522858 kernel-stable-Prepare-package-end:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:27 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:03 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522918] Re: linux: 3.19.0-41.46 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-41.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 17:34 UTC kernel-stable-Prepare-package-end:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:26 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:02 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:02 UTC + kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522918 Title: linux: 3.19.0-41.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-41.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 17:34 UTC kernel-stable-Prepare-package-end:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:26 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:02 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522858] Re: linux: 3.13.0-73.116 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-73.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 14:25 UTC kernel-stable-Prepare-package-end:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-start:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:25 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:01 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:01 UTC + kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522858 Title: linux: 3.13.0-73.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-73.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 14:25 UTC kernel-stable-Prepare-package-end:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-start:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:25 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:01 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Security-signoff-end:Tuesday, 08. December 2015 20:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518570] Re: Touchpad not working on Asus Zenbook UX305CA-FC022T
upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=108581 ** Bug watch added: Linux Kernel Bug Tracker #108581 http://bugzilla.kernel.org/show_bug.cgi?id=108581 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518570 Title: Touchpad not working on Asus Zenbook UX305CA-FC022T Status in linux package in Ubuntu: Triaged Bug description: New install of Ubuntu 15.10 Touchpad is not working, using usb mouse. Tested mainstream kernel upto 4.4-rc1, still not working. Asus Zenbook UX305CA-FC022T ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pelle 1532 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 21 16:02:10 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=199cbad3-e17e-4549-b0ba-8eedbbbc3795 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 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/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305CA 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/1518570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522918] Re: linux: 3.19.0-41.46 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522918 Title: linux: 3.19.0-41.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-41.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 17:34 UTC kernel-stable-Prepare-package-end:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 05. December 2015 03:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:26 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:02 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:02 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522991] Re: linux-lts-trusty: 3.13.0-73.116~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1522991 Title: linux-lts-trusty: 3.13.0-73.116~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-73.116~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 23:03 UTC kernel-stable-master-bug:1522858 kernel-stable-Prepare-package-end:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. December 2015 00:01 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:27 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:03 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:03 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523586] Re: [PPA] 4.4 regression: kernel panic on reboot
Thanks for the update, Martin. ** Tags removed: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1523586 Title: [PPA] 4.4 regression: kernel panic on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: While testing the unstable kernel PPA with linux-image-4.4.0-0-generic on ppc64el, autopkgtests often fail with this kernel crash on boot: ubuntu@juju-prod-ues-proposed-migration-machine-12:~⟫ nova console-log adt-xenial-ppc64el-systemd-20151207-161711 SLOF[0m[?25l ** [1mQEMU Starting [0m Build Date = Oct 9 2015 00:25:21 FW Version = buildd@ release 20140630 Press "s" to enter Open Firmware. [0m[?25hCC0100C0120C0140C0200C0201C0220C0240C0260C0270C02E0C0300C0320C0340C0360C0370C0380C0371C0372C0373C0374C0390C03F0C0400C0480C04C0C04D0C0500Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/vty@30001000 Populating /vdevice/nvram@7100 C0580C05A0Populating /pci@8002000 Adapters on 08002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 106b 003fserial bus [ usb-ohci ] 00 1800 (D) : 1af4 1001virtio [ block ] 00 2000 (D) : 1af4 1002unknown-legacy-device* C0600C0640C0690C06A0C06A8C06B0C06B8C06C0C06E0C0700C0800C0880No NVRAM common partition, re-initializing... C0890C08A0C08A8C08B0Scanning USB OHCI: initializing C08C0C08D0Using default console: /vdevice/vty@3000 C08E0C08E8C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... No DOS disk-label found. Successfully loaded [?25l[37m[40m[37m[40merror: no suitable video mode found. [?25l[37m[40m[2J[m[1;1H[2;22HGNU GRUB version 2.02~beta2-32ubuntu1 [37m[40m[4;2H++[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H++[37m[40m[18;2H[19;2H[37m[40m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [30m[47m[5;3H*Ubuntu [37m[40m[5;78H[37m[40m[37m[40m[6;3H Advanced options for Ubuntu [37m[40m[6;78H[37m[40m[37m[40m[7;3H [37m[40m[7;78H[37m[40m[37m[40m[8;3H [37m[40m[8;78H[37m[40m[37m[40m[9;3H [37m[40m[9;78H[37m[40m[37m[40m[10;3H [37m[40m[10;78H[37m[40m[37m[40m[11;3H [37m[40m[11;78H[37m[40m[37m[40m[12;3H [37m[40m[12;78H[37m[40m[37m[40m[13;3H [37m[40m[13;78H[37m[40m[37m[40m[14;3H [37m[40m[14;78H[37m[40m[37m[40m[15;3H [37m[40m[15;78H[37m[40m[37m[40m[16;3H [37m[40m[16;78H[37m[40m[16;80H [5;78H[22;1H The highlighted entry will be executed automatically in 10s.[5;78H[22;1H The highlighted entry will be executed automatically in 9s. [5;78H[22;1H The highlighted entry will be executed automatically in 8s. [5;78H[22;1H The highlighted entry will be executed automatically in 7s. [5;78H[22;1H The highlighted entry will be executed automatically in 6s. [5;78H[22;1H The highlighted entry will be executed automatically in 5s. [5;78H[22;1H The highlighted entry will be executed automatically in 4s. [5;78H[22;1H The highlighted entry will be executed automatically in 3s.
[Kernel-packages] [Bug 1518570] Re: Touchpad not working on Asus Zenbook UX305CA-FC022T
Still not working on 4.4.0-040400rc4-generic ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518570/+attachment/4531573/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518570 Title: Touchpad not working on Asus Zenbook UX305CA-FC022T Status in linux package in Ubuntu: Triaged Bug description: New install of Ubuntu 15.10 Touchpad is not working, using usb mouse. Tested mainstream kernel upto 4.4-rc1, still not working. Asus Zenbook UX305CA-FC022T ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pelle 1532 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 21 16:02:10 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=199cbad3-e17e-4549-b0ba-8eedbbbc3795 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 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/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305CA 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/1518570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522858] Re: linux: 3.13.0-73.116 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522858 Title: linux: 3.13.0-73.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-73.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 04. December 2015 14:25 UTC kernel-stable-Prepare-package-end:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-start:Friday, 04. December 2015 23:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 07. December 2015 19:25 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 07. December 2015 21:01 UTC kernel-stable-Verification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Certification-testing-start:Monday, 07. December 2015 21:01 UTC kernel-stable-Security-signoff-start:Monday, 07. December 2015 21:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 07. December 2015 21:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523586] Re: [PPA] 4.4 regression: kernel panic on reboot
Yes, it is a regression. Andy found the offending commit and the fix is already queued in Tejun's tree, so this should get fixed with the next upstream update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1523586 Title: [PPA] 4.4 regression: kernel panic on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: While testing the unstable kernel PPA with linux-image-4.4.0-0-generic on ppc64el, autopkgtests often fail with this kernel crash on boot: ubuntu@juju-prod-ues-proposed-migration-machine-12:~⟫ nova console-log adt-xenial-ppc64el-systemd-20151207-161711 SLOF[0m[?25l ** [1mQEMU Starting [0m Build Date = Oct 9 2015 00:25:21 FW Version = buildd@ release 20140630 Press "s" to enter Open Firmware. [0m[?25hCC0100C0120C0140C0200C0201C0220C0240C0260C0270C02E0C0300C0320C0340C0360C0370C0380C0371C0372C0373C0374C0390C03F0C0400C0480C04C0C04D0C0500Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/vty@30001000 Populating /vdevice/nvram@7100 C0580C05A0Populating /pci@8002000 Adapters on 08002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 106b 003fserial bus [ usb-ohci ] 00 1800 (D) : 1af4 1001virtio [ block ] 00 2000 (D) : 1af4 1002unknown-legacy-device* C0600C0640C0690C06A0C06A8C06B0C06B8C06C0C06E0C0700C0800C0880No NVRAM common partition, re-initializing... C0890C08A0C08A8C08B0Scanning USB OHCI: initializing C08C0C08D0Using default console: /vdevice/vty@3000 C08E0C08E8C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... No DOS disk-label found. Successfully loaded [?25l[37m[40m[37m[40merror: no suitable video mode found. [?25l[37m[40m[2J[m[1;1H[2;22HGNU GRUB version 2.02~beta2-32ubuntu1 [37m[40m[4;2H++[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H++[37m[40m[18;2H[19;2H[37m[40m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [30m[47m[5;3H*Ubuntu [37m[40m[5;78H[37m[40m[37m[40m[6;3H Advanced options for Ubuntu [37m[40m[6;78H[37m[40m[37m[40m[7;3H [37m[40m[7;78H[37m[40m[37m[40m[8;3H [37m[40m[8;78H[37m[40m[37m[40m[9;3H [37m[40m[9;78H[37m[40m[37m[40m[10;3H [37m[40m[10;78H[37m[40m[37m[40m[11;3H [37m[40m[11;78H[37m[40m[37m[40m[12;3H [37m[40m[12;78H[37m[40m[37m[40m[13;3H [37m[40m[13;78H[37m[40m[37m[40m[14;3H [37m[40m[14;78H[37m[40m[37m[40m[15;3H [37m[40m[15;78H[37m[40m[37m[40m[16;3H [37m[40m[16;78H[37m[40m[16;80H [5;78H[22;1H The highlighted entry will be executed automatically in 10s.[5;78H[22;1H The highlighted entry will be executed automatically in 9s. [5;78H[22;1H The highlighted entry will be executed automatically in 8s. [5;78H[22;1H The highlighted entry will be executed automatically in 7s. [5;78H[22;1H The highlighted entry will be executed automatically in 6s. [5;78H[22;1H The highlighted entry will be executed automatically in 5s. [5;78H[22;1H The highlighted entry will be executed automaticall
[Kernel-packages] [Bug 1499203] Re: memory leak in hv_storvsc (3.13.0-63-generic)
Would it be possible for you test test the latest mainline kernel, to see if the memory leak happens there as well? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-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/1499203 Title: memory leak in hv_storvsc (3.13.0-63-generic) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: Slab and SUnreclaim values in /proc/meminfo keep increasing. On one servers it reached 85% of physical memory after 14 days - but on most other servers it increases more slowly. I checked /proc/slabinfo and almost all allocations were in kmalloc-512. So I enabled "slub_debug=U,kmalloc-512" on one server, and after only 24h of uptime 11% of the memory was used by kmalloc-512 and unreclaimable. With debugging enabled I could see the following in /sys/kernel/slab/kmalloc-512/alloc_calls: 521294 storvsc_queuecommand+0x359/0x790 [hv_storvsc] age=161922/955116/20882927 pid=1-41545 All other counters were below 2000. In /sys/kernel/slab/kmalloc-512/free_calls I see the following: 516823 age=4315783846 pid=0 The hv_storvsc module is for Hyper-V. We are (unfortunately) running Hyper-V 6.3.9600.16384 with Microsoft System Center 2012 R2 Update rollup 3 for all the servers with this issue. Kernels are stock linux-image-3.13.0-63-generic, 3.13.0-63.103, x86_64, from Ubuntu 14.04 LTS . /proc/version_signature contains: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 No output from lspci -vnvn. The problem described above happens on both single and multicore virtual machines. CPU in hypervisors are E5-2630 v2 @ 2.60GHz. Let me know if you need more info or if I can do more debugging. Regards, Oskar Liljeblad --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 24 00:31 seq crw-rw 1 root audio 116, 33 Sep 24 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [59081.977909] systemd-udevd[26480]: starting version 204 [59124.051974] init: systemd-logind main process (756) killed by TERM signal DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-09-09 (380 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic.efi.signed root=UUID=f4d228d6-2eee-40fc-bf3f-633e46fa8301 ro slub_debug=U,kmalloc-512 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: Sep 24 02:06:19 adm-backup1 dhclient: message repeated 1447 times: [ DHCPREQUEST of 10.40.128.9 on eth0 to 192.0.2.253 port 67 (xid=0x429dad4)] Sep 24 02:06:37 adm-backup1 dhclient: DHCPREQUEST of 10.40.128.9 on eth0 to 255.255.255.255 port 67 (xid=0x429dad4) Sep 24 02:06:37 adm-backup1 dhclient: DHCPACK of 10.40.128.9 from 192.0.2.253 Sep 24 02:06:37 adm-backup1 dhclient: bound to 10.40.128.9 -- renewal in 44877 seconds. _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6126-4244-1659-0314-3158-3955-44 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Co
[Kernel-packages] [Bug 1516547] Re: Ubuntu 15.10 crashes with RAID-10
I built the next test kernel, up to the following commit: c0c3a718e3ab2430a52a60d614b109e5e48e83e2 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1516547 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/1516547 Title: Ubuntu 15.10 crashes with RAID-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: In Progress Bug description: When trying to install Ubuntu 15.10 with a RAID-10 created the system crashes after some time during the installation. Hitting Alt+F4 gives the following output as seen from screenshots in attachments. It looks like kernel 4.2 have some issues with RAID-10 as we can install Ubuntu 15.04 (with kernel 3.19) without problems. If we upgrade to kernel 4.2 in Ubuntu 15.04 we get the same errors. We have no problems when installing without RAID, RAID-0 or RAID-1. We've also tried on different hardware and different disk types/sizes but we still get system crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing
I built a Vivid test kernel with the backport from Andy Whitcroft. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1520427/ Can you test this kernel and see if it resolves this bug? 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/1520427 Title: drm/fbdev: Return -EBUSY when oopsing Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Issue: Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access, the screen would be frozen and never come back,but the system does not hang. Generally, an SMEP/SMAP violation should cause the involved process killed, an oops from page fault exception generated to the syslog, and the system survived. Fix: One patch from 4.3 kernel fix this issue commit c50bfd08d60cefbe1714c4a53b1c325982858549 Author: Daniel Vetter Date: Tue Jul 28 13:18:40 2015 +0200 drm/fbdev: Return -EBUSY when oopsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest (14.04 regression)
*** This bug is a duplicate of bug 1346917 *** https://bugs.launchpad.net/bugs/1346917 Hi, could you please file a new bug with debugging information as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/comments/11 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308341 Title: Multiple CPUs causes blue screen on Windows guest (14.04 regression) Status in QEMU: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Configuring a Windows 7 guest using more than one CPU cases the guest to fail. This happens after a few hours after guest boot. This is the error on the blue screen: "A clock interrupt was not received on a secondary processor within the allocated time interval" After resetting, the guest will never boot and a new bluescreen with the error "STOP: 0x005c" appears. Shutting down the guest completely and restarting it will allow it to boot and run for a few hours again. The guest was created using virt-manager. The error happens with or without virtio devices and with both 32-bit and 64-bit Windows 7 guests. I am using Ubuntu 14.04 release candidate. qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1308341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523036] Re: linux-lts-vivid: 3.19.0-41.46~14.04.2 -proposed tracker
Rebuilding as linux-lts-vivid (3.19.0-41.46~14.04.2). The .1 package was accidentally build without a .orig tarball. ** Summary changed: - linux-lts-vivid: 3.19.0-41.46~14.04.1 -proposed tracker + linux-lts-vivid: 3.19.0-41.46~14.04.2 -proposed tracker ** Description changed: - This bug is for tracking the 3.19.0-41.46~14.04.1 upload package. This + This bug is for tracking the 3.19.0-41.46~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 05. December 2015 03:02 UTC kernel-stable-master-bug:1522918 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 07. December 2015 22:02 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. December 2015 22:02 UTC kernel-stable-phase-changed:Monday, 07. December 2015 22:02 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1523036 Title: linux-lts-vivid: 3.19.0-41.46~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-41.46~14.04.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 05. December 2015 03:02 UTC kernel-stable-master-bug:1522918 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 07. December 2015 22:02 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. December 2015 22:02 UTC kernel-stable-phase-changed:Monday, 07. December 2015 22:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1523036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing
It looks like you already submitted an SRU request, so please ignore comment #4. And it looks like apw has performed the backport for #5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520427 Title: drm/fbdev: Return -EBUSY when oopsing Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Issue: Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access, the screen would be frozen and never come back,but the system does not hang. Generally, an SMEP/SMAP violation should cause the involved process killed, an oops from page fault exception generated to the syslog, and the system survived. Fix: One patch from 4.3 kernel fix this issue commit c50bfd08d60cefbe1714c4a53b1c325982858549 Author: Daniel Vetter Date: Tue Jul 28 13:18:40 2015 +0200 drm/fbdev: Return -EBUSY when oopsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing
Commit c50bfd08 does not pick cleanly in the Vivid(3.19) kernel. The 3.19 kernel does not have intel_fbdev_blank() or intel_fbdev_pan_display(). intel_fbdev_blank() was added by commit 03e515f7 in v4.1-rc1. intel_fbdev_pan_display() was added by commit d9a946b5 in v4.2-rc1. Can you confirm where or not commit c50bfd08 is needed in the 3.19 Wily kernel? If it is, I can backport the commit. 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/1520427 Title: drm/fbdev: Return -EBUSY when oopsing Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Issue: Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access, the screen would be frozen and never come back,but the system does not hang. Generally, an SMEP/SMAP violation should cause the involved process killed, an oops from page fault exception generated to the syslog, and the system survived. Fix: One patch from 4.3 kernel fix this issue commit c50bfd08d60cefbe1714c4a53b1c325982858549 Author: Daniel Vetter Date: Tue Jul 28 13:18:40 2015 +0200 drm/fbdev: Return -EBUSY when oopsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing
Thanks for the update. I will submit an SRU request for that commit. ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520427 Title: drm/fbdev: Return -EBUSY when oopsing Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Issue: Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access, the screen would be frozen and never come back,but the system does not hang. Generally, an SMEP/SMAP violation should cause the involved process killed, an oops from page fault exception generated to the syslog, and the system survived. Fix: One patch from 4.3 kernel fix this issue commit c50bfd08d60cefbe1714c4a53b1c325982858549 Author: Daniel Vetter Date: Tue Jul 28 13:18:40 2015 +0200 drm/fbdev: Return -EBUSY when oopsing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455654] Re: Using battery power even when plugged in
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455654 Title: Using battery power even when plugged in Status in linux package in Ubuntu: Triaged Bug description: I am using Ubuntu 15.04 on Asus Zenbook UX301L. The problem is that battery indicator always says "using battery power", even when laptop is on AC power. There is no such problem under Windows. I always thought it was a minor issue until my laptop got shutdown today because it thought battery power was critical (it was at 100% and on AC power of course, but system decided it wasn't). Worst of all is that I cannot disable this action in power options. Which makes this bug kinda critical. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 16 00:04:09 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2015-05-06 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 pcie_aspm=force acpi_osi= vt.handoff=7 SourcePackage: compiz UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri May 15 23:36:17 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5126 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+
Thanks for the update, Miguel. Would you be able to test the kernel posted in comment #9? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501281 Title: Frequent freezes on 15.04 with kernel 3.19.0-29+ Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Incomplete Bug description: I am experiencing systematic freezes since my kernel was automatically upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30. If I use kernel 3.19.0-28 it does not freeze any more. Behaviour is described with more details at http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with- kernel-3-19-0-29 and at http://askubuntu.com/questions/673767/frequent-freezes ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrea 3174 F pulseaudio /dev/snd/pcmC0D0p: andrea 3174 F...m pulseaudio /dev/snd/controlC0: andrea 3174 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 30 12:45:03 2015 HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68 InstallationDate: Installed on 2010-04-15 (1993 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IwConfig: eth2 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd
The above working patch has been merged in linux-4.1.y branch of linux- stable repository as can been seen here: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/log/?qt=grep&q=mmc%3A+core%3A+Enable+runtime+PM+management+of+host+devices&h=linux-4.1.y Since Ubuntu 15.10 comes with Kernel version 4.2, I guess using Ubuntu 15.10 would fix the issue. I would wait for 14.04.4 to come out in Feb 2016 with updated kernel as depicted here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2BAC8-Support.A14.04.x_Ubuntu_Kernel_Support And then upgrade to Ubuntu 16.04 LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488426 Title: High CPU usage of kworker/ksoftirqd Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: kworker consuming 71.5% cpu resource ksoftirqd consuming 28.9% cpu resource It leads to power consumption issue and sometimes leads to BT does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1488426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522108] kili (amd64) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/4.2.0-21.25/kili__4.2.0-21.25__2015-12-08_12-53-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522108 Title: linux: 4.2.0-21.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Confirmed Bug description: This bug is for tracking the 4.2.0-21.25 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 02. December 2015 17:43 UTC kernel-stable-Prepare-package-end:Thursday, 03. December 2015 11:34 UTC kernel-stable-Promote-to-proposed-start:Thursday, 03. December 2015 11:34 UTC kernel-stable-Promote-to-proposed-end:Thursday, 03. December 2015 16:01 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 03. December 2015 17:01 UTC kernel-stable-Verification-testing-start:Thursday, 03. December 2015 17:01 UTC kernel-stable-Certification-testing-start:Thursday, 03. December 2015 17:01 UTC kernel-stable-Security-signoff-start:Thursday, 03. December 2015 17:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 03. December 2015 17:01 UTC kernel-stable-Security-signoff-end:Friday, 04. December 2015 08:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1522108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523586] Re: [PPA] 4.4 regression: kernel panic on reboot
Is this a regression with the 4.4 kernel? Do you happen to know if the panic occurred with prior kernels as well? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-key xenial ** Also affects: linux (Ubuntu Xenial) Importance: High Status: 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/1523586 Title: [PPA] 4.4 regression: kernel panic on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: While testing the unstable kernel PPA with linux-image-4.4.0-0-generic on ppc64el, autopkgtests often fail with this kernel crash on boot: ubuntu@juju-prod-ues-proposed-migration-machine-12:~⟫ nova console-log adt-xenial-ppc64el-systemd-20151207-161711 SLOF[0m[?25l ** [1mQEMU Starting [0m Build Date = Oct 9 2015 00:25:21 FW Version = buildd@ release 20140630 Press "s" to enter Open Firmware. [0m[?25hCC0100C0120C0140C0200C0201C0220C0240C0260C0270C02E0C0300C0320C0340C0360C0370C0380C0371C0372C0373C0374C0390C03F0C0400C0480C04C0C04D0C0500Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/vty@30001000 Populating /vdevice/nvram@7100 C0580C05A0Populating /pci@8002000 Adapters on 08002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 106b 003fserial bus [ usb-ohci ] 00 1800 (D) : 1af4 1001virtio [ block ] 00 2000 (D) : 1af4 1002unknown-legacy-device* C0600C0640C0690C06A0C06A8C06B0C06B8C06C0C06E0C0700C0800C0880No NVRAM common partition, re-initializing... C0890C08A0C08A8C08B0Scanning USB OHCI: initializing C08C0C08D0Using default console: /vdevice/vty@3000 C08E0C08E8C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... No DOS disk-label found. Successfully loaded [?25l[37m[40m[37m[40merror: no suitable video mode found. [?25l[37m[40m[2J[m[1;1H[2;22HGNU GRUB version 2.02~beta2-32ubuntu1 [37m[40m[4;2H++[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H++[37m[40m[18;2H[19;2H[37m[40m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [30m[47m[5;3H*Ubuntu [37m[40m[5;78H[37m[40m[37m[40m[6;3H Advanced options for Ubuntu [37m[40m[6;78H[37m[40m[37m[40m[7;3H [37m[40m[7;78H[37m[40m[37m[40m[8;3H [37m[40m[8;78H[37m[40m[37m[40m[9;3H [37m[40m[9;78H[37m[40m[37m[40m[10;3H [37m[40m[10;78H[37m[40m[37m[40m[11;3H [37m[40m[11;78H[37m[40m[37m[40m[12;3H [37m[40m[12;78H[37m[40m[37m[40m[13;3H [37m[40m[13;78H[37m[40m[37m[40m[14;3H [37m[40m[14;78H[37m[40m[37m[40m[15;3H [37m[40m[15;78H[37m[40m[37m[40m[16;3H [37m[40m[16;78H[37m[40m[16;80H [5;78H[22;1H The highlighted entry will be executed automatically in 10s.[5;78H[22;1H The highlighted entry will be executed automatically in 9s. [5;78H[22;1H The highlighted entry will be executed automatically in 8s. [5;78H[22;1H The highlighted entry will be executed automatically in 7s. [5;78H[22;1H The highlighted entry will be executed automatically in 6s. [5;78H[22;1H The hi
[Kernel-packages] [Bug 1523586] Re: [PPA] 4.4 regression: kernel panic on reboot
Is this regression between the 4.3 and 4.4 kernels? Do you have a way to install test kernels to test this? If so, I can perform a kernel bisect to identify the exact commit that caused this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1523586 Title: [PPA] 4.4 regression: kernel panic on reboot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: While testing the unstable kernel PPA with linux-image-4.4.0-0-generic on ppc64el, autopkgtests often fail with this kernel crash on boot: ubuntu@juju-prod-ues-proposed-migration-machine-12:~⟫ nova console-log adt-xenial-ppc64el-systemd-20151207-161711 SLOF[0m[?25l ** [1mQEMU Starting [0m Build Date = Oct 9 2015 00:25:21 FW Version = buildd@ release 20140630 Press "s" to enter Open Firmware. [0m[?25hCC0100C0120C0140C0200C0201C0220C0240C0260C0270C02E0C0300C0320C0340C0360C0370C0380C0371C0372C0373C0374C0390C03F0C0400C0480C04C0C04D0C0500Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/vty@30001000 Populating /vdevice/nvram@7100 C0580C05A0Populating /pci@8002000 Adapters on 08002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 106b 003fserial bus [ usb-ohci ] 00 1800 (D) : 1af4 1001virtio [ block ] 00 2000 (D) : 1af4 1002unknown-legacy-device* C0600C0640C0690C06A0C06A8C06B0C06B8C06C0C06E0C0700C0800C0880No NVRAM common partition, re-initializing... C0890C08A0C08A8C08B0Scanning USB OHCI: initializing C08C0C08D0Using default console: /vdevice/vty@3000 C08E0C08E8C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... No DOS disk-label found. Successfully loaded [?25l[37m[40m[37m[40merror: no suitable video mode found. [?25l[37m[40m[2J[m[1;1H[2;22HGNU GRUB version 2.02~beta2-32ubuntu1 [37m[40m[4;2H++[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H++[37m[40m[18;2H[19;2H[37m[40m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [30m[47m[5;3H*Ubuntu [37m[40m[5;78H[37m[40m[37m[40m[6;3H Advanced options for Ubuntu [37m[40m[6;78H[37m[40m[37m[40m[7;3H [37m[40m[7;78H[37m[40m[37m[40m[8;3H [37m[40m[8;78H[37m[40m[37m[40m[9;3H [37m[40m[9;78H[37m[40m[37m[40m[10;3H [37m[40m[10;78H[37m[40m[37m[40m[11;3H [37m[40m[11;78H[37m[40m[37m[40m[12;3H [37m[40m[12;78H[37m[40m[37m[40m[13;3H [37m[40m[13;78H[37m[40m[37m[40m[14;3H [37m[40m[14;78H[37m[40m[37m[40m[15;3H [37m[40m[15;78H[37m[40m[37m[40m[16;3H [37m[40m[16;78H[37m[40m[16;80H [5;78H[22;1H The highlighted entry will be executed automatically in 10s.[5;78H[22;1H The highlighted entry will be executed automatically in 9s. [5;78H[22;1H The highlighted entry will be executed automatically in 8s. [5;78H[22;1H The highlighted entry will be executed automatically in 7s. [5;78H[22;1H The highlighted entry will be executed automatically in 6s. [5;78H[22;1H The highlighted entry will be executed automatically in 5s. [5;78H[22;1H The highlighted en
[Kernel-packages] [Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest (14.04 regression)
*** This bug is a duplicate of bug 1346917 *** https://bugs.launchpad.net/bugs/1346917 Same problem I using kernel 3.16.0-55-generic, Ubuntu 14.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308341 Title: Multiple CPUs causes blue screen on Windows guest (14.04 regression) Status in QEMU: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Configuring a Windows 7 guest using more than one CPU cases the guest to fail. This happens after a few hours after guest boot. This is the error on the blue screen: "A clock interrupt was not received on a secondary processor within the allocated time interval" After resetting, the guest will never boot and a new bluescreen with the error "STOP: 0x005c" appears. Shutting down the guest completely and restarting it will allow it to boot and run for a few hours again. The guest was created using virt-manager. The error happens with or without virtio devices and with both 32-bit and 64-bit Windows 7 guests. I am using Ubuntu 14.04 release candidate. qemu-kvm version 2.0.0~rc1+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1308341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
We'll test the kernel in -proposed right away. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)
** Tags removed: verification-needed-trusty verification-needed-vivid ** Tags added: verification-done-preciseverification-done-vivid ** Tags removed: verification-done-preciseverification-done-vivid verification-needed-precise ** Tags added: verification-done-precise verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504778 Title: Lenovo G50-80 - Inverted Internal microphone (phase inversion) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Wily: Fix Released Bug description: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
We'll test the kernel in -proposed right away. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosof
[Kernel-packages] [Bug 1519106] Re: Unprivileged lxc container fails to start due to error mounting proc
Works as expected in 3.19.0-41.46. ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1519106 Title: Unprivileged lxc container fails to start due to error mounting proc Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: == SRU Justification == Impact: Unprivileged lxc containers fail to start whenever a filesystem is mounted on /proc/fs/nfsd. Fix: Cherry pick upstream commit d443b9fd56e85c0e58d10b75cf5eb38e0b2c4c02. Regression Potential: This commit modifies proc_register so that callers must set the proc_fops and/or proc_iops before calling rather that proc_register assigning them based on the type of inode passed. All call sites in 3.19 match exactly with those upstream at the time the patch was merged, except for proc_create_mount_point which is the call site causing this issue. Which is to say that there is no functional change for any proc inodes except for the ones which can cause this problem, therefore there should be little potential for regression. --- Unprivileged lxc containers fail to start in some instances under vivid: lxc-start 1448306932.775 ERRORlxc_utils - utils.c:safe_mount:1686 - Operation not permitted - Failed to mount proc onto /usr/lib/x86_64-linux-gnu/lxc/proc lxc-start 1448306932.775 ERRORlxc_conf - conf.c:lxc_mount_auto_mounts:828 - Operation not permitted - error mounting proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14 The failure is caused by the backport of 7236c85e1be51a9e25ba0f6e087a66ca89605a49 "mnt: Update fs_fully_visible to test for permanently empty directories." The backport itself is correct but some of its assumptions are not met to do a change which happened after 3.19. This causes /proc/fs/nfsd to fail the "directory is permanently empty" test, and when the nfsd fs another filesystem is mounted on that directory it causes the mount of proc in the container to fail. The fix is to bakcport d443b9fd56e85c0e58d10b75cf5eb38e0b2c4c02 "gut proc_register() a bit" as well. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38 ProcVersionSignature: User Name 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 23 21:22 seq crw-rw 1 root audio 116, 33 Nov 23 21:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Nov 23 21:24:16 2015 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic root=UUID=63d8816d-53d7-4318-b873-2cfe367b957a ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.19.0-33-generic N/A linux-backports-modules-3.19.0-33-generic N/A linux-firmware 1.143.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-trusty dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1514785] Re: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1514785 Title: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table) Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Kernel breaks PBR routing on several versions. Problem occurs on server and desktop. Example using linux-image-3.13.0-70 lsb_release: Ubutu 14.04.3 LTS Release 14.04 Expected: To have the normal rule table when using 'ip rule show' 0: from all lookup local 32766: from all lookup main 32767: from all lookup default Instead: The 'ip rule show' command is messed up showing lots of repeated rules for local/main/default (did not count them - simply too much) A sec prob in my case as it is making policy based routing useless if you need to grep whether your rule exists already. Workaraound, go back to/remain on either of these series: 3.13.0-68 3.16.0.51 3.19.0-33 Confirmed working after the fix (see below messages) 3.13.0-71.114 3.16.0-55.74 3.19.0-39.44 PBR NOT working on: 3.13.0-69 3.13.0-70 3.16.0-52 3.16.0-53 3.19.0-37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
We'll test the kernel in -proposed right away. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1508593
Title:
[Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Status in linux package in Ubuntu:
Triaged
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:
Fix Committed
Bug description:
A sporadic hang with consequent crash is observed when booting Hyper-V
Gen1 guests...
Sauce request for upstream submission:
https://lkml.org/lkml/2015/10/15/673
From Vitaly Kuznetsov <>
Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Date Thu, 15 Oct 2015 19:42:23 +0200
A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
guests:
Call Trace:
[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...
[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
The issue is easily reproducible with a simple instrumentation: if
mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
IRQ0. The issue seems to be caused by the fact that we don't disable
interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
happens. Decorate manipulations with legacy IRQs with local_irq_save()/
local_irq_restore().
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Jiang Liu
Cc: Yinghai Lu
Cc: K. Y. Srinivasan
Signed-off-by: Vitaly Kuznetsov
---
It may make sense to have interrupts disabled for non-legacy IRQs as well
but I'm unaware of any bugs with them at this moment.
---
arch/x86/kernel/apic/io_apic.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
index 5c60bb1..9aac777 100644
--- a/arch/x86/kernel/apic/io_apic.c
+++ b/arch/x86/kernel/apic/io_apic.c
@@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
+ unsigned long flags = 0;
if (!info || nr_irqs > 1)
return -EINVAL;
@@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
+
+ if (virq < nr_legacy_irqs())
+ local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
- if (virq < nr_legacy_irqs())
+ if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
+ local_irq_restore(flags);
+ }
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d
Mode:%i Active:%i Dest:%d)\n",
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508593/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501260] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000
Always occurs randomly when I click in some web link but not related with website visited. Occurs about one time at day. I only use Google Chrome as browser. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501260 Title: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x Status in linux package in Ubuntu: Confirmed Bug description: While surfing, I clicked on something,, X died, I was thrown back to a console and finally was able to log back in. dmesg is cluttered with: [79849.958943] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x) [79849.958944] [ cut here ] [79849.958962] WARNING: CPU: 0 PID: 14689 at /build/linux-1dujk3/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() [79849.958963] pipe state doesn't match! [79849.958981] Modules linked in: bnep bluetooth binfmt_misc nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_realtek input_leds snd_hda_codec_generic kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul snd_seq_midi snd_seq_midi_event snd_rawmidi crc32_pclmul ghash_clmulni_intel snd_seq snd_seq_device snd_timer mei_me aesni_intel snd mei aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd soundcore serio_raw 8250_fintek fujitsu_laptop lpc_ich tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid i915 psmouse ahci libahci i2c_algo_bit drm_kms_helper e1000e drm ptp pps_core video [79849.958983] CPU: 0 PID: 14689 Comm: Xorg Tainted: GW 4.2.0-11-generic #13-Ubuntu [79849.958983] Hardware name: FUJITSU ESPRIMO E920/D3222-A1, BIOS V4.6.5.4 R1.34.0 for D3222-A1x 01/08/2015 [79849.958985] c0232ab0 88030edef538 817b0cc5 [79849.958986] 88030edef588 88030edef578 81076536 88030edef5a8 [79849.958986] 88030edef610 88030a600800 0001 88030a600b50 [79849.958987] Call Trace: [79849.958991] [] dump_stack+0x45/0x57 [79849.958994] [] warn_slowpath_common+0x86/0xc0 [79849.958995] [] warn_slowpath_fmt+0x46/0x50 [79849.959008] [] ? intel_pipe_config_compare+0xa67/0xc60 [i915] [79849.959015] [] check_crtc_state+0x2c5/0x440 [i915] [79849.959024] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [79849.959032] [] intel_crtc_set_config+0x4c7/0x580 [i915] [79849.959042] [] drm_mode_set_config_internal+0x66/0x100 [drm] [79849.959045] [] restore_fbdev_mode+0xc2/0xf0 [drm_kms_helper] [79849.959048] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper] [79849.959050] [] drm_fb_helper_set_par+0x22/0x40 [drm_kms_helper] [79849.959060] [] intel_fbdev_set_par+0x1a/0x60 [i915] [79849.959062] [] ? ttwu_do_activate.constprop.89+0x5d/0x70 [79849.959064] [] fb_set_var+0x238/0x460 [79849.959066] [] ? do_sys_poll+0x127/0x5a0 [79849.959068] [] fbcon_blank+0x2e9/0x330 [79849.959070] [] ? check_preempt_wakeup+0x193/0x220 [79849.959071] [] do_unblank_screen+0xd3/0x1a0 [79849.959073] [] vt_ioctl+0x4fb/0x12c0 [79849.959074] [] ? default_wake_function+0x12/0x20 [79849.959076] [] ? autoremove_wake_function+0x16/0x40 [79849.959078] [] tty_ioctl+0x3cc/0xbb0 [79849.959079] [] ? __wake_up+0x48/0x60 [79849.959080] [] ? wake_nocb_leader+0x4d/0x50 [79849.959081] [] ? __call_rcu_nocb_enqueue+0xcd/0xd0 [79849.959083] [] do_vfs_ioctl+0x285/0x470 [79849.959084] [] ? mntput+0x24/0x40 [79849.959085] [] ? __fput+0x190/0x220 [79849.959086] [] SyS_ioctl+0x79/0x90 [79849.959088] [] entry_SYSCALL_64_fastpath+0x16/0x75 [79849.959089] ---[ end trace c15f693470bdbc48 ]--- [79849.959131] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x) [79849.959131] [ cut here ] 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.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hildeb25581 F pulseaudio /dev/snd/controlC1: hildeb25581 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 30 12:04:59 2015 HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3 InstallationDate: Installed on 2014-06-19 (467 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: FUJITSU ESPRIMO E920 ProcFB: 0
[Kernel-packages] [Bug 1522766] Re: cryptsetup hangs after kernel upgrade to 3.13.0-72.115
Running 3.13.0-73-generic #116-Ubuntu and am able to unlock the encrypted drive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522766 Title: cryptsetup hangs after kernel upgrade to 3.13.0-72.115 Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: After upgrading to the proposed kernel for Trusty (3.13.0-72.115) I cannot unlock a luks formatted usb drive. The cryptsetup process seems to hang with the following stack: [] __synchronize_srcu+0xfe/0x180 [] synchronize_srcu+0x1d/0x20 [] __dm_destroy+0x117/0x290 [] dm_destroy+0x13/0x20 [] dev_remove+0xde/0x120 [] ctl_ioctl+0x255/0x500 [] dm_ctl_ioctl+0x13/0x20 [] do_vfs_ioctl+0x2e0/0x4c0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522766] Re: cryptsetup hangs after kernel upgrade to 3.13.0-72.115
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522766 Title: cryptsetup hangs after kernel upgrade to 3.13.0-72.115 Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: After upgrading to the proposed kernel for Trusty (3.13.0-72.115) I cannot unlock a luks formatted usb drive. The cryptsetup process seems to hang with the following stack: [] __synchronize_srcu+0xfe/0x180 [] synchronize_srcu+0x1d/0x20 [] __dm_destroy+0x117/0x290 [] dm_destroy+0x13/0x20 [] dev_remove+0xde/0x120 [] ctl_ioctl+0x255/0x500 [] dm_ctl_ioctl+0x13/0x20 [] do_vfs_ioctl+0x2e0/0x4c0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518483] Re: problem with PIE binaries and kernels <= 3.19
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518483 Title: problem with PIE binaries and kernels <= 3.19 Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: When bash is built as a Position Independent Executable (PIE), it very sporadically crashes due to some issue with memory layout in kernels before 4.2. I'm currently testing enabling PIE by default in gcc on amd64 for xenial, and some of my builds (e.g. cpio) are failing in the buildds with the following message emitted: bash: xmalloc: .././locale.c:81: cannot allocate 2 bytes (0 bytes allocated) when the bash that is used is built as PIE. I have seen these failures on buildds where the host is running 3.13 and 3.19. I am also able to reproduce this locally on a machine running trusty with the stock trusty kernel. However, when I boot that same machine with the linux- lts-wily (4.2) kernel and retry the build with everything else exactly the same, the failure disappears. I discussed this a bit with Kees Cook, and he noted that some cleanups to the kernel's ASLR code happened in 4.1. Specifically, he noted: commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 Author: Michael Davidson fs/binfmt_elf.c: fix bug in loading of PIE binaries However, that landed in stable and has been picked up in our kernels as 668965be56ea0b2c45ed6bec84dc2088490ae6b1, landing in Ubuntu-3.13.0-56.93 and b51621abbcb4694b8d2842ce3a66006a60bba6e5 / Ubuntu-3.19.0-19.19. Kees also pointed out that he landed a series of patches from 204db6ed17743000691d930368a5abd6ea541c58 until Michael Davidson's patch (i.e. a87938b2e246b81b4fb713edb371a9fa3c5c3c86..204db6ed17743000691d930368a5abd6ea541c58 ), and in particular, there's: commit d1fd836dcf00d2028c700c7e44d2c23404062c90 Author: Kees Cook mm: split ET_DYN ASLR from mmap ASLR Other fixes that I see to fs/binfmt_elf.c and arch/x86/mm/mmap.c look like they either occurred only in 4.3 or have already been backported via the stable kernels. I should also point out that these cleanups may address some of the ASLR failed tests that occur on non-x86 architectures for pre 4.2 kernels. I am happy to test out kernels to try to address this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 20 13:58:40 2015 HibernationDevice: RESUME=UUID=dc63f523-507a-4f9d-aa30-a2e880199150 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc SG33 ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=d30e91cf-3c43-41a9-a72d-c07d1be1d53e ro loop.max_loop=64 rootflags=data=ordered nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to trusty on 2014-04-16 (583 days ago) WpaSupplicantLog: dmi.bios.date: 11/28/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: FG33 dmi.board.vendor: Shuttle Inc dmi.board.version: V10 dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: G5 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/28/2007:svnShuttleInc:pnSG33:pvrV10:rvnShuttleInc:rnFG33:rvrV10:cvnShuttleInc:ct3:cvrG5: dmi.product.name: SG33 dmi.product.version: V10 dmi.sys.vendor: S
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid ** Tags added: verification-needed-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/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498862] Re: autopkgtest: rebuild test should not run when testing ourselves
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498862 Title: autopkgtest: rebuild test should not run when testing ourselves Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: We have a rebuild test which is intended to confirm the kernel still builds when core-utils, gcc, ld etc change. It makes no sense for this test to run for the kernel itself as it takes a very long time to run and we have literally just built the kernel with those tools. Check for the trigger being something other than the kernel packages themselves before doing the rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi
[Kernel-packages] [Bug 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1508593
Title:
[Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Status in linux package in Ubuntu:
Triaged
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:
Fix Committed
Bug description:
A sporadic hang with consequent crash is observed when booting Hyper-V
Gen1 guests...
Sauce request for upstream submission:
https://lkml.org/lkml/2015/10/15/673
From Vitaly Kuznetsov <>
Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Date Thu, 15 Oct 2015 19:42:23 +0200
A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
guests:
Call Trace:
[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...
[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
The issue is easily reproducible with a simple instrumentation: if
mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
IRQ0. The issue seems to be caused by the fact that we don't disable
interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
happens. Decorate manipulations with legacy IRQs with local_irq_save()/
local_irq_restore().
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Jiang Liu
Cc: Yinghai Lu
Cc: K. Y. Srinivasan
Signed-off-by: Vitaly Kuznetsov
---
It may make sense to have interrupts disabled for non-legacy IRQs as well
but I'm unaware of any bugs with them at this moment.
---
arch/x86/kernel/apic/io_apic.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
index 5c60bb1..9aac777 100644
--- a/arch/x86/kernel/apic/io_apic.c
+++ b/arch/x86/kernel/apic/io_apic.c
@@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
+ unsigned long flags = 0;
if (!info || nr_irqs > 1)
return -EINVAL;
@@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
+
+ if (virq < nr_legacy_irqs())
+ local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
- if (virq < nr_legacy_irqs())
+ if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
+ local_irq_restore(flags);
+ }
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d
Mode:%i Active:%i Dest:%d)\n",
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508593/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498862] Re: autopkgtest: rebuild test should not run when testing ourselves
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498862 Title: autopkgtest: rebuild test should not run when testing ourselves Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: We have a rebuild test which is intended to confirm the kernel still builds when core-utils, gcc, ld etc change. It makes no sense for this test to run for the kernel itself as it takes a very long time to run and we have literally just built the kernel with those tools. Check for the trigger being something other than the kernel packages themselves before doing the rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504778 Title: Lenovo G50-80 - Inverted Internal microphone (phase inversion) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Wily: Fix Released Bug description: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-trusty
** Tags added: verification-needed-vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- precise' to 'verification-done-precise'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-precise ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504778 Title: Lenovo G50-80 - Inverted Internal microphone (phase inversion) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Wily: Fix Released Bug description: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1504778 Title: Lenovo G50-80 - Inverted Internal microphone (phase inversion) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Wily: Fix Released Bug description: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1433290] Re: xgene-enet: doesn't work at 100Mbit
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1433290 Title: xgene-enet: doesn't work at 100Mbit Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Fix Committed Bug description: [Impact] The onboard NICs on APM Mustang boards don't work when connected to a 100MBit switch. [Test Case] 1) Connect onboard NIC of a Mustang to a 100Mbit switch. I reproduced with both a Linksys WRT54GL and an old unmanaged Netgear switch. 2) Try to use it (e.g. dhclient) [Regression Risk] The fix is restricted to the xgene_enet driver, which limits the regression exposure to APM X-Gene systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515503] Re: Need support for some buggy Synaptics RMI4 device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid ** Tags added: verification-needed-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/1515503 Title: Need support for some buggy Synaptics RMI4 device Status in HWE Next: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: [Impact] Some RMI4 touchpad doesn't work properly even the probing returns no error. Further investigation shows the interrupt doesn't increase at all. There's already a public bug and the patch is already upstreamed: https://bugs.freedesktop.org/show_bug.cgi?id=91102 [Fix] There's a fix contains in v4.3-rc1 and has already been tested: commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba Author: Andrew Duggan AuthorDate: Thu Jul 16 17:14:00 2015 -0700 Commit: Jiri Kosina CommitDate: Fri Jul 17 11:29:53 2015 +0200 HID: rmi: Set F01 interrupt enable register when not set Note: So far the platform we encounter with this issue use GPIO interrupt, so it also needs 3.19.0-32 or Wily kernel to work too. [Test] 1. Boot with v4.3-rc1 -> pass 2. Boot with patched Vivid kernel -> pass 3. Boot with patched Wily kernel -> pass To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1515503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510405] Re: Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1510405 Title: Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2 Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Wily: In Progress Status in linux-firmware source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-firmware source package in Xenial: Invalid Bug description: == SRU Justification == Impact: CONFIG_DRM_AMDGPU_CIK enables experimental support for some AMD hardware in the amdgpu driver. It's not considered stable yet and is not working properly with some hardware. Fix: Disable this option. The hardware which is no longer supported by amdgpu is all supported by the radeon driver. Regression Potential: It's possible that some regressions might be seen by users with affected hardware, but generally using radeon for this hardware should be more stable. --- Version 1.149 of the package does not have /lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM module. After booting my monitor is blank. For other AMD chipsets *_sdma1.bin is needed as well: drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, sizeof(fw_name), "radeon/%s_sdma1.bin", chip_name); Similar to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source /linux-firmware/+bug/1218691 Best regards, Timothy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515541] Re: debian/tests/control specified unconditional gcc-multilib which is not available on ppc64el
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1515541 Title: debian/tests/control specified unconditional gcc-multilib which is not available on ppc64el Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: We have an unconditional test dependency on gcc-multilib which is not available on ppc64el as that is not multi personality architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513847] Re: WWAN modules is recognized as an ethernet device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1513847 Title: WWAN modules is recognized as an ethernet device Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Committed Bug description: Bus 001 Device 005: ID 413c:81ba Dell Computer Corp. This device should be a WWAN module, but it's recognized as an ethernet device instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513980] Re: Ubuntu 14.04.03 did not detect Link down on Houston CU network adapter ports when cable pulled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1513980 Title: Ubuntu 14.04.03 did not detect Link down on Houston CU network adapter ports when cable pulled Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Problem Description: I installed Houston CU (feature code 2CC1) PCIe2 10GbE SFP+ CU 4-port Converged Network Adapter in slot P1-C2 of tul117fp1 system. The system is configured as PowerNV and running Ubuntu 14.04.03 - I configured 2 copper ports of the adapter and running network stress on it for several hours. I then pulled cable and waited for sometime. - The OS did not detect the link down. Even though the TX/RX traffic stopped on the ports. - Kernel log and dmesg did not have any entry to indicate link down after cable pulled. 0007:00:00.0 PCI bridge: IBM Device 03dc 0007:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0007:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0007:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0007:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0007:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 0007:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) - ifconfig -a cmd still show link up eth43 Link encap:Ethernet HWaddr 00:90:fa:6e:e0:f2 inet addr:103.1.1.15 Bcast:103.1.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:7543074880 errors:1 dropped:9 overruns:0 frame:1 TX packets:5926170683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8997647070924 (8.9 TB) TX bytes:7177651764733 (7.1 TB) eth44 Link encap:Ethernet HWaddr 00:90:fa:6e:e0:f3 inet addr:103.1.2.15 Bcast:103.1.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:5926170613 errors:1 dropped:0 overruns:0 frame:1 TX packets:7543089239 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7488707854629 (7.4 TB) TX bytes:8619256135370 (8.6 TB) Paul, looking at the source code for the driver in Ubuntu 14.04.3 the driver doesn't log any messages after an update to the link status. The following commit upstream adds this functionality: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18824894dbec3eb2202fc92d52a0c8bd27c8a63f I'll create a test kernel with this patch applied and will attach it here so you can test this commit - I installed Ubuntu patched kernel - I setup and re-ran the test on Houston adapter. I verified that with the patch link Up/Down events now get logged properly when cable pulls. I verified the patch and it fixed the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1514971] Re: [SRU trusty] arm64 USB support not enabled for APM Mustang
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1514971 Title: [SRU trusty] arm64 USB support not enabled for APM Mustang Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: [Impact] Currently USB is not enabled for arm64 platforms. The patches will enable USB for arm64 and for APM's Mustang platform. [Test Case] Insert a USB device into an APM Mustang based platform. [Regression Risk] This patch set enables USB for all arm64 platforms, but they have all been accepted by upstream and have been tested on a couple Mustang platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515503] Re: Need support for some buggy Synaptics RMI4 device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1515503 Title: Need support for some buggy Synaptics RMI4 device Status in HWE Next: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: [Impact] Some RMI4 touchpad doesn't work properly even the probing returns no error. Further investigation shows the interrupt doesn't increase at all. There's already a public bug and the patch is already upstreamed: https://bugs.freedesktop.org/show_bug.cgi?id=91102 [Fix] There's a fix contains in v4.3-rc1 and has already been tested: commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba Author: Andrew Duggan AuthorDate: Thu Jul 16 17:14:00 2015 -0700 Commit: Jiri Kosina CommitDate: Fri Jul 17 11:29:53 2015 +0200 HID: rmi: Set F01 interrupt enable register when not set Note: So far the platform we encounter with this issue use GPIO interrupt, so it also needs 3.19.0-32 or Wily kernel to work too. [Test] 1. Boot with v4.3-rc1 -> pass 2. Boot with patched Vivid kernel -> pass 3. Boot with patched Wily kernel -> pass To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1515503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1516686] Re: linux: reduce stub delta to simplify review and fix rebuild test
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1516686 Title: linux: reduce stub delta to simplify review and fix rebuild test Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: In Progress Bug description: We emit a lot of unnecessary delta to debian files, caused by ordering issues and lack of general clenliness. Backport these fixes from v/w/x to make all series consistant. Also fix rebuild test to not fire if triggered for the kernel which just built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515541] Re: debian/tests/control specified unconditional gcc-multilib which is not available on ppc64el
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1515541 Title: debian/tests/control specified unconditional gcc-multilib which is not available on ppc64el Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: We have an unconditional test dependency on gcc-multilib which is not available on ppc64el as that is not multi personality architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519106] Re: Unprivileged lxc container fails to start due to error mounting proc
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1519106 Title: Unprivileged lxc container fails to start due to error mounting proc Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: == SRU Justification == Impact: Unprivileged lxc containers fail to start whenever a filesystem is mounted on /proc/fs/nfsd. Fix: Cherry pick upstream commit d443b9fd56e85c0e58d10b75cf5eb38e0b2c4c02. Regression Potential: This commit modifies proc_register so that callers must set the proc_fops and/or proc_iops before calling rather that proc_register assigning them based on the type of inode passed. All call sites in 3.19 match exactly with those upstream at the time the patch was merged, except for proc_create_mount_point which is the call site causing this issue. Which is to say that there is no functional change for any proc inodes except for the ones which can cause this problem, therefore there should be little potential for regression. --- Unprivileged lxc containers fail to start in some instances under vivid: lxc-start 1448306932.775 ERRORlxc_utils - utils.c:safe_mount:1686 - Operation not permitted - Failed to mount proc onto /usr/lib/x86_64-linux-gnu/lxc/proc lxc-start 1448306932.775 ERRORlxc_conf - conf.c:lxc_mount_auto_mounts:828 - Operation not permitted - error mounting proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14 The failure is caused by the backport of 7236c85e1be51a9e25ba0f6e087a66ca89605a49 "mnt: Update fs_fully_visible to test for permanently empty directories." The backport itself is correct but some of its assumptions are not met to do a change which happened after 3.19. This causes /proc/fs/nfsd to fail the "directory is permanently empty" test, and when the nfsd fs another filesystem is mounted on that directory it causes the mount of proc in the container to fail. The fix is to bakcport d443b9fd56e85c0e58d10b75cf5eb38e0b2c4c02 "gut proc_register() a bit" as well. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38 ProcVersionSignature: User Name 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 23 21:22 seq crw-rw 1 root audio 116, 33 Nov 23 21:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Nov 23 21:24:16 2015 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic root=UUID=63d8816d-53d7-4318-b873-2cfe367b957a ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.19.0-33-generic N/A linux-backports-modules-3.19.0-33-generic N/A linux-firmware 1.143.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-trusty dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.n
[Kernel-packages] [Bug 1516686] Re: linux: reduce stub delta to simplify review and fix rebuild test
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1516686 Title: linux: reduce stub delta to simplify review and fix rebuild test Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: In Progress Bug description: We emit a lot of unnecessary delta to debian files, caused by ordering issues and lack of general clenliness. Backport these fixes from v/w/x to make all series consistant. Also fix rebuild test to not fire if triggered for the kernel which just built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513583] Re: Add CAPI flash driver (cxlflash) patches to 15.10 SRU stream
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1513583 Title: Add CAPI flash driver (cxlflash) patches to 15.10 SRU stream Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Released Bug description: CAPI flash driver fixes. Contact Information = Matthew Ochs mro...@linux.vnet.ibm.com ---uname output--- n/a Machine Type = p8 ---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 Matthew Ochs mro...@linux.vnet.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #2 - Matthew R. Ochs - 2015-11-04 16:14:17 == == Comment: #3 - Matthew R. Ochs - 2015-11-04 16:15:19 == == Comment: #4 - Matthew R. Ochs - 2015-11-04 16:17:40 == Patch 1 sends a link reset for port1 following a login timeout error. This same fix was delivered previously for port0. Patch 2 provides feedback to applications so that they may know when it is acceptable to perform an I/O retry for a virtual LUN. == Comment: #5 - Matthew R. Ochs - 2015-11-04 16:25:54 == These patches are not yet upstreamed but will be as part of the 4.4 'rc' phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1522766] Re: cryptsetup hangs after kernel upgrade to 3.13.0-72.115
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522766 Title: cryptsetup hangs after kernel upgrade to 3.13.0-72.115 Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: After upgrading to the proposed kernel for Trusty (3.13.0-72.115) I cannot unlock a luks formatted usb drive. The cryptsetup process seems to hang with the following stack: [] __synchronize_srcu+0xfe/0x180 [] synchronize_srcu+0x1d/0x20 [] __dm_destroy+0x117/0x290 [] dm_destroy+0x13/0x20 [] dev_remove+0xde/0x120 [] ctl_ioctl+0x255/0x500 [] dm_ctl_ioctl+0x13/0x20 [] do_vfs_ioctl+0x2e0/0x4c0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
