[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Me too. Nvidia gtx 960m and i7 6700hq. New install ,anything not change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112247] [] entry_SYSCALL_64_fastpath+0x16/0x71 Dec 31 19:13:12 COMPUTERNAME kernel: [ 6
[Kernel-packages] [Bug 1582431] fozzie (amd64) - tests ran: 18, failed: 3
tests ran: 18, failed: 3; http://kernel.ubuntu.com/testing/4.4.0-22.40/fozzie__4.4.0-22.40__2016-05-24_02-48-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-24_04-52-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582963] dagmar (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/dagmar__3.19.0-60.67~14.04.1__2016-05-24_05-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1582963 Title: linux-lts-vivid: 3.19.0-60.67~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-60.67~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1582780 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582963] dagmar (amd64) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/dagmar__3.19.0-60.67~14.04.1__2016-05-24_05-19-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1582963 Title: linux-lts-vivid: 3.19.0-60.67~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-60.67~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1582780 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582963] dagmar (i386) - tests ran: 13, failed: 1
tests ran: 13, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/dagmar__3.19.0-60.67~14.04.1__2016-05-24_04-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1582963 Title: linux-lts-vivid: 3.19.0-60.67~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-60.67~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1582780 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-24_03-40-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 9
tests ran: 18, failed: 9; http://kernel.ubuntu.com/testing/4.4.0-23.41/ms10-35-mcdivittB0-kernel__4.4.0-23.41__2016-05-24_00-59-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541845] Re: IIntel Dualband Wireless 7260 not working
[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/1541845 Title: IIntel Dualband Wireless 7260 not working Status in linux package in Ubuntu: Expired Bug description: Hi I try to install Ubuntu on ASUS Pro B451JA, which uses Intel Dualband Wireless Chipset, I can not make it up: @B451JA:~$ dmesg|grep iwlwifi [1.907649] iwlwifi :03:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2 [1.913878] iwlwifi :03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [1.944866] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [1.944957] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [1.945233] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [2.168081] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 [3.325274] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [3.325529] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [3.532126] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [3.532384] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 13.005757] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio. l@lB451JA:~$ $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 2: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: yes B451JA:~$ iwconfig enp0s25 no wireless extensions. lono wireless extensions. wlp3s0IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=off Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off lshw: *-network DISABLED description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 73 serial: 80:19:34:33:4a:46 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-2-generic firmware=16.242414.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn resources: irq:29 memory:f7c0-f7c01fff -B451JA:~$ modinfo iwlwifi filename: /lib/modules/4.4.0-2-generic/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko license:GPL author: Copyright(c) 2003- 2015 Intel Corporation description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-5.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-4.ucode firmware: iwlwifi-7265D-13.ucode firmware: iwlwifi-7265-13.ucode firmware: iwlwifi-3160-13.ucode firmware: iwlwifi-7260-13.ucode firmware: iwlwifi-8000-13.ucode srcversion: E837FB282F9DBA383B753F2 alias: pci:v8086d24F3sv*sd0930bc*sc*i* - I have tried all other Ubuntu versions, e.g 15.10, 14.04 LTS, Kubuntu, and the latest 16.04 LTS testing image, but it still has the same wifi problem: Intel 7260 Wifi does not work. I have also tried to copy firmware from Intel website to /lib/firmware, but it still has the same problem. I think this issue is very urgent now, because the Intel 7260 is very common. THanks a lot for your kind helps. HIENVCU ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Feb 4 14:21:08 2016 InstallationDate: Installed on 2016-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom:
[Kernel-packages] [Bug 1560224] Re: [Dell Inc. Inspiron 3537] suspend/resume failure
[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/1560224 Title: [Dell Inc. Inspiron 3537] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: ... ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cefre001872 F pulseaudio /dev/snd/controlC0: cefre001872 F pulseaudio Date: Sat Mar 19 20:50:59 2016 DuplicateSignature: suspend/resume:Dell Inc. Inspiron 3537:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=8cfcecee-87f7-4cf4-bd92-79464cdd3733 InstallationDate: Installed on 2016-02-18 (32 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.5 MachineType: Dell Inc. Inspiron 3537 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic root=UUID=1c08c9f9-54ca-416e-b4ed-8fcf5e13fe85 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux Title: [Dell Inc. Inspiron 3537] suspend/resume failure UpgradeStatus: Upgraded to xenial on 2016-03-19 (2 days ago) UserGroups: dmi.bios.date: 09/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0PHTY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/27/2013:svnDellInc.:pnInspiron3537:pvrA06:rvnDellInc.:rn0PHTY0:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 3537 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1560845] Re: Wifi issue in Aspire E5-573 laptop
[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/1560845 Title: Wifi issue in Aspire E5-573 laptop Status in linux package in Ubuntu: Expired Bug description: Wifi issue in Aspire E5-573 laptop. Wifi option is avilable in ubuntu 12.0 and 14.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-83-generic 3.13.0-83.127 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bitlasoft 1800 F pulseaudio /dev/snd/controlC0: bitlasoft 1800 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 23 13:21:47 2016 HibernationDevice: RESUME=UUID=5cee7869-394c-42aa-beb4-dac893ab594e InstallationDate: Installed on 2016-03-22 (0 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=eace4efd-a76e-49ef-84e8-f0604ce93675 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-83-generic N/A linux-backports-modules-3.13.0-83-generic N/A linux-firmware 1.127.20 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2016-03-23 (0 days ago) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd05/27/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1530012] Re: Asus Touch not detected in AUSUS F555U after installation of Ubuntu.
[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/1530012 Title: Asus Touch not detected in AUSUS F555U after installation of Ubuntu. Status in linux package in Ubuntu: Expired Bug description: I bought a new Asus laptop about a couple of weeks back. Touchpad is working fine in windows 10 (default OS), however the touchpad wasn't detected by Ubuntu and therefore I'm unable to use touchpad at all. Laptop Model: ASUS F555U OS: Ubuntu 15.04 GNOME: 3.14.1 (Ubuntu 2015-03-18) Kernel:3.19.0-42-generic (#48-Ubuntu SMP Thu Dec 17 22:54:45 UTC 2015) And executing the commands below doesn't generate any output. 1) cat /proc/version_signature > version.log 2) sudo lspci -vnvn > lspci-vnvn.log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-42-generic 3.19.0-42.48 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: sakshamsingh 1554 F...m pulseaudio /dev/snd/controlC0: sakshamsingh 1554 F pulseaudio sakshamsingh 1795 F alsamixer CurrentDesktop: Unity Date: Wed Dec 30 12:21:33 2015 HibernationDevice: RESUME=UUID=7ac31225-e251-4e00-b4d1-0f9848cf28de InstallationDate: Installed on 2015-12-24 (5 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57de Realtek Semiconductor Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52e Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555UJ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-42-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-42-generic N/A linux-backports-modules-3.19.0-42-generic N/A linux-firmware 1.143.7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UJ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UJ 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.:bvrX555UJ.203:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX555UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UJ 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/1530012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477729] Re: /proc/meminfo reports 6.7 GiB, while lshw reports 8 GiB, meminfo reports 1.3 GiB less than lshw, a difference of 16.27%
[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/1477729 Title: /proc/meminfo reports 6.7 GiB, while lshw reports 8 GiB, meminfo reports 1.3 GiB less than lshw, a difference of 16.27% Status in linux package in Ubuntu: Expired Bug description: I have this laptop Acer Aspire E5-551G-T0KC http://www.acer.de/ac/de/DE/content/model/NX.MLEEG.009 It has 8 GiB memory. Meminfo system test fails with this message: "/proc/meminfo reports: 7024084.0 kB lshw reports: 8388608.0 kB FAIL: Meminfo reports 1397272576 bytes less than lshw, a difference of 16.27%. Only a variance of 10% in reported memory is allowed." I didn't test any other kernel because I don't know which version I should install. The system testing report is attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-44.59~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 23 20:51:49 2015 InstallationDate: Installed on 2015-06-16 (37 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: amr2526 F pulseaudio /dev/snd/controlC0: amr2526 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=a91d1031-cbcc-4078-903f-e781d597bee7 InstallationDate: Installed on 2015-06-16 (217 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire E5-551G NonfreeKernelModules: fglrx wl Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed root=UUID=80d75317-abae-46f8-af85-6dc9e9c10c5a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10 RelatedPackageVersions: linux-restricted-modules-3.19.0-43-generic N/A linux-backports-modules-3.19.0-43-generic N/A linux-firmware 1.127.19 Tags: trusty Uname: Linux 3.19.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EA50_KV dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd06/10/2015:svnAcer:pnAspireE5-551G:pvrV1.12:rvnAcer:rnEA50_KV:rvrV1.12:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-551G dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 13, failed: 2
tests ran: 13, failed: 2; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-24_03-19-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582963] dagmar (amd64) - tests ran: 40, failed: 1
tests ran: 40, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/dagmar__3.19.0-60.67~14.04.1__2016-05-24_02-45-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1582963 Title: linux-lts-vivid: 3.19.0-60.67~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-60.67~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1582780 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onibi (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-86.131/onibi__3.13.0-86.131__2016-05-24_02-25-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (i386) - tests ran: 18, failed: 6
tests ran: 18, failed: 6; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-24_01-28-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584953] Re: backport fix for /proc/net issues with containers
I posted a test build with the backport at the link below. Please test and verify that the issue is fixed in this build. Thanks! http://people.canonical.com/~sforshee/lp1584953/ ** Changed in: linux (Ubuntu Xenial) Status: In Progress => 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/1584953 Title: backport fix for /proc/net issues with containers Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Incomplete Bug description: Request to backport Kernel changes from Kernel 4.5 to lts kernel 4.4 for xenial and if possible to lts kernel for 14.04 Change upstream: netfilter: Set /proc/net entries owner to root in namespace http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/?id=f13f2aeed154da8e48f90b85e720f8ba39b1e881 This is the Kernel-side part of the fix for "iptables-save does not work inside lxd containers" https://github.com/lxc/lxd/issues/1978#issuecomment-220998013 The necessary changes in lxc landed in lxc/lxd https://github.com/lxc/lxc/pull/1014 and is available in version 2.0.1, currently in xenial-proposed. It would be great if this would be backported asap. As it allows to manage the firewall within lxd instances using Puppet and probably other configuration management systems. And to use iptables-save manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 26, failed: 4
tests ran: 26, failed: 4; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-24_02-42-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://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 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
Hi Christopher, I will give it a try but it may take some time. I have to learn to backup my system first. Appreciate if you can answer the 2 questions in my earlier post. This is to help me understand the error messages and how they affects my setup. Thanks. On 23/05/2016 19:34, Christopher M. Penalver wrote: > SunBear, in order to allow additional upstream developers to examine the > issue, at your earliest convenience, could you please test the latest > upstream kernel available from > http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind > the following: > 1) The one to test is at the very top line at the top of the page (not the > daily folder). > 2) The release names are irrelevant. > 3) The folder time stamps aren't indicative of when the kernel actually was > released upstream. > 4) Install instructions are available at > https://wiki.ubuntu.com/Kernel/MainlineBuilds . > > If testing on your main install would be inconvenient, one may: > 1) Install Ubuntu to a different partition and then test this there. > 2) Backup, or clone the primary install. > > If the latest kernel did not allow you to test to the issue (ex. you couldn't > boot into the OS) please make a comment in your report about this, and > continue to test the next most recent kernel version until you can test to > the issue. Once you've tested the upstream kernel, please comment on which > kernel version specifically you tested. If this issue is fixed in the > mainline kernel, please add the following tags by clicking on the yellow > circle with a black pencil icon, next to the word Tags, located at the bottom > of the report description: > kernel-fixed-upstream > kernel-fixed-upstream-X.Y-rcZ > > Where X, and Y are the first two numbers of the kernel version, and Z is > the release candidate number if it exists. > > If the mainline kernel does not fix the issue, please add the following tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-X.Y-rcZ > > Please note, an error to install the kernel does not fit the criteria of > kernel-bug-exists-upstream. > > Also, you don't need to apport-collect further unless specifically > requested to do so. > > Once testing of the latest upstream kernel is complete, please mark this > report Status Confirmed. Please let us know your results. > > Thank you for your understanding. > > ** Summary changed: > > - Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 > table load failures > + ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, > AE_NOT_FOUND (20150930/dswload-210) > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) Status in linux package in Ubuntu: Incomplete Bug description: [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-227) [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20150930/tbxfload-193) [ 0.021348] ACPI Error: 1 table load failures, 7 successful (20150930/tbxfload-214) I have noticed this ACPI error persisting in my syslog and dmesg. Based on what I have learnt from ACPI, acpitool -w and lspci, I think the error is related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which I think concerns the Root → System bus tree → PCI bus → USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB settings but to no avail. Appreciate help to fix this bug. I reported it as a question https://answers.launchpad.net/ubuntu/+question/293489 and to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690. https://launchpad.net/~penalvch advice me to make this ubuntu-bug report. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ uname -r 4.4.0-22-generic MB Bios: ASUS z170m-plus version 0704 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sunbear1604 1905 F pulseaudio /dev/snd/controlC0: sunbear1604 1905 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 07:48:53 2016 HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59 InstallationD
[Kernel-packages] [Bug 1582431] fozzie (amd64) - tests ran: 23, failed: 0
tests ran: 23, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/fozzie__4.4.0-23.41__2016-05-24_02-13-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 18, failed: 6
tests ran: 18, failed: 6; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-24_01-16-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
** Tags removed: severity-critical ** Tags added: severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onibi (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-87.132/onibi__3.13.0-87.132__2016-05-24_01-24-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] fozzie (i386) - tests ran: 13, failed: 0
tests ran: 13, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/fozzie__4.4.0-23.41__2016-05-24_00-48-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
** Tags added: architecture-ppc64le bugnameltc-141723 severity-critical targetmilestone-inin16041 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onibi (i386) - tests ran: 18, failed: 6
tests ran: 18, failed: 6; http://kernel.ubuntu.com/testing/3.13.0-86.131/onibi__3.13.0-86.131__2016-05-23_21-28-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-24_00-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584997] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
Public bug reported: No wifi connection with new installed ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: bcmwl-kernel-source: Install bcmwl-kernel-source: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon May 23 19:49:43 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-05-22 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1584997 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in bcmwl package in Ubuntu: New Bug description: No wifi connection with new installed ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: bcmwl-kernel-source: Install bcmwl-kernel-source: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon May 23 19:49:43 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-05-22 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1584997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 23, failed: 1
tests ran: 23, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-23.41/ms10-35-mcdivittB0-kernel__4.4.0-23.41__2016-05-24_00-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] fozzie (amd64) - tests ran: 40, failed: 0
tests ran: 40, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/fozzie__4.4.0-23.41__2016-05-23_23-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
Perfect. This is an upstream bugreport site: https://bugzilla.kernel.org/show_bug.cgi?id=109051 There are a lot of informations there. Is this the same thing? ** Bug watch added: Linux Kernel Bug Tracker #109051 http://bugzilla.kernel.org/show_bug.cgi?id=109051 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: In Progress Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac
This is fixed in zfs-linux in yakkety by way of having the 0.6.5.7
release.
** Changed in: zfs-linux (Ubuntu Yakkety)
Status: Confirmed => Fix Released
--
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/1567558
Title:
ZFS is confused by user namespaces (uid/gid mapping) when used with
acltype=posixac
Status in linux package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Confirmed
Status in linux source package in Yakkety:
Fix Released
Status in zfs-linux source package in Yakkety:
Fix Released
Bug description:
This report is copy/paste from the following upstream issue:
https://github.com/zfsonlinux/zfs/issues/4177
I was asked to file a matching Ubuntu bug for tracking.
Hello,
# First a quick introduction to the world of containers
I'm the project leader for LXC and LXD, working on containers on
Linux. We now extensively use the user namespaces to provide an extra
layer of security in Linux containers.
The user namespace allows one to map a range of uid and gid from the
host or parent namespace into another range of uid and gid of a new
namespace.
Typically what's done is that 65536 uids and gids are set aside per
non-system users on the host. Those users through a couple of setuid
helpers (newuidmap and newgidmap) can then setup a uid and gid map for
their processes. Their 65536 allocation is therefore mapped from
uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible
environment.
That means that given a user on the host with uid and gid range 10
through 165536, uid 100 in their container will be mapped to uid
100100 outside of it.
# The problem with ZFS
When using ZFS with acltype=posixacl and an ACL entry on the host set
for a uid (or gid) that's then mapped into the container, the
container doesn't see the right mapped value when querying the acl
from inside the namespace.
# Example with zfs (broken)
root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test
root@dakara:~# zfs set acltype=posixacl lxd/test
root@dakara:~# cd /tmp/test/
root@dakara:/tmp/test# mkdir a
root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a
root@dakara:/tmp/test# setfacl -m user:100100:rwX a
root@dakara:/tmp/test# getfacl a
# file: a
# owner: root
# group: root
user::rwx
user:100100:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:user:100100:rwx
default:group::r-x
default:mask::rwx
default:other::r-x
root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536
-- /bin/bash
root@dakara:/tmp/test (in userns)# ls -lh
total 512
drwxrwxr-x+ 2 nobody nogroup 2 Jan 7 22:19 a
root@dakara:/tmp/test (in userns)# getfacl -n a
# file: a
# owner: nobody
# group: nogroup
user::rwx
user:4294967295:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:user:4294967295:rwx
default:group::r-x
default:mask::rwx
default:other::r-x
# Example with ext4 (working)
root@dakara:/tmp/test.ext4# mkdir a
root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a
root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a
root@dakara:/tmp/test.ext4# getfacl a
# file: a
# owner: root
# group: root
user::rwx
user:100100:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:user:100100:rwx
default:group::r-x
default:mask::rwx
default:other::r-x
root@dakara:/tmp/test.ext4# lxc-usernsexec -m u:0:10:65536 -m
g:0:10:65536 -- /bin/bash
root@dakara:/tmp/test.ext4 (in userns)# ls -lh
total 4.0K
drwxrwxr-x+ 2 nobody nogroup 4.0K Jan 7 22:22 a
root@dakara:/tmp/test.ext4 (in userns)# getfacl -n a
# file: a
# owner: 65534
# group: 65534
user::rwx
user:100:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:user:100:rwx
default:group::r-x
default:mask::rwx
default:other::r-x
# Environment
This was noticed on Ubuntu 14.04 using the zfs stable PPA. I first
found it in production environments first with file servers
misbehaving due to the problem, then reproduced it on my development
systems.
The zfs version here is 0.6.5.3-1~trusty and I've seen this on 3.13,
3.16, 3.19 and 4.2 kernels (not that it should matter, the dkms code
was the same). zfs-dkms is at 2.53-zfs1.
The lxc-usernsexec helper tool I'm using there comes from the LXC
package in Ubuntu. It essentially causes a call to fork() followed by
a call to unshare(CLONE_NEWUSER), then calls the newuidmap and
newgidmap setuid helpers with the provided map so that the namespace
can be configured properly.
You could reproduce something similar using the simple unshare tool
and manual writes to /proc/PID/{u,g}i
[Kernel-packages] [Bug 1582431] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 13, failed: 3
tests ran: 13, failed: 3; http://kernel.ubuntu.com/testing/4.4.0-23.41/ms10-35-mcdivittB0-kernel__4.4.0-23.41__2016-05-23_22-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-23_23-54-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584528] Re: Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date A07 10/16/2015 The issue may not have improved but has not gotten worse. I did see it happen where the cursor did not go to the left edge, but it did happen to move to the left. ** 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/1584528 Title: Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly Status in linux package in Ubuntu: Confirmed Bug description: At times (mostly undetermined) when touching the glide pad to take an action the cursor will jump to the left edge of the screen. I do not recall the system ever taking ACTION based on the click at the new location. ex: side bar opening, etc It may not ever take the action at the ORIGINAL location, I can't be sure since I am only alerted when things don't happen as I expect. If I am using the keyboard to type or scroll (arrows) I have not noticed anything strange. I am not sure if it only happens when attempting a Left click or a Right Click. As a developer I think it is seeing my Click and reading the position incorrectly or hitting some other error condition. I do believe it is a result of my click. Tom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tom2103 F pulseaudio /dev/snd/controlC0: tom2103 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 16:30:13 2016 HibernationDevice: RESUME=UUID=ebc3eae4-8f8a-49c6-9d22-a59e4bdf0ec5 InstallationDate: Installed on 2015-07-17 (310 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3543 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=5b06297b-c923-468b-bc52-d2dfa945174c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-03 (19 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 01Y5DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn01Y5DY:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-23_20-06-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac
I tested this the xenial-proposed kernel (4.4.0-23) on a machine that was showing the exact symptoms described by the original reporter in Xenial. Here's the sequence of commands on the -proposed kernel: root@bonnetmaker:~# uname -a Linux bonnetmaker 4.4.0-23-lowlatency #41-Ubuntu SMP PREEMPT Mon May 16 23:55:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux root@bonnetmaker:~# zfs create lxd/test -o mountpoint=/tmp/test root@bonnetmaker:~# zfs set acltype=posixacl lxd/test root@bonnetmaker:~# cd /tmp/test/ root@bonnetmaker:/tmp/test# mkdir a root@bonnetmaker:/tmp/test# setfacl -m default:user:100100:rwX a root@bonnetmaker:/tmp/test# setfacl -m user:100100:rwX a root@bonnetmaker:/tmp/test# getfacl -n a # file: a # owner: 0 # group: 0 user::rwx user:100100:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:100100:rwx default:group::r-x default:mask::rwx default:other::r-x root@bonnetmaker:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 -- /bin/bash bash: /root/.bashrc: Permission denied root@bonnetmaker:/tmp/test# ls -lh total 512 drwxrwxr-x+ 2 nobody nogroup 2 May 23 16:24 a root@bonnetmaker:/tmp/test# getfacl -n a # file: a # owner: 65534 # group: 65534 user::rwx user:100:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:100:rwx default:group::r-x default:mask::rwx default:other::r-x root@bonnetmaker:/tmp/test# Numbers check out - looks like it's working now! ** Tags removed: verification-needed-xenial ** 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/1567558 Title: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Fix Released Status in zfs-linux source package in Yakkety: Confirmed Bug description: This report is copy/paste from the following upstream issue: https://github.com/zfsonlinux/zfs/issues/4177 I was asked to file a matching Ubuntu bug for tracking. Hello, # First a quick introduction to the world of containers I'm the project leader for LXC and LXD, working on containers on Linux. We now extensively use the user namespaces to provide an extra layer of security in Linux containers. The user namespace allows one to map a range of uid and gid from the host or parent namespace into another range of uid and gid of a new namespace. Typically what's done is that 65536 uids and gids are set aside per non-system users on the host. Those users through a couple of setuid helpers (newuidmap and newgidmap) can then setup a uid and gid map for their processes. Their 65536 allocation is therefore mapped from uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible environment. That means that given a user on the host with uid and gid range 10 through 165536, uid 100 in their container will be mapped to uid 100100 outside of it. # The problem with ZFS When using ZFS with acltype=posixacl and an ACL entry on the host set for a uid (or gid) that's then mapped into the container, the container doesn't see the right mapped value when querying the acl from inside the namespace. # Example with zfs (broken) root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test root@dakara:~# zfs set acltype=posixacl lxd/test root@dakara:~# cd /tmp/test/ root@dakara:/tmp/test# mkdir a root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a root@dakara:/tmp/test# setfacl -m user:100100:rwX a root@dakara:/tmp/test# getfacl a # file: a # owner: root # group: root user::rwx user:100100:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:100100:rwx default:group::r-x default:mask::rwx default:other::r-x root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 -- /bin/bash root@dakara:/tmp/test (in userns)# ls -lh total 512 drwxrwxr-x+ 2 nobody nogroup 2 Jan 7 22:19 a root@dakara:/tmp/test (in userns)# getfacl -n a # file: a # owner: nobody # group: nogroup user::rwx user:4294967295:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:4294967295:rwx default:group::r-x default:mask::rwx default:other::r-x # Example with ext4 (working) root@dakara:/tmp/test.ext4# mkdir a root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a root@dakara:/tmp/test.ext4# getfacl a # file: a # owner: root # group: root user::rwx user:100100:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:100100:rwx default:group::r-x defau
[Kernel-packages] [Bug 1582398] onza (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-23_23-09-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: On a xenial machine, I tried to use fanatic to configure the fan with underlay 10.88.0.0/16 and the suggested overlay 250.0.0.0/8, but the underlay suggested by fanatic (192.168.0.0/16) was used instead of 10.88.0.0/16 I specified. Here's the paste of the session: http://paste.ubuntu.com/16630235/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584092] Re: Docker misconfigured when using non-default overlay/underlay netmask size
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584092 Title: Docker misconfigured when using non-default overlay/underlay netmask size Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: Fan allows for variable sized subnet map sizes. For example, if I want to map a /24 to a /16 instead of the default /16 to /8, Fan supports this. However, when configuring this via fanatic, I see that docker configuration fails. In /etc/default/docker, the --fixed-cidr flag is defined incorrectly. $ sudo fanatic Welcome to the fanatic fan networking wizard. This will help you set up an example fan network and optionally configure docker and/or LXD touse this network. See fanatic(1) for more details. Configure fan underlay (hit return to accept, or specify alternative) [192.168.0.0/16]: 192.168.1.0/24 Configure fan overlay (hit return to accept, or specify alternative) [250.0.0.0/8]: 250.99.0.0/16 Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Profile fan-250-99 created Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: n Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: n This host IP address: 192.168.1.10 Remote test host IP address (none to skip): /usr/sbin/fanatic: Testing skipped $ grep "DOCKER_OPTS" /etc/default/docker # Use DOCKER_OPTS to modify the daemon startup options. #DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" DOCKER_OPTS=" -b fan-250-99 --mtu=1450 --iptables=false --fixed-cidr=250.99.10.0/40" May 20 05:15:30 macbook docker[27364]: time="2016-05-20T05:15:30.411933688-07:00" level=fatal msg="Error starting daemon: Error initializing network controller: invalid CIDR address: 250.99.10.0/40" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584150] Re: fanatic: legacy mode triggers syntax error
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584150 Title: fanatic: legacy mode triggers syntax error Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: Attempting to use the legacy command line format leads to a syntax error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584845] Re: fanctl.8: typeo of interface (as interfane) in manual
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584845 Title: fanctl.8: typeo of interface (as interfane) in manual Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: To bring up Fan slices corresponding to the addresses on the primary network interfane (the inteface with the default route), the keyword To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1535054] Re: fanatic doesn't respond to --help
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1535054 Title: fanatic doesn't respond to --help Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: Trying out fanatic today I found it didn't respect a lot of conventional input, like --help or -h. Please provide useful output for -? and -h and --help as well as "fanatic help" Also, you have a typo with "uknown command" :) Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1535054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584775] Re: fanatic does not use the correct LXD command to import image for fanatic-test container
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584775 Title: fanatic does not use the correct LXD command to import image for fanatic-test container Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: Something I noticed while trying to use fanatic (see related bug 1584692): /usr/sbin/fanatic: 808: /usr/sbin/fanatic: lxd-images: not found Because of this the lxd test cannot spin up the test container, as it can't import the image. I managed to get it to work by patching fanatic like this: --- # Check if we have images already... lxc image show fanatic-test >/dev/null 2>&1 if [ "$?" -ne 0 ]; then echo "local lxd test: pulling container images ..." lxc image copy ubuntu:xenial local: --alias fanatic-test local rc="$?" if [ "$rc" -ne 0 ]; then echo "local lxd test: lxc image import failure, skipping test." return "$rc" fi fi --- There's no lxd-images on my machine and I suspect it used to be one in an earlier version of the LXD package. I'm using lxd 2.0.1-0ubuntu1~16 amd64 ubuntu-fan is 0.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582956] Re: fan[ctl | atic] man page has reference to ubuntu.com/fan which 404s
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1582956 Title: fan[ctl | atic] man page has reference to ubuntu.com/fan which 404s Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: Reading the man page for fanctl and fanatic I see a reference to ubuntu.com/fan, but that page is currently 404'ing Specifically: $ man fanctl -or- $ man fanatic . . . SEE ALSO fanctl(8) /usr/share/doc/ubuntu-fan/README http://www.ubuntu.com/fan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1582956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584878] Re: fanatic remote host test fails when using non-default subnet sizes
This bug was fixed in the package ubuntu-fan - 0.10.0 --- ubuntu-fan (0.10.0) yakkety; urgency=medium [ Andy Whitcroft ] * fanatic: fix legacy command line form syntax error (LP: #1584150) * fanctl/fanatic: add help commands/options with initial pointers (LP: #1535054) [ Jay Vosburgh ] * fanatic: fix underlay with calculation (LP: #1584092) [ Andy Whitcroft ] * fanctl/fanatic: remove invalid web reference from manual pages. (LP: #1582956) * debian/control: fix use of obsolete > operator * fanatic: detect user specified underlay address without overlay (LP: #1584692) * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775) * fanctl.8: fix interfane type (LP: #1584845) * fanatic: test-host -- use the selected underlay width to calculate the remote addresses (LP: #1584878) -- Andy Whitcroft Mon, 23 May 2016 22:05:19 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released -- 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/1584878 Title: fanatic remote host test fails when using non-default subnet sizes Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: When conducting the remote host testing, fanatic incorrectly calculates the ip for the remote test host on the Fan. My remote host ip's are 192.168.1.3 and 192.168.1.10. I'm using non- default subnet sizes for the overlay/underlays (ie -o 250.99.0.0/16 and -u 192.168.1.0/24). Both LXD and Docker tests pass, but, as noted, the remote host testing fails: test slave: ping test (250.99.1.4) ... test slave: ping test ... FAIL You'll notice the ip is incorrect, 250.99.1.4. It should be 250.99.3.1 in this example. Raw output of failing fanatic test run is below: $ sudo fanatic Welcome to the fanatic fan networking wizard. This will help you set up an example fan network and optionally configure docker and/or LXD to use this network. See fanatic(1) for more details. Configure fan underlay (hit return to accept, or specify alternative) [192.168.0.0/16]: 192.168.1.0/24 Configure fan overlay (hit return to accept, or specify alternative) [250.0.0.0/8]: 250.99.0.0/16 Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Profile fan-250-99 created Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: Y Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: Y local lxd test: creating test container (Ubuntu:16.04) ... Creating fanatic-test Starting fanatic-test lxd test: Waiting for addresses on eth0 ... lxd test: Waiting for addresses on eth0 ... lxd test: Waiting for addresses on eth0 ... lxd test: Waiting for addresses on eth0 ... test master: ping test (250.99.10.166) ... test slave: ping test (250.99.10.1) ... test master: ping test ... PASS test master: short data test (250.99.10.1 -> 250.99.10.166) ... test slave: ping test ... PASS test slave: short data test (250.99.10.166 -> 250.99.10.1) ... test slave: short data ... PASS test master: short data ... PASS test slave: long data test (250.99.10.166 -> 250.99.10.1) ... test master: long data test (250.99.10.1 -> 250.99.10.166) ... test master: long data ... PASS test slave: long data ... PASS local lxd test: destroying test container ... local lxd test: test complete PASS (master=0 slave=0) Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16 (NOTE: potentially triggers large image downloads) [Yn]: Y local docker test: creating test container ... e47583ee4f18c95edfcb28e5b2514c0924527f30b3485f62d343fe8bf1000170 test master: ping test (250.99.10.0) ... test slave: ping test (250.99.10.1) ... test master: ping test ... PASS test master: short data test (250.99.10.1 -> 250.99.10.0) ... test slave: ping test ... PASS test slave: short data test (250.99.10.0 -> 250.99.10.1) ... test slave: short data ... PASS test master: short data ... PASS test slave: long data test (250.99.10.0 -> 250.99.10.1) ... test master: long data test (250.99.10.1 -> 250.99.10.0) ... test master: long data ... PASS test slave: long data ... PASS local docker test: destroying test container ... fanatic-test fanatic-test local docker test: test complete PASS (master=0 slave=0) This host IP address: 192.168.1.10 Remote test host IP address (none to skip): 192.168.1.3 host test: starting ... test slave: ping test (250.99.1.4) ... test slave: ping test ... FAIL --- transcript start --- PING 250.99.1.4 (250.99.1.4) 56(84) bytes of data. From 250.99.10.1 icmp_seq=1 Destination Host Unreachable From 250.99.10.1 icmp_seq=2 Destination Host Unreachable From 250.99.10.1 icmp_seq=3 Destination Host Unreachable From
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
yup, commit 8d7804a2f03dbd34940fcb426450c730adf29dae has the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: In Progress Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
Chris, rc7 was the newest kernel for Wily. I reinstalled the newest 16.04 (again 64 bit) and tested the 4.6.0 version from a week later (4.6.0-040600-generic #201605151930) and it's stll bad. Dan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION Status in linux package in Ubuntu: Incomplete Bug description: The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 seconds until reset. The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 7419]. The Dell Poweredge 1800 has newest BIOS (A07). All hardware has been tested thoroughly OK except possibly the APIC component (Serverset Northbridge?). The 14.04LTS with all updates (or not) works fine with a perfectly consistent throughput of 77MB/s (slowest HD=66MB/s), RAID5. 15.10 has the hangs of 10-60 seconds, AND with newest updates as of 26-FEB-2016. I have changed PCI interrupts around and moved card slots to minimize sharing and removed cards - repeatedly. All hard drives and cables have been thoroughly tested, but the drives are mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s. The drives not only work perfectly in 14.04LTS, but all Windows versions and DOS/BIOS-INT 19 as well (0x13). I have tried all combinations of card RAID options Read ahead, Write cache, and other BIOS options. Relevant dmesg lines (these were consecutive): [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0) [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ? [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0) [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.365 CurrentDesktop: Unity Date: Thu Mar 3 05:08:57 2016 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi file=u15.10-64/preseed/username.seed boot=casper netboot=nfs nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz ipv6.disable=1 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0P8611 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A04 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (amd64) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-23_22-51-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584967] 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/1584967 Title: package linux-image-3.13.0-86-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: Computer went to sleep, asked for password to log in but couldn't log back in again. Had to restart the computer. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-86-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cory 1767 F pulseaudio Date: Mon May 23 17:51:05 2016 DuplicateSignature: package:linux-image-3.13.0-86-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=52b16263-e494-402e-9ccd-fc9d0788aac6 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-86-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/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM DVI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.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.:bvr0905:bd12/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMDVI:rvrRevx.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/ubuntu/+source/linux/+bug/1584967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (i386) - tests ran: 13, failed: 1
tests ran: 13, failed: 1; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-23_21-11-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668934/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668930/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668935/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668936/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668931/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668937/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668928/+files/CurrentDmesg.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/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] Re: Java threads produce OutOfMemoryError with 4.4.0-22 kernel
Would it be more helpful to run apport-collect with the 4.4.0-22 kernel running after the OutOfMemoryError has occurred? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668929/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668932/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668933/+files/ProcCpuinfo.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/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 16:44 seq crw-rw 1 root audio 116, 33 May 21 16:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 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: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 InstallationDate: Installed on 2015-04-08 (411 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: HP ProLiant DL380 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584471] Re: Java threads produce OutOfMemoryError with 4.4.0-22 kernel
apport information ** Tags added: apport-collected ** Description changed: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.start0(Native Method)|at java.lang.Thread.start(Thread.java:714)|at org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)| Thanks. Mike. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 21 16:44 seq + crw-rw 1 root audio 116, 33 May 21 16:44 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2 + 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: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1 + InstallationDate: Installed on 2015-04-08 (411 days ago) + InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) + MachineType: HP ProLiant DL380 G7 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro + ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-41-generic N/A + linux-backports-modules-3.16.0-41-generic N/A + linux-firmware 1.157 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 3.16.0-41-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/02/2013 + dmi.bios.vendor: HP + dmi.bios.version: P67 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380 G7 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1584471/+attachment/4668927/+files/CRDA.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/1584471 Title: Java threads produce OutOfMemoryError with 4.4.0-22 kernel Status in linux package in Ubuntu: Incomplete Bug description: Hi all. I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM. I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it. When I stopped the Wowza service from the command line, the service command would hang until I killed the java process. I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7. Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel? Wowza starts Java with the -Xmx1M option. One of the log entries for this error is: WARNserver comment 2016-05-20 23:55:21- - - --5405.152- - - - - - - - Unexpected exception.: java.lang.OutOfMemoryError: unable to create new native thread|at java.lang.Thread.
[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
Hi! What kind of (realistic) timeline can we expect here? (With the move
to ZFS for containers, I wonder :)
E.g. is this part of your goals for 16.10? (I mean: for the AppArmor
/Ubuntu-specific parts, as I've learnt to be patient wrt. the
upstreaming to Linux mainline.)
Thanks for your work on AppArmor!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status in AppArmor:
In Progress
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Triaged
Bug description:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include
profile foo {
#include
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i < argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
}
else {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt",
argv[i]);
}
mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
}
chdir("/mnt");
pivot_root(".", ".");
chroot(".");
chdir("/");
execl("/bin/bash", "/bin/bash", NULL);
}
$ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable. UPDATE: upstream is
currently working on this and Ubuntu will engage with them
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584967] Re: package linux-image-3.13.0-86-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/1584967 Title: package linux-image-3.13.0-86-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: Computer went to sleep, asked for password to log in but couldn't log back in again. Had to restart the computer. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-86-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cory 1767 F pulseaudio Date: Mon May 23 17:51:05 2016 DuplicateSignature: package:linux-image-3.13.0-86-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=52b16263-e494-402e-9ccd-fc9d0788aac6 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-86-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/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM DVI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.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.:bvr0905:bd12/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMDVI:rvrRevx.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/ubuntu/+source/linux/+bug/1584967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584967] [NEW] package linux-image-3.13.0-86-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Computer went to sleep, asked for password to log in but couldn't log back in again. Had to restart the computer. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-86-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cory 1767 F pulseaudio Date: Mon May 23 17:51:05 2016 DuplicateSignature: package:linux-image-3.13.0-86-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=52b16263-e494-402e-9ccd-fc9d0788aac6 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-86-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/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM DVI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.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.:bvr0905:bd12/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMDVI:rvrRevx.xx: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 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584967 Title: package linux-image-3.13.0-86-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: Computer went to sleep, asked for password to log in but couldn't log back in again. Had to restart the computer. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-86-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cory 1767 F pulseaudio Date: Mon May 23 17:51:05 2016 DuplicateSignature: package:linux-image-3.13.0-86-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=52b16263-e494-402e-9ccd-fc9d0788aac6 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: linux Title: package linux-image-3.13.0-86-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/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM DVI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modal
[Kernel-packages] [Bug 1525969] Re: Brightness Hotkeys FN (F5, F6) not working in Asus F555L
I did a Video . https://www.youtube.com/watch?v=AeF02zoLQi0 Sorry that my English is so pur. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525969 Title: Brightness Hotkeys FN (F5,F6) not working in Asus F555L Status in linux package in Ubuntu: Confirmed Bug description: Brightness Hotkeys FN (F5,F6) not working. WORKAROUND: I can adjust the backlight when I click on Power Settings then screen brightness. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yevhen 2338 F pulseaudio /dev/snd/controlC0: yevhen 2338 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a4a0847f-abca-4a89-b8e3-a0a4bfba845c InstallationDate: Installed on 2015-11-28 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 248a:8564 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=cb214afc-47f5-4e1e-9d00-77f967de126f ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LB.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LB 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.:bvrX555LB.505:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LB 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/1525969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582823] Re: Text not rendering correctly after resume from suspend
Changed status to "Confirmed" since hackel seems to have executed the requested "apport-collect". This bug affects me too. I'm also running the i915 driver: $ sudo lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:f000-f03f memory:e000-efff ioport:5000(size=64) ** 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/1582823 Title: Text not rendering correctly after resume from suspend Status in gtk+3.0 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Chromium renders just fine when this happens, other than the titlebar. Similarly, Cool Retro Term renders correctly, which obviously doesn't use gtk, while Gnome Terminal and Guake do not. This suggests it could be related to framebuffer corruption, but this report was made with a much earlier kernel, and I had no such problems under 15.10. http://askubuntu.com/questions/688306/text-missing- garbled-after-laptop-resumes-from-sleep-mode libgtk-3-0 3.18.9-1ubuntu3 linux-image-4.4.0-22-generic 4.4.0-22.40 xserver-xorg-core 2:1.18.3-1ubuntu2 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) dmesg | grep i915 [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, scanline start 1059, end 1090 [ 277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, scanline start 875, end 900 [ 284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, scanline start 891, end 905 [ 300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, scanline start 1070, end 1084 [ 302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, scanline start 1061, end 1078 [ 470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, scanline start 1071, end 1091 [ 595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, scanline start 1056, end 1083 [ 1043.512803] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=63370 end=63371) time 402 us, min 1073, max 1079, scanline start 1058, end 1084 [ 1106.508551] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=66184 end=66185) time 424 us, min 894, max 899, scanline start 876, end 895 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: U
[Kernel-packages] [Bug 1582823] Re: Text not rendering correctly after resume from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (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/1582823 Title: Text not rendering correctly after resume from suspend Status in gtk+3.0 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Chromium renders just fine when this happens, other than the titlebar. Similarly, Cool Retro Term renders correctly, which obviously doesn't use gtk, while Gnome Terminal and Guake do not. This suggests it could be related to framebuffer corruption, but this report was made with a much earlier kernel, and I had no such problems under 15.10. http://askubuntu.com/questions/688306/text-missing- garbled-after-laptop-resumes-from-sleep-mode libgtk-3-0 3.18.9-1ubuntu3 linux-image-4.4.0-22-generic 4.4.0-22.40 xserver-xorg-core 2:1.18.3-1ubuntu2 xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 lshw -c video *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:30 memory:b200-b23f memory:a000-afff ioport:5000(size=64) dmesg | grep i915 [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0 [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, scanline start 1059, end 1090 [ 277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, scanline start 875, end 900 [ 284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, scanline start 891, end 905 [ 300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, scanline start 1070, end 1084 [ 302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, scanline start 1061, end 1078 [ 470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, scanline start 1071, end 1091 [ 595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, scanline start 1056, end 1083 [ 1043.512803] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=63370 end=63371) time 402 us, min 1073, max 1079, scanline start 1058, end 1084 [ 1106.508551] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=66184 end=66185) time 424 us, min 894, max 899, scanline start 876, end 895 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hackel 4767 F pulseaudio /dev/snd/controlC0: hackel 4767 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=74970338-0a72-4e51-8fbf-71e3a0831acb InstallationDate: Installed on 2014-08-03 (653 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite P75-A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=9b00c4
[Kernel-packages] [Bug 1584953] Re: backport fix for /proc/net issues with containers
Fix is already present in yakkety unstable. Marking devleopment task fixed. ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584953 Title: backport fix for /proc/net issues with containers Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Request to backport Kernel changes from Kernel 4.5 to lts kernel 4.4 for xenial and if possible to lts kernel for 14.04 Change upstream: netfilter: Set /proc/net entries owner to root in namespace http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/?id=f13f2aeed154da8e48f90b85e720f8ba39b1e881 This is the Kernel-side part of the fix for "iptables-save does not work inside lxd containers" https://github.com/lxc/lxd/issues/1978#issuecomment-220998013 The necessary changes in lxc landed in lxc/lxd https://github.com/lxc/lxc/pull/1014 and is available in version 2.0.1, currently in xenial-proposed. It would be great if this would be backported asap. As it allows to manage the firewall within lxd instances using Puppet and probably other configuration management systems. And to use iptables-save manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1583288] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi not available
Update: First I tried to perform: apport-collect 1583288 which ended in this error/bug mentioned here: Error Msg: "ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt4.QtCore" Bug: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784 I tried to fix this error to no avail. I followed the following hints mentioned here: https://stackoverflow.com/questions/7119844/importerror-no-module-named- pyqt4-qtcore Which did not help. But I tried to collect an many infos about the system as possible: --- The Notebook is: HP ProBook 455 G2 Version: A3009DD10303 (Made in China - No P/N nor S/N on any sticker!!!) --- lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) I/O Memory Management Unit 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R4 Graphics] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:03.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1424 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - BIOS Information Vendor: Hewlett-Packard Version: M75 Ver. 01.06 Release Date: 07/25/2014 - wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:off 3.13.0-86-generic Architecture: x86_64 Module Size Used by rtl8723be 139363 0 btcoexist 183378 1 rtl8723be rtl_pci39740 1 rtl8723be rtlwifi 101828 3 btcoexist,rtl_pci,rtl8723be ctr13049 1 ccm17773 1 rt2800usb 27034 0 rt2x00usb 20742 1 rt2800usb rt2800lib 89076 1 rt2800usb rt2x00lib 55307 3 rt2x00usb,rt2800lib,rt2800usb crc_ccitt 12707 1 rt2800lib rfcomm 69160 12 bnep 19624 2 snd_hda_codec_realtek65904 1 snd_hda_codec_hdmi 46368 1 uvcvideo 80885 0 videobuf2_vmalloc 13216 1 uvcvideo vi
[Kernel-packages] [Bug 1584953] Re: backport fix for /proc/net issues with containers
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584953 Title: backport fix for /proc/net issues with containers Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Request to backport Kernel changes from Kernel 4.5 to lts kernel 4.4 for xenial and if possible to lts kernel for 14.04 Change upstream: netfilter: Set /proc/net entries owner to root in namespace http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/?id=f13f2aeed154da8e48f90b85e720f8ba39b1e881 This is the Kernel-side part of the fix for "iptables-save does not work inside lxd containers" https://github.com/lxc/lxd/issues/1978#issuecomment-220998013 The necessary changes in lxc landed in lxc/lxd https://github.com/lxc/lxc/pull/1014 and is available in version 2.0.1, currently in xenial-proposed. It would be great if this would be backported asap. As it allows to manage the firewall within lxd instances using Puppet and probably other configuration management systems. And to use iptables-save manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
okay, just tested it. commit 8d7804a2f03dbd34940fcb426450c730adf29dae seems to have the bug! andrew@andrew-Inspiron-3451:~$ uname -a Linux andrew-Inspiron-3451 4.1.0-040100-generic #201605230749 SMP Mon May 23 12:55:56 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux BAD Will test again to make sure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: In Progress Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525969] Re: Brightness Hotkeys FN (F5, F6) not working in Asus F555L
** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525969 Title: Brightness Hotkeys FN (F5,F6) not working in Asus F555L Status in linux package in Ubuntu: Confirmed Bug description: Brightness Hotkeys FN (F5,F6) not working. WORKAROUND: I can adjust the backlight when I click on Power Settings then screen brightness. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yevhen 2338 F pulseaudio /dev/snd/controlC0: yevhen 2338 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a4a0847f-abca-4a89-b8e3-a0a4bfba845c InstallationDate: Installed on 2015-11-28 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 248a:8564 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=cb214afc-47f5-4e1e-9d00-77f967de126f ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LB.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LB 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.:bvrX555LB.505:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LB 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/1525969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onibi (amd64) - tests ran: 18, failed: 5
tests ran: 18, failed: 5; http://kernel.ubuntu.com/testing/3.13.0-87.132/onibi__3.13.0-87.132__2016-05-23_18-48-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584953] [NEW] backport fix for /proc/net issues with containers
Public bug reported: Request to backport Kernel changes from Kernel 4.5 to lts kernel 4.4 for xenial and if possible to lts kernel for 14.04 Change upstream: netfilter: Set /proc/net entries owner to root in namespace http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/?id=f13f2aeed154da8e48f90b85e720f8ba39b1e881 This is the Kernel-side part of the fix for "iptables-save does not work inside lxd containers" https://github.com/lxc/lxd/issues/1978#issuecomment-220998013 The necessary changes in lxc landed in lxc/lxd https://github.com/lxc/lxc/pull/1014 and is available in version 2.0.1, currently in xenial-proposed. It would be great if this would be backported asap. As it allows to manage the firewall within lxd instances using Puppet and probably other configuration management systems. And to use iptables-save manually ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Seth Forshee (sforshee) 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/1584953 Title: backport fix for /proc/net issues with containers Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Request to backport Kernel changes from Kernel 4.5 to lts kernel 4.4 for xenial and if possible to lts kernel for 14.04 Change upstream: netfilter: Set /proc/net entries owner to root in namespace http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/?id=f13f2aeed154da8e48f90b85e720f8ba39b1e881 This is the Kernel-side part of the fix for "iptables-save does not work inside lxd containers" https://github.com/lxc/lxd/issues/1978#issuecomment-220998013 The necessary changes in lxc landed in lxc/lxd https://github.com/lxc/lxc/pull/1014 and is available in version 2.0.1, currently in xenial-proposed. It would be great if this would be backported asap. As it allows to manage the firewall within lxd instances using Puppet and probably other configuration management systems. And to use iptables-save manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584935] Re: Backport cxlflash patch related to EEH recovery into Xenial SRU stream
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584935 Title: Backport cxlflash patch related to EEH recovery into Xenial SRU stream Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: ---Problem Description--- Request to backport cxlflash EEH patch to Xenial SRU ---System Hang--- When a cxlflash adapter goes into EEH recovery and multiple processes (each having established its own context) are active, the EEH recovery can hang if the processes attempt to recover in parallel. After debugging the problem, patch has been upstreamed for this issue and the system has been rebooted with the fix for the problem ---Steps to Reproduce--- Injecting EEH when multiple processes are active can trigger the issue Stack trace output: Call Trace: __switch_to+0x2f0/0x410 __schedule+0x300/0x980 schedule+0x48/0xc0 rwsem_down_write_failed+0x294/0x410 down_write+0x88/0xb0 cxlflash_pci_error_detected+0x100/0x1c0 [cxlflash] cxl_vphb_error_detected+0x88/0x110 [cxl] cxl_pci_error_detected+0xb0/0x1d0 [cxl] eeh_report_error+0xbc/0x130 eeh_pe_dev_traverse+0x94/0x160 eeh_handle_normal_event+0x17c/0x450 eeh_handle_event+0x184/0x370 eeh_event_handler+0x1c8/0x1d0 kthread+0x110/0x130 ret_from_kernel_thread+0x5c/0xa4 INFO: task blockio:33215 blocked for more than 120 seconds. The upstream patch we need backported to Xenial SRU stream is 635f6b0893cff193a1774881ebb1e4a4b9a7fead cxlflash: Fix to resolve dead-lock during EEH recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584935/+subscriptions -- Mailing list: https://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 1506817] Re: left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)
good, I'm glad someone else is seeing this problem. Here is a test I would like you to try: boot up into the BIOS, and turn off only the trackpad. Leave the pointing (red button) on. Then boot up into linux, and BEFORE you login in, see if the trackpad responds to the touch. On my X250, it does, and that is a problem with the BIOS not working properly. I have three thinkpads with a trackpad, and the with the two that work, I can turn off the trackpad, and the trackpad is off before I login in. This may not be the only issue with this bug, but it aggravates it. If the trackpad could be turned off in the BIOS (as it should be) then that would be a work-around. I am able to use the X250 only if I use a USB (external) mouse. The trackpad is too buggy to use. On 05/23/2016 02:31 PM, HorstBort wrote: > FWIW, I have this problem with the middle trackpoint button on a T460s. > > hauke ~ uname -a > Linux tbort 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > > Here's an excerpt from sudo evtest /dev/input/event6: > > Event: time 1464031476.627418, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031476.627418, -- SYN_REPORT > Event: time 1464031476.733121, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031476.733121, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031477.097493, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031477.097493, -- SYN_REPORT > Event: time 1464031477.193284, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031477.193284, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031477.403549, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031477.403549, -- SYN_REPORT > Event: time 1464031477.498914, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031477.498914, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031478.182503, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031478.182503, -- SYN_REPORT > Event: time 1464031478.287124, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031478.287124, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031479.629252, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031479.629252, -- SYN_REPORT > Event: time 1464031479.754756, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031479.754756, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031480.616778, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031480.616778, -- SYN_REPORT > Event: time 1464031480.733700, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031480.733700, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031481.835976, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031481.835976, -- SYN_REPORT > Event: time 1464031481.970351, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031481.970351, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031482.307006, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031482.307006, -- SYN_REPORT > Event: time 1464031482.402378, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031482.402378, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031482.584996, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031482.584996, -- SYN_REPORT > Event: time 1464031482.709775, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031482.709775, -- SYN_REPORT > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031201.617512, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031483.035733, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 > Event: time 1464031483.035733, -- SYN_REPORT > Event: time 1464031483.131556, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 > Event: time 1464031483.131556,
[Kernel-packages] [Bug 1584947] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1584947 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/1584947 Title: I have the same issue Status in linux package in Ubuntu: Incomplete Bug description: I have Asus F555L To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582398] onza (amd64) - tests ran: 40, failed: 2
tests ran: 40, failed: 2; http://kernel.ubuntu.com/testing/3.13.0-87.132/onza__3.13.0-87.132__2016-05-23_19-33-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582398 Title: linux: 3.13.0-87.132 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-87.132 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang
I don't use MATE either. I am using 16.04 LTS but I have the same problem as it is described in this bug. Besides the bug report mentioned above is a duplicate of bug #1574347. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Fix Committed Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581869] Re: CVE-2016-4581
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1581869 Title: CVE-2016-4581 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-man
[Kernel-packages] [Bug 1580372] Re: CVE-2016-4565
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1580372 Title: CVE-2016-4565 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in
[Kernel-packages] [Bug 1583963] Re: CVE-2016-4805
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1583963 Title: CVE-2016-4805 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source pac
[Kernel-packages] [Bug 1578496] Re: CVE-2016-4485
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1578496 Title: CVE-2016-4485 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in lin
[Kernel-packages] [Bug 1578493] Re: CVE-2016-4482
** Description changed: [information leak in devio] + + Break-Fix: - 681fef8380eb818c0b845fca5d2ab1dcbab114ee -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1578493 Title: CVE-2016-4482 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-ras
[Kernel-packages] [Bug 1579140] Re: CVE-2016-4558
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1579140 Title: CVE-2016-4558 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: Invalid Status in linux-goldfish source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status i
[Kernel-packages] [Bug 1578497] Re: CVE-2016-4486
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1578497 Title: CVE-2016-4486 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in lin
[Kernel-packages] [Bug 1584192] Re: CVE-2016-4440
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1584192 Title: CVE-2016-4440 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2
[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1571020 Title: CVE-2016-3961 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in
[Kernel-packages] [Bug 1575706] Re: CVE-2016-2187
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1575706 Title: CVE-2016-2187 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in lin
[Kernel-packages] [Bug 1584935] Re: Backport cxlflash patch related to EEH recovery into Xenial SRU stream
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Released ** Changed in: linux (Ubuntu Yakkety) Assignee: Taco Screen team (taco-screen-team) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584935 Title: Backport cxlflash patch related to EEH recovery into Xenial SRU stream Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: ---Problem Description--- Request to backport cxlflash EEH patch to Xenial SRU ---System Hang--- When a cxlflash adapter goes into EEH recovery and multiple processes (each having established its own context) are active, the EEH recovery can hang if the processes attempt to recover in parallel. After debugging the problem, patch has been upstreamed for this issue and the system has been rebooted with the fix for the problem ---Steps to Reproduce--- Injecting EEH when multiple processes are active can trigger the issue Stack trace output: Call Trace: __switch_to+0x2f0/0x410 __schedule+0x300/0x980 schedule+0x48/0xc0 rwsem_down_write_failed+0x294/0x410 down_write+0x88/0xb0 cxlflash_pci_error_detected+0x100/0x1c0 [cxlflash] cxl_vphb_error_detected+0x88/0x110 [cxl] cxl_pci_error_detected+0xb0/0x1d0 [cxl] eeh_report_error+0xbc/0x130 eeh_pe_dev_traverse+0x94/0x160 eeh_handle_normal_event+0x17c/0x450 eeh_handle_event+0x184/0x370 eeh_event_handler+0x1c8/0x1d0 kthread+0x110/0x130 ret_from_kernel_thread+0x5c/0xa4 INFO: task blockio:33215 blocked for more than 120 seconds. The upstream patch we need backported to Xenial SRU stream is 635f6b0893cff193a1774881ebb1e4a4b9a7fead cxlflash: Fix to resolve dead-lock during EEH recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584947] [NEW] I have the same issue
Public bug reported: I have Asus F555L ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584947 Title: I have the same issue Status in linux package in Ubuntu: New Bug description: I have Asus F555L To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561403] Re: CVE-2016-2117
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561403 Title: CVE-2016-2117 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package
[Kernel-packages] [Bug 1581202] Re: CVE-2016-0758
** Changed in: linux-raspi2 (Ubuntu Yakkety) Status: Fix Released => New ** Changed in: linux-snapdragon (Ubuntu Yakkety) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1581202 Title: CVE-2016-0758 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source packa
[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1566580 Title: CVE-2015-8839 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package i
[Kernel-packages] [Bug 1582991] Re: conflicting modules in udebs - arc4.ko
** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582991 Title: conflicting modules in udebs - arc4.ko Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Bug description: cryptop/arc4.ko appears to be in both nic-moudles and crypto-modules. Unpacking nic-modules-4.4.0-22-generic-di (4.4.0-22.40) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/lib/modules/4.4.0-22-generic/kernel/crypto/arc4.ko', which is also in package crypto-modules-4.4.0-22-generic-di 4.4.0-22.40 Not a problem per se, as d-i build just forces through this, but still ugly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1582431] modoc (ppc64el) - tests ran: 65, failed: 1
tests ran: 65, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-23.41/modoc__4.4.0-23.41__2016-05-23_19-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1582431 Title: linux: 4.4.0-23.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-23.41 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584912] Re: Xenial update to 4.4.11 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584912 Title: Xenial update to 4.4.11 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed 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.11 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.11 stable release shall be applied: decnet: Do not build routes to devices without decnet private data. route: do not cache fib route info on local routes with oif packet: fix heap info leak in PACKET_DIAG_MCLIST sock_diag interface net: sched: do not requeue a NULL skb bpf/verifier: reject invalid LD_ABS | BPF_DW instruction cdc_mbim: apply "NDP to end" quirk to all Huawei devices net: use skb_postpush_rcsum instead of own implementations vlan: pull on __vlan_insert_tag error path and fix csum correction openvswitch: use flow protocol when recalculating ipv6 checksums ipv4/fib: don't warn when primary address is missing if in_dev is dead net/mlx4_en: fix spurious timestamping callbacks bpf: fix check_map_func_compatibility logic samples/bpf: fix trace_output example net: Implement net_dbg_ratelimited() for CONFIG_DYNAMIC_DEBUG case gre: do not pull header in ICMP error processing net_sched: introduce qdisc_replace() helper net_sched: update hierarchical backlog too sch_htb: update backlog as well sch_dsmark: update backlog as well netem: Segment GSO packets on enqueue net: fec: only clear a queue's work bit if the queue was emptied VSOCK: do not disconnect socket when peer has shutdown SEND only net: bridge: fix old ioctl unlocked net device walk bridge: fix igmp / mld query parsing uapi glibc compat: fix compile errors when glibc net/if.h included before linux/if.h MIME-Version: 1.0 net: fix a kernel infoleak in x25 module net: thunderx: avoid exposing kernel stack tcp: refresh skb timestamp at retransmit time net/route: enforce hoplimit max value ocfs2: revert using ocfs2_acl_chmod to avoid inode cluster lock hang ocfs2: fix posix_acl_create deadlock zsmalloc: fix zs_can_compact() integer overflow crypto: qat - fix invalid pf2vf_resp_wq logic crypto: hash - Fix page length clamping in hash walk crypto: testmgr - Use kmalloc memory for RSA input ALSA: usb-audio: Quirk for yet another Phoenix Audio devices (v2) ALSA: usb-audio: Yet another Phoneix Audio device quirk ALSA: hda - Fix subwoofer pin on ASUS N751 and N551 ALSA: hda - Fix white noise on Asus UX501VW headset ALSA: hda - Fix broken reconfig spi: pxa2xx: Do not detect number of enabled chip selects on Intel SPT spi: spi-ti-qspi: Fix FLEN and WLEN settings if bits_per_word is overridden spi: spi-ti-qspi: Handle truncated frames properly pinctrl: at91-pio4: fix pull-up/down logic regmap: spmi: Fix regmap_spmi_ext_read in multi-byte case perf/core: Disable the event on a truncated AUX record vfs: add vfs_select_inode() helper vfs: rename: check backing inode being equal ARM: dts: at91: sam9x5: Fix the memory range assigned to the PMC workqueue: fix rebind bound workers warning regulator: s2mps11: Fix invalid selector mask and voltages for buck9 regulator: axp20x: Fix axp22x ldo_io voltage ranges atomic_open(): fix the handling of create_error qla1280: Don't allocate 512kb of host tags tools lib traceevent: Do not reassign parg after collapse_tree() get_rock_ridge_filename(): handle malformed NM entries Input: max8997-haptic - fix NULL pointer dereference Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing" drm/radeon: fix PLL sharing on DCE6.1 (v2) drm/i915: Bail out of pipe config compute loop on LPT drm/i915/bdw: Add missing delay during L3 SQC credit programming drm/radeon: fix DP link training issue with second 4K monitor nf_conntrack: avoid kernel pointer value leak in slab name Linux 4.4.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
