[Kernel-packages] [Bug 1697137] 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/1697137 Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: I need to know how to fix it regarding that I've already tried many things! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noha 2075 F pulseaudio Date: Sat Jun 10 06:03:21 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=2d9345b1-4781-4e82-a5f9-62ab50983e34 InstallationDate: Installed on 2015-02-19 (842 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. X201EP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic.efi.signed root=UUID=7606bba8-bed9-4f62-9fb4-a9696ff27d5a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-17 (297 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP 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.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP 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/1697137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697137] [NEW] package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: I need to know how to fix it regarding that I've already tried many things! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noha 2075 F pulseaudio Date: Sat Jun 10 06:03:21 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=2d9345b1-4781-4e82-a5f9-62ab50983e34 InstallationDate: Installed on 2015-02-19 (842 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. X201EP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic.efi.signed root=UUID=7606bba8-bed9-4f62-9fb4-a9696ff27d5a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-17 (297 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP 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.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697137 Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: I need to know how to fix it regarding that I've already tried many things! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noha 2075 F pulseaudio Date: Sat Jun 10 06:03:21 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=2d9345b1-4781-4e82-a5f9-62ab50983e34 InstallationDate: Installed on 2015-02-19 (842 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. X201EP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic.efi.signed root=UUID=7606bba8-bed9-4f62-9fb4-a9696ff27d5a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-17 (297 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP 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.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP 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/1697137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681150] Re: Has anyone noticed zesty linux-image-generic_4.10.0.19.21_amd64 has no initrd.img AND can't see Root=UUID= AND read any partitions?
[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/1681150 Title: Has anyone noticed zesty linux-image-generic_4.10.0.19.21_amd64 has no initrd.img AND can't see Root=UUID= AND read any partitions? Status in linux package in Ubuntu: Expired Bug description: I'm running Zesty 17.04 linux-image.4.10.0.13 I can log in but compiz has to be --replaced. Then I update-grub. kernel .14 downloads yesterday and .19 today. Both don't have a initrd.img-4.10.0-1[49]-generic. Most would stop here. In grub.cfg I tried adding a initrd /initrd.img with is linked to /boot/initrd.img-4.10.0-13-generic to both linux vmlinuz-4.10.0-14-generic and linux vmlinuz-4.10.0-19-generic What does it mean when it boots until a kernel panic "can't find root." This also happens if there is no initrd line (as intended.) ubuntu-bug linux reports "not a real package. please remove third party packs" $cat /proc/version_signature |tee version.log Ubuntu 4.10.0-13.15-generic 4.10.1 #install new crash kernels: zesty echo deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates \ main restricted universe multiverse > /etc/apt/sources.list.d/ddebs.list $ sudo apt-get install linux-image-$(uname -r)-dbgsym E: Unable to locate package linux-image-4.10.0-13-generic-dbgsym E: Unable to locate package linux-image-4.10.0-14-generic-dbgsym E: Unable to locate package linux-image-4.10.0-19-generic-dbgsym oh well. I'm learning so much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681434] Re: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
[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/1681434 Title: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Expired Bug description: Happens on boot up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2017 F pulseaudio /dev/snd/controlC0: tim2017 F pulseaudio Date: Fri Apr 7 21:16:40 2017 DpkgHistoryLog: Start-Date: 2017-04-07 21:16:11 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), linux-headers-4.4.0-72:amd64 (4.4.0-72.93, automatic), linux-image-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), linux-image-extra-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), lightdm:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1), liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1) ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=13756ac8-2730-4c73-9a30-4ffbf49eccb8 InstallationDate: Installed on 2016-10-08 (183 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: tun0 no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=0174b67e-8087-4a08-a594-a5166cecd313 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0908 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LK 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.:bvr0908:bd11/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694800] Re: Frequent Core Lock
FYI I have since reinstalled with 17.04 and have the same crashes. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697132 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694800 Title: Frequent Core Lock Status in linux package in Ubuntu: Incomplete Bug description: I get these frequent CPU core locks. I got this on current CPU AMD Ryzen 1700 as well as AMD FX-8350. All hardware has been switched out except HD. Same issue. This seems to be a Kernal issue as far as i can tell. I started getting this issue in Ubuntu 14.04 with and without proprietary drivers. May 30 21:08:39 TheSource kernel: [ 5707.856597] NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [kworker/8:0:11225] May 30 21:08:39 TheSource kernel: [ 5707.859040] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables xt_multiport iptable_filter ip_tables x_tables des_generic md4 nls_utf8 cifs fscache bi$ May 30 21:08:39 TheSource kernel: [ 5707.859105] CPU: 8 PID: 11225 Comm: kworker/8:0 Tainted: PW O L 4.4.0-78-generic #99-Ubuntu May 30 21:08:39 TheSource kernel: [ 5707.859108] Hardware name: Micro-Star International Co., Ltd MS-7A32/X370 GAMING PRO CARBON (MS-7A32), BIOS 1.50 04/27/2017 May 30 21:08:39 TheSource kernel: [ 5707.859115] Workqueue: events once_deferred May 30 21:08:39 TheSource kernel: [ 5707.859118] task: 8803d001c600 ti: 8803323e8000 task.ti: 8803323e8000 May 30 21:08:39 TheSource kernel: [ 5707.859120] RIP: 0010:[] [] smp_call_function_many+0x1f8/0x260 May 30 21:08:39 TheSource kernel: [ 5707.859127] RSP: 0018:8803323ebc90 EFLAGS: 0202 May 30 21:08:39 TheSource kernel: [ 5707.859129] RAX: 0003 RBX: 0200 RCX: 0001 May 30 21:08:39 TheSource kernel: [ 5707.859131] RDX: 88041ec5b160 RSI: 0200 RDI: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859132] RBP: 8803323ebcc8 R08: R09: feff May 30 21:08:39 TheSource kernel: [ 5707.859134] R10: 0008 R11: 88041ee17d48 R12: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859136] R13: 88041ee17d40 R14: 81035d30 R15: May 30 21:08:39 TheSource kernel: [ 5707.859139] FS: 7f2b0f110700() GS:88041ee0() knlGS:0c4a1880 May 30 21:08:39 TheSource kernel: [ 5707.859141] CS: 0010 DS: ES: CR0: 80050033 May 30 21:08:39 TheSource kernel: [ 5707.859142] CR2: 55d6977db0a0 CR3: 0003f7fae000 CR4: 003406e0 May 30 21:08:39 TheSource kernel: [ 5707.859145] Stack: May 30 21:08:39 TheSource kernel: [ 5707.859146] 00017d00 01ff88030001 81773cae 81035d30 May 30 21:08:39 TheSource kernel: [ 5707.859149] 81773caf 8803ece2e280 8803323ebcf0 May 30 21:08:39 TheSource kernel: [ 5707.859152] 81104aad 81773cae 0005 8803323ebd43 May 30 21:08:39 TheSource kernel: [ 5707.859154] Call Trace: May 30 21:08:39 TheSource kernel: [ 5707.859160] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859163] [] ? arch_unregister_cpu+0x30/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859166] [] ? ipqhashfn+0x2f/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859170] [] on_each_cpu+0x2d/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859172] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859175] [] text_poke_bp+0x6a/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859178] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859182] [] arch_jump_label_transform+0x9b/0x120 May 30 21:08:39 TheSource kernel: [ 5707.859187] [] __jump_label_update+0x76/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859190] [] jump_label_update+0x88/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859194] [] __static_key_slow_dec+0x41/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859197] [] static_key_slow_dec+0x22/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859200] [] once_deferred+0x1a/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859204] [] process_one_work+0x165/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859207] [] worker_thread+0x4b/0x4c0 May 30 21:08:39 TheSource kernel: [ 5707.859210] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859214] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859217] [] kthread+0xd8/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859220] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859225] [] ret_from_fork+0x3f/0x70 May 30 21:08:39 TheSource kernel: [ 5707.859227] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859229] Code: d2 e8 4d 92 30
[Kernel-packages] [Bug 1694800] Re: Frequent Core Lock
I have had this issue since i first built this machine and installed 14.04 when 14.04 was current version. I can't remember what update this occurred after it was a long time ago. I thought this was a hardware issue originally. I am happy to try upstream kernel however i can't get ZFS to run and is required for my workflow. If someone can provide an upstream kernel with ZFS support I would be happy to install it and give it a try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694800 Title: Frequent Core Lock Status in linux package in Ubuntu: Incomplete Bug description: I get these frequent CPU core locks. I got this on current CPU AMD Ryzen 1700 as well as AMD FX-8350. All hardware has been switched out except HD. Same issue. This seems to be a Kernal issue as far as i can tell. I started getting this issue in Ubuntu 14.04 with and without proprietary drivers. May 30 21:08:39 TheSource kernel: [ 5707.856597] NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [kworker/8:0:11225] May 30 21:08:39 TheSource kernel: [ 5707.859040] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables xt_multiport iptable_filter ip_tables x_tables des_generic md4 nls_utf8 cifs fscache bi$ May 30 21:08:39 TheSource kernel: [ 5707.859105] CPU: 8 PID: 11225 Comm: kworker/8:0 Tainted: PW O L 4.4.0-78-generic #99-Ubuntu May 30 21:08:39 TheSource kernel: [ 5707.859108] Hardware name: Micro-Star International Co., Ltd MS-7A32/X370 GAMING PRO CARBON (MS-7A32), BIOS 1.50 04/27/2017 May 30 21:08:39 TheSource kernel: [ 5707.859115] Workqueue: events once_deferred May 30 21:08:39 TheSource kernel: [ 5707.859118] task: 8803d001c600 ti: 8803323e8000 task.ti: 8803323e8000 May 30 21:08:39 TheSource kernel: [ 5707.859120] RIP: 0010:[] [] smp_call_function_many+0x1f8/0x260 May 30 21:08:39 TheSource kernel: [ 5707.859127] RSP: 0018:8803323ebc90 EFLAGS: 0202 May 30 21:08:39 TheSource kernel: [ 5707.859129] RAX: 0003 RBX: 0200 RCX: 0001 May 30 21:08:39 TheSource kernel: [ 5707.859131] RDX: 88041ec5b160 RSI: 0200 RDI: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859132] RBP: 8803323ebcc8 R08: R09: feff May 30 21:08:39 TheSource kernel: [ 5707.859134] R10: 0008 R11: 88041ee17d48 R12: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859136] R13: 88041ee17d40 R14: 81035d30 R15: May 30 21:08:39 TheSource kernel: [ 5707.859139] FS: 7f2b0f110700() GS:88041ee0() knlGS:0c4a1880 May 30 21:08:39 TheSource kernel: [ 5707.859141] CS: 0010 DS: ES: CR0: 80050033 May 30 21:08:39 TheSource kernel: [ 5707.859142] CR2: 55d6977db0a0 CR3: 0003f7fae000 CR4: 003406e0 May 30 21:08:39 TheSource kernel: [ 5707.859145] Stack: May 30 21:08:39 TheSource kernel: [ 5707.859146] 00017d00 01ff88030001 81773cae 81035d30 May 30 21:08:39 TheSource kernel: [ 5707.859149] 81773caf 8803ece2e280 8803323ebcf0 May 30 21:08:39 TheSource kernel: [ 5707.859152] 81104aad 81773cae 0005 8803323ebd43 May 30 21:08:39 TheSource kernel: [ 5707.859154] Call Trace: May 30 21:08:39 TheSource kernel: [ 5707.859160] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859163] [] ? arch_unregister_cpu+0x30/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859166] [] ? ipqhashfn+0x2f/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859170] [] on_each_cpu+0x2d/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859172] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859175] [] text_poke_bp+0x6a/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859178] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859182] [] arch_jump_label_transform+0x9b/0x120 May 30 21:08:39 TheSource kernel: [ 5707.859187] [] __jump_label_update+0x76/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859190] [] jump_label_update+0x88/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859194] [] __static_key_slow_dec+0x41/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859197] [] static_key_slow_dec+0x22/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859200] [] once_deferred+0x1a/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859204] [] process_one_work+0x165/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859207] [] worker_thread+0x4b/0x4c0 May 30 21:08:39 TheSource kernel: [ 5707.859210] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859214] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859217] [] kthread+0xd8/0xf0 May 30 21:08:39 TheSource ker
[Kernel-packages] [Bug 1697132] 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/1697132 Title: CPU Cores Stalls/Lock Status in linux package in Ubuntu: Confirmed Bug description: CPU Stalls or Locks up after a random period of time. Can not trace issue to high resources or heat. System will crash while sitting essentially idle. Sometimes system will crash after a few minutes some times it will take days. A large file transfer will usually force the crash though. I have been having similar issue since Ubuntu 14.04. I have upgrade to every version along the way to 17.04 with the same issue. I have replaced every piece of hardware except HDD. MB, Proc, power supply, memory, video card. With and without AMD micro code. This is a server so no GUI. I've tried upstream kernels but they don't support ZFS and I haven't had any luck shimming it in. Happy to try newer kernels if someone can provide one with ZFS support. Jun 9 18:54:57 TheSource kernel: [46465.931527] INFO: rcu_sched detected stalls on CPUs/tasks: Jun 9 18:54:57 TheSource kernel: [46465.931583]9-...: (12 GPs behind) idle=f03/1/0 softirq=261811/261811 fqs=6599 Jun 9 18:54:57 TheSource kernel: [46465.931624](detected by 0, t=15002 jiffies, g=380049, c=380048, q=118270) Jun 9 18:54:57 TheSource kernel: [46465.931665] Task dump for CPU 9: Jun 9 18:54:57 TheSource kernel: [46465.931666] swapper/9 R running task0 0 1 0x0008 Jun 9 18:54:57 TheSource kernel: [46465.931670] Call Trace: Jun 9 18:54:57 TheSource kernel: [46465.931677] ? cpuidle_enter_state+0x122/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931680] ? cpuidle_enter_state+0x110/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931683] ? cpuidle_enter+0x17/0x20 Jun 9 18:54:57 TheSource kernel: [46465.931685] ? call_cpuidle+0x23/0x40 Jun 9 18:54:57 TheSource kernel: [46465.931688] ? do_idle+0x189/0x200 Jun 9 18:54:57 TheSource kernel: [46465.931690] ? cpu_startup_entry+0x71/0x80 Jun 9 18:54:57 TheSource kernel: [46465.931693] ? start_secondary+0x154/0x190 Jun 9 18:54:57 TheSource kernel: [46465.931696] ? start_cpu+0x14/0x14 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.10.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Fri Jun 9 20:17:45 2017 InstallationDate: Installed on 2017-06-03 (6 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Micro-Star International Co., Ltd MS-7A32 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=bba67c63-3cd9-4475-bf3a-a0890087330d ro RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd04/27/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:
[Kernel-packages] [Bug 1697132] [NEW] CPU Cores Stalls/Lock
Public bug reported: CPU Stalls or Locks up after a random period of time. Can not trace issue to high resources or heat. System will crash while sitting essentially idle. Sometimes system will crash after a few minutes some times it will take days. A large file transfer will usually force the crash though. I have been having similar issue since Ubuntu 14.04. I have upgrade to every version along the way to 17.04 with the same issue. I have replaced every piece of hardware except HDD. MB, Proc, power supply, memory, video card. With and without AMD micro code. This is a server so no GUI. I've tried upstream kernels but they don't support ZFS and I haven't had any luck shimming it in. Happy to try newer kernels if someone can provide one with ZFS support. Jun 9 18:54:57 TheSource kernel: [46465.931527] INFO: rcu_sched detected stalls on CPUs/tasks: Jun 9 18:54:57 TheSource kernel: [46465.931583]9-...: (12 GPs behind) idle=f03/1/0 softirq=261811/261811 fqs=6599 Jun 9 18:54:57 TheSource kernel: [46465.931624](detected by 0, t=15002 jiffies, g=380049, c=380048, q=118270) Jun 9 18:54:57 TheSource kernel: [46465.931665] Task dump for CPU 9: Jun 9 18:54:57 TheSource kernel: [46465.931666] swapper/9 R running task0 0 1 0x0008 Jun 9 18:54:57 TheSource kernel: [46465.931670] Call Trace: Jun 9 18:54:57 TheSource kernel: [46465.931677] ? cpuidle_enter_state+0x122/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931680] ? cpuidle_enter_state+0x110/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931683] ? cpuidle_enter+0x17/0x20 Jun 9 18:54:57 TheSource kernel: [46465.931685] ? call_cpuidle+0x23/0x40 Jun 9 18:54:57 TheSource kernel: [46465.931688] ? do_idle+0x189/0x200 Jun 9 18:54:57 TheSource kernel: [46465.931690] ? cpu_startup_entry+0x71/0x80 Jun 9 18:54:57 TheSource kernel: [46465.931693] ? start_secondary+0x154/0x190 Jun 9 18:54:57 TheSource kernel: [46465.931696] ? start_cpu+0x14/0x14 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.10.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Fri Jun 9 20:17:45 2017 InstallationDate: Installed on 2017-06-03 (6 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Micro-Star International Co., Ltd MS-7A32 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=bba67c63-3cd9-4475-bf3a-a0890087330d ro RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd04/27/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697132 Title: CPU Cores Stalls/L
[Kernel-packages] [Bug 1696445] Attach multipath log file that has several failed paths with no redundancy.
Default Comment by Bridge ** Attachment added: "Attach multipath log file that has several failed paths with no redundancy." https://bugs.launchpad.net/bugs/1696445/+attachment/4893337/+files/multipath.log.05312017 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696445 Title: OpenPower: Some multipaths temporarily have only a single path Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Bug description: [Impact] * The SES driver causes a long delay in disk discovery when a large number of disks is present in the disk enclosure, which increases with the number of disks attached. * This delays the addition and visibility of the disk devices to userspace, which among other things causes multipath not to have multiple paths, actually, until the disk discovery eventually/finally finishes. * The fix significantly shortens the time taken by the SES driver to handle disk discovery, causing no extra delays, by removing a superfluous SCSI command sent to enclosure. [Test Case] * Load the module to access the enclosure and its disks; e.g., $ sudo modprobe mpt3sas * Notice the interval between the discovery of each disk; e.g., dmesg $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk * The interval should be in the same second or so range with the fix. $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Wed Jun 7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk [Wed Jun 7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk [Regression Potential] * The power status of the disks in the enclosure is no longer checked during probe time. However, the patch demonstrates that initial value was never used in any way. So, little regression potential. * Nonetheless, users of SES enclosures which verify the power status of disks in the enclosure might _theoretically_ see a problem, iff the fix has a problem (which has not been found yet). [Other Info] * None at this time. Problem Description: This week, I went ahead and scaled up my test configuration to max configuration 2x5U84_Enclosures,_MaxCfg_168HDDs. This time, it hit a different issue. The issue is that some multipaths only have a single path and no redundancy. Others have multiple paths and redundancy. Checkpoint #1: == - system reboot around 2pm (14:00) Checkpoint # 2: === - It took several minutes for first disk to be detected. root@smb1p1:~# multipath -ll|grep dm |wc -l 103 root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' | grep 'Attached SCSI disk' | tail [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk [Thu Jun 1 14:18:40 2017] sd 17:0:102:0: [sdct] Attached SCSI disk [Thu Jun 1 14:18:44 2017] sd 17:0:103:0: [sdcu] Attached SCSI disk [Thu Jun 1 14:18:54 2017] sd 17:0:105:0: [sdcv] Attached SCSI disk [Thu Jun 1 14:18:59 2017] sd 17:0:106:0: [sdcw] Attached SCSI disk [Thu Jun 1 14:19:04 2017] sd 17:0:107:0: [sdcx] Attached SCSI disk [Thu Jun 1 14:19:09 2017] sd 17:0:108:0: [sdcy] Attached SCSI disk [Thu Jun 1 14:19:14 2017] sd 17:0:109:0: [sdcz] Attached SCSI disk [Thu Jun 1 14:19:19 2017] sd 17:0:110:0: [sdda] Attached SCSI disk root@smb1p1:~# ... root@smb1p1:~# multipath -ll|grep dm |wc -l 142 root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' | grep 'Attached SCSI disk' | tail [Thu Jun 1 14:21:54 2017] sd 17:0:141:0: [sdee] Attached SCSI disk [Thu Jun 1 14:21:58 2017] sd 17:0:142:0: [sdef] Attached SCSI disk [Thu Jun 1 14:22:04 2017] sd 17:0:143:0: [sdeg] Attached SCSI disk [Thu Jun 1 14:22:08 2017] sd 17:0:144:0: [sdeh] Attached SCSI disk [Thu Jun 1 14:22:14 2017] sd 17:0:145:0: [sdei] Attached SCSI disk [Thu Jun 1 14:22:18 2017] sd 17:0:146:0: [sdej] Attached SCSI disk [Thu Jun 1 14:22:24 2017] sd 17:0:147:0: [sdek] Attached SCSI disk [Thu Jun 1 14:22:29 2017] sd 17:0:148:0: [sdel] Attached SCSI disk [Thu Jun 1 14:22:34 2017] sd 17:0:149:0: [sdem] Attached SCSI disk [Thu Jun 1 14:22:39 2017] sd 17:0:150:0: [sden] Attached SCSI disk root@smb1p1:~# ... - After 43 minutes, multipath -ll command shows some paths with only single path and no redundancy and some path with multiple paths and redundancy. root@smb1p1:~# date Thu Jun 1 14:43:00 CDT 2017 root@smb1p1:~# multipath -ll | grep -c 'sd[a-z]\+' 252 root@smb1p1:~# ... - After 47 minutes, multipath -ll command still
[Kernel-packages] [Bug 1697116] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1697116 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/1697116 Title: Power button does not work on Latitude 7480 Status in linux package in Ubuntu: Incomplete Bug description: When power button is pressed, a menu should pop up or the system should enter suspend; however, neither occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697116] [NEW] Power button does not work on Latitude 7480
Public bug reported: When power button is pressed, a menu should pop up or the system should enter suspend; however, neither occurs. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697116 Title: Power button does not work on Latitude 7480 Status in linux package in Ubuntu: Incomplete Bug description: When power button is pressed, a menu should pop up or the system should enter suspend; however, neither occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697022] Re: linux: 4.11.0-6.11 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-artful ** Description changed: This bug is for tracking the 4.11.0-6.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 -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697022 Title: linux: 4.11.0-6.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New 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: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-6.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 -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1697022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Also affects: update-notifier (Ubuntu Artful) Importance: Low Status: Confirmed ** Also affects: unattended-upgrades (Ubuntu Artful) Importance: Low Status: Confirmed ** Also affects: linux (Ubuntu Artful) Importance: Low Assignee: Adam Conrad (adconrad) 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Status in unattended-upgrades source package in Artful: Confirmed Status in update-notifier source package in Artful: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments
$ dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.10-1ubuntu2.2 arm64tools to support fast kexec reboots $ sudo cat /proc/iomem | grep "System RAM" 0082-0307 : System RAM 0309-031f : System RAM 0341-0402 : System RAM 0404-0549 : System RAM 054c4000-054c8fff : System RAM 084de000-0854 : System RAM 085f-0866 : System RAM 0871-0877 : System RAM 0882-08a7 : System RAM 0916-0918 : System RAM 0928-0928cfff : System RAM 0967c000-0e65 : System RAM 0e69-0fff : System RAM 1080-17fe : System RAM 1c01-1c7f : System RAM 1c81-7efb : System RAM 7efe-7efe : System RAM 7f00-17 : System RAM $ sudo kexec -d -l /boot/vmlinuz-4.10.0-22-generic --reuse-cmd --initrd=/boot/vmlinuz-4.10.0-22-generic | grep "System RAM" arch_process_options:141: command_line: root=UUID=968531c2-2cee-41ca-9fb4-9975a1a8bb70 ro module_blacklist=at803x splash quiet vt.handoff=7 arch_process_options:143: initrd: /boot/vmlinuz-4.10.0-22-generic arch_process_options:144: dtb: (null) Try gzip decompression. kernel: 0x7c4ea010 kernel_size: 0x12bc200 get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM get_memory_ranges_iomem_cb: 0309 - 031f : System RAM get_memory_ranges_iomem_cb: 0341 - 0402 : System RAM get_memory_ranges_iomem_cb: 0404 - 0549 : System RAM get_memory_ranges_iomem_cb: 054c4000 - 054c8fff : System RAM get_memory_ranges_iomem_cb: 084de000 - 0854 : System RAM get_memory_ranges_iomem_cb: 085f - 0866 : System RAM get_memory_ranges_iomem_cb: 0871 - 0877 : System RAM get_memory_ranges_iomem_cb: 0882 - 08a7 : System RAM get_memory_ranges_iomem_cb: 0916 - 0918 : System RAM get_memory_ranges_iomem_cb: 0928 - 0928cfff : System RAM get_memory_ranges_iomem_cb: 0967c000 - 0e65 : System RAM get_memory_ranges_iomem_cb: 0e69 - 0fff : System RAM get_memory_ranges_iomem_cb: 1080 - 17fe : System RAM get_memory_ranges_iomem_cb: 1c01 - 1c7f : System RAM get_memory_ranges_iomem_cb: 1c81 - 7efb : System RAM get_memory_ranges_iomem_cb: 7efe - 7efe : System RAM get_memory_ranges_iomem_cb: 7f00 - 0017 : System RAM $ cat /etc/issue Ubuntu 16.04.2 LTS \n \l ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1663400 Title: kexec: arm64: Increase the upper limit for RAM segments Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Status in kexec-tools package in Debian: New Bug description: [Impact] Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem. On a newer UEFI based Qualcomm target the number of system ram regions retrieved from /proc/iomem are ~40. Currently KEXEC_SEGMENT_MAX is set to 16, which represents the kexec segments passed to kexec_load syscall, like kernel image, initrd image etc. The patch increases the value to 64. This enables kexec to see all the "System RAM" as recorded in /proc/iomem. [Test Case] == System RAM reported by /proc/iomem == ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM" 0020-0020 : System RAM 0082-0307 : System RAM 0308-0308 : System RAM 0309-031f : System RAM 0320-033f : System RAM 0341-0589 : System RAM 058a-058a : System RAM 058b-058b : System RAM 058c-0597 : System RAM 0598-05987fff : System RAM 05988000-0598bfff : System RAM 0598c000-05a0 : System RAM 05a1-05aa : System RAM 05ab-05ca0fff : System RAM 05ca1000-08ca : System RAM 08cb-08cf : System RAM 08d0-08ed : System RAM 08ee-08ee0fff : System RAM 08ee1000-08ee3fff : System RAM 08ee4000-08ee : System RAM 08ef-092a : System RAM 092b-092d : System RAM 092e-09422fff : System RAM 09423000-0949 : System RAM 094a-0957 : System RAM 0958-0958cfff : System RAM 0958d000-098c : System RAM 098d-098d0fff : System RAM 098d1000-098dbfff : System RAM 098dc000-0e8b : System RAM 0e8c-0e8e : System RAM 0e8f-0fff : System RAM 1080-17fe : System RAM 1c02-1c7f : System RAM 1c80-1c80 : System RAM 1c81-7efb : System RAM 7efc-7efd : System RAM 7efe-7efe : S
[Kernel-packages] [Bug 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments
$ dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.10-2ubuntu1.2 arm64tools to support fast kexec reboots $ sudo cat /proc/iomem | grep "System RAM" 0082-0307 : System RAM 0309-031f : System RAM 0341-0402 : System RAM 0404-0549 : System RAM 054c4000-054c8fff : System RAM 084de000-0854 : System RAM 085f-0866 : System RAM 0871-0877 : System RAM 0882-08a7 : System RAM 0916-0918 : System RAM 0928-0928cfff : System RAM 0967c000-0e65 : System RAM 0e69-0fff : System RAM 1080-17fe : System RAM 1c01-1c7f : System RAM 1c81-7efb : System RAM 7efe-7efe : System RAM 7f00-17 : System RAM $ sudo kexec -d -l /boot/vmlinuz-4.10.0-22-generic --reuse-cmd --initrd=/boot/vmlinuz-4.10.0-22-generic | grep "System RAM" arch_process_options:141: command_line: root=UUID=968531c2-2cee-41ca-9fb4-9975a1a8bb70 ro module_blacklist=at803x splash quiet vt.handoff=7 arch_process_options:143: initrd: /boot/vmlinuz-4.10.0-22-generic arch_process_options:144: dtb: (null) Try gzip decompression. kernel: 0xa122f010 kernel_size: 0x12bc200 get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM get_memory_ranges_iomem_cb: 0309 - 031f : System RAM get_memory_ranges_iomem_cb: 0341 - 0402 : System RAM get_memory_ranges_iomem_cb: 0404 - 0549 : System RAM get_memory_ranges_iomem_cb: 054c4000 - 054c8fff : System RAM get_memory_ranges_iomem_cb: 084de000 - 0854 : System RAM get_memory_ranges_iomem_cb: 085f - 0866 : System RAM get_memory_ranges_iomem_cb: 0871 - 0877 : System RAM get_memory_ranges_iomem_cb: 0882 - 08a7 : System RAM get_memory_ranges_iomem_cb: 0916 - 0918 : System RAM get_memory_ranges_iomem_cb: 0928 - 0928cfff : System RAM get_memory_ranges_iomem_cb: 0967c000 - 0e65 : System RAM get_memory_ranges_iomem_cb: 0e69 - 0fff : System RAM get_memory_ranges_iomem_cb: 1080 - 17fe : System RAM get_memory_ranges_iomem_cb: 1c01 - 1c7f : System RAM get_memory_ranges_iomem_cb: 1c81 - 7efb : System RAM get_memory_ranges_iomem_cb: 7efe - 7efe : System RAM get_memory_ranges_iomem_cb: 7f00 - 0017 : System RAM ** Tags removed: verification-needed ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1663400 Title: kexec: arm64: Increase the upper limit for RAM segments Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Status in kexec-tools package in Debian: New Bug description: [Impact] Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem. On a newer UEFI based Qualcomm target the number of system ram regions retrieved from /proc/iomem are ~40. Currently KEXEC_SEGMENT_MAX is set to 16, which represents the kexec segments passed to kexec_load syscall, like kernel image, initrd image etc. The patch increases the value to 64. This enables kexec to see all the "System RAM" as recorded in /proc/iomem. [Test Case] == System RAM reported by /proc/iomem == ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM" 0020-0020 : System RAM 0082-0307 : System RAM 0308-0308 : System RAM 0309-031f : System RAM 0320-033f : System RAM 0341-0589 : System RAM 058a-058a : System RAM 058b-058b : System RAM 058c-0597 : System RAM 0598-05987fff : System RAM 05988000-0598bfff : System RAM 0598c000-05a0 : System RAM 05a1-05aa : System RAM 05ab-05ca0fff : System RAM 05ca1000-08ca : System RAM 08cb-08cf : System RAM 08d0-08ed : System RAM 08ee-08ee0fff : System RAM 08ee1000-08ee3fff : System RAM 08ee4000-08ee : System RAM 08ef-092a : System RAM 092b-092d : System RAM 092e-09422fff : System RAM 09423000-0949 : System RAM 094a-0957 : System RAM 0958-0958cfff : System RAM 0958d000-098c : System RAM 098d-098d0fff : System RAM 098d1000-098dbfff : System RAM 098dc000-0e8b : System RAM 0e8c-0e8e : System RAM 0e8f-0fff : System RAM 1080-17fe : System RAM 1c02-1c7f : System RAM 1c80-1c80 : System RAM 1c81-7efb : System RAM 7efc-7efd : System RAM 7efe-7efe : System
[Kernel-packages] [Bug 1662554] Re: [Yakkety SRU] Enable KEXEC support in ARM64 kernel
$ uname -a Linux myvm 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:41 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662554 Title: [Yakkety SRU] Enable KEXEC support in ARM64 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: [Impact] * If the kernel is not built with CONFIG_KEXEC support, kexec-tools will not be able to live boot a new kernel over the running one. * Our partners/customers have requested this feature. [Test Case] * Install a version of kexec-tools that supports ARM64 * Run the command: sudo kexec -l /boot/ --initrd=/boot/ --append=" * You should see the message: kexec_load failed: Function not implemented [Regression Potential] * The proposed config changes are limited to ARM64 architecture, overall risk of regression is low. [Other Info] * Please note that kexec-tools currently is not built for ARM64 * I have an SRU to enable that https://bugs.launchpad.net/bugs/1659618 * I am working with dannf to get kexec-tools to support ARM64 in yakkety. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662554] Re: [Yakkety SRU] Enable KEXEC support in ARM64 kernel
$ cat /etc/issue Ubuntu 16.10 \n \l $ sudo file /boot/vmlinuz-4.10.0-22-generic /boot/vmlinuz-4.10.0-22-generic: gzip compressed data, max compression, from Unix $ sudo kexec -d -l /boot/vmlinuz-4.10.0-22-generic --initrd=/boot/initrd.img-4.10.0-22-generic --reuse-cmdline arch_process_options:141: command_line: root=LABEL=cloudimg-rootfs ro quiet splash vt.handoff=7 arch_process_options:143: initrd: /boot/initrd.img-4.10.0-22-generic arch_process_options:144: dtb: (null) Try gzip decompression. kernel: 0xaeb49010 kernel_size: 0x12bc200 get_memory_ranges_iomem_cb: 4000 - 5855 : System RAM get_memory_ranges_iomem_cb: 585c - 585ebfff : System RAM get_memory_ranges_iomem_cb: 5875 - 5bc1 : System RAM get_memory_ranges_iomem_cb: 5c00 - 5fff : System RAM elf_arm64_probe: Not an ELF executable. image_arm64_load: kernel_segment: 4000 image_arm64_load: text_offset:0008 image_arm64_load: image_size: 013cf000 image_arm64_load: phys_offset:4000 image_arm64_load: vp_offset: image_arm64_load: PE format: yes read_1st_dtb: found /sys/firmware/fdt initrd: base 4144f000, size 1af840fh (28279823) dtb_set_initrd: start 1095036928, end 1123316751, size 28279823 (27617 KiB) dtb:base 42f48000, size 1c49h (7241) sym: sha256_starts info: 12 other: 00 shndx: 1 value: e80 size: 58 sym: sha256_starts value: 42f4ae80 addr: 42f4a014 machine_apply_elf_rel: CALL26 580006539400->580006539400039b sym: sha256_update info: 12 other: 00 shndx: 1 value: 2df0 size: c sym: sha256_update value: 42f4cdf0 addr: 42f4a030 machine_apply_elf_rel: CALL26 eb16027f9400->eb16027f94000b70 sym: sha256_finish info: 12 other: 00 shndx: 1 value: 2e00 size: 1bc sym: sha256_finish value: 42f4ce00 addr: 42f4a048 machine_apply_elf_rel: CALL26 aa1603e19400->aa1603e194000b6e sym: memcmp info: 12 other: 00 shndx: 1 value: 604 size: 34 sym: memcmp value: 42f4a604 addr: 42f4a058 machine_apply_elf_rel: CALL26 340003a09400->340003a09400016b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a068 machine_apply_elf_rel: CALL26 580004209400->580004209400012f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a070 machine_apply_elf_rel: CALL26 580004369400->580004369400012d sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a084 machine_apply_elf_rel: CALL26 f100827f9400->f100827f94000128 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a0 machine_apply_elf_rel: CALL26 580003209400->5800032094000121 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a8 machine_apply_elf_rel: CALL26 38736a819400->38736a819400011f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0b8 machine_apply_elf_rel: CALL26 f100827f9400->f100827f9400011b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0c8 machine_apply_elf_rel: CALL26 528000209400->5280002094000117 sym: .data info: 03 other: 00 shndx: 4 value: 0 size: 0 sym: .data value: 42f4d038 addr: 42f4a0e0 machine_apply_elf_rel: ABS64 ->42f4d038 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfc8 addr: 42f4a0e8 machine_apply_elf_rel: ABS64 ->42f4cfc8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfe8 addr: 42f4a0f0 machine_apply_elf_rel: ABS64 ->42f4cfe8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cff8 addr: 42f4a0f8 machine_apply_elf_rel: ABS64 ->42f4cff8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cffe addr: 42f4a100 machine_apply_elf_rel: ABS64 ->42f4cffe sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4d000 addr: 42f4a108 machine_apply_elf_rel: ABS64 ->42f4d000 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a11c machine_apply_elf_rel: CALL26 94009400->940094000102 sym: setup_arch info: 12 other: 00 shndx: 1 value: e78 size: 4 sym: setup_arch value: 42f4ae78 addr: 42f4a120 machine_apply_elf_rel: CALL26 94009400->940094000356 sym: verify_sha256_digest info: 12 other: 00 shndx: 1 value: 0 size: e0 sym: verify_sha256_digest value: 42f4a000 addr: 42f4a124 machine_apply_elf_rel: CALL26 34409400->344097b7 sym: post_verification_setup_arch info: 12 other: 00 shndx: 1 value: e74
[Kernel-packages] [Bug 1662554] Re: [Yakkety SRU] Enable KEXEC support in ARM64 kernel
$ dpkg -l | grep kexec-toolsii kexec-tools 1:2.0.10-2ubuntu1.2 arm64tools to support fast kexec reboots ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662554 Title: [Yakkety SRU] Enable KEXEC support in ARM64 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: [Impact] * If the kernel is not built with CONFIG_KEXEC support, kexec-tools will not be able to live boot a new kernel over the running one. * Our partners/customers have requested this feature. [Test Case] * Install a version of kexec-tools that supports ARM64 * Run the command: sudo kexec -l /boot/ --initrd=/boot/ --append=" * You should see the message: kexec_load failed: Function not implemented [Regression Potential] * The proposed config changes are limited to ARM64 architecture, overall risk of regression is low. [Other Info] * Please note that kexec-tools currently is not built for ARM64 * I have an SRU to enable that https://bugs.launchpad.net/bugs/1659618 * I am working with dannf to get kexec-tools to support ARM64 in yakkety. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661363] Re: Fails to load compressed kernels on arm64
Testing on Yakkety (16.10) $ cat /etc/issue Ubuntu 16.10 \n \l $ uname -a Linux myvm 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:41 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux $ sudo file /boot/vmlinuz-4.10.0-22-generic /boot/vmlinuz-4.10.0-22-generic: gzip compressed data, max compression, from Unix $ sudo kexec -d -l /boot/vmlinuz-4.10.0-22-generic --initrd=/boot/initrd.img-4.10.0-22-generic --reuse-cmdline arch_process_options:141: command_line: root=LABEL=cloudimg-rootfs ro quiet splash vt.handoff=7 arch_process_options:143: initrd: /boot/initrd.img-4.10.0-22-generic arch_process_options:144: dtb: (null) Try gzip decompression. kernel: 0xaf279010 kernel_size: 0x12bc200 get_memory_ranges_iomem_cb: 4000 - 5855 : System RAM get_memory_ranges_iomem_cb: 585c - 585ebfff : System RAM get_memory_ranges_iomem_cb: 5875 - 5bc1 : System RAM get_memory_ranges_iomem_cb: 5c00 - 5fff : System RAM elf_arm64_probe: Not an ELF executable. image_arm64_load: kernel_segment: 4000 image_arm64_load: text_offset:0008 image_arm64_load: image_size: 013cf000 image_arm64_load: phys_offset:4000 image_arm64_load: vp_offset: image_arm64_load: PE format: yes read_1st_dtb: found /sys/firmware/fdt initrd: base 4144f000, size 1af840fh (28279823) dtb_set_initrd: start 1095036928, end 1123316751, size 28279823 (27617 KiB) dtb:base 42f48000, size 1c49h (7241) sym: sha256_starts info: 12 other: 00 shndx: 1 value: e80 size: 58 sym: sha256_starts value: 42f4ae80 addr: 42f4a014 machine_apply_elf_rel: CALL26 580006539400->580006539400039b sym: sha256_update info: 12 other: 00 shndx: 1 value: 2df0 size: c sym: sha256_update value: 42f4cdf0 addr: 42f4a030 machine_apply_elf_rel: CALL26 eb16027f9400->eb16027f94000b70 sym: sha256_finish info: 12 other: 00 shndx: 1 value: 2e00 size: 1bc sym: sha256_finish value: 42f4ce00 addr: 42f4a048 machine_apply_elf_rel: CALL26 aa1603e19400->aa1603e194000b6e sym: memcmp info: 12 other: 00 shndx: 1 value: 604 size: 34 sym: memcmp value: 42f4a604 addr: 42f4a058 machine_apply_elf_rel: CALL26 340003a09400->340003a09400016b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a068 machine_apply_elf_rel: CALL26 580004209400->580004209400012f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a070 machine_apply_elf_rel: CALL26 580004369400->580004369400012d sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a084 machine_apply_elf_rel: CALL26 f100827f9400->f100827f94000128 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a0 machine_apply_elf_rel: CALL26 580003209400->5800032094000121 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a8 machine_apply_elf_rel: CALL26 38736a819400->38736a819400011f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0b8 machine_apply_elf_rel: CALL26 f100827f9400->f100827f9400011b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0c8 machine_apply_elf_rel: CALL26 528000209400->5280002094000117 sym: .data info: 03 other: 00 shndx: 4 value: 0 size: 0 sym: .data value: 42f4d038 addr: 42f4a0e0 machine_apply_elf_rel: ABS64 ->42f4d038 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfc8 addr: 42f4a0e8 machine_apply_elf_rel: ABS64 ->42f4cfc8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfe8 addr: 42f4a0f0 machine_apply_elf_rel: ABS64 ->42f4cfe8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cff8 addr: 42f4a0f8 machine_apply_elf_rel: ABS64 ->42f4cff8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cffe addr: 42f4a100 machine_apply_elf_rel: ABS64 ->42f4cffe sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4d000 addr: 42f4a108 machine_apply_elf_rel: ABS64 ->42f4d000 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a11c machine_apply_elf_rel: CALL26 94009400->940094000102 sym: setup_arch info: 12 other: 00 shndx: 1 value: e78 size: 4 sym: setup_arch value: 42f4ae78 addr: 42f4a120 machine_apply_elf_rel: CALL26 94009400->940094000356 sym: verify_sha256_digest info: 12 other: 00 shndx: 1 value: 0 size: e0 sym: verify_sha256_digest value: 42f4a000 addr
[Kernel-packages] [Bug 1671246] Re: kexec-tools does not build for armhf
$ cat /etc/issue Ubuntu 16.10 \n \l $ uname -a Linux myvm 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:41 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux $ dpkg -l | grep kexec-tools ii kexec-tools1:2.0.10-2ubuntu1.2 arm64tools to support fast kexec reboots $ sudo file /boot/vmlinuz-4.10.0-22-generic /boot/vmlinuz-4.10.0-22-generic: gzip compressed data, max compression, from Unix $ sudo kexec -d -l /boot/vmlinuz-4.10.0-22-generic --initrd=/boot/initrd.img-4.10.0-22-generic --reuse-cmdline arch_process_options:141: command_line: root=LABEL=cloudimg-rootfs ro quiet splash vt.handoff=7 arch_process_options:143: initrd: /boot/initrd.img-4.10.0-22-generic arch_process_options:144: dtb: (null) Try gzip decompression. kernel: 0xaf279010 kernel_size: 0x12bc200 get_memory_ranges_iomem_cb: 4000 - 5855 : System RAM get_memory_ranges_iomem_cb: 585c - 585ebfff : System RAM get_memory_ranges_iomem_cb: 5875 - 5bc1 : System RAM get_memory_ranges_iomem_cb: 5c00 - 5fff : System RAM elf_arm64_probe: Not an ELF executable. image_arm64_load: kernel_segment: 4000 image_arm64_load: text_offset:0008 image_arm64_load: image_size: 013cf000 image_arm64_load: phys_offset:4000 image_arm64_load: vp_offset: image_arm64_load: PE format: yes read_1st_dtb: found /sys/firmware/fdt initrd: base 4144f000, size 1af840fh (28279823) dtb_set_initrd: start 1095036928, end 1123316751, size 28279823 (27617 KiB) dtb:base 42f48000, size 1c49h (7241) sym: sha256_starts info: 12 other: 00 shndx: 1 value: e80 size: 58 sym: sha256_starts value: 42f4ae80 addr: 42f4a014 machine_apply_elf_rel: CALL26 580006539400->580006539400039b sym: sha256_update info: 12 other: 00 shndx: 1 value: 2df0 size: c sym: sha256_update value: 42f4cdf0 addr: 42f4a030 machine_apply_elf_rel: CALL26 eb16027f9400->eb16027f94000b70 sym: sha256_finish info: 12 other: 00 shndx: 1 value: 2e00 size: 1bc sym: sha256_finish value: 42f4ce00 addr: 42f4a048 machine_apply_elf_rel: CALL26 aa1603e19400->aa1603e194000b6e sym: memcmp info: 12 other: 00 shndx: 1 value: 604 size: 34 sym: memcmp value: 42f4a604 addr: 42f4a058 machine_apply_elf_rel: CALL26 340003a09400->340003a09400016b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a068 machine_apply_elf_rel: CALL26 580004209400->580004209400012f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a070 machine_apply_elf_rel: CALL26 580004369400->580004369400012d sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a084 machine_apply_elf_rel: CALL26 f100827f9400->f100827f94000128 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a0 machine_apply_elf_rel: CALL26 580003209400->5800032094000121 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0a8 machine_apply_elf_rel: CALL26 38736a819400->38736a819400011f sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0b8 machine_apply_elf_rel: CALL26 f100827f9400->f100827f9400011b sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a0c8 machine_apply_elf_rel: CALL26 528000209400->5280002094000117 sym: .data info: 03 other: 00 shndx: 4 value: 0 size: 0 sym: .data value: 42f4d038 addr: 42f4a0e0 machine_apply_elf_rel: ABS64 ->42f4d038 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfc8 addr: 42f4a0e8 machine_apply_elf_rel: ABS64 ->42f4cfc8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cfe8 addr: 42f4a0f0 machine_apply_elf_rel: ABS64 ->42f4cfe8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cff8 addr: 42f4a0f8 machine_apply_elf_rel: ABS64 ->42f4cff8 sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4cffe addr: 42f4a100 machine_apply_elf_rel: ABS64 ->42f4cffe sym: .rodata.str1.1 info: 03 other: 00 shndx: 3 value: 0 size: 0 sym: .rodata.str1.1 value: 42f4d000 addr: 42f4a108 machine_apply_elf_rel: ABS64 ->42f4d000 sym: printf info: 12 other: 00 shndx: 1 value: 524 size: 80 sym: printf value: 42f4a524 addr: 42f4a11c machine_apply_elf_rel: CALL26 94009400->940094000102 sym: setup_arch info: 12 other: 00 shndx: 1 value: e78 size: 4 sym: setup_arch value: 42f4ae78 addr: 42f4a120 machine_apply_elf_rel: CALL26 94000
[Kernel-packages] [Bug 1695093] Re: arm64: "unsupported RELA relocation: 275" loading certain modules
Attached is a buildlog of the kernel w/ V=1 set to see the full gcc commandline. I confirmed that the symptoms are present w/ this build. ** Attachment added: "buildlog.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695093/+attachment/4893293/+files/buildlog.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695093 Title: arm64: "unsupported RELA relocation: 275" loading certain modules Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: Confirmed Bug description: With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659111] Comment bridged from LTC Bugzilla
--- Comment From thiag...@br.ibm.com 2017-06-09 16:08 EDT--- Hello Lekshmi, Do you need this fix in Ubuntu kernels 4.8 and 4.10 too, or just 4.4? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659111 Title: UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Incomplete Bug description: Attn. Canonical: For your awareness only at this time. == Comment: #0 - LEKSHMI C. PILLAI - 2016-11-22 03:49:38 == Machine INFO KVM HOST: luckyv1 Guest :lucky05 lucky05 crashed while running the I/O stress test for SAN disks. Installed lucky05 and enabled the xmon on that.After that started the RAW disk test on around 50 disks.After 6-7 hours after running,Now machine dropped into xmon. Logs: [25023.224182] Unable to handle kernel paging request for data at address 0x [25023.224257] Faulting instruction address: 0xc0324c60 cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620] pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290 lr: c032831c: writeback_sb_inodes+0x30c/0x590 sp: c000fffc38a0 msr: 80019033 dar: 0 dsisr: 4000 current = 0xc000ff99e470 paca= 0xcfb41c80 softe: 0irq_happened: 0x01 pid = 14736, comm = kworker/u16:8 enter ? for help [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> f 3:mon> th [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570 [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0 [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680 [c000fffc3d80] c00e6980 kthread+0x110/0x130 [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 3:mon> sh [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks: [27384.651220] (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992) [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 (4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0 [27384.651501] rcu_sched kthread starved for 40596 jiffies! g2849830 c2849829 f0x2 s3 ->state=0x0 [27384.651747] INFO: rcu_sched detected stalls on CPUs/tasks: [27384.651905] (detected by 4, t=590354 jiffies, g=2849830, c=2849829, q=1285) [27384.652012] All QSes seen, last rcu_sched kthread activity 590352 (4301738470-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0 [27384.652191] rcu_sched kthread starved for 590352 jiffies! g2849830 c2849829 f0x2 s3 ->state=0x0 [27384.730645] Unable to handle kernel paging request for data at address 0xffd8 [27384.730781] Faulting instruction address: 0xc00e7258 cpu 0x3: Vector: 300 (Data Access) at [c000fffc3000] pc: c00e7258: kthread_data+0x28/0x40 lr: c00de940: wq_worker_sleeping+0x30/0x110 sp: c000fffc3280 msr: 80019033 dar: ffd8 dsisr: 4000 current = 0xc000ff99e470 paca= 0xcfb41c80 softe: 0irq_happened: 0x01 pid = 14736, comm = kworker/u16:8 enter ? for help == Comment: #1 - LEKSHMI C. PILLAI - 2016-11-22 04:05:41 == 3:mon> th [c000fffc32b0] c00de940 wq_worker_sleeping+0x30/0x110 [c000fffc32f0] c0af31bc __schedule+0x6ec/0x990 [c000fffc33c0] c0af34a8 schedule+0x48/0xc0 [c000fffc33f0] c00bd3d0 do_exit+0x760/0xc30 [c000fffc34b0] c0020bf4 die+0x314/0x470 [c000fffc3540] c0050d98 bad_page_fault+0xd8/0x150 [c000fffc35b0] c0008680 handle_page_fault+0x2c/0x30 --- Exception: 300 (Data Access) at c0324c60 locked_inode_to_wb_and_lock_list+0x50/0x290 [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590 [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150 [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450 [c000fffc3b40] c03296b4 wb
[Kernel-packages] [Bug 1696352] Re: linux: 3.13.0-120.167 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed ** Description changed: This bug is for tracking the 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 backports: 1696354 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 09. June 2017 14:00 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696352 Title: linux: 3.13.0-120.167 -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: Confirmed 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 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 backports: 1696354 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 09. June 2017 14:00 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1696352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697053] Re: Missing IOTLB flush causes DMAR errors with SR-IOV
** Changed in: linux (Ubuntu) Status: In Progress => 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/1697053 Title: Missing IOTLB flush causes DMAR errors with SR-IOV Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Using SR-IOV with Intel IOMMUs can observe DMAR errors of the following type: [606483.223009] DMAR:[fault reason 05] PTE Write access is not set [606484.071974] dmar: DRHD: handling fault status reg 402 [606484.077121] dmar: DMAR:[DMA Write] Request device [d8:0a.1] fault addr 35c6e000 The DMAR error causes, at a minimum, loss of network traffic because the request being serviced is lost. Network cards were also observed to experience transmit timeouts after a DMAR fault. In this case, these errors arise from a race condition in the IOTLB management; this race is described (and fixed) in upstream commit: commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d Author: David Woodhouse Date: Wed Mar 5 17:09:32 2014 + iommu/vt-d: Clean up and fix page table clear/free behaviour This commit first appeared in mainline 3.15. This issue affects only the Ubuntu 3.13 kernel series. Fix: The race avoidance portion of the above was backported to 3.14-stable, but was never incorporated into the Ubuntu 3.13 kernel series. commit 51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c Author: David Woodhouse Date: Mon Jun 9 14:09:53 2014 +0100 iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap() Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream This 3.14-stable patch was tested by the customer and observed to resolve the issue in their environment. Testcase: In this case, the issue occurs on very recent Intel based servers using two different SR-IOV network cards (i40e and bnxt) at a customer site. The customer has tested the patch in their environment and confirmed that it resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697053/+subscriptions -- Mailing list: https://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 1696620] Re: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1696440 *** https://bugs.launchpad.net/bugs/1696440 Thank you very much for helping me. 2017-06-09 15:02 GMT+02:00 Apport retracing service < 1696...@bugs.launchpad.net>: > *** This bug is a duplicate of bug 1696440 *** > https://bugs.launchpad.net/bugs/1696440 > > Thank you for taking the time to report this crash and helping to make > this software better. This particular crash has already been reported > and is a duplicate of bug #1696440, so is being marked as such. Please > look at the other bug report to see if there is any missing information > that you can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Please continue to report any other bugs you may > find. > > ** Tags removed: need-duplicate-check > > ** This bug has been marked a duplicate of bug 1696440 >package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 128 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1696620 > > Title: > package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error > exit status 128 > > Status in linux package in Ubuntu: > New > > Bug description: > I can't up date the last file > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-79-generic (not installed) > ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 > Uname: Linux 4.4.0-78-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: olivier1569 F pulseaudio > Date: Wed Jun 7 17:06:30 2017 > ErrorMessage: subprocess new pre-installation script returned error exit > status 128 > HibernationDevice: RESUME=UUID=41d54e07-3eb6-4837-a4d1-385398069e87 > InstallationDate: Installed on 2016-12-01 (188 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed > root=UUID=d2526c10-fb82-4392-a9c5-1a74a5bba6b4 ro quiet splash > vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc N/A > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux > Title: package linux-image-4.4.0-79-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 128 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/04/2014 > dmi.bios.vendor: Insyde > dmi.bios.version: F.23 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 1972 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 95.33 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: dmi:bvnInsyde:bvrF.23:bd06/04/2014:svnHewlett-Packard: > pnHPPavilion17NotebookPC:pvr088C1030591620100: > rvnHewlett-Packard:rn1972:rvr95.33:cvnHewlett-Packard: > ct10:cvrChassisVersion: > dmi.product.name: HP Pavilion 17 Notebook PC > dmi.product.version: 088C1030591620100 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1696620/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696620 Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: I can't up date the last file ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier1569 F pulseaudio Date: Wed Jun 7 17:06:30 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=41d54e07-3eb6-4837-a4d1-385398069e87 InstallationDate: Installed on 2016-12-01 (188 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion 17 Not
[Kernel-packages] [Bug 1696623] Re: macvtap creation issue using net namespaces
Hi Joseph, the server where I'm trying to run this is a headless system and have no any VNC or anything else. The apport-collect command mentioned above requires access authorization through a web browser and Lynx (the only thing I could think of) was of no help to successfully authenticate myself. That said, I think the bug is easy to reproduce, was reproduced by Christian and he also found later versions where this works as expected so setting back to confirmed. Thanks, Rolando ** 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/1696623 Title: macvtap creation issue using net namespaces Status in linux package in Ubuntu: Confirmed Bug description: Hi there, There seems to be a bug when trying to create two macvtap links that are contained within different net namespaces. This is what I'm facing and, at the same time, the steps to reproduce the issue: 1 - Create two net namespaces: # root@rjz-nuc:~# ip netns add bng1 root@rjz-nuc:~# ip netns add bng2 2 - Create two veth links, one in one net NS and another one in the other net NS: # root@rjz-nuc:~# ip link add netns bng1 bng1-111_veth type veth peer name subs-lg111_veth root@rjz-nuc:~# ip link add netns bng2 bng2-111_veth type veth peer name subs-lg211_veth 3a - Add a macvtap link on top of the 1st veth in the 1st net NS: # root@rjz-nuc:~# ip netns exec bng1 ip link add link bng1-111_veth name bng1-111_mcvtp type macvtap mode passthru 3b - This executes correctly and creates a tap device: # root@rjz-nuc:~# ip netns exec bng1 ip link show bng1-111_mcvtp 3: bng1-111_mcvtp@bng1-111_veth: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500 link/ether ae:c6:bc:d8:d2:e7 brd ff:ff:ff:ff:ff:ff 3c - Note the "3:" at the beginning of above output pointing to "tap3" that the command created: # root@rjz-nuc:~# ls -tral /dev/tap* crw--- 1 root root 241, 1 Jun 7 20:16 /dev/tap3 4a - Try to add another macvtap link but now on top of the 1st veth in the 2nd net NS: # root@rjz-nuc:~# ip netns exec bng2 ip link add link bng2-111_veth name bng2-111_mcvtp type macvtap mode passthru RTNETLINK answers: File exists 4b - As it can be seen, it fails stating "file exists". Checking the output of "dmesg", it can be seen the reason behind this is that instead of choosing as the tap device the next system-wide free one (for instance, say, tap4) it chooses the "tap3" that was already created by the command in step 3a above: # [Jun 7 20:17] [ cut here ] [ +0.32] WARNING: CPU: 3 PID: 1216 at /build/linux-As38az/linux-4.4.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80() [ +0.07] sysfs: cannot create duplicate filename '/class/macvtap/tap3' [ +0.05] Modules linked in: macvtap macvlan veth drbg ansi_cprng ctr ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp espaf_key xfrm_algo arc4 snd_hda_codec_hdmi 8250_dw snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec inte iwlmvm snd_hda_core x86_pkg_temp_thermal intel_powerclamp coretemp snd_hwdep crct10dif_pclmul mac80211 snd_pcm crc32_pclmul ghash_i_intel snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi glue_helper ablk_helper iwlwifi cryptd snd_put_leds snd_seq_device serio_raw cfg80211 snd_timer snd ir_lirc_codec soundcore lirc_dev ir_xmp_decoder ir_mce_kbd_decoder [ +0.000149] ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder btusb hci_uart btrtl btbcm ir_rc5_debtqca ir_nec_decoder idma64 virt_dma mei_me shpchp mei btintel intel_lpss_pci bluetooth rc_rc6_mce ite_cir rc_core intel_lpss_acpi ad mac_hid acpi_als intel_lpss kfifo_buf industrialio kvm_intel kvm irqbypass autofs4 i915_bpo intel_ips i2c_algo_bit drm_kms_helpe0e syscopyarea sysfillrect sysimgblt ptp sdhci_pci fb_sys_fops pps_core drm sdhci ahci libahci video pinctrl_sunrisepoint i2c_hid p_intel hid fjes [ +0.000124] CPU: 3 PID: 1216 Comm: ip Not tainted 4.4.0-79-generic #100-Ubuntu [ +0.07] Hardware name: /NUC6i3SYB, BIOS SYSKLi35.86A.0024.2015.1027.2142 10/27/2015 [ +0.06] 0286 ffea66e1 88083a5ef5b8 813f94d3 [ +0.13] 88083a5ef600 81ce3010 88083a5ef5f0 81081322 [ +0.11] 88083a56c000 88083c212900 88083a5fbca8 88083a5fbca8 [ +0.11] Call Trace: [ +0.17] [] dump_stack+0x63/0x90 [ +0.15] [] warn_slowpath_common+0x82/0xc0 [ +0.11] [] warn_slowpath_fmt+0x5c/0x80 [ +0.15] [] sysfs_warn_dup+0x62/0x80 [ +0.14] [] sysfs_do_create_link_sd.isra.2+0x9e/0xb0
[Kernel-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted
... and on my Lubuntu 17.04 # journalctl -b | grep bluetoothd [...] Jun 09 20:31:34 acer bluetoothd[1986]: Failed to obtain handles for "Service Changed" characteristic Jun 09 20:31:34 acer bluetoothd[1986]: Sap driver initialization failed. Jun 09 20:31:34 acer bluetoothd[1986]: sap-server: Operation not permitted (1) [...] -- 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/1629632 Title: Sap driver initialization failed, sap-server: Operation not permitted Status in bluez package in Ubuntu: Confirmed Status in bluez package in Debian: New Bug description: Hi, here are are messages from the bluetooth daemon: $ journalctl -b | grep bluetoothd Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41 Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 initialized Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service Changed" characteristic Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed. Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1) There are at least 2 errors concerning: - handles - Sap driver/server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 09:59:43 2016 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:57:27:6F ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1974 acl:0 sco:0 events:132 errors:0 TX bytes:6033 acl:0 sco:0 commands:132 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695780] Re: On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial VM does not boot
I built the next test kernel, up to the following commit: c173e45ac6939f124d6645369e8981c3b4c4c75b The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1695780/c173e45ac6939f124d6645369e8981c3b4c4c75b 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 Hide -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695780 Title: On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial VM does not boot Status in linux package in Ubuntu: Confirmed Bug description: My set up is a Cisco UCS c240 server with an Intel NVMe 1.6TB drive running VMware ESXi version 6.0U2. NVMe device is made available as a PCI passthru device and not claimed by ESXi kernel. This NVMe device when added to a Ubuntu 16.04.2 running kernel version 4.4.0-62 and above does not boot, kernel does not boot fully and hangs for while before the VM powers off. However, running kernel versions 4.4.0-43, 4.4.0-53, 4.4.0-57, and 4.4.0-59 everything works as expected. Earlier versions of the kernel also do not work. Here is a short list of the I tested with 4.4.0-31 -> kernel panic (different issue) 4.4.0-43 -> works 4.4.0-53 -> works 4.4.0-57 -> works 4.4.0-59 -> works 4.4.0-62 -> fail 4.4.0-64 -> fail 4.4.0-75 -> fail 4.4.0-77 -> fail 4.8.0-51 -> fail ~# cat /proc/version_signature Ubuntu 4.4.0-75.96-generic 4.4.59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697053] Re: Missing IOTLB flush causes DMAR errors with SR-IOV
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697053 Title: Missing IOTLB flush causes DMAR errors with SR-IOV Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Using SR-IOV with Intel IOMMUs can observe DMAR errors of the following type: [606483.223009] DMAR:[fault reason 05] PTE Write access is not set [606484.071974] dmar: DRHD: handling fault status reg 402 [606484.077121] dmar: DMAR:[DMA Write] Request device [d8:0a.1] fault addr 35c6e000 The DMAR error causes, at a minimum, loss of network traffic because the request being serviced is lost. Network cards were also observed to experience transmit timeouts after a DMAR fault. In this case, these errors arise from a race condition in the IOTLB management; this race is described (and fixed) in upstream commit: commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d Author: David Woodhouse Date: Wed Mar 5 17:09:32 2014 + iommu/vt-d: Clean up and fix page table clear/free behaviour This commit first appeared in mainline 3.15. This issue affects only the Ubuntu 3.13 kernel series. Fix: The race avoidance portion of the above was backported to 3.14-stable, but was never incorporated into the Ubuntu 3.13 kernel series. commit 51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c Author: David Woodhouse Date: Mon Jun 9 14:09:53 2014 +0100 iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap() Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream This 3.14-stable patch was tested by the customer and observed to resolve the issue in their environment. Testcase: In this case, the issue occurs on very recent Intel based servers using two different SR-IOV network cards (i40e and bnxt) at a customer site. The customer has tested the patch in their environment and confirmed that it resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696369] Re: linux: 4.10.0-23.25 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 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 backports: 1696370,1696371 derivatives: 1696372 kernel-stable-phase-changed:Friday, 09. June 2017 10:03 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696369 Title: linux: 4.10.0-23.25 -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: Confirmed 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: New Bug description: This bug is for tracking the 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 backports: 1696370,1696371 derivatives: 1696372 kernel-stable-phase-changed:Friday, 09. June 2017 10:03 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1696369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
Checking the issue that was referred shows it was handled and fixed in
1. Kernel
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd
230 which also means part of >=Yakkety.
I'm filing bug tasks for systemd and kernel to check and maybe consider
for Xenial
** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: nbd (Ubuntu)
Status: Confirmed => Invalid
** Also affects: nbd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: nbd (Ubuntu Xenial)
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package in Ubuntu:
Fix Released
Status in nbd package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in systemd source package in Xenial:
New
Bug description:
When using an nbd root, wait-for-root blocks for 30 seconds before
booting continues successfully.
Using Ubuntu Natty, related packages versions:
nbd-client 1:2.9.16-6ubuntu1
initramfs-tools 0.98.1ubuntu9
The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})
# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop. If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done
I replaced wait-for-root with a sh script that did `set >&2`, here are the
relevant environment variables at the time wait-for-root was called:
ROOT='/dev/nbd0'
ROOTDELAY=''
ROOTFLAGS=''
ROOTFSTYPE=''
nbdroot='192.168.0.1,2011'
It's probably worth noting that "nbd0: unknown partition table" was
displayed asynchronously 1-2 seconds after wait-for-root was invoked
and while it was still waiting. But I tried adding a "sleep 5" as the
last line of local-top/nbd, so that the nbd message was displayed a
lot before wait-for-root was called, and it didn't make a difference.
So I don't think a race condition is involved in this problem.
Temporarily I'm passing rootdelay=1 in the kernel command line to work
around the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Can folks affected by this bug test the following kernel, since it seemed to resolve the bug for the original bug reporter: http://kernel.ubuntu.com/~jsalisbury/lp1679898/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no 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: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _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: 5894-4187-8369-8212-0547-2747-15 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 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions.
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
Sorry for the late answer. Please find the log in attachment. ** Attachment added: "kdump-trace.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+attachment/4893178/+files/kdump-trace.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/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel. This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77 kdump-tools 1:1.5.9-5ubuntu0.4 makedumpfile1:1.5.9-5ubuntu0.4 linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1 # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697027] Re: ath9k freezes suspend resume Ubuntu 17.04
I can confirm that the same issue occurs with kernel 4.12.0-041200rc4-generic and that the issue did not exist with Ubuntu 16.10. I do not know which kernel introduced the issue but immediately after upgrading to Ubuntu 17.04 I started observing the machine occasionally freezing upon resuming from suspend. I have just installed kernel version 4.12.0-041200rc4-generic and reproduced the bug. To reproduce the bug I usually need to suspend the system about five times. Most of the times suspend/resume does work just fine, and then occasionally it leaves the system in an unrecoverable state. Not sure if a specific state triggers the issue. It seems random to me. I have attached the dmesg output I obtained with kernel 4.12.0-041200rc4-generic. The issue seems to be exactly the same as with kernel 4.10.0-22-generic. Once the bug arises, I cannot file the report with apport as the machine is unable to use the network: $ apport-collect 1697027 ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net You can reset the credentials by removing the file /home/genovese/.cache/apport/launchpad.credentials Is there a way to collect the data with apport into a file and upload it later after rebooting the machine? ** Attachment added: "dmesg.4.12.0-041200rc4-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697027/+attachment/4893177/+files/dmesg.4.12.0-041200rc4-generic ** 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/1697027 Title: ath9k freezes suspend resume Ubuntu 17.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu Zesty Zapus Release: 17.04 What was expected to happen? I expected the laptop would suspend and resume without issues What happened instead? First the network fails, then all other programs slowly start to fail as well until the system freezes completely. The system is unable to shutdown and it requires a forced shutdown. Often when suspending my system, a recent upgrade to 17.04 from 16.10, after resuming the network does not work and then slowly the whole system freezes. Looking at dmesg, the problem seems to arise just before the system suspends with the kernel trace attached below. My best guess is that the issue is caused by ath9k. My system is a Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with 8GB of RAM and no swap) and it is often connected to a Dell U3011 monitor. I could not find other reports of this bug and this behaviour is new to 17.04, that is, it was not present in 16.10. I was always able to suspend and resume without issues before. I have been waiting to see bug 1674838 fixed before reporting this bug thinking that they might be related, but they are clearly independent as I am still having this suspend issue. Happy to try to collect more info if this information is not enough to understand where the problem lies, however it is impossible to run apport once the bug arises. [11292.289928] [ cut here ] [11292.289935] WARNING: CPU: 0 PID: 943 at /build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110 [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd input_leds joydev soundcore serio_raw shpchp mei_me mei [11292.289977] lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi fjes video [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 4.10.0-22-generic #24-Ubuntu [11292.289996] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [11292.289997] Call Trace: [11292.290001] dump_stack+0x63/0x81 [11292.290003] __warn+0xcb/0xf0 [11292.290005] warn_slowpath_null+0x1d/0x20 [11292.290007] kthread_stop+0x102/0x110 [11292.290014] ath9k_rng_stop+0x1a/0x20 [ath9k] [11292.290018] ath9k_stop+0x3b/0x1d0 [ath9k] [11292.290036] drv_stop+0x33/0x100 [mac80211] [11292.29005
[Kernel-packages] [Bug 1697053] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1697053 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/1697053 Title: Missing IOTLB flush causes DMAR errors with SR-IOV Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: Using SR-IOV with Intel IOMMUs can observe DMAR errors of the following type: [606483.223009] DMAR:[fault reason 05] PTE Write access is not set [606484.071974] dmar: DRHD: handling fault status reg 402 [606484.077121] dmar: DMAR:[DMA Write] Request device [d8:0a.1] fault addr 35c6e000 The DMAR error causes, at a minimum, loss of network traffic because the request being serviced is lost. Network cards were also observed to experience transmit timeouts after a DMAR fault. In this case, these errors arise from a race condition in the IOTLB management; this race is described (and fixed) in upstream commit: commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d Author: David Woodhouse Date: Wed Mar 5 17:09:32 2014 + iommu/vt-d: Clean up and fix page table clear/free behaviour This commit first appeared in mainline 3.15. This issue affects only the Ubuntu 3.13 kernel series. Fix: The race avoidance portion of the above was backported to 3.14-stable, but was never incorporated into the Ubuntu 3.13 kernel series. commit 51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c Author: David Woodhouse Date: Mon Jun 9 14:09:53 2014 +0100 iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap() Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream This 3.14-stable patch was tested by the customer and observed to resolve the issue in their environment. Testcase: In this case, the issue occurs on very recent Intel based servers using two different SR-IOV network cards (i40e and bnxt) at a customer site. The customer has tested the patch in their environment and confirmed that it resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] [NEW] wait-for-root fails to detect nbd root
You have been subscribed to a public bug:
When using an nbd root, wait-for-root blocks for 30 seconds before
booting continues successfully.
Using Ubuntu Natty, related packages versions:
nbd-client 1:2.9.16-6ubuntu1
initramfs-tools 0.98.1ubuntu9
The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})
# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop. If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done
I replaced wait-for-root with a sh script that did `set >&2`, here are the
relevant environment variables at the time wait-for-root was called:
ROOT='/dev/nbd0'
ROOTDELAY=''
ROOTFLAGS=''
ROOTFSTYPE=''
nbdroot='192.168.0.1,2011'
It's probably worth noting that "nbd0: unknown partition table" was
displayed asynchronously 1-2 seconds after wait-for-root was invoked and
while it was still waiting. But I tried adding a "sleep 5" as the last
line of local-top/nbd, so that the nbd message was displayed a lot
before wait-for-root was called, and it didn't make a difference. So I
don't think a race condition is involved in this problem.
Temporarily I'm passing rootdelay=1 in the kernel command line to work
around the problem.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: nbd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: bot-stop-nagging
--
wait-for-root fails to detect nbd root
https://bugs.launchpad.net/bugs/696435
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697053] [NEW] Missing IOTLB flush causes DMAR errors with SR-IOV
Public bug reported: SRU Justification: Impact: Using SR-IOV with Intel IOMMUs can observe DMAR errors of the following type: [606483.223009] DMAR:[fault reason 05] PTE Write access is not set [606484.071974] dmar: DRHD: handling fault status reg 402 [606484.077121] dmar: DMAR:[DMA Write] Request device [d8:0a.1] fault addr 35c6e000 The DMAR error causes, at a minimum, loss of network traffic because the request being serviced is lost. Network cards were also observed to experience transmit timeouts after a DMAR fault. In this case, these errors arise from a race condition in the IOTLB management; this race is described (and fixed) in upstream commit: commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d Author: David Woodhouse Date: Wed Mar 5 17:09:32 2014 + iommu/vt-d: Clean up and fix page table clear/free behaviour This commit first appeared in mainline 3.15. This issue affects only the Ubuntu 3.13 kernel series. Fix: The race avoidance portion of the above was backported to 3.14-stable, but was never incorporated into the Ubuntu 3.13 kernel series. commit 51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c Author: David Woodhouse Date: Mon Jun 9 14:09:53 2014 +0100 iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap() Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream This 3.14-stable patch was tested by the customer and observed to resolve the issue in their environment. Testcase: In this case, the issue occurs on very recent Intel based servers using two different SR-IOV network cards (i40e and bnxt) at a customer site. The customer has tested the patch in their environment and confirmed that it resolves the issue. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jay Vosburgh (jvosburgh) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jay Vosburgh (jvosburgh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697053 Title: Missing IOTLB flush causes DMAR errors with SR-IOV Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: Using SR-IOV with Intel IOMMUs can observe DMAR errors of the following type: [606483.223009] DMAR:[fault reason 05] PTE Write access is not set [606484.071974] dmar: DRHD: handling fault status reg 402 [606484.077121] dmar: DMAR:[DMA Write] Request device [d8:0a.1] fault addr 35c6e000 The DMAR error causes, at a minimum, loss of network traffic because the request being serviced is lost. Network cards were also observed to experience transmit timeouts after a DMAR fault. In this case, these errors arise from a race condition in the IOTLB management; this race is described (and fixed) in upstream commit: commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d Author: David Woodhouse Date: Wed Mar 5 17:09:32 2014 + iommu/vt-d: Clean up and fix page table clear/free behaviour This commit first appeared in mainline 3.15. This issue affects only the Ubuntu 3.13 kernel series. Fix: The race avoidance portion of the above was backported to 3.14-stable, but was never incorporated into the Ubuntu 3.13 kernel series. commit 51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c Author: David Woodhouse Date: Mon Jun 9 14:09:53 2014 +0100 iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap() Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream This 3.14-stable patch was tested by the customer and observed to resolve the issue in their environment. Testcase: In this case, the issue occurs on very recent Intel based servers using two different SR-IOV network cards (i40e and bnxt) at a customer site. The customer has tested the patch in their environment and confirmed that it resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697027] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1697027 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 ** Tags added: zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697027 Title: ath9k freezes suspend resume Ubuntu 17.04 Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu Zesty Zapus Release: 17.04 What was expected to happen? I expected the laptop would suspend and resume without issues What happened instead? First the network fails, then all other programs slowly start to fail as well until the system freezes completely. The system is unable to shutdown and it requires a forced shutdown. Often when suspending my system, a recent upgrade to 17.04 from 16.10, after resuming the network does not work and then slowly the whole system freezes. Looking at dmesg, the problem seems to arise just before the system suspends with the kernel trace attached below. My best guess is that the issue is caused by ath9k. My system is a Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with 8GB of RAM and no swap) and it is often connected to a Dell U3011 monitor. I could not find other reports of this bug and this behaviour is new to 17.04, that is, it was not present in 16.10. I was always able to suspend and resume without issues before. I have been waiting to see bug 1674838 fixed before reporting this bug thinking that they might be related, but they are clearly independent as I am still having this suspend issue. Happy to try to collect more info if this information is not enough to understand where the problem lies, however it is impossible to run apport once the bug arises. [11292.289928] [ cut here ] [11292.289935] WARNING: CPU: 0 PID: 943 at /build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110 [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd input_leds joydev soundcore serio_raw shpchp mei_me mei [11292.289977] lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi fjes video [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 4.10.0-22-generic #24-Ubuntu [11292.289996] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [11292.289997] Call Trace: [11292.290001] dump_stack+0x63/0x81 [11292.290003] __warn+0xcb/0xf0 [11292.290005] warn_slowpath_null+0x1d/0x20 [11292.290007] kthread_stop+0x102/0x110 [11292.290014] ath9k_rng_stop+0x1a/0x20 [ath9k] [11292.290018] ath9k_stop+0x3b/0x1d0 [ath9k] [11292.290036] drv_stop+0x33/0x100 [mac80211] [11292.290055] ieee80211_stop_device+0x43/0x50 [mac80211] [11292.290072] ieee80211_do_stop+0x55a/0x860 [mac80211] [11292.290075] ? _raw_spin_unlock_bh+0x1e/0x20 [11292.290077] ? dev_deactivate_many+0x205/0x240 [11292.290093] ieee80211_stop+0x1a/0x20 [mac80211] [11292.290096] __dev_close_many+0x99/0x100 [11292.290098] __dev_close+0x45/0x70 [11292.290100] __dev_change_flags+0x9d/0x160 [11292.290102] dev_change_flags+0x29/0x60 [11292.290104] do_setlink+0x338/0xd20 [11292.290107] ? load_balance+0x1b4/0xa00 [11292.290109] ? update_load_avg+0x6b/0x510 [11292.290112] ? dequeue_entity+0xed/0x420 [11292.290114] ? nla_parse+0x31/0x110 [11292.290115] rtnl_newlink+0x5c6/0x860 [11292.290118] ? lookup_fast+0x57/0x310 [11292.290121] ? security_capget+0x60/0x70 [11292.290123] ? ns_capable_common+0x68/0x80 [11292.290125] ? ns_capa
[Kernel-packages] [Bug 1697027] Re: ath9k freezes suspend resume Ubuntu 17.04
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697027 Title: ath9k freezes suspend resume Ubuntu 17.04 Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu Zesty Zapus Release: 17.04 What was expected to happen? I expected the laptop would suspend and resume without issues What happened instead? First the network fails, then all other programs slowly start to fail as well until the system freezes completely. The system is unable to shutdown and it requires a forced shutdown. Often when suspending my system, a recent upgrade to 17.04 from 16.10, after resuming the network does not work and then slowly the whole system freezes. Looking at dmesg, the problem seems to arise just before the system suspends with the kernel trace attached below. My best guess is that the issue is caused by ath9k. My system is a Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with 8GB of RAM and no swap) and it is often connected to a Dell U3011 monitor. I could not find other reports of this bug and this behaviour is new to 17.04, that is, it was not present in 16.10. I was always able to suspend and resume without issues before. I have been waiting to see bug 1674838 fixed before reporting this bug thinking that they might be related, but they are clearly independent as I am still having this suspend issue. Happy to try to collect more info if this information is not enough to understand where the problem lies, however it is impossible to run apport once the bug arises. [11292.289928] [ cut here ] [11292.289935] WARNING: CPU: 0 PID: 943 at /build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110 [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd input_leds joydev soundcore serio_raw shpchp mei_me mei [11292.289977] lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi fjes video [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 4.10.0-22-generic #24-Ubuntu [11292.289996] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [11292.289997] Call Trace: [11292.290001] dump_stack+0x63/0x81 [11292.290003] __warn+0xcb/0xf0 [11292.290005] warn_slowpath_null+0x1d/0x20 [11292.290007] kthread_stop+0x102/0x110 [11292.290014] ath9k_rng_stop+0x1a/0x20 [ath9k] [11292.290018] ath9k_stop+0x3b/0x1d0 [ath9k] [11292.290036] drv_stop+0x33/0x100 [mac80211] [11292.290055] ieee80211_stop_device+0x43/0x50 [mac80211] [11292.290072] ieee80211_do_stop+0x55a/0x860 [mac80211] [11292.290075] ? _raw_spin_unlock_bh+0x1e/0x20 [11292.290077] ? dev_deactivate_many+0x205/0x240 [11292.290093] ieee80211_stop+0x1a/0x20 [mac80211] [11292.290096] __dev_close_many+0x99/0x100 [11292.290098] __dev_close+0x45/0x70 [11292.290100] __dev_change_flags+0x9d/0x160 [11292.290102] dev_change_flags+0x29/0x60 [11292.290104] do_setlink+0x338/0xd20 [11292.290107] ? load_balance+0x1b4/0xa00 [11292.290109] ? update_load_avg+0x6b/0x510 [11292.290112] ? dequeue_entity+0xed/0x420 [11292.290114] ? nla_parse+0x31/0x110 [11292.290115] rtnl_newlink+0x5c6/0x860 [11292.290118] ? lookup_fast+0x57/0x310 [11292.290121] ? security_capget+0x60/0x70 [11292.290123] ? ns_capable_co
[Kernel-packages] [Bug 1696558] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1696558 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/1696558 Title: Enable CONFIG_SECURITY_DMESG_RESTRICT Status in linux package in Ubuntu: Incomplete Bug description: There is a request to enable the following for linux-aws. config SECURITY_DMESG_RESTRICT bool "Restrict unprivileged access to the kernel syslog" default n help This enforces restrictions on unprivileged users reading the kernel syslog via dmesg(8). If this option is not selected, no restrictions will be enforced unless the dmesg_restrict sysctl is explicitly set to (1). If you are unsure how to answer this question, answer N. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696531] Re: (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696531 Title: (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 Status in linux package in Ubuntu: Invalid Bug description: (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 (P)(a)(y)(p)(a)(l) Customer Service of Smart snake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical supportDial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Call US||!!1-800-208-0139||PayPal technical Support phone number 1-800-208-0139 ||PayPal customer support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number C@LL^^US=1^(800)^208^0139\\PayPal Support phone number 1-800-208-0139\\PayPal support number PayPal Customer Support 1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal
[Kernel-packages] [Bug 1696582] 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/1696582 Title: package linux-image-4.8.0-54-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Problemas sérios para abrir os aplicativos, principalmente o ubuntu store. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-54-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patricmmenezes 3924 F pulseaudio /dev/snd/controlC0: patricmmenezes 3924 F pulseaudio Date: Wed Jun 7 18:19:11 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=ea7984c1-307a-4b16-88fb-16ee3c9c155f InstallationDate: Installed on 2017-04-27 (41 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 3437 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic.efi.signed root=UUID=378296e0-4da7-408b-b80b-ebd59144c548 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.8.0-54-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to yakkety on 2017-04-28 (40 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 02TT83 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn02TT83:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696592] 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/1696592 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: I was installing an update from Ubuntu Software and the system freeze during this process. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: italo 1731 F pulseaudio Date: Wed Jun 7 18:12:10 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-22 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b128 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite L505 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=0b3b775f-906f-4a2f-a82b-513b3b7c96e0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd08/31/2010:svnTOSHIBA:pnSatelliteL505:pvrPSLU6U-00P009:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L505 dmi.product.version: PSLU6U-00P009 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659618] Re: Enable ARM64 support in kexec-tools
Yakkety verification: [ 77.450371] kexec_core: Starting new kernel [0.618716] kvm [1]: HYP mode not available [0.00] arch_timer: WARNING: Invalid trigger for IRQ3, assuming level low [0.00] arch_timer: WARNING: Please fix your firmware [0.00] arch_timer: cp15 timer(s) running at 20.00MHz (virt). [0.00] clocksource: arch_sys_counter: mask: 0xff max_cycles: 0x49cd42e20, max_idle_ns: 440795202120 ns [0.01] sched_clock: 56 bits at 20MHz, resolution 50ns, wraps every 4398046511100ns [0.31] vt handoff: transparent VT on vt#7 [0.39] Console: colour dummy device 80x25 [0.43] console [tty0] enabled [0.64] Calibrating delay loop (skipped), value calculated using timer frequency.. 40.00 BogoMIPS (lpj=8) [0.66] pid_max: default: 32768 minimum: 301 [0.000104] Security Framework initialized [0.000107] Yama: becoming mindful. [0.000126] AppArmor: AppArmor initialized [0.000236] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) [0.000344] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) [0.000387] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) [0.000392] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes) [0.000641] ftrace: allocating 33642 entries in 132 pages [0.065708] ASID allocator initialised with 65536 entries [0.066225] PCI/MSI: /intc/its domain created [0.066237] Platform MSI: /intc/its domain created [0.066307] Remapping and enabling EFI services. [0.066317] EFI remap 0x0400 => 2000 [0.066322] EFI remap 0x0901 => 2400 [0.066326] EFI remap 0x585f => 2401 [0.066330] EFI remap 0x5860 => 2402 [0.066333] EFI remap 0x586e => 240e [0.066339] EFI remap 0x5bc2 => 2415 [0.066346] EFI remap 0x5bdb => 242e [0.066429] smp: Bringing up secondary CPUs ... [0.066431] smp: Brought up 1 node, 1 CPU [0.066432] SMP: Total of 1 processors activated. [0.066434] CPU features: detected feature: GIC system register CPU interface [0.066436] CPU features: detected feature: Privileged Access Never [0.066451] CPU: All CPU(s) started at EL1 [0.066454] alternatives: patching kernel code [0.067989] devtmpfs: initialized [0.068605] evm: security.selinux [0.068606] evm: security.SMACK64 [0.068606] evm: security.SMACK64EXEC [0.068607] evm: security.SMACK64TRANSMUTE [0.068608] evm: security.SMACK64MMAP [0.068609] evm: security.ima [0.068610] evm: security.capability [0.068688] SMBIOS 3.0.0 present. [0.068692] DMI: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [0.068756] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns ** Tags removed: verification-failed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1659618 Title: Enable ARM64 support in kexec-tools Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Status in kexec-tools package in Debian: Fix Released Bug description: [IMPACT] * kexec-tools in Xenial (16.04) currently does not support ARM64 architecture. * Backport support for ARM64 arch from upstream https://github.com/horms/kexec-tools * Majority of the patches are contained in kexec/arch/arm64/ except for one patch that impacts purgatory and common device tree routines. [TEST CASE] * I built kexec-tools for ARM64 and tested it on HW using the following testcase: $ sudo kexec -l /boot/vmlinuz--generic --initrd=/boot/initrd.img--generic --command-line="root=UUID= ro vt.handoff=7" $ sudo kexec -e * I was able to kexec the new kernel successfully. * [ 6702.357899] kexec_core: Starting new kernel [0.00] Booting Linux on physical CPU 0x200 [0.00] Linux version -generic (buildd@bos01-arm64-008) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) [0.00] Boot CPU: AArch64 Processor [510f8000] [REGRESSION POTENTIAL] * Since patches are confined to arm[64] there is a low overall risk of regression. [OTHER INFO] * You can find a Xenial kexec-tools package built for AMD64, i386 and ARM64 in my PPA https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools * This package is built using the Xenial source package for kexec-tools with ARM64 enablement patches applied. * Please pull the changes from my PPA package and integrate into Ubuntu Xenial kexec-tools aft
[Kernel-packages] [Bug 1696754] 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/1696754 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: i am unable to install chrome via software centre. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veeky 1592 F pulseaudio Date: Thu Jun 8 19:21:09 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8ca4ad2c-22fc-49e0-b36a-f97ca0540e55 InstallationDate: Installed on 2017-06-05 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 8460p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=UUID=bd21ca2f-a01f-4be9-b74c-29947a60ed1b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: 5100283924 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696623] Re: macvtap creation issue using net namespaces
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1696623 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) Importance: Undecided => Medium ** Tags added: needs-bisect ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696623 Title: macvtap creation issue using net namespaces Status in linux package in Ubuntu: Incomplete Bug description: Hi there, There seems to be a bug when trying to create two macvtap links that are contained within different net namespaces. This is what I'm facing and, at the same time, the steps to reproduce the issue: 1 - Create two net namespaces: # root@rjz-nuc:~# ip netns add bng1 root@rjz-nuc:~# ip netns add bng2 2 - Create two veth links, one in one net NS and another one in the other net NS: # root@rjz-nuc:~# ip link add netns bng1 bng1-111_veth type veth peer name subs-lg111_veth root@rjz-nuc:~# ip link add netns bng2 bng2-111_veth type veth peer name subs-lg211_veth 3a - Add a macvtap link on top of the 1st veth in the 1st net NS: # root@rjz-nuc:~# ip netns exec bng1 ip link add link bng1-111_veth name bng1-111_mcvtp type macvtap mode passthru 3b - This executes correctly and creates a tap device: # root@rjz-nuc:~# ip netns exec bng1 ip link show bng1-111_mcvtp 3: bng1-111_mcvtp@bng1-111_veth: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500 link/ether ae:c6:bc:d8:d2:e7 brd ff:ff:ff:ff:ff:ff 3c - Note the "3:" at the beginning of above output pointing to "tap3" that the command created: # root@rjz-nuc:~# ls -tral /dev/tap* crw--- 1 root root 241, 1 Jun 7 20:16 /dev/tap3 4a - Try to add another macvtap link but now on top of the 1st veth in the 2nd net NS: # root@rjz-nuc:~# ip netns exec bng2 ip link add link bng2-111_veth name bng2-111_mcvtp type macvtap mode passthru RTNETLINK answers: File exists 4b - As it can be seen, it fails stating "file exists". Checking the output of "dmesg", it can be seen the reason behind this is that instead of choosing as the tap device the next system-wide free one (for instance, say, tap4) it chooses the "tap3" that was already created by the command in step 3a above: # [Jun 7 20:17] [ cut here ] [ +0.32] WARNING: CPU: 3 PID: 1216 at /build/linux-As38az/linux-4.4.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80() [ +0.07] sysfs: cannot create duplicate filename '/class/macvtap/tap3' [ +0.05] Modules linked in: macvtap macvlan veth drbg ansi_cprng ctr ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp espaf_key xfrm_algo arc4 snd_hda_codec_hdmi 8250_dw snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec inte iwlmvm snd_hda_core x86_pkg_temp_thermal intel_powerclamp coretemp snd_hwdep crct10dif_pclmul mac80211 snd_pcm crc32_pclmul ghash_i_intel snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi glue_helper ablk_helper iwlwifi cryptd snd_put_leds snd_seq_device serio_raw cfg80211 snd_timer snd ir_lirc_codec soundcore lirc_dev ir_xmp_decoder ir_mce_kbd_decoder [ +0.000149] ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder btusb hci_uart btrtl btbcm ir_rc5_debtqca ir_nec_decoder idma64 virt_dma mei_me shpchp mei btintel intel_lpss_pci bluetooth rc_rc6_mce ite_cir rc_core intel_lpss_acpi ad mac_hid acpi_als intel_lpss kfifo_buf industrialio kvm_intel kvm irqbypass autofs4 i915_bpo intel_ips i2c_algo_bit drm_kms_helpe0e syscopyarea sysfillrect sysimgblt ptp sdhci_pci fb_sys_fops pps_core drm sdhci ahci libahci video pinctrl_sunrisepoint i2c_hid p_intel hid fjes [ +0.000124] CPU: 3 PID: 1216 Comm: ip Not tainted 4.4.0-79-generic #100-Ubuntu [ +0.07] Hardware name: /NUC6i3SYB, BIOS SYSKLi35.86A.0024.2015.1027.2142 10/27/2015 [ +0.06] 0286 ffea66e1 88083a5ef5b8 813f94d3 [ +0.13] 88083a5ef600 81ce3010 88083a5ef5f0 81081322 [ +0.11] 88083a56c000 88083c212900 88083a5fbca8 88083a5fbca8 [ +0.11] Call Trace: [ +0.17] [] dump_stack+0x63/0x90 [ +0.15] [] warn_slowpath_commo
[Kernel-packages] [Bug 1696624] 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/1696624 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Meu sistema tem travado bastante ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adsjcsp1313 F pulseaudio Date: Wed Jun 7 21:46:33 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-21 (17 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 4745 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=fa3e2149-d2c8-40e6-9c9a-d2dcb815343b ro locale=pt_BR quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZQ1 dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.18:bd08/10/2010:svnAcer:pnAspire4745:pvrV1.18:rvnAcer:rnZQ1:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 4745 dmi.product.version: V1.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696811] 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/1696811 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Hello! Package did not install, and also the OS Updates are not installing (using Ubuntu Software section/app). I'm new to linux, so sorry for not providing further informations. Thank you! Regards, Valeriu ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: valeriu1429 F pulseaudio Date: Thu Jun 8 20:34:39 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (6 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20157 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=fcc764c7-bbad-4d93-95a9-0f8ef72c84aa ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN44WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN44WW:bd02/01/2013:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 20157 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696610] 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/1696610 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: I simply booted up ubuntu and began to run skype for linux beta and firefox when a message appeared saying that the package manager was broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nathan 2004 F pulseaudio /dev/snd/controlC1: nathan 2004 F pulseaudio Date: Tue Jun 6 17:34:39 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=28170f57-1728-432b-ba14-ebf0ee280ac7 InstallationDate: Installed on 2017-05-22 (16 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: MSI MS-7817 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux StagingDrivers: r8188eu Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-05-22 (16 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E34 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.5:bd03/30/2015:svnMSI:pnMS-7817:pvr3.0:rvnMSI:rnH81M-E34(MS-7817):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7817 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696603] 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/1696603 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: using update via ubuntu software ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1805 F pulseaudio /dev/snd/controlC1: dan1805 F pulseaudio Date: Wed Jun 7 23:42:03 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=4dcdcfe5-4711-4e3b-9ffa-505193601afb InstallationDate: Installed on 2017-05-28 (10 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire V3-772 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=0f82e32c-7487-4927-b57a-37954469dbcf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA70_HW dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd03/07/2014:svnAcer:pnAspireV3-772:pvrV1.15:rvnAcer:rnVA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-772 dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696673] 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/1696673 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: idk ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: at0m1que 1733 F pulseaudio /dev/snd/controlC0: at0m1que 1733 F pulseaudio Date: Wed Jun 7 21:05:55 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=30cb6637-b58b-4a1e-9abc-3e3d425029ff InstallationDate: Installed on 2017-04-19 (49 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: MSI MS-7693 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=a830e8e1-6eeb-4b40-b216-b4939aacf5d2 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.3:bd03/28/2013:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7693 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696651] 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/1696651 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: I downloaded OS updates and shut down. Next boot I got this error message. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doctorwu 1693 F pulseaudio Date: Wed Jun 7 22:01:41 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-19 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E402SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=29feef4a-96ae-4680-bdca-76622ff6a7ac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA 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.:bvrE402SA.209:bd02/22/2016:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E402SA 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/1696651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696770] 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/1696770 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Tá muito ruim meu computador não atualizar diariamente quando vem atualização elas não instalam por favor der um jeito nisso, Obrigado! ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anonymous 1953 F pulseaudio /dev/snd/controlC1: anonymous 1953 F pulseaudio Date: Thu Jun 8 11:02:01 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-19 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=c628a0b6-7b2e-47f6-8eca-f6cb2c3bb728 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M4Y41 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd07/12/2016:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn0M4Y41:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696859] 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/1696859 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnybegood 1415 F pulseaudio /dev/snd/controlC1: johnnybegood 1415 F pulseaudio Date: Wed Jun 7 06:52:02 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8e8fcdb0-767f-4fa7-a8e3-e06bf12ae742 InstallationDate: Installed on 2017-04-15 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=9056280d-1b43-47b6-b5ed-5b796780a968 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M77 Ver. 01.14 dmi.board.name: 2271 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.50 dmi.chassis.asset.tag: 5CG5517PNY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM77Ver.01.14:bd09/26/2016:svnHewlett-Packard:pnHPEliteBookFolio1020G1:pvrA3009FD18303:rvnHewlett-Packard:rn2271:rvrKBCVersion91.50:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1020 G1 dmi.product.version: A3009FD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695989] Re: i915 *ERROR* CPU pipe A FIFO underrun - graphic glitches
Hi Chris (penalvch) Kernel 4.12rc1 and rc4 are both fine in terms of the bug and seem to run very smoothly, but the 4.11rc1, 4.11.1, 4.11.3 all show the bug (and I have seen them crash HARD, not just screen glitches). I havent yet gone back through 4.10 yet to find the first 'bad' kernel. Can you confirm that the following Ubuntu kernels correlate to the upstream as follows? 4.10.0-22.24 is equivalent to 4.10.15 mainline 4.10.0-21.23 is equivalent to 4.10.11 mainline 4.10.0-19.21 is equivalent to 4.10.8 mainline Ubuntu -19 kernel is the first one i saw on my 17.04 install, which did show the bug. Where would you suggest going back to? I dont have any experience with git so am not sure I can dig deeper to find the bad commit, I'm afraid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695989 Title: i915 *ERROR* CPU pipe A FIFO underrun - graphic glitches Status in linux package in Ubuntu: Incomplete Bug description: 17.04 Ubuntu Gnome with default kernel. Seeing black bars flash on screen, sometimes whole screen goes black. Easily reproduced by having the Gnome Terminal app on the lower part of the screen. Often so bad that the laptop locks up (screen goes black and shuts off without warning after a few seconds). dmesg is full of the "CPU pipe A FIFO underrun" errors. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1632 F pulseaudio CurrentDesktop: GNOME Date: Mon Jun 5 21:16:06 2017 InstallationDate: Installed on 2017-05-03 (33 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude E4310 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=fad75c7e-4ba7-49fd-95c6-dc5d2446b31b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/26/2011:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697019] Re: YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697019 Title: YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) Status in linux package in Ubuntu: Invalid Bug description: YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)((BAHUBALI2))PayPal Customer Support +1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal call center,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,contacting PayPal,PayPal support phone number,PayPal tech support number,contact PayPal phone number,PayPal contact email,PayPal help page,PayPal customer care,help PayPal,call PayPal support,PayPal contact phone number,contact PayPal phone,call PayPal customer service,how to contact PayPal support,PayPal phone support,phone number PayPal,email PayPal support,PayPal helpline phone number,help with PayPal,how to contact PayPal by phone,contacting PayPal by phone,telephone number for PayPal,how can i contact PayPal,customer service PayPal,PayPal customer support number,PayPal technical support phone number,PayPal 1800 number,phone number to PayPal,PayPal technical support number,PayPal help center number,PayPal contact information,PayPal email support,PayPal hotline number,PayPal phone numbers,PayPal support contact,phone number for PayPa l help center,call PayPal help,how to contact PayPal directly,PayPal tech support phone number,PayPal customer service live chat,contact PayPal by email,customer service number for PayPal,how can i contact PayPal by phone,contact PayPal directly,can i call PayPal,PayPal customer support team,PayPal help contact,number to PayPal,number for PayPal,support PayPal,PayPal.com phone number,PayPal help desk,PayPal customer support phone number,phone number for PayPal support,PayPal headquarters phone number,PayPal support team,PayPal help desk phone number,PayPal support chat,customer service for PayPal,PayPal company phone number,PayPal service number,PayPal email contact,PayPal customer service phone,phone number for PayPal help,PayPal help contact number,PayPal online support,phone number to contact PayPal,contact phone number for PayPal,PayPal live help,contact PayPal number,PayPal number to call,contact PayPal customer support,phone number for PayPal customer service,email PayPal help ,contacting PayPal support,PayPal live support,PayPal customer support email,how to email PayPal support,call PayPal for help,call PayPal help center,PayPal phone number customer service,contact information for PayPal,PayPal contact support,contact PayPal help,customer service phone number for PayPal,contact PayPal team,PayPal custmer service telephone number,PayPal by phone number,can you call PayPal,how to get in touch with PayPal,PayPal 1 800 number,PayPal security phone number,contact fb,help center PayPal,fb phone number,contact PayPal support phone,ph
[Kernel-packages] [Bug 1696980] Re: ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696980 Title: ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 Status in linux package in Ubuntu: Invalid Bug description: ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139 ~$%MUN@++18002080139 magicjack customer service1-800-208-0139how does magicjack phone service work1-800-208-0139magicjack voip phone,1-800-208-0139 magic jack voip, voip magicjack,1-800-208-0139 magicjack voip,1-800-208-0139 voip jack, magicjack voip phones1-800-208-0139, jack voip, voip magic Magicjack Sign (10)1-800-208-0139 sign up for magicjack app,1-800-208-0139 sign up for magicjack,1-800-208-0139 magicjack sign up, magicjack app sign up, sign up magicjack app, magicjack sign in, sign up magicjack, sign up for free magicjack account, magicjack free calls sign up, sign up for magicjack free Magicjack Telephone (9) magicjack telephone number, magicjack telephone number for customer service, magicjack telephone, magicjack support telephone number, magicjack telephone number customer service, telephone number for magicjack customer service,1-800-208-0139 telephone number for magicjack, telephone magicjack1-800-208-0139, magicjack plus customer service telephon e number Jack International (14) magic jack international rates, magic jack international, magic jack free international calls, magic jack international calls free, magic jack international calling, can magic jack make international calls, magic jack free international phone calls, magic jack free call international, magic jack phone international calls, magic jack international free, magic jack reviews international calls, magic jack free international calling, magic jack plus free international calls, magic jack international call Magicjack Pc (7) magicjack app for pc, magicjack for pc, magicMagic Customer (58) magic jack customer service, magic jack customer service phone number, magic jack customer service number, magic jack customer care, magic jack.com customer care, magic jack customer service phone number 1800, magic jack plus customer service, magic jack customer service phone, magic jack customer support, magic jack.com customer service, magic jack customer service toll free number, magic jack customer, magic jack phone number customer service, magic jack customer care number, magic jack customer service telephone number, magic jack customer service number 1800, magic jack customer support phone number, magic jack customer service toll free phone number, customer care magic jack, magic jet customer… Magicjack Service (32) magicjack customer service, magicjack phone number customer service, magicjack.com customer service, magicjack plus customer service, customer service magicjack, my magicjack.com customer service, magicjack 1800 number customer service, magicjack customer service phone number, magicjack phone service, customer service for magicjack, magicjack customer service number, phone number for magicjack customer service, magicjack plus customer service phone number, customer service number for magicjack, magicjack.com customer service phone number, magicjack customers services phone number, magicjack toll free customer service, magicjack service, magicjack phone number for customer service, customer service magicjack phone number… Jack Review (23) magic jack reviews, magic jack plus reviews, magic jack review, magic jack consumer reviews, magic jack reviews 2013, magic jack phone service reviews, magic jack phone reviews, reviews on magic jack, reviews on magic jack phone service, reviews for magic jack, review magic jack, reviews for magic jack plus, magic jack plus reviews 2013, reviews on magic jack plus, magic jack plus review, magic jack plus reviews consumer reports, magic jack.com reviews, reviews on magic jack plus phone service, reviews magic jack plus, reviews magic jack… Magicjack Phone (35) magicjack phone number, magicjack phone, magicjack home phone, magicjack support phone number, phone number for magicjack, magicjack.com phone number, magicjack phone numbers, magicjack voip p
[Kernel-packages] [Bug 1697015] Re: *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697015 Title: *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician Status in linux package in Ubuntu: Invalid Bug description: *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician*&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician ((BAHUBALI2))PayPal Customer Support +1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal call center,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,contacting PayPal,PayPal support phone number,PayPal tech support number,contact PayPal phone number,PayPal contact email,PayPal help page,PayPal customer care,help PayPal,call PayPal support,PayPal contact phone number,contact PayPal phone,call PayPal customer service,how to contact PayPal support,PayPal phone support,phone number PayPal,email PayPal support,PayPal helpline phone number,help with PayPal,how to contact PayPal by phone,contacting PayPal by phone,telephone number for PayPal,how can i contact PayPal,customer service PayPal,PayPal customer support number,PayPal technical support phone number,PayPal 1800 number,phone number to PayPal,PayPal technical support number,PayPal help center number,PayPal contact information,PayPal email support,PayPal hotline number,PayPal phone numbers,PayPal support contact,phone number for PayPa l help center,call PayPal help,how to contact PayPal directly,PayPal tech support phone number,PayPal customer service live chat,contact PayPal by email,customer service number for PayPal,how can i contact PayPal by phone,contact PayPal directly,can i call PayPal,PayPal customer support team,PayPal help contact,number to PayPal,number for PayPal,support PayPal,PayPal.com phone number,PayPal help desk,PayPal customer support phone number,phone number for PayPal support,PayPal headquarters phone number,PayPal support team,PayPal help desk phone number,PayPal support chat,customer service for PayPal,PayPal company phone number,PayPal service number,PayPal email contact,PayPal customer service phone,phone number for PayPal help,PayPal help contact number,PayPal online support,phone number to contact PayPal,contact phone number for PayPal,PayPal live help,contact PayPal number,PayPal number to call,contact PayPal customer support,phone number for PayPal customer service,email PayPal help ,contacting PayPal support,PayPal live support,PayPal customer support email,how to email PayPal support,call PayPal for help,call PayPal help center,PayPal phone number customer service,contact information for PayPal,PayPal contact support,contact
[Kernel-packages] [Bug 1697012] Re: $!%ERVICE paypal 1?800"208"0139customer service phone number""""1?800"208"0139"PayPal help desk phone number
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697012 Title: $!%ERVICE paypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number Status in linux package in Ubuntu: Invalid Bug description: $!%*E*R*V*IC*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number$!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical supportDial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Call US||!!1-800-208-0139||PayPal technical Support phone number 1-800-208-0139 ||PayPal customer support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number Call US||11-800-208-0139||PayPal Support phone number 1-800-208-0139||PayPal support number PayPal Customer Support 1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal call c enter,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,co
[Kernel-packages] [Bug 1697022] Re: linux: 4.11.0-6.11 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-development-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-development-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Description changed: This bug is for tracking the 4.11.0-6.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-phase:Packaging - kernel-phase-changed:Friday, 09. June 2017 16:04 UTC - -- swm properties -- phase: Packaging + kernel-phase-changed:Friday, 09. June 2017 17:04 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.11.0-6.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 -- swm properties -- - phase: Packaging - kernel-phase-changed:Friday, 09. June 2017 17:04 UTC - kernel-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697022 Title: linux: 4.11.0-6.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New 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: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-6.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 -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1697022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Update for those not following my other bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695989) I found the bug in all the 4.11 and 4.10, but not 4.12rc1 or 4.12rc4. NOTE - @Jochen - I dont see the FIFO underrun error while running the 4.12 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Kernel-packages] [Bug 1696840] Re: m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696840 Title: m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number Status in linux package in Ubuntu: Invalid Bug description: m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number m@g*ic*ja*ck phone 18002080139 number customer service1-800-208-0139magicjack 1800 number magicjack voip phone,1-800-208-0139 magic jack voip, voip magicjack,1-800-208-0139 magicjack voip,1-800-208-0139 voip jack, magicjack voip phones1-800-208-0139, jack voip, voip magic Magicjack Sign (10)1-800-208-0139 sign up for magicjack app,1-800-208-0139 sign up for magicjack,1-800-208-0139 magicjack sign up, magicjack app sign up, sign up magicjack app, magicjack sign in, sign up magicjack, sign up for free magicjack account, magicjack free calls sign up, sign up for magicjack free Magicjack Telephone (9) magicjack telephone number, magicjack telephone number for customer service, magicjack telephone, magicjack support telephone number, magicjack telephone number customer service, telephone number for magicjack customer service,1-800-208-0139 telephone number for magicjack, telephone magicjack1-800-208-0139, magicjack plus customer service telephon e number Jack International (14) magic jack international rates, magic jack international, magic jack free international calls, magic jack international calls free, magic jack international calling, can magic jack make international calls, magic jack free international phone calls, magic jack free call international, magic jack phone international calls, magic jack international free, magic jack reviews international calls, magic jack free international calling, magic jack plus free international calls, magic jack international call Magicjack Pc (7) magicjack app for pc, magicjack for pc, magicMagic Customer (58) magic jack customer service, magic jack customer service phone number, magic jack customer service number, magic jack customer care, magic jack.com customer care, magic jack customer service phone number 1800, magic jack plus customer service, magic jack customer service phone, magic jack customer support, magic jack.com customer service, magic jack customer service toll free number, magic jack customer, magic jack phone number customer service, magic jack customer care number, magic jack customer service telephone number, magic jack customer service number 1800, magic jack customer support phone number, magic jack customer service toll free phone number, customer care magic jack, magic jet customer… Magicjack Service (32) magicjack customer service, magicjack phone number customer service, magicjack.com customer service, magicjack plus customer service, customer service magicjack, my magicjack.com customer service, magicjack 1800 number customer service, magicjack customer service phone number, magicjack phone service, customer service for magicjack, magicjack customer service number, phone number for magicjack customer service, magicjack plus customer service phone number, customer service number for magicjack, magicjack.com customer service phone number, magicjack customers services phone number, magicjack toll free customer service, magicjack service, magicjack phone number for customer service, customer service magicjack phone number… Jack Review (23) magic jack reviews, magic jack plus reviews, magic jack review, magic jack consumer reviews, magic jack reviews 2013, magic jack phone service reviews, magic jack phone reviews, reviews on magic jack, reviews on magic jack phone service, reviews for magic jack, review magic jack, reviews for magic jack plus, magic jack plus reviews 2013, reviews on magic jack plus, magic jack plus review, magic jack plus reviews consumer reports, magic jack.com reviews, reviews on magic jack plus phone service, reviews magic jack plus, reviews magic jack… Magicjack Phone (35) magicjack phone number, magicjack phone, magicjack home phone, magicjack support phone number, phone number for magicjack, magicjack.com phone number, magicjack phone numbers, magicjack voip phone, magicjack technical support phone number, phone for magicjack, magicjack Live $upporT @1-800-208-0139@ MAGIC JACK MAIL tech support number, MAGIC JACK MAI
[Kernel-packages] [Bug 1697038] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697038 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Can not update software. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1166 F pulseaudio kishalay 1636 F pulseaudio Date: Fri Jun 9 22:10:47 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-16 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp0s29f7u2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=62b6b6a2-c6e3-4310-82cf-7f262837d942 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM/PS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 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.:bvr0309:bd09/08/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697038] [NEW] package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Can not update software. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1166 F pulseaudio kishalay 1636 F pulseaudio Date: Fri Jun 9 22:10:47 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-16 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp0s29f7u2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=62b6b6a2-c6e3-4310-82cf-7f262837d942 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM/PS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 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.:bvr0309:bd09/08/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697038 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Can not update software. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1166 F pulseaudio kishalay 1636 F pulseaudio Date: Fri Jun 9 22:10:47 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-16 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp0s29f7u2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=62b6b6a2-c6e3-4310-82cf-7f262837d942 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM/PS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 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.:bvr0309:bd09/08/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad
[Kernel-packages] [Bug 1614789] Re: zfs.target should not require zfs-share.service
** Tags removed: verification-done ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1614789 Title: zfs.target should not require zfs-share.service Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Xenial: Fix Committed Bug description: == SRU Xenial == [Justification] Currently package zfsutils-linux contains systemd target file /lib/systemd/system/zfs.target that specifies following dependencies: Requires=zfs-mount.service Requires=zfs-share.service Wants=zed.service zfs-share.service is not essential in setups where file sharing is not used, or when it is configured without the use of the zfs utility. The user may therefore choose to mask this service. However, doing so has an unexpected and confusing effect, preventing zfs from starting on boot at all. This is because zfs.target is the only zfs-related unit that is wanted by multi-user.target, and if one of its required services is masked, zfs.target is skipped, together with zfs- mount.service. A solution is to replace "Requires=zfs-share.service" with "Wants=zfs-share.service". [Testcase] Steps to reproduce: systemctl mask zfs-share.service reboot Expected results: Module zfs is loaded zfs-mount.service is active and ZFS filesystems are mounted ZFS filesystems are not shared Observed results: Module zfs is not loaded ZFS filesystems are not mounted zpool status produces an error: "The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them." With the fix, the modules are loaded and zfs filesystems are mounted [Fix] A solution is to replace "Requires=zfs-share.service" with "Wants=zfs-share.service". [Regression Potential] Minimal, this affects the start up of a service that should be starting and currently isn't. Limited to just this specific scenario. - $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686815] Re: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04
** Tags removed: verification-done ** Tags added: verification-done-xenial -- 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/1686815 Title: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Missing firmware causes Intel 8265 wireless to not work in 16.04.2 installs on new hardware. Fix: Backport upstream linux-firmware commits to add the firmware and subsequent changes which fix some issues with the firmware. Regression Potential: The bug fix commits also fix the same issue in another Intel bluetooth firmware file. Regressions are possible but not expected since it's a bug fix update. Test Case: This is difficult to test since the bluetooth module only fails to work if it has never had firmware loaded to it previously. Three different users have confirmed that the test package fixed the issue. --- Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265 wireless modules that haven't yet had firmware loaded onto them. dmesg reports the following: Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2 This could be difficult for many people to reproduce, since installing a later version of Ubuntu once will load the necessary firmware, which will persist through reinstalling the operating system. So installing Ubuntu 17.04 just once, will leave Bluetooth in a working state forever. I was able to consistently produce the issue on a *brand new* Kabylake Meerkat 3. With Ubuntu 16.04.2, bluetooth didn't work. I copied the ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted. After this point, Bluetooth worked (and continued to work after reinstalling Ubuntu 16.04.2 and *not* copying the firmware files again). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1686815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695989] Re: i915 *ERROR* CPU pipe A FIFO underrun - graphic glitches
** Tags added: kernel-bug-exists-upstream-4.11.0rc1 kernel-bug-exists- upstream-4.11.1 kernel-bug-exists-upstream-4.11.3 kernel-fixed- upstream-4.12.0rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695989 Title: i915 *ERROR* CPU pipe A FIFO underrun - graphic glitches Status in linux package in Ubuntu: Incomplete Bug description: 17.04 Ubuntu Gnome with default kernel. Seeing black bars flash on screen, sometimes whole screen goes black. Easily reproduced by having the Gnome Terminal app on the lower part of the screen. Often so bad that the laptop locks up (screen goes black and shuts off without warning after a few seconds). dmesg is full of the "CPU pipe A FIFO underrun" errors. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1632 F pulseaudio CurrentDesktop: GNOME Date: Mon Jun 5 21:16:06 2017 InstallationDate: Installed on 2017-05-03 (33 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude E4310 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=fad75c7e-4ba7-49fd-95c6-dc5d2446b31b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/26/2011:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697027] Re: ath9k freezes suspend resume Ubuntu 17.04
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697027 Title: ath9k freezes suspend resume Ubuntu 17.04 Status in linux package in Ubuntu: New Bug description: Description: Ubuntu Zesty Zapus Release: 17.04 What was expected to happen? I expected the laptop would suspend and resume without issues What happened instead? First the network fails, then all other programs slowly start to fail as well until the system freezes completely. The system is unable to shutdown and it requires a forced shutdown. Often when suspending my system, a recent upgrade to 17.04 from 16.10, after resuming the network does not work and then slowly the whole system freezes. Looking at dmesg, the problem seems to arise just before the system suspends with the kernel trace attached below. My best guess is that the issue is caused by ath9k. My system is a Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with 8GB of RAM and no swap) and it is often connected to a Dell U3011 monitor. I could not find other reports of this bug and this behaviour is new to 17.04, that is, it was not present in 16.10. I was always able to suspend and resume without issues before. I have been waiting to see bug 1674838 fixed before reporting this bug thinking that they might be related, but they are clearly independent as I am still having this suspend issue. Happy to try to collect more info if this information is not enough to understand where the problem lies, however it is impossible to run apport once the bug arises. [11292.289928] [ cut here ] [11292.289935] WARNING: CPU: 0 PID: 943 at /build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110 [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd input_leds joydev soundcore serio_raw shpchp mei_me mei [11292.289977] lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi fjes video [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 4.10.0-22-generic #24-Ubuntu [11292.289996] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [11292.289997] Call Trace: [11292.290001] dump_stack+0x63/0x81 [11292.290003] __warn+0xcb/0xf0 [11292.290005] warn_slowpath_null+0x1d/0x20 [11292.290007] kthread_stop+0x102/0x110 [11292.290014] ath9k_rng_stop+0x1a/0x20 [ath9k] [11292.290018] ath9k_stop+0x3b/0x1d0 [ath9k] [11292.290036] drv_stop+0x33/0x100 [mac80211] [11292.290055] ieee80211_stop_device+0x43/0x50 [mac80211] [11292.290072] ieee80211_do_stop+0x55a/0x860 [mac80211] [11292.290075] ? _raw_spin_unlock_bh+0x1e/0x20 [11292.290077] ? dev_deactivate_many+0x205/0x240 [11292.290093] ieee80211_stop+0x1a/0x20 [mac80211] [11292.290096] __dev_close_many+0x99/0x100 [11292.290098] __dev_close+0x45/0x70 [11292.290100] __dev_change_flags+0x9d/0x160 [11292.290102] dev_change_flags+0x29/0x60 [11292.290104] do_setlink+0x338/0xd20 [11292.290107] ? load_balance+0x1b4/0xa00 [11292.290109] ? update_load_avg+0x6b/0x510 [11292.290112] ? dequeue_entity+0xed/0x420 [11292.290114] ? nla_parse+0x31/0x110 [11292.290115] rtnl_newlink+0x5c6/0x860 [11292.290118] ? lookup_fast+0x57/0x310 [11292.290121] ? security_capget+0x60/0x70 [11292.290123] ? ns_capable_common+0x68/0x80 [11292.290125] ? ns_capable+0x13/0x20 [11292.290127] rtnetlink_rcv_msg+0xe6/0x210 [11292.290130] ? __kmalloc_node_track_caller+0x1f0/0x2a0 [11292.290133] ? __alloc_skb+0x87/0x1e0 [11292.290135] ? rtnl_newlink+0x860/0x860 [11292.290137] netlink_rcv_skb+0xa4/0xc0 [11292.290138] rtnetlink_rcv+0x28/0x30 [11292.290140] netlink_unicast+0x18c/0x220 [11292.290141] netlink_sendmsg+0x2f7/0x3b0 [11292.290144] ? aa_sock_msg_perm+0x61/0x150 [11292.290146] sock_sendmsg+0x38/0x50 [11292.290148] ___sys_sendmsg+0x2c2/0x2d0 [11292.290149] ? try_to_wake_up+0x59/0x3e0 [11292.290152] ? up
[Kernel-packages] [Bug 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks
** Tags removed: verification-done ** Tags added: verification-done-trusty -- 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/1498074 Title: Package is not being installed if you install from a usb pendrive created from disks Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: WORKAROUND: The issue here is that the driver is not able to be automatically installed, you can however install it manually. From the usbkey used to install the system copy the following files to your home directory: Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb Ubuntu 15.10 amd64/pool/restricted/b/bcmwl bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb Now open terminal and from the home directory run sudo dpkg -i dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom- 0ubuntu6_amd64.deb You should see a message to say networks available from the network- indicator and then be able to connect to wifi. STEPS: Pre-requisite: Laptop with bcmwl supported chipset, intel based macs or dell xps for example. 1. Grab the latest 15.10 daily image from cdimages 2. Plug a usb pendrive into the system 3. Open Disks 4. Format the pendrive 5. Select restore image to drive 6. Select the image you just downloaded 7. Click on okay if the install is happening on the pendrive 8. Click on okay again to confirm 9. Add the user password for permission to write to the drive 10. Insert the written image into the laptop you want to install on 11. In the uefi menu select the pendrive 12. Select the live session 13. Open system settings 14. Open Software and updates 15. Tap on the Additional Drivers tab EXPECTED: I expect to the bcmwl driver available to install ACTUAL: I see only micro code driver for the cpu (see screenshot) Included files: Screenshot /etc/apt/sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1498074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697027] [NEW] ath9k freezes suspend resume Ubuntu 17.04
You have been subscribed to a public bug: Description: Ubuntu Zesty Zapus Release: 17.04 What was expected to happen? I expected the laptop would suspend and resume without issues What happened instead? First the network fails, then all other programs slowly start to fail as well until the system freezes completely. The system is unable to shutdown and it requires a forced shutdown. Often when suspending my system, a recent upgrade to 17.04 from 16.10, after resuming the network does not work and then slowly the whole system freezes. Looking at dmesg, the problem seems to arise just before the system suspends with the kernel trace attached below. My best guess is that the issue is caused by ath9k. My system is a Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with 8GB of RAM and no swap) and it is often connected to a Dell U3011 monitor. I could not find other reports of this bug and this behaviour is new to 17.04, that is, it was not present in 16.10. I was always able to suspend and resume without issues before. I have been waiting to see bug 1674838 fixed before reporting this bug thinking that they might be related, but they are clearly independent as I am still having this suspend issue. Happy to try to collect more info if this information is not enough to understand where the problem lies, however it is impossible to run apport once the bug arises. [11292.289928] [ cut here ] [11292.289935] WARNING: CPU: 0 PID: 943 at /build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110 [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd input_leds joydev soundcore serio_raw shpchp mei_me mei [11292.289977] lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi fjes video [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 4.10.0-22-generic #24-Ubuntu [11292.289996] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [11292.289997] Call Trace: [11292.290001] dump_stack+0x63/0x81 [11292.290003] __warn+0xcb/0xf0 [11292.290005] warn_slowpath_null+0x1d/0x20 [11292.290007] kthread_stop+0x102/0x110 [11292.290014] ath9k_rng_stop+0x1a/0x20 [ath9k] [11292.290018] ath9k_stop+0x3b/0x1d0 [ath9k] [11292.290036] drv_stop+0x33/0x100 [mac80211] [11292.290055] ieee80211_stop_device+0x43/0x50 [mac80211] [11292.290072] ieee80211_do_stop+0x55a/0x860 [mac80211] [11292.290075] ? _raw_spin_unlock_bh+0x1e/0x20 [11292.290077] ? dev_deactivate_many+0x205/0x240 [11292.290093] ieee80211_stop+0x1a/0x20 [mac80211] [11292.290096] __dev_close_many+0x99/0x100 [11292.290098] __dev_close+0x45/0x70 [11292.290100] __dev_change_flags+0x9d/0x160 [11292.290102] dev_change_flags+0x29/0x60 [11292.290104] do_setlink+0x338/0xd20 [11292.290107] ? load_balance+0x1b4/0xa00 [11292.290109] ? update_load_avg+0x6b/0x510 [11292.290112] ? dequeue_entity+0xed/0x420 [11292.290114] ? nla_parse+0x31/0x110 [11292.290115] rtnl_newlink+0x5c6/0x860 [11292.290118] ? lookup_fast+0x57/0x310 [11292.290121] ? security_capget+0x60/0x70 [11292.290123] ? ns_capable_common+0x68/0x80 [11292.290125] ? ns_capable+0x13/0x20 [11292.290127] rtnetlink_rcv_msg+0xe6/0x210 [11292.290130] ? __kmalloc_node_track_caller+0x1f0/0x2a0 [11292.290133] ? __alloc_skb+0x87/0x1e0 [11292.290135] ? rtnl_newlink+0x860/0x860 [11292.290137] netlink_rcv_skb+0xa4/0xc0 [11292.290138] rtnetlink_rcv+0x28/0x30 [11292.290140] netlink_unicast+0x18c/0x220 [11292.290141] netlink_sendmsg+0x2f7/0x3b0 [11292.290144] ? aa_sock_msg_perm+0x61/0x150 [11292.290146] sock_sendmsg+0x38/0x50 [11292.290148] ___sys_sendmsg+0x2c2/0x2d0 [11292.290149] ? try_to_wake_up+0x59/0x3e0 [11292.290152] ? update_load_avg+0x6b/0x510 [11292.290154] ? update_load_avg+0x6b/0x510 [11292.290156] ? set_next_entity+0xc3/0x1b0 [11292.290157] ? pick_next_task_fair+0x47a/0x4b0 [11292.290160] ? __switch_to+0x23c/0x520 [11292.290162] ? __fget_light+0x25/0x60 [11292.290164] __sys_sendmsg+0x54/0x90 [11292.290166] SyS_sendmsg+0x12/0x20 [11292.290168] entry_SYSCALL_64_fastpath+0x1e/0xad [11292.290169] RIP: 0033:0x7f6e2e5fb460
[Kernel-packages] [Bug 1661363] Re: Fails to load compressed kernels on arm64
I don't see any mention of 16.10 being tested - switching to 'only xenial tested'. ** Tags removed: verification-done ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1661363 Title: Fails to load compressed kernels on arm64 Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Bug description: [Impact] kexec-tools will not load a compressed kernel on arm64. Ubuntu ships compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 16.04). A workaround is to manually decompress the kernel before loading it, but this is not supported by the use-kexec-for-reboot-by-default feature of the kexec-tools package. [Test Case] ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from Unix ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image arch_process_options:141: command_line: (null) arch_process_options:143: initrd: (null) arch_process_options:144: dtb: (null) kernel: 0x8ff61010 kernel_size: 0x6ee18b get_memory_ranges_iomem_cb: 4000 - bfff : System RAM get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM image_arm64_probe: Bad arm64 image header. elf_arm64_probe: Not an ELF executable. image_arm64_probe: Bad arm64 image header. Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic [Regression Risk] kexec-tools did not support arm64 until zesty so, assuming the fix is localized to arm64 code, regression risk is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1661363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments
Please mention which versions were tested and re-mark verification-done- RELEASE in the tags. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1663400 Title: kexec: arm64: Increase the upper limit for RAM segments Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: Fix Committed Status in kexec-tools package in Debian: New Bug description: [Impact] Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem. On a newer UEFI based Qualcomm target the number of system ram regions retrieved from /proc/iomem are ~40. Currently KEXEC_SEGMENT_MAX is set to 16, which represents the kexec segments passed to kexec_load syscall, like kernel image, initrd image etc. The patch increases the value to 64. This enables kexec to see all the "System RAM" as recorded in /proc/iomem. [Test Case] == System RAM reported by /proc/iomem == ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM" 0020-0020 : System RAM 0082-0307 : System RAM 0308-0308 : System RAM 0309-031f : System RAM 0320-033f : System RAM 0341-0589 : System RAM 058a-058a : System RAM 058b-058b : System RAM 058c-0597 : System RAM 0598-05987fff : System RAM 05988000-0598bfff : System RAM 0598c000-05a0 : System RAM 05a1-05aa : System RAM 05ab-05ca0fff : System RAM 05ca1000-08ca : System RAM 08cb-08cf : System RAM 08d0-08ed : System RAM 08ee-08ee0fff : System RAM 08ee1000-08ee3fff : System RAM 08ee4000-08ee : System RAM 08ef-092a : System RAM 092b-092d : System RAM 092e-09422fff : System RAM 09423000-0949 : System RAM 094a-0957 : System RAM 0958-0958cfff : System RAM 0958d000-098c : System RAM 098d-098d0fff : System RAM 098d1000-098dbfff : System RAM 098dc000-0e8b : System RAM 0e8c-0e8e : System RAM 0e8f-0fff : System RAM 1080-17fe : System RAM 1c02-1c7f : System RAM 1c80-1c80 : System RAM 1c81-7efb : System RAM 7efc-7efd : System RAM 7efe-7efe : System RAM 7eff-7eff : System RAM 7f00-17 : System RAM ubuntu@ubuntu:~$ == BEFORE PATCH: System RAM reported by kexec == ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd --initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM" get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM get_memory_ranges_iomem_cb: 0309 - 031f : System RAM get_memory_ranges_iomem_cb: 0320 - 033f : System RAM get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM get_memory_ranges_iomem_cb: 058a - 058a : System RAM get_memory_ranges_iomem_cb: 058b - 058b : System RAM get_memory_ranges_iomem_cb: 058c - 0597 : System RAM get_memory_ranges_iomem_cb: 0598 - 05987fff : System RAM get_memory_ranges_iomem_cb: 05988000 - 0598bfff : System RAM get_memory_ranges_iomem_cb: 0598c000 - 05a0 : System RAM get_memory_ranges_iomem_cb: 05a1 - 05aa : System RAM get_memory_ranges_iomem_cb: 05ab - 05ca0fff : System RAM get_memory_ranges_iomem_cb: 05ca1000 - 08ca : System RAM get_memory_ranges_iomem_cb: 08cb - 08cf : System RAM ==AFTER PATCH: System RAM reported by kexec == ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd --initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM" get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM get_memory_ranges_iomem_cb: 0309 - 031f : System RAM get_memory_ranges_iomem_cb: 0320 - 033f : System RAM get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM get_memory_ranges_iomem_cb: 058a - 058a : System RAM get_memory_ranges_iomem_cb: 058b - 058b : System RAM get_memory_ranges_iomem_cb: 058c - 0597 : System RAM get_memory_ranges_iomem_cb: 0598 - 0
[Kernel-packages] [Bug 1697022] Re: linux: 4.11.0-6.11 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.11.0-6.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-phase:Packaging + kernel-phase-changed:Friday, 09. June 2017 16:04 UTC ** Description changed: This bug is for tracking the 4.11.0-6.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-phase:Packaging kernel-phase-changed:Friday, 09. June 2017 16:04 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697022 Title: linux: 4.11.0-6.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-6.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-phase:Packaging kernel-phase-changed:Friday, 09. June 2017 16:04 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1697022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693962] Re: linux: 4.11.0-5.10 -proposed tracker
*** This bug is a duplicate of bug 1697022 *** https://bugs.launchpad.net/bugs/1697022 ** This bug has been marked a duplicate of bug 1697022 linux: 4.11.0-6.11 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released 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: Confirmed Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690999] Re: linux: 4.11.0-3.8 -proposed tracker
*** This bug is a duplicate of bug 1697022 *** https://bugs.launchpad.net/bugs/1697022 ** This bug is no longer a duplicate of bug 1693962 linux: 4.11.0-5.10 -proposed tracker ** This bug has been marked a duplicate of bug 1697022 linux: 4.11.0-6.11 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New 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: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693229] Re: linux: 4.11.0-4.9 -proposed tracker
*** This bug is a duplicate of bug 1697022 *** https://bugs.launchpad.net/bugs/1697022 ** This bug is no longer a duplicate of bug 1693962 linux: 4.11.0-5.10 -proposed tracker ** This bug has been marked a duplicate of bug 1697022 linux: 4.11.0-6.11 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693229 Title: linux: 4.11.0-4.9 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New 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: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-4.9 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695688] 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/1695688 Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: cordial saludos recien instale ubuntu 17.4 al principio funcionaba bien pero luego de un rato me arrojo un error no puedo usar la terminal ni puedo instalar las actualizaciones ni instalar algun programa desde la tienda ubuntu sofware por favor ayudenme con esto please ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amindiola 1901 F pulseaudio Date: Fri Jun 2 01:11:29 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=60fe5903-36d0-426d-ad09-6e17d756df10 InstallationDate: Installed on 2017-06-02 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Biostar I945C-M7B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=d8524017-2f28-4371-8448-5bcd35d099e5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: I945C-M7B dmi.board.vendor: Biostar dmi.chassis.type: 3 dmi.chassis.vendor: Biostar dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/12/2007:svnBiostar:pnI945C-M7B:pvr:rvnBiostar:rnI945C-M7B:rvr:cvnBiostar:ct3:cvr: dmi.product.name: I945C-M7B dmi.sys.vendor: Biostar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696623] Re: macvtap creation issue using net namespaces
I upgraded my Xenial test system to linux-virtual-hwe-16.04-edge and with that it is working fine. So we have a good testcase (thanks Rolando) a crash dmesg on the issue and confirmed that it is solved in a newer kernel. Comes down to bisecting maybe, but there is a chance the kernel team just knows. That said I'm rerouting the bug to the kernel Team. ** Package changed: iproute2 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696623 Title: macvtap creation issue using net namespaces Status in linux package in Ubuntu: New Bug description: Hi there, There seems to be a bug when trying to create two macvtap links that are contained within different net namespaces. This is what I'm facing and, at the same time, the steps to reproduce the issue: 1 - Create two net namespaces: # root@rjz-nuc:~# ip netns add bng1 root@rjz-nuc:~# ip netns add bng2 2 - Create two veth links, one in one net NS and another one in the other net NS: # root@rjz-nuc:~# ip link add netns bng1 bng1-111_veth type veth peer name subs-lg111_veth root@rjz-nuc:~# ip link add netns bng2 bng2-111_veth type veth peer name subs-lg211_veth 3a - Add a macvtap link on top of the 1st veth in the 1st net NS: # root@rjz-nuc:~# ip netns exec bng1 ip link add link bng1-111_veth name bng1-111_mcvtp type macvtap mode passthru 3b - This executes correctly and creates a tap device: # root@rjz-nuc:~# ip netns exec bng1 ip link show bng1-111_mcvtp 3: bng1-111_mcvtp@bng1-111_veth: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500 link/ether ae:c6:bc:d8:d2:e7 brd ff:ff:ff:ff:ff:ff 3c - Note the "3:" at the beginning of above output pointing to "tap3" that the command created: # root@rjz-nuc:~# ls -tral /dev/tap* crw--- 1 root root 241, 1 Jun 7 20:16 /dev/tap3 4a - Try to add another macvtap link but now on top of the 1st veth in the 2nd net NS: # root@rjz-nuc:~# ip netns exec bng2 ip link add link bng2-111_veth name bng2-111_mcvtp type macvtap mode passthru RTNETLINK answers: File exists 4b - As it can be seen, it fails stating "file exists". Checking the output of "dmesg", it can be seen the reason behind this is that instead of choosing as the tap device the next system-wide free one (for instance, say, tap4) it chooses the "tap3" that was already created by the command in step 3a above: # [Jun 7 20:17] [ cut here ] [ +0.32] WARNING: CPU: 3 PID: 1216 at /build/linux-As38az/linux-4.4.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80() [ +0.07] sysfs: cannot create duplicate filename '/class/macvtap/tap3' [ +0.05] Modules linked in: macvtap macvlan veth drbg ansi_cprng ctr ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp espaf_key xfrm_algo arc4 snd_hda_codec_hdmi 8250_dw snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec inte iwlmvm snd_hda_core x86_pkg_temp_thermal intel_powerclamp coretemp snd_hwdep crct10dif_pclmul mac80211 snd_pcm crc32_pclmul ghash_i_intel snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi glue_helper ablk_helper iwlwifi cryptd snd_put_leds snd_seq_device serio_raw cfg80211 snd_timer snd ir_lirc_codec soundcore lirc_dev ir_xmp_decoder ir_mce_kbd_decoder [ +0.000149] ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder btusb hci_uart btrtl btbcm ir_rc5_debtqca ir_nec_decoder idma64 virt_dma mei_me shpchp mei btintel intel_lpss_pci bluetooth rc_rc6_mce ite_cir rc_core intel_lpss_acpi ad mac_hid acpi_als intel_lpss kfifo_buf industrialio kvm_intel kvm irqbypass autofs4 i915_bpo intel_ips i2c_algo_bit drm_kms_helpe0e syscopyarea sysfillrect sysimgblt ptp sdhci_pci fb_sys_fops pps_core drm sdhci ahci libahci video pinctrl_sunrisepoint i2c_hid p_intel hid fjes [ +0.000124] CPU: 3 PID: 1216 Comm: ip Not tainted 4.4.0-79-generic #100-Ubuntu [ +0.07] Hardware name: /NUC6i3SYB, BIOS SYSKLi35.86A.0024.2015.1027.2142 10/27/2015 [ +0.06] 0286 ffea66e1 88083a5ef5b8 813f94d3 [ +0.13] 88083a5ef600 81ce3010 88083a5ef5f0 81081322 [ +0.11] 88083a56c000 88083c212900 88083a5fbca8 88083a5fbca8 [ +0.11] Call Trace: [ +0.17] [] dump_stack+0x63/0x90 [ +0.15] [] warn_slowpath_common+0x82/0xc0 [ +0.11] [] warn_slowpath_fmt+0x5c/0x80 [ +0.15] [] sysfs_warn_dup+0x62/0x80 [ +0.14] [] sysfs_do_create_link_sd.isra.2+0x9e/0xb0 [ +0.14] [] sysfs_create_link+0x25/0x40 [ +0.13] [] device_add+0x22e/0x650 [ +0.12] [] device_create_groups_vargs+0xe0/0xf0
[Kernel-packages] [Bug 1697017] Re: CAT$@#%Paypal online support of Smartsnake:1-800-208-0139
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697017 Title: CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 Status in linux package in Ubuntu: Invalid Bug description: CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 Need help1-800-208-0139 for making payment via Paypal1-800-208-0139? You are at the right place to get wonder solutions for making instant online payment with no delays. Traditional paper methods used to make the payments are replaced by modern methods like Paypal. Gone are the days when people used to send money via money order or check. We are here to help you with all the Paypal related issues you are getting. World-class remote tech support is just one call away. Call 1-800-208-0139 (Paypal Support of Smartsnake) to get access to our online remote tech support paypal 1-800-208-0139. Paypal has come up as a wonderful solution for making online payment 1-800-208-0139. It gives you the option of making payment in any currency you want. You need not to worry even if you need to make payment overseas. All you need to have is a credit card when moving forward. Nominal charges are incurred by Paypal for giving you a “Peace of Mind”. Electronic alternatives for making payments have no doubt made our lives very easier. It is a boon for all the businessmen. People like us also use it for making online payments in different scenarios. Buyers as well as sellers are asked to pay some charges for the services made by Paypal. Despite of all this ease, trouble-free payments via Paypal cannot be guaranteed by Paypal itself. This is where you should reach Paypal customer service of Smartsnake. The number is toll-free. Your calls will be answered by smart technicians who will give you best solutions in just no time. Paypal Helpline of Smartsnake: 1-800-208-0139 Paypal Helpline for password related issues is available at paypal 1-800-208-0139. Smart Snake offers quick support through Microsoft certified technicians. Smartsnake understands the importance of your time and ease when you make online payments using Paypal. Paypal Support of Smartsnake makes sure that its customers should not suffer at all. Our certified technicians are available paypal 24/7 to deal 1-800-208-0139 with all your Paypal related issues. Call our toll-free phone number now to get instant answers for your Paypal related queries. “Make online payment right now that too uninterruptedly” says Paypal help center of Smartsnake. How easy it is to get rid of unwanted Paypal hurdles with 24*7 Helpline- 1-800-208-0139!! Forgot Paypal password1-800-208-0139? Do not worry. Seek support for Paypal now by dialing the toll-free number- 1-800-208-0139. Say No to pop-ups!! Blocking pop-ups paypal contact number1-800-208-0139 is for your convenience only. Free Diagnose of all your Paypal queries is1-800-208-0139available at toll-free number- 1-800-208-0139. So, call the toll-free number now without waiting any longer. Smartsnake’s support for Paypal: 1-800-208-0139 At Smart Snake we offer you assistance to block all the time-consuming interruptions when you make payments online via Paypal. Lost Paypal password and want solution? We are here to provide you immediate solutions in case you have lost your Paypal password and are stuck in between while making online payment Paypal customer service of Smartsnake gives you relief from miscellaneous Paypal obstacles. Our technicians are expert in troubleshooting and nullifying these Paypal hurdles permanently. Call Paypal helpline if you do not want the unwanted hurdles to eat up your precious time. What else we do for you? We keep you updated on how to use Paypal smoothly. You can easily reach us via Paypal customer service number- 1-800-208-0139. Unmatched Paypal support can now you give you incredible experience while you use electronic alternative to make your payment. Hassle-free Paypal help is now available at 1-800-208-0139 Paypal Customer Service of Smartsnake – 1-800-208-0139 (toll- free)Paypal Helpline of Smartsnake: 1-800-208-0139 If you want to reset Paypal password, call Paypal helpline of Smartsnake now. Call on this number provided here immediately. Our expert technicians will assist you remotely. Just call us no wonder what the time is. We are available 24*7*365 for you. Take the help from our technicians at Paypal Helpline – 1-800-208-0139. Our technicians are happy to assist you with any number of queries in
[Kernel-packages] [Bug 1697019] [NEW] YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)
Public bug reported: YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree) YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)YUP#$#$^Call Paypal Help Center (1-800-208-0139-tollfree)((BAHUBALI2))PayPal Customer Support +1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal c all center,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,contacting PayPal,PayPal support phone number,PayPal tech support number,contact PayPal phone number,PayPal contact email,PayPal help page,PayPal customer care,help PayPal,call PayPal support,PayPal contact phone number,contact PayPal phone,call PayPal customer service,how to contact PayPal support,PayPal phone support,phone number PayPal,email PayPal support,PayPal helpline phone number,help with PayPal,how to contact PayPal by phone,contacting PayPal by phone,telephone number for PayPal,how can i contact PayPal,customer service PayPal,PayPal customer support number,PayPal technical support phone number,PayPal 1800 number,phone number to PayPal,PayPal technical support number,PayPal help center number,PayPal contact information,PayPal email support,PayPal hotline number,PayPal phone numbers,PayPal support contact,phone number for PayPal help center,call PayPal help,how to contact PayPal directly,PayPal tech support phone number,PayPal customer service live chat,contact PayPal by email,customer service number for PayPal,how can i contact PayPal by phone,contact PayPal directly,can i call PayPal,PayPal customer support team,PayPal help contact,number to PayPal,number for PayPal,support PayPal,PayPal.com phone number,PayPal help desk,PayPal customer support phone number,phone number for PayPal support,PayPal headquarters phone number,PayPal support team,PayPal help desk phone number,PayPal support chat,customer service for PayPal,PayPal company phone number,PayPal service number,PayPal email contact,PayPal customer service phone,phone number for PayPal help,PayPal help contact number,PayPal online support,phone number to contact PayPal,contact phone number for PayPal,PayPal live help,contact PayPal number,PayPal number to call,contact PayPal customer support,phone number for PayPal customer service,email PayPal help,c ontacting PayPal support,PayPal live support,PayPal customer support email,how to email PayPal support,call PayPal for help,call PayPal help center,PayPal phone number customer service,contact information for PayPal,PayPal contact support,contact PayPal help,customer service phone number for PayPal,contact PayPal team,PayPal custmer service telephone number,PayPal by phone number,can you call PayPal,how to get in touch with PayPal,PayPal 1 800 number,PayPal security phone number,contact fb,help center PayPal,fb phone number,contact PayPal support phone,phone number for PayPal headquarters,i need to call PayPal,PayPal customer service contact,PayPal advertising phone number,800 number for PayPal,PayPal 800 number,PayPal office phone number,PayPal phone number help,contact PayPal administrator,PayPal service,PayPal ads support,contact PayPal ads,how to get in contact with PayPal,contact PayPal support em
[Kernel-packages] [Bug 1697022] [NEW] linux: 4.11.0-6.11 -proposed tracker
Public bug reported: This bug is for tracking the 4.11.0-6.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 ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Artful) Importance: Medium Status: Confirmed ** Tags: artful block-proposed kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Tags added: artful ** Changed in: linux (Ubuntu Artful) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697022 Title: linux: 4.11.0-6.11 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated
[Kernel-packages] [Bug 1696623] [NEW] macvtap creation issue using net namespaces
You have been subscribed to a public bug: Hi there, There seems to be a bug when trying to create two macvtap links that are contained within different net namespaces. This is what I'm facing and, at the same time, the steps to reproduce the issue: 1 - Create two net namespaces: # root@rjz-nuc:~# ip netns add bng1 root@rjz-nuc:~# ip netns add bng2 2 - Create two veth links, one in one net NS and another one in the other net NS: # root@rjz-nuc:~# ip link add netns bng1 bng1-111_veth type veth peer name subs-lg111_veth root@rjz-nuc:~# ip link add netns bng2 bng2-111_veth type veth peer name subs-lg211_veth 3a - Add a macvtap link on top of the 1st veth in the 1st net NS: # root@rjz-nuc:~# ip netns exec bng1 ip link add link bng1-111_veth name bng1-111_mcvtp type macvtap mode passthru 3b - This executes correctly and creates a tap device: # root@rjz-nuc:~# ip netns exec bng1 ip link show bng1-111_mcvtp 3: bng1-111_mcvtp@bng1-111_veth: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500 link/ether ae:c6:bc:d8:d2:e7 brd ff:ff:ff:ff:ff:ff 3c - Note the "3:" at the beginning of above output pointing to "tap3" that the command created: # root@rjz-nuc:~# ls -tral /dev/tap* crw--- 1 root root 241, 1 Jun 7 20:16 /dev/tap3 4a - Try to add another macvtap link but now on top of the 1st veth in the 2nd net NS: # root@rjz-nuc:~# ip netns exec bng2 ip link add link bng2-111_veth name bng2-111_mcvtp type macvtap mode passthru RTNETLINK answers: File exists 4b - As it can be seen, it fails stating "file exists". Checking the output of "dmesg", it can be seen the reason behind this is that instead of choosing as the tap device the next system-wide free one (for instance, say, tap4) it chooses the "tap3" that was already created by the command in step 3a above: # [Jun 7 20:17] [ cut here ] [ +0.32] WARNING: CPU: 3 PID: 1216 at /build/linux-As38az/linux-4.4.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80() [ +0.07] sysfs: cannot create duplicate filename '/class/macvtap/tap3' [ +0.05] Modules linked in: macvtap macvlan veth drbg ansi_cprng ctr ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp espaf_key xfrm_algo arc4 snd_hda_codec_hdmi 8250_dw snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec inte iwlmvm snd_hda_core x86_pkg_temp_thermal intel_powerclamp coretemp snd_hwdep crct10dif_pclmul mac80211 snd_pcm crc32_pclmul ghash_i_intel snd_seq_midi aesni_intel snd_seq_midi_event aes_x86_64 lrw gf128mul snd_rawmidi glue_helper ablk_helper iwlwifi cryptd snd_put_leds snd_seq_device serio_raw cfg80211 snd_timer snd ir_lirc_codec soundcore lirc_dev ir_xmp_decoder ir_mce_kbd_decoder [ +0.000149] ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder btusb hci_uart btrtl btbcm ir_rc5_debtqca ir_nec_decoder idma64 virt_dma mei_me shpchp mei btintel intel_lpss_pci bluetooth rc_rc6_mce ite_cir rc_core intel_lpss_acpi ad mac_hid acpi_als intel_lpss kfifo_buf industrialio kvm_intel kvm irqbypass autofs4 i915_bpo intel_ips i2c_algo_bit drm_kms_helpe0e syscopyarea sysfillrect sysimgblt ptp sdhci_pci fb_sys_fops pps_core drm sdhci ahci libahci video pinctrl_sunrisepoint i2c_hid p_intel hid fjes [ +0.000124] CPU: 3 PID: 1216 Comm: ip Not tainted 4.4.0-79-generic #100-Ubuntu [ +0.07] Hardware name: /NUC6i3SYB, BIOS SYSKLi35.86A.0024.2015.1027.2142 10/27/2015 [ +0.06] 0286 ffea66e1 88083a5ef5b8 813f94d3 [ +0.13] 88083a5ef600 81ce3010 88083a5ef5f0 81081322 [ +0.11] 88083a56c000 88083c212900 88083a5fbca8 88083a5fbca8 [ +0.11] Call Trace: [ +0.17] [] dump_stack+0x63/0x90 [ +0.15] [] warn_slowpath_common+0x82/0xc0 [ +0.11] [] warn_slowpath_fmt+0x5c/0x80 [ +0.15] [] sysfs_warn_dup+0x62/0x80 [ +0.14] [] sysfs_do_create_link_sd.isra.2+0x9e/0xb0 [ +0.14] [] sysfs_create_link+0x25/0x40 [ +0.13] [] device_add+0x22e/0x650 [ +0.12] [] device_create_groups_vargs+0xe0/0xf0 [ +0.15] [] device_create+0x51/0x70 [ +0.15] [] macvtap_device_event+0xde/0x170 [macvtap] [ +0.12] [] notifier_call_chain+0x4a/0x70 [ +0.11] [] raw_notifier_call_chain+0x16/0x20 [ +0.14] [] call_netdevice_notifiers_info+0x35/0x60 [ +0.11] [] register_netdevice+0x342/0x480 [ +0.15] [] macvlan_common_newlink+0x166/0x450 [macvlan] [ +0.12] [] macvtap_newlink+0x67/0x70 [macvtap] [ +0.10] [] rtnl_newlink+0x6ee/0x8a0 [ +0.09] [] ? rtnl_newlink+0x176/0x8a0 [ +0.15] [] rtnetlink_rcv_msg+0xe6/0x230 [ +0.15] [] ? __alloc_skb+0x87/0x1f0 [ +0.08] [] ? rtnetlink_rcv+0x30/0x30 [ +0.14] [] netlink_rcv_skb+0xa4/0xc0 [ +0.08] [] rtnetlink_rcv+0x28/0x30 [ +0.11] []
[Kernel-packages] [Bug 1696859] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
I could more or less solve the issue on my ubuntu-install by booting into recovery mode and clean the system. (the commands i executed were dkpg-remove, apt-get update, apt-get upgrade, apt autoremove, apt autoclean and several others) As far as i remember i was removing some old kernel packages and then manually install new kernel headers and the new kernel package. It seems to be all fine now :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696859 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnybegood 1415 F pulseaudio /dev/snd/controlC1: johnnybegood 1415 F pulseaudio Date: Wed Jun 7 06:52:02 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8e8fcdb0-767f-4fa7-a8e3-e06bf12ae742 InstallationDate: Installed on 2017-04-15 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=9056280d-1b43-47b6-b5ed-5b796780a968 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M77 Ver. 01.14 dmi.board.name: 2271 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.50 dmi.chassis.asset.tag: 5CG5517PNY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM77Ver.01.14:bd09/26/2016:svnHewlett-Packard:pnHPEliteBookFolio1020G1:pvrA3009FD18303:rvnHewlett-Packard:rn2271:rvrKBCVersion91.50:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1020 G1 dmi.product.version: A3009FD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697017] [NEW] CAT$@#%Paypal online support of Smartsnake:1-800-208-0139
Public bug reported: CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 CAT$@#%Paypal online support of Smartsnake:1-800-208-0139 Need help1-800-208-0139 for making payment via Paypal1-800-208-0139? You are at the right place to get wonder solutions for making instant online payment with no delays. Traditional paper methods used to make the payments are replaced by modern methods like Paypal. Gone are the days when people used to send money via money order or check. We are here to help you with all the Paypal related issues you are getting. World-class remote tech support is just one call away. Call 1-800-208-0139 (Paypal Support of Smartsnake) to get access to our online remote tech support paypal 1-800-208-0139. Paypal has come up as a wonderful solution for making online payment 1-800-208-0139. It gives you the option of making payment in any currency you want. You need not to worry even if you need to make payment overseas. All you need to have is a credit card when moving forward. Nominal charges are incurred by Paypal for giving you a “Peace of Mind”. Electronic alternatives for making payments have no doubt made our lives very easier. It is a boon for all the businessmen. People like us also use it for making online payments in different scenarios. Buyers as well as sellers are asked to pay some charges for the services made by Paypal. Despite of all this ease, trouble-free payments via Paypal cannot be guaranteed by Paypal itself. This is where you should reach Paypal customer service of Smartsnake. The number is toll-free. Your calls will be answered by smart technicians who will give you best solutions in just no time. Paypal Helpline of Smartsnake: 1-800-208-0139 Paypal Helpline for password related issues is available at paypal 1-800-208-0139. Smart Snake offers quick support through Microsoft certified technicians. Smartsnake understands the importance of your time and ease when you make online payments using Paypal. Paypal Support of Smartsnake makes sure that its customers should not suffer at all. Our certified technicians are available paypal 24/7 to deal 1-800-208-0139 with all your Paypal related issues. Call our toll-free phone number now to get instant answers for your Paypal related queries. “Make online payment right now that too uninterruptedly” says Paypal help center of Smartsnake. How easy it is to get rid of unwanted Paypal hurdles with 24*7 Helpline- 1-800-208-0139!! Forgot Paypal password1-800-208-0139? Do not worry. Seek support for Paypal now by dialing the toll-free number- 1-800-208-0139. Say No to pop-ups!! Blocking pop-ups paypal contact number1-800-208-0139 is for your convenience only. Free Diagnose of all your Paypal queries is1-800-208-0139available at toll-free number- 1-800-208-0139. So, call the toll-free number now without waiting any longer. Smartsnake’s support for Paypal: 1-800-208-0139 At Smart Snake we offer you assistance to block all the time-consuming interruptions when you make payments online via Paypal. Lost Paypal password and want solution? We are here to provide you immediate solutions in case you have lost your Paypal password and are stuck in between while making online payment Paypal customer service of Smartsnake gives you relief from miscellaneous Paypal obstacles. Our technicians are expert in troubleshooting and nullifying these Paypal hurdles permanently. Call Paypal helpline if you do not want the unwanted hurdles to eat up your precious time. What else we do for you? We keep you updated on how to use Paypal smoothly. You can easily reach us via Paypal customer service number- 1-800-208-0139. Unmatched Paypal support can now you give you incredible experience while you use electronic alternative to make your payment. Hassle-free Paypal help is now available at 1-800-208-0139 Paypal Customer Service of Smartsnake – 1-800-208-0139 (toll-free)Paypal Helpline of Smartsnake: 1-800-208-0139 If you want to reset Paypal password, call Paypal helpline of Smartsnake now. Call on this number provided here immediately. Our expert technicians will assist you remotely. Just call us no wonder what the time is. We are available 24*7*365 for you. Take the help from our technicians at Paypal Helpline – 1-800-208-0139. Our technicians are happy to assist you with any number of queries in a day. Recommendation: Support for uninterrupted Paypal payments is strongly recommended by Smartsnake to all the users. This Paypal Helpline is always there to assist you. Get free diagnose without leaving the comfort of your home and office. Don’t panic if you are facing Paypal issues every now and then. Getting support for the same is now a phone call away. Paypal support can be easily availed
[Kernel-packages] [Bug 1690084] Re: mouse disappeared
I tried the latest linux-generic-hwe-16.04-edge again (providing 4.10.0-22-generic). The mouse works, so the problem has disappeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690084 Title: mouse disappeared Status in linux package in Ubuntu: Incomplete Bug description: When installing linux-generic-hwe-16.04-edge, my "DELL Laser Mouse" didn't work any more, as confirmed by xinput(1). I went from linux-generic-hwe-16.04 (providing Linux 4.8) to linux- generic-hwe-16.04-edge (providing Linux 4.10). When I reverted back to Linux 4.8, the mouse appeared again. The enclosed info from lspci(8) is from the working system Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17. The system is a Dell Latitude E7470 and has an up-to-date "Xenial Xerus" installation. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mhu027 4051 F pulseaudio DistroRelease: Ubuntu 16.04 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=/dev/mapper/vg0-lv_root ro acpi=force irqpoll quiet splash ipv6.disable=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-51-generic N/A linux-backports-modules-4.8.0-51-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/11/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.3:bd12/11/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
NVidia setup is also including a second intel card (for power saving mode), but yes I mainly try to use NVidia profile (kernel used to complain about the intel card just like it is in your case). Secondly not only 4.4.0-72-generic is working also 4.10.1-041001-generic does very good job. As for last, as mentioned above I also use the DELL dock. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697012] [NEW] $!%ERVICE paypal 1?800"208"0139customer service phone number""""1?800"208"0139"PayPal help desk phone number
Public bug reported: $!%*E*R*V*IC*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number $!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number$!%*E*R*V*I*C*Epaypal 1?800"208"0139customer service phone number1?800"208"0139"PayPal help desk phone number Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical supportDial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Dial<<>>1-800-208-0139-PayPal tech support number netflix customer service care number technical support Call US||!!1-800-208-0139||PayPal technical Support phone number 1-800-208-0139 ||PayPal customer support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number Call US||1-800-208-0139||PayPal Support phone number 1-800-208-0139 ||PayPal support number Call US||11-800-208-0139||PayPal Support phone number 1-800-208-0139||PayPal support number PayPal Customer Support 1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal call cen ter,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,contacting PayPal,PayPal support phone number,PayPal tech support number,contact PayPal phone number,PayPal contact email,PayPal help page,PayPal customer care,help PayPal,call PayPal support,PayPal contact phone number,contact PayPal phone,call PayPal customer service,how to contact PayPal support,PayPal phone support,phone number PayPal,email PayPal support,PayPal helpline phone number,help with PayPal,how to contact PayPal by phone,co
[Kernel-packages] [Bug 1697015] [NEW] *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician
Public bug reported: *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician*&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician *&P%$@sk paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician ((BAHUBALI2))PayPal Customer Support +1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 ((BAHUBALI2))PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 PayPal Support phone number+1-800-208-0139 Phone number. PayPal Customer Care Phone Number.Call @ PayPal Customer Support +1-800-208-0139 Phone number. PayPal Support Phone Number. We provide dedicated customer supportthrough PayPal phone number +1-800-208-0139. PayPal has become an eminent way to communicate with your friends and family and is also an intriguing way to make new friends. ... For PayPal Support, ask paypal for Toll range 1-800-208-0139 and counsel with our guaranteed technician. we have a gathering of consultants for giving best and shabby organizations. PayPal support number 1-800-208-0139,PayPal phone number 1-800-208-0139,PayPal help,PayPal customer service,PayPal contact number 1-800-208-0139,PayPal support,contact PayPal,PayPal contact,PayPal help number,PayPal customer service number,how to contact PayPal,PayPal customer support,contact PayPal by phone,phone number for PayPal,PayPal customer service phone number,PayPal number,PayPal helpline,PayPal tech support,PayPal support email,PayPal help phone number,PayPal problems,call PayPal,contact PayPal support,PayPal customer service email,PayPal contact info,PayPal phone number search,PayPal customer service toll free number,PayPal help center,PayPal call,PayPal contact us,how do i contact PayPal,email PayPal,PayPal supportnumber,PayPal helpline number,PayPal telephone number,PayPal help email,PayPal c all center,contact PayPal customer service,PayPal technical support,contact PayPal email,contact number for PayPal,PayPal help center phone number,contacting PayPal,PayPal support phone number,PayPal tech support number,contact PayPal phone number,PayPal contact email,PayPal help page,PayPal customer care,help PayPal,call PayPal support,PayPal contact phone number,contact PayPal phone,call PayPal customer service,how to contact PayPal support,PayPal phone support,phone number PayPal,email PayPal support,PayPal helpline phone number,help with PayPal,how to contact PayPal by phone,contacting PayPal by phone,telephone number for PayPal,how can i contact PayPal,customer service PayPal,PayPal customer support number,PayPal technical support phone number,PayPal 1800 number,phone number to PayPal,PayPal technical support number,PayPal help center number,PayPal contact information,PayPal email support,PayPal hotline number,PayPal phone numbers,PayPal support contact,phone number for PayPal help center,call PayPal help,how to contact PayPal directly,PayPal tech support phone number,PayPal customer service live chat,contact PayPal by email,customer service number for PayPal,how can i contact PayPal by phone,contact PayPal directly,can i call PayPal,PayPal customer support team,PayPal help contact,number to PayPal,number for PayPal,support PayPal,PayPal.com phone number,PayPal help desk,PayPal customer support phone number,phone number for PayPal support,PayPal headquarters phone number,PayPal support team,PayPal help desk phone number,PayPal support chat,customer service for PayPal,PayPal company phone number,PayPal service number,PayPal email contact,PayPal customer service phone,phone number for PayPal help,PayPal help contact number,PayPal online support,phone number to contact PayPal,contact phone number for PayPal,PayPal live help,contact PayPal number,PayPal number to call,contact PayPal customer support,phone number for PayPal customer service,email PayPal help,c ontacting PayPal support,PayPal live support,PayPal customer support email,how to email PayPal support,call PayPal for help,call PayPal help center,PayPal phone number customer service,contact information for PayPal,PayPal contact support,contact PayPal help,customer service phone number for PayPal,contact PayPal team,PayPal custmer service telephone number,PayPal by phone number,can you call PayPal,how to get in touch with PayPal,PayPal 1 800 number,PayPal security phone number,contact fb,help center PayPal,fb phone number,contact PayPal support phone,phone number for PayPal headquarters,i need to call PayPal,PayPal customer serv
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
This is relatively hard to reproduce. It happens sometimes directly after boot and login, sometimes after more than a week uptime. I've simply selected an older kernel at boot (4.8.0-46-generic; the newest one I had installed from Yakkety) and I didn't experience a crash, yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11
[Kernel-packages] [Bug 1691485] Re: fanatic disable-fan fails without docker installed
Hello Stefan, or anyone else affected, Accepted ubuntu-fan into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- fan/0.12.0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Yakkety: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Released Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts
*** This bug is a duplicate of bug 1667750 *** https://bugs.launchpad.net/bugs/1667750 Patch being worked on - https://www.spinics.net/lists/linux- usb/msg157958.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/1663975 Title: XHCI errors causes dock USB and network adapter dropouts Status in linux package in Ubuntu: Confirmed Bug description: Machine: Dell XPS 15 (9560) - released 2017 January Install: disk completely erased Ubuntu 16.04.1 installed over wireless with: - download updates while installing ubuntu - install third-party hardware - full disk crypto+luks Note 1: Installation process did not realize there exists a GTX 1050 so we are solely using Intel integrated graphics. Note 2: Installation done not on Dell TB16 Dock to isolate wireless problems alone first. First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted After testing wireless problems and being able to reproduce them, machine was rebooted to the login screen, and then plugged into a Dell TB16 dock. 1. Turn down wireless networking. 2. Turn up wired networking. 3. Browse things until this happens, after which the wired interface no longer works and can sometimes be successfully `down/up`ed but at other times locks up and requires a reboot: [ 598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 605.601884] [ cut here ] [ 605.601890] WARNING: CPU: 1 PID: 0 at /build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 dev_watchdog+0x237/0x240() [ 605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 timed out [ 605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx_pci_ms memstick snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm x86_pkg_temp_thermal coretemp snd_seq_midi kvm_intel snd_seq_midi_event snd_rawmidi kvm snd_seq uvcvideo irqbypass snd_seq_device snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 input_leds videobuf2_core snd joydev v4l2_common serio_
[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts
*** This bug is a duplicate of bug 1667750 *** https://bugs.launchpad.net/bugs/1667750 This is an issue with the host controller. The vendor (ASMedia) has submitted a patch here that fixes the issue: http://www.spinics.net/lists/linux-usb/msg157958.html ** This bug has been marked a duplicate of bug 1667750 xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1663975 Title: XHCI errors causes dock USB and network adapter dropouts Status in linux package in Ubuntu: Confirmed Bug description: Machine: Dell XPS 15 (9560) - released 2017 January Install: disk completely erased Ubuntu 16.04.1 installed over wireless with: - download updates while installing ubuntu - install third-party hardware - full disk crypto+luks Note 1: Installation process did not realize there exists a GTX 1050 so we are solely using Intel integrated graphics. Note 2: Installation done not on Dell TB16 Dock to isolate wireless problems alone first. First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted After testing wireless problems and being able to reproduce them, machine was rebooted to the login screen, and then plugged into a Dell TB16 dock. 1. Turn down wireless networking. 2. Turn up wired networking. 3. Browse things until this happens, after which the wired interface no longer works and can sometimes be successfully `down/up`ed but at other times locks up and requires a reboot: [ 598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 seg-end 0008550aaff0 [ 605.601884] [ cut here ] [ 605.601890] WARNING: CPU: 1 PID: 0 at /build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 dev_watchdog+0x237/0x240() [ 605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 timed out [ 605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx_pci_ms memstick snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm x86_pkg_t
[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
This is an issue with the host controller. The vendor (ASMedia) has submitted a patch here that fixes the issue: http://www.spinics.net/lists/linux-usb/msg157958.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/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: New Bug description: My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2 Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2 Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2 Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2 Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 3 using xhci_hcd I can't seem to make this bug appear with any other type of USB traffic. I've reported it to the realtek kernel dev t
[Kernel-packages] [Bug 1612492] Re: remounting breaks size reporting and rsync
Also verified in 3.3.8 I compile the kernel (3.3.8) on Ubuntu 14.04 and Centos 7-1511. After I mount ecryptfs with ecryptfs_xattr option, it will terminate if I copy some file in it. First time I copy files, it will be killed. Next time I copy files, it will hang and do nothing. Test outputs: $ sudo mount -t ecryptfs secure raw -o ecryptfs_xattr [...] $ cp file.out2 raw Killed I test 3.3.8 kernel on different machines including VM-ware, the outputs are all the same! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612492 Title: remounting breaks size reporting and rsync Status in eCryptfs: Triaged Status in ecryptfs-utils: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Sorry to resurrect an old bug, it looks like a fix applied a while back may end up breaking rsync. For reference, it looks like the decision in this bug fix was to pass on the encrypted file size on disk to stat calls looking at the unencrypted mount: https://bugs.launchpad.net/ecryptfs/+bug/390833 For reference, to reproduce: mkdir /mnt/raw mkdir /mnt/decrypted dd if=/dev/urandom of=file.out2 bs=1MB count=100 mount -t ecryptfs -o ecryptfs_passthrough=n,no_sig_cache,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_xattr,ecryptfs_enable_filename_crypto=y,passphrase_passwd=SECRET,ecryptfs_fnek_sig=SECRET /mnt/raw /mnt/decrypted rsync file.out2 /mnt/decrypted/ stat /mnt/decrypted/file.out2 # you get size 1 umount /mnt/decrypted/ mount -t ecryptfs -o ecryptfs_passthrough=n,no_sig_cache,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_xattr,ecryptfs_enable_filename_crypto=y,passphrase_passwd=SECRET,ecryptfs_fnek_sig=SECRET /mnt/raw /mnt/decrypted stat /mnt/decrypted/file.out2 # you get size 13840 What this means in practice is any additional rsyncs to that target after remounting will see the file size as different than the original, and issue a full new copy. My use case is ecryptfs over a remote file system, so rsync is no better than cp. Would it be possible to make file size reporting consistent, and reflective of the size of the file as a reader would see it? To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1612492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697001] Re: Xenial update to 4.4.71 stable release
The following patches were skipped as they already were applied:
* CVE-2017-9242
- pv6: fix out of bound writes in __ip6_append_data()
* CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
* CVE-2017-9075
- sctp: do not inherit ipv6_{mc|ac|fl}_list from parent
* CVE-2017-9076 and CVE-2017-9077
- ipv6/dccp: do not inherit ipv6_mc_list from parent
* CVE-2017-8890
- dccp/tcp: do not inherit mc_list from parent
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The 4.4.71 upstream stable
+ patch set is now available. It should be included in the Ubuntu
+ kernel as well.
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.71 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+ git://git.kernel.org/
-git://git.kernel.org/
+ TEST CASE: TBD
- TEST CASE: TBD
-
-The following patches from the 4.4.71 stable release shall be
- applied:
+ The following patches from the 4.4.71 stable release shall be applied:
+ * sparc: Fix -Wstringop-overflow warning
+ * s390/qeth: handle sysfs error during initialization
+ * s390/qeth: unbreak OSM and OSN support
+ * s390/qeth: avoid null pointer dereference on OSN
+ * tcp: avoid fragmenting peculiar skbs in SACK
+ * sctp: fix src address selection if using secondary addresses for ipv6
+ * tcp: eliminate negative reordering in tcp_clean_rtx_queue
+ * net: Improve handling of failures on link and route dumps
+ * ipv6: Check ip6_find_1stfragopt() return value properly.
+ * bridge: netlink: check vlan_default_pvid range
+ * qmi_wwan: add another Lenovo EM74xx device ID
+ * bridge: start hello_timer when enabling KERNEL_STP in br_stp_start
+ * be2net: Fix offload features for Q-in-Q packets
+ * virtio-net: enable TSO/checksum offloads for Q-in-Q vlans
+ * tcp: avoid fastopen API to be used on AF_UNSPEC
+ * sctp: fix ICMP processing if skb is non-linear
+ * ipv4: add reference counting to metrics
+ * netem: fix skb_orphan_partial()
+ * net: phy: marvell: Limit errata to 88m1101
+ * vlan: Fix tcp checksum offloads in Q-in-Q vlans
+ * i2c: i2c-tiny-usb: fix buffer not being DMA capable
+ * mmc: sdhci-iproc: suppress spurious interrupt with Multiblock read
+ * HID: wacom: Have wacom_tpc_irq guard against possible NULL dereference
+ * scsi: mpt3sas: Force request partial completion alignment
+ * drm/radeon/ci: disable mclk switching for high refresh rates (v2)
+ * drm/radeon: Unbreak HPD handling for r600+
+ * pcmcia: remove left-over %Z format
+ * ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430
+ * slub/memcg: cure the brainless abuse of sysfs attributes
+ * drm/gma500/psb: Actually use VBT mode when it is found
+ * mm/migrate: fix refcount handling when !hugepage_migration_supported()
+ * mlock: fix mlock count can not decrease in race condition
+ * xfs: Fix missed holes in SEEK_HOLE implementation
+ * xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()
+ * xfs: fix over-copying of getbmap parameters from userspace
+ * xfs: handle array index overrun in xfs_dir2_leaf_readbuf()
+ * xfs: prevent multi-fsb dir readahead from reading random blocks
+ * xfs: fix up quotacheck buffer list error handling
+ * xfs: support ability to wait on new inodes
+ * xfs: update ag iterator to support wait on new inodes
+ * xfs: wait on new inodes during quotaoff dquot release
+ * xfs: fix indlen accounting error on partial delalloc conversion
+ * xfs: bad assertion for delalloc an extent that start at i_size
+ * xfs: fix unaligned access in xfs_btree_visit_blocks
+ * xfs: in _attrlist_by_handle, copy the cursor back to userspace
+ * xfs: only return -errno or success from attr ->put_listent
+ * Linux 4.4.71
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8890
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9074
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9075
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9076
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9077
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9242
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
[Kernel-packages] [Bug 1696352] Re: linux: 3.13.0-120.167 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Description changed: This bug is for tracking the 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 backports: 1696354 derivatives: + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Friday, 09. June 2017 14:00 UTC ** Description changed: This bug is for tracking the 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 backports: 1696354 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 09. June 2017 14:00 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696352 Title: linux: 3.13.0-120.167 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 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 backports: 1696354 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Friday, 09. June 2017 14:00 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1696352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697001] [NEW] Xenial update to 4.4.71 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.71 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.71 stable release shall be applied: * sparc: Fix -Wstringop-overflow warning * s390/qeth: handle sysfs error during initialization * s390/qeth: unbreak OSM and OSN support * s390/qeth: avoid null pointer dereference on OSN * tcp: avoid fragmenting peculiar skbs in SACK * sctp: fix src address selection if using secondary addresses for ipv6 * tcp: eliminate negative reordering in tcp_clean_rtx_queue * net: Improve handling of failures on link and route dumps * ipv6: Check ip6_find_1stfragopt() return value properly. * bridge: netlink: check vlan_default_pvid range * qmi_wwan: add another Lenovo EM74xx device ID * bridge: start hello_timer when enabling KERNEL_STP in br_stp_start * be2net: Fix offload features for Q-in-Q packets * virtio-net: enable TSO/checksum offloads for Q-in-Q vlans * tcp: avoid fastopen API to be used on AF_UNSPEC * sctp: fix ICMP processing if skb is non-linear * ipv4: add reference counting to metrics * netem: fix skb_orphan_partial() * net: phy: marvell: Limit errata to 88m1101 * vlan: Fix tcp checksum offloads in Q-in-Q vlans * i2c: i2c-tiny-usb: fix buffer not being DMA capable * mmc: sdhci-iproc: suppress spurious interrupt with Multiblock read * HID: wacom: Have wacom_tpc_irq guard against possible NULL dereference * scsi: mpt3sas: Force request partial completion alignment * drm/radeon/ci: disable mclk switching for high refresh rates (v2) * drm/radeon: Unbreak HPD handling for r600+ * pcmcia: remove left-over %Z format * ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430 * slub/memcg: cure the brainless abuse of sysfs attributes * drm/gma500/psb: Actually use VBT mode when it is found * mm/migrate: fix refcount handling when !hugepage_migration_supported() * mlock: fix mlock count can not decrease in race condition * xfs: Fix missed holes in SEEK_HOLE implementation * xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff() * xfs: fix over-copying of getbmap parameters from userspace * xfs: handle array index overrun in xfs_dir2_leaf_readbuf() * xfs: prevent multi-fsb dir readahead from reading random blocks * xfs: fix up quotacheck buffer list error handling * xfs: support ability to wait on new inodes * xfs: update ag iterator to support wait on new inodes * xfs: wait on new inodes during quotaoff dquot release * xfs: fix indlen accounting error on partial delalloc conversion * xfs: bad assertion for delalloc an extent that start at i_size * xfs: fix unaligned access in xfs_btree_visit_blocks * xfs: in _attrlist_by_handle, copy the cursor back to userspace * xfs: only return -errno or success from attr ->put_listent * Linux 4.4.71 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697001 Title: Xenial update to 4.4.71 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.71 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.71 stable release shall be applied: * sparc: Fix -Wstringop-overflow warning * s390/qeth: handle sysfs error during initialization * s390/qeth: unbreak OSM and OSN support * s390/qeth: avoid null pointer dereference on OSN * tcp: avoid fragmenting
[Kernel-packages] [Bug 1696355] Re: linux: 3.19.0-86.94 -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696355 Title: linux: 3.19.0-86.94 -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Invalid Bug description: This bug is for tracking the 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 backports: 1696356 derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1696355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
just install 4.8-X from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.8.17/ but yeah I agree this should have been fix long time ago. there is even a backport for 4.10 this has to go into the ubuntu kernel what takes so much time i donno -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] C
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I'm running 4.10.0-22-generic and it is still crashing (at least 2 to 5 times a day) (not only when running chrome, a couple of other applications also cause this kernel panic to happen which completely makes ubuntu (and any other linux distro on 4.10/4.11) unusable for work @the moment... I hope somebody can/will fix(/backport) this soon since I might have to resort to using OSX or Windows to actually get some work done :( (and a blame to the freedesktop kernel dev's for not backporting this asap into mainline, this affects almost every user on 4.10/4.11 kernels and should be fixed upstream) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 do
