[Kernel-packages] [Bug 1614887] Re: Lage samba file transfers block btrfs to hung task
this bug exsits since ubuntu moved to Samba 4.3. with 4.2 everything worked gerat currently used: Version 4.3.11-Ubuntu ** Changed in: linux (Ubuntu) Status: Expired => 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/1614887 Title: Lage samba file transfers block btrfs to hung task Status in linux package in Ubuntu: New Bug description: this bug occurs when user transfer big files ~1gb to the samba server on xenial/wily on wily this problem was NOT showing with samba 4.2 (i guess) until samba was also upgraded to 4.3. the samba runs on a KVM VM samba version: 4.3.9+dfsg-0ubuntu0.16.04. [ 30.171211] zram: Added device: zram0 [ 30.356301] zram0: detected capacity change from 0 to 1518252032 [ 30.668855] Adding 1482664k swap on /dev/zram0. Priority:5 extents:1 across:1482664k SSFS [ 35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors config: c9e3, 0 [ 45.008364] Non-volatile memory driver v1.3 [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds. [65636.820128] Not tainted 4.4.0-36-generic #55-Ubuntu [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [65636.820131] btrfs-cleaner D 88005ae93ce8 0 631 2 0x [65636.820137] 88005ae93ce8 8800bbb86400 8801b0dc3e80 8801b0dc2580 [65636.820139] 88005ae94000 8801851971f0 880185197000 8801851971f0 [65636.820141] 0001 88005ae93d00 81829ec5 8801b7fc4000 [65636.820143] Call Trace: [65636.820182] [] schedule+0x35/0x80 [65636.820360] [] wait_current_trans.isra.21+0xd3/0x120 [btrfs] [65636.820395] [] ? wake_atomic_t_function+0x60/0x60 [65636.820409] [] start_transaction+0x2c5/0x4b0 [btrfs] [65636.820434] [] btrfs_start_transaction+0x18/0x20 [btrfs] [65636.820452] [] btrfs_drop_snapshot+0x7f/0x830 [btrfs] [65636.820454] [] ? __schedule+0x3b6/0xa30 [65636.820467] [] btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs] [65636.820480] [] cleaner_kthread+0xcf/0x220 [btrfs] [65636.820493] [] ? check_leaf+0x360/0x360 [btrfs] [65636.820497] [] kthread+0xd8/0xf0 [65636.820499] [] ? kthread_create_on_node+0x1e0/0x1e0 [65636.820505] [] ret_from_fork+0x3f/0x70 [65636.820507] [] ? kthread_create_on_node+0x1e0/0x1e0 [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds. [65636.820551] Not tainted 4.4.0-36-generic #55-Ubuntu [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [65636.820559] kworker/u4:1D 880008433c48 0 7760 2 0x [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs] [65636.820581] 880008433c48 0040 8800b9d98c80 8801b51a9900 [65636.820582] 880008434000 8801851941f0 880185194000 8801851941f0 [65636.820584] 0001 880008433c60 81829ec5 8801b7fc4000 [65636.820586] Call Trace: [65636.820588] [] schedule+0x35/0x80 [65636.820602] [] wait_current_trans.isra.21+0xd3/0x120 [btrfs] [65636.820604] [] ? wake_atomic_t_function+0x60/0x60 [65636.820620] [] start_transaction+0x275/0x4b0 [btrfs] [65636.820650] [] btrfs_join_transaction+0x17/0x20 [btrfs] [65636.820667] [] btrfs_finish_ordered_io+0x435/0x650 [btrfs] [65636.820692] [] finish_ordered_fn+0x15/0x20 [btrfs] [65636.820718] [] btrfs_scrubparity_helper+0xca/0x2f0 [btrfs] [65636.820723] [] ? try_to_wake_up+0x47/0x3b0 [65636.820741] [] btrfs_endio_write_helper+0xe/0x10 [btrfs] [65636.820753] [] process_one_work+0x165/0x480 [65636.820755] [] worker_thread+0x4b/0x4c0 [65636.820757] [] ? process_one_work+0x480/0x480 [65636.820758] [] kthread+0xd8/0xf0 [65636.820760] [] ? kthread_create_on_node+0x1e0/0x1e0 [65636.820761] [] ret_from_fork+0x3f/0x70 [65636.820763] [] ? kthread_create_on_node+0x1e0/0x1e0 [65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds. [65636.820771] Not tainted 4.4.0-36-generic #55-Ubuntu [65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [65636.820773] kworker/u4:2D 880102027c48 0 7814 2 0x [65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs] [65636.820850] 880102027c48 0040 8801b51ae400 8801b51a8c80 [65636.820852] 880102028000 8801851941f0 880185194000 8801851941f0 [65636.820853] 0001 880102027c60 81829ec5 8801b7fc4000 [65636.820855] Call Trace: [65636.820857] [] schedule+0x35/0x80 [65636.820877] [] wait_current_trans.isra.21+0xd3/0x120 [btrfs] [65636.820879] [] ? wake_atomic_t_function+0x60/0x60 [65636.820893
[Kernel-packages] [Bug 1614887] Re: Lage samba file transfers block btrfs to hung task
still not fixed INFO: task smbd:7543 blocked for more than 120 seconds. [39600.198893] Not tainted 4.4.0-46-generic #67-Ubuntu [39600.198894] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [39600.198896] smbdD 88000970be18 0 7543 1346 0x [39600.198902] 88000970be18 00020010 81e11500 8801539c5780 [39600.198904] 88000970c000 8800ba7eb524 8801539c5780 [39600.198906] 8800ba7eb528 88000970be30 81830795 8800ba7eb520 [39600.198908] Call Trace: [39600.198942] [] schedule+0x35/0x80 [39600.198944] [] schedule_preempt_disabled+0xe/0x10 [39600.198946] [] __mutex_lock_slowpath+0xb9/0x130 [39600.198948] [] mutex_lock+0x1f/0x30 [39600.198967] [] do_unlinkat+0x12b/0x2d0 [39600.198969] [] SyS_unlink+0x16/0x20 [39600.198974] [] entry_SYSCALL_64_fastpath+0x16/0x71 [39720.198606] INFO: task btrfs-cleaner:212 blocked for more than 120 seconds. [39720.198614] Not tainted 4.4.0-46-generic #67-Ubuntu [39720.198616] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [39720.198619] btrfs-cleaner D 8801539bfce8 0 212 2 0x [39720.198625] 8801539bfce8 8801bfd16d00 8801b8228000 8801539c [39720.198629] 8801539c 8800a7ed11f0 8800a7ed1000 8800a7ed11f0 [39720.198632] 0001 8801539bfd00 81830795 8801b797ef30 [39720.198636] Call Trace: [39720.198647] [] schedule+0x35/0x80 [39720.198783] [] wait_current_trans.isra.21+0xd3/0x120 [btrfs] [39720.198802] [] ? wake_atomic_t_function+0x60/0x60 [39720.198815] [] start_transaction+0x2c5/0x4b0 [btrfs] [39720.198828] [] btrfs_start_transaction+0x18/0x20 [btrfs] [39720.198839] [] btrfs_drop_snapshot+0x7f/0x830 [btrfs] [39720.198841] [] ? __schedule+0x3b6/0xa30 [39720.198854] [] btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs] [39720.198866] [] cleaner_kthread+0xcf/0x220 [btrfs] [39720.198878] [] ? check_leaf+0x360/0x360 [btrfs] [39720.198914] [] kthread+0xd8/0xf0 [39720.198917] [] ? kthread_create_on_node+0x1e0/0x1e0 [39720.198919] [] ret_from_fork+0x3f/0x70 [39720.198921] [] ? kthread_create_on_node+0x1e0/0x1e0 [39720.198938] INFO: task nmbd:1308 blocked for more than 120 seconds. [39720.198940] Not tainted 4.4.0-46-generic #67-Ubuntu [39720.198941] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [39720.198942] nmbdD 8801b6277ac8 0 1308 1 0x [39720.198945] 8801b6277ac8 0286 8801539c0c80 8801b4a52580 [39720.198947] 8801b6278000 8801bfd16d00 7fff 81830f90 [39720.198949] 8801b6277c20 8801b6277ae0 81830795 [39720.198951] Call Trace: [39720.198953] [] ? bit_wait+0x60/0x60 [39720.198954] [] schedule+0x35/0x80 [39720.198956] [] schedule_timeout+0x1b5/0x270 [39720.198963] [] ? sched_clock+0x9/0x10 [39720.198971] [] ? kvm_clock_get_cycles+0x1e/0x20 [39720.198983] [] ? ktime_get+0x3c/0xb0 [39720.198985] [] ? bit_wait+0x60/0x60 [39720.198986] [] io_schedule_timeout+0xa4/0x110 [39720.198988] [] bit_wait_io+0x1b/0x70 [39720.198990] [] __wait_on_bit+0x5d/0x90 [39720.199000] [] wait_on_page_bit+0xcb/0xf0 [39720.199003] [] ? autoremove_wake_function+0x40/0x40 [39720.199016] [] prepare_pages+0x17d/0x190 [btrfs] [39720.199030] [] __btrfs_buffered_write+0x200/0x5f0 [btrfs] [39720.199044] [] btrfs_file_write_iter+0x171/0x560 [btrfs] [39720.199051] [] ? kmem_cache_alloc+0x187/0x1f0 [39720.199055] [] ? getname_flags+0x56/0x1f0 [39720.199058] [] new_sync_write+0x9b/0xe0 [39720.199060] [] __vfs_write+0x26/0x40 [39720.199065] [] vfs_write+0xa9/0x1a0 [39720.199067] [] SyS_write+0x55/0xc0 [39720.199069] [] entry_SYSCALL_64_fastpath+0x16/0x71 [39720.199075] INFO: task kworker/u4:0:6969 blocked for more than 120 seconds. [39720.199076] Not tainted 4.4.0-46-generic #67-Ubuntu [39720.199077] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [39720.199078] kworker/u4:0D 880028903c48 0 6969 2 0x [39720.199106] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs] [39720.199108] 880028903c48 0001801a001a 8801b7708000 8801b7c98000 [39720.199110] 880028904000 8800a7ed59f0 8800a7ed5800 8800a7ed59f0 [39720.199112] 0001 880028903c60 81830795 8801b797ef30 [39720.199114] Call Trace: [39720.199116] [] schedule+0x35/0x80 [39720.199129] [] wait_current_trans.isra.21+0xd3/0x120 [btrfs] [39720.199131] [] ? wake_atomic_t_function+0x60/0x60 [39720.199144] [] start_transaction+0x275/0x4b0 [btrfs] [39720.199158] [] btrfs_join_transaction+0x17/0x20 [btrfs] [39720.199172] [] btrfs_finish_ordered_io+0x435/0x650 [btrfs] [39720.199196] [] ? find_next_bit+0x15/0x20 [39720.199211] [] finish_ordered_fn+0x15/0x20 [btrfs] [39720.199227] [] btrfs_scrubp
[Kernel-packages] [Bug 1626564] Re: 4.8 regression: SLAB is being used instead of SLUB
Are you sure SLAB vs. SLUB fixed this? I have images built from October 13 and today (October 22) with 4.8.0-22-generic and 4.8.0-26-generic respectively. On a 4.8.0-22-generic boot there are 37 kworker threads, on 4.8.0-26-generic there are 524 kworker threads. It could be that with enough reboots the older version would spawn as many threads, I'm not sure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626564 Title: 4.8 regression: SLAB is being used instead of SLUB Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: We're seeing hundreds of kernel worker threads being spawned with some actions, for example, after booting the desktop and hutting the brightness keys causes this. On investigation, this occurs when CONFIG_SLAB is being used. 1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of CONFIG_SLAB (why was it changed for Yakkety?) 2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker threads 3 CONFIG_SLUB seems more performant on the boot too over SLAB. Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial configs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported
** Changed in: hwe-next Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1589905 Title: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Yakkety: Fix Released Bug description: Firmware for this card isn't in the current linux-firmware package. Latest upstream firmware is also tested but doesn't work either. The only working firmware is extracted from Windows driver. By comparing the md5sum, the only different file is ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is df5ba1), we need Qualcomm to upstream the file to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1589905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec
When the fixed gonna release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447909 Title: external mic not detected on machines with alc256 codec Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is used for tracking, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1447909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635242] onibi (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-46.67/onibi__4.4.0-46.67__2016-10-27_04-35-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/1635242 Title: linux: 4.4.0-46.67 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635424] onza (i386) - tests ran: 19, failed: 1
tests ran: 19, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-74.82/onza__3.19.0-74.82__2016-10-27_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/1635424 Title: linux: 3.19.0-74.82 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-74.82 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
I've completed the AppArmor test plan: https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor I've also manually verified the AppArmor portion of this SRU with the kernel currently in xenial-updates (4.4.0-45.66) and the kernel in xenial-proposed (4.4.0-46.67), which contains a number of AppArmor changes. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630069 Title: Regression tests can not detect binfmt_elf mmpa semantic change Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: New Status in apparmor source package in Yakkety: Won't Fix Status in linux source package in Yakkety: Fix Released Bug description: == apparmor SRU == [Impact] * The exec_stack.sh regression test fails due to a behavior change in 4.8 kernels from this patch: commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 Author: Linus Torvalds Date: Mon Aug 22 16:41:46 2016 -0700 binfmt_elf: switch to new creds when switching to new mm * The regression tests were fixed for this kernel change but they were fixed in a way that always assumed that kernel change is present. They should have been adjusted so that they act differently according to whether or not the kernel change is present (it is a change that could end up being backported through the stable trees). [Test Case] $ apt-get source apparmor # make sure this fetches the new apparmor source $ sudo apt-get install libapparmor-dev $ cd tests/regression/apparmor $ make USE_SYSTEM=1 $ sudo bash exec_stack.sh The previous command should result in no output and return value of 0. [Regression Potential] * This is an extremely low risk change since it only touches regression testing code that is not user-facing. [Other] * Fixed in upstream lp:apparmor tree: https://bazaar.launchpad.net/~apparmor- dev/apparmor/master/revision/3558 == Original description == The regression tests are currently hard coded to the semantics of mmap in binfmt_elf With the recent upstream commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap changed resulting in test failures. The tests have been patched for this change but it results in the test breaking for everyone using upstream releases against pre 4.8 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1630069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573648] Re: 16.04 -> AMD APU via VGA gives blank screen
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1573648 Title: 16.04 -> AMD APU via VGA gives blank screen Status in linux package in Ubuntu: Fix Released Bug description: After upgrade to 16.04, the system will only show a blank screen when a monitor is connected to the VGA output. The system itself is able to completely start-up (checked via a ssh login). Starting up using an older kernel (in this case 4.2.0) gives a functional graphical system. Possibly related dmesg lines (when booting 4.4.0): kernel: [9.131059] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage kernel: [9.131088] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed It might be related to the following kernel post (but i am not entirely sure): https://lists.freedesktop.org/archives/dri-devel/2016-March/10.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 2014 F pulseaudio /dev/snd/controlC0: rene 2014 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 16:29:44 2016 HibernationDevice: RESUME=UUID=98dbb6ee-ff08-4e9f-b01d-55b2f28c6a1e InstallationDate: Installed on 2015-12-29 (114 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=/dev/mapper/VGelmo-LVroot ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd12/04/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635428] onibi (amd64) - tests ran: 5, failed: 0
tests ran: 5, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/onibi__3.16.0-78.101~14.04.1__2016-10-27_03-43-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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug is for tracking the 3.19.0-74.82~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 -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-47.68 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: Uploaded + kernel-stable-phase-changed:Thursday, 27. October 2016 03:04 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true derivative-trackers-created: true phase: Uploaded - kernel-stable-phase-changed:Thursday, 27. October 2016 03:04 UTC - kernel-stable-phase:Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636330] Comment bridged from LTC Bugzilla
--- Comment From p...@au1.ibm.com 2016-10-26 22:34 EDT--- (In reply to comment #150) > Was the attached patch accepted upstream? There were two patches, and they were both accepted upstream. Commit IDs are 56c46222af0d09149fadec2a3ce9d4 and 09b7e37b18eecc1e347f4b1a3bc863. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: New Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637031] 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/1637031 Title: In cold startup there is dark/blank screen Status in linux package in Ubuntu: Confirmed Bug description: When I startup my computer, I can see very fast screen given any information. When cold startup process finish the screen is dark, usb mouse light is on, keyboard light is on, but the computer does not accept ctrl+alt+del and I must reboot with reset button on computer case. Several seconds latter, the screen displays such as hard drives, one ssd, are mounted and then the system information appears until the gnome desktop. This problem always appears in the cold start. I changed CR2032 motherboard battery and the problems continues. This problem first appeared in the update and upgrade kernel and grub cat /proc/version_signature Ubuntu 3.13.0-101.148-lowlatency 3.13.11-ckt39 sudo lspci -vnvn [sudo] password for hugo: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4191 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 27. October 2016 01:18 UTC ** Description changed: This bug is for tracking the 4.4.0-47.68 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: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 27. October 2016 01:18 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637031] [NEW] In cold startup there is dark/blank screen
Public bug reported: When I startup my computer, I can see very fast screen given any information. When cold startup process finish the screen is dark, usb mouse light is on, keyboard light is on, but the computer does not accept ctrl+alt+del and I must reboot with reset button on computer case. Several seconds latter, the screen displays such as hard drives, one ssd, are mounted and then the system information appears until the gnome desktop. This problem always appears in the cold start. I changed CR2032 motherboard battery and the problems continues. This problem first appeared in the update and upgrade kernel and grub cat /proc/version_signature Ubuntu 3.13.0-101.148-lowlatency 3.13.11-ckt39 sudo lspci -vnvn [sudo] password for hugo: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4191 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0
[Kernel-packages] [Bug 1587265] Re: ubuntu not work with tickless kernel boot option
What specific kernel version had the problem? You can check with: uname -a The CONFIG_NO_HZ_FULL kernel param was turned off at some point between trusty's 3.13 and xenial's 4.4, and without that kernel param enabled the nohz_full boot param has no effect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1587265 Title: ubuntu not work with tickless kernel boot option Status in linux package in Ubuntu: Confirmed Bug description: For redhat, we have such guide like https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Performance_Tuning_Guide/Red_Hat_Enterprise_Linux-7-Performance_Tuning_Guide-en-US.pdf and for tickless kernel, (use dynamic tickless ways) 1. config grub with following cmdline $ cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash isolcpus=1-2 nohz_full=1-2" GRUB_CMDLINE_LINUX="" I used nohz_full here, and it is CPU 1, 2 here. 2. update-grub after that. 3. Then reboot system 4. execute following $ sudo perf stat -C 1 -e irq_vectors:local_timer_entry taskset -c 1 stress -t 1 -c 1 stress: info: [3869] dispatching hogs: 1 cpu, 0 io, 0 vm, 0 hdd stress: info: [3869] successful run completed in 1s Performance counter stats for 'CPU(s) 1': 252 irq_vectors:local_timer_entry 1.001491203 seconds time elapsed It always 252, (the default 250 HZ), seems tickless kernel option not have any effect, whether config it or not, both have same results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
I built the another test kernel, up to the same commit: a7fd20d1c476af4563e66865213474a2f9f473a4 This kernel also has the two patches. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1626436/a7fd20d1c476af4563e66865213474a2f9f473a4 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626466] Re: [Yakkety] suspend fail and reboot while resuming
The latest Yakkety kernel now also has all the updates that are in upstream 4.8 final. Can you apply the latest updates and see if this bug still exits? Thanks! ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626466 Title: [Yakkety] suspend fail and reboot while resuming Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Suspend by closing lid or setting menu, both randomly(2 out of 3 times) cause system reboot after suspend. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-6git1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 22 18:07:09 2016 InstallationDate: Installed on 2016-09-22 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=5ce90c47-3ebd-4119-9522-ad3d23f95ce3 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1576815] Re: No wireless access for BCM 43162 [14e4:43ae] rev 02
I ended up replacing the wifi/bluetooth module by an "Intel Dual Band Wireless-AC 3160" module, which is supported both by Linux (Mint) and W10. Costs about 30 euros Kind regards, Benno -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1576815 Title: No wireless access for BCM 43162 [14e4:43ae] rev 02 Status in linux package in Ubuntu: Triaged Bug description: I would like to report missing driver for Broadcom wlan identified as BCM 43162 [14e4:43ae] rev 02. Bug was reported in past here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chobot 1406 F pulseaudio /dev/snd/controlC0: chobot 1406 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 29 20:11:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 80N6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=e86ca941-78f4-4c7f-89f0-845a49b61a7d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN61WW:bd07/21/2015:svnLENOVO:pn80N6:pvrLenovoYoga500-15IBD:rvnLENOVO:rnLenovoYoga500-15IBD:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15IBD: dmi.product.name: 80N6 dmi.product.version: Lenovo Yoga 500-15IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1576815] Re: No wireless access for BCM 43162 [14e4:43ae] rev 02
Hello! I just bought a Laptop and aimed to use it with Ubuntu. What I didn't know was that it contained this WiFi-chip. I followed the trail of e-mails between Chobot and the community, after that i ended up here. I can see that the status is "triage" and importance is "wishlist". So my question is: Is there some ongoing development that i can provide information too? Or should i aim to either switch out the WiFi-chip or roll it back to Win 8.1? (hopeing not to get the rollback answer, my frist attempt at useing Linux and Ubuntu, kind of the reason i bought the laptop. But thats my problem and not yours.) Best regards Martin Steen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1576815 Title: No wireless access for BCM 43162 [14e4:43ae] rev 02 Status in linux package in Ubuntu: Triaged Bug description: I would like to report missing driver for Broadcom wlan identified as BCM 43162 [14e4:43ae] rev 02. Bug was reported in past here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432869 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chobot 1406 F pulseaudio /dev/snd/controlC0: chobot 1406 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 29 20:11:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: LENOVO 80N6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=e86ca941-78f4-4c7f-89f0-845a49b61a7d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN61WW:bd07/21/2015:svnLENOVO:pn80N6:pvrLenovoYoga500-15IBD:rvnLENOVO:rnLenovoYoga500-15IBD:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15IBD: dmi.product.name: 80N6 dmi.product.version: Lenovo Yoga 500-15IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627496] Re: radeon broken with kernel 4.6.0+
There's a test patch at https://bugzilla.kernel.org/show_bug.cgi?id=175391 Any test reports would be welcome. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627496 Title: radeon broken with kernel 4.6.0+ Status in linux package in Ubuntu: Confirmed Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 4.6.0 inclusive (4.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
> In the meantime, it might be worthwhile to test v4.9-rc2. It's available from: > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2/ Still slow boot/high load, i. e. BAD. > I built the another test kernel, up to the same commit: > 7afd16f882887c9adc69cd1794f5e5723217 That's GOOD. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1622502] Re: pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override
So, TL;DR you switched from 4.8.0.7-13 (unstable, right?) to 4.8.0-17 generic and profit? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1622502 Title: pmd_set_huge: Cannot satisfy [mem 0xf000-0xf020] with a huge- page mapping due to MTRR override Status in linux package in Ubuntu: Invalid Bug description: This is logged with the 4.8 kernels 4.8.0.7-13 actualy used, from the unstable ppa Its an upstream problem, as such error is found all over the distros. Can not say if its due to incompatible hardware, buggy bios or lintian/systemd/acpi/... reason(s) nor if a booting setting is required note: this does not semms affecting the system (in my case at least). The hardware is quite old, and the bios is no more upgradable. Relative links: https://lwn.net/Articles/635357/ https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.2.y&id=b73522e0c1be58d3c69b124985b8ccf94e3677f7 " Drivers should make a mapping request aligned to a single MTRR entry when the range is covered by MTRRs. " cat /proc/mtrr reg00: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable reg01: base=0x0 (0MB), size= 4096MB, count=1: write-back reg02: base=0x1 ( 4096MB), size= 1024MB, count=1: write-back sudo dmesg | grep -5 -i mtrr [0.00] SMBIOS 2.4 present. [0.00] DMI: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 300207/22/2010 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x14 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-D uncachable [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0C000 mask FC000 uncachable [0.00] 1 base 0 mask F write-back [0.00] 2 base 1 mask FC000 write-back [0.00] 3 disabled [0.00] 4 disabled -- [0.249861] ACPI: Interpreter enabled [0.249882] ACPI: (supports S0 S1 S3 S4 S5) [0.249886] ACPI: Using IOAPIC for interrupt routing [0.249918] PCI: MMCONFIG for domain [bus 00-3f] at [mem 0xf000-0xf3ff] (base 0xf000) [0.250976] PCI: MMCONFIG at [mem 0xf000-0xf3ff] reserved in ACPI motherboard resources [0.250986] pmd_set_huge: Cannot satisfy [mem 0xf000-0xf020] with a huge-page mapping due to MTRR override. [0.251065] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.255750] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.255758] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.255767] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [0.255778] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1821 F pulseaudio /dev/snd/pcmC0D0p: oem1821 F...m pulseaudio /dev/snd/controlC0: oem1821 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. lono wireless extensions. eth1 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-7-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.8.0-7.8-generic 4.8.0-rc5 RelatedPackageVersions: linux-restricted-modules-4.8.0-7-generic N/A linux-backports-modules-4.8.0-7-generic N/A linux-firmware 1.160 RfKill: Tags: yakkety Uname: Linux 4.8.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled
[Kernel-packages] [Bug 1636625] 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: Confirmed Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636940] Re: linux: 4.4.0-46.67 -proposed tracker
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636940 Title: linux: 4.4.0-46.67 -proposed tracker Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.4.0-46.67 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4
** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: New Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634050] Re: Please enable CONFIG_VFIO_NOIOMMU
** Changed in: linux (Ubuntu Zesty) 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/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Fix Committed Status in dpdk source package in Zesty: New Status in linux source package in Zesty: Fix Committed Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8] May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 1000a73-1000a83 rw-p
[Kernel-packages] [Bug 1636625] Re: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile
Is it not complete now? ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1636625 Title: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile Status in linux package in Ubuntu: New Bug description: Recommended change: remove incorrect extra ) character root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile 615c615 < -fstack-protector not supported by compiler) --- > -fstack-protector not supported by compiler)) This bug causes driver builds to fail like this make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic' /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: CONFIG_X86_X32 enabled but no binutils support Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not supported by compiler Makefile:614: *** missing separator. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic' make: *** [all] Error 2 --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493 InstallationDate: Installed on 2014-09-03 (784 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: bond0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant ML110 G5 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-100-generic N/A linux-backports-modules-3.13.0-100-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-100-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/25/2010 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.asset.tag: No Asset Tag dmi.board.name: ProLiant ML110 G5 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633634] Re: sr-iov not working on ubuntu 16.04 kvm
Kernel 4.5-wily => same result as 4.4.0-42 and 4.4.25 for both vfio and kvm Kernel 4.6-yakkety => same result as 4.7 for vfio (as I said earlier vm starts but with no networking and logs of errors in logs) and same as 4.5-wily for kvm Kernel 4.7 => same as 4.6-yakkety for both vfio and kvm Kernel 4.8-rc1 => fails to boot with "Loading initial ramdisk..." So kernel 4.8.4 and 4.9-rc1 both worked with the kvm option but none of the others. (4.8-rc1 unknown) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633634 Title: sr-iov not working on ubuntu 16.04 kvm Status in linux package in Ubuntu: Confirmed Bug description: The exact same set up (hardware and commands I have made) worked perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The only thing I have changed between the 2 setups is adding to the network definition as the now default vfio also failed with qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 0x7fa68770) = -14 (Bad address) qemu: hardware error: vfio: DMA mapping failed, unable to continue If I am doing something wrong I apologise, this is my first bug report and I'm still relatively new to Linux. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-42-generic 4.4.0-42.62 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 14 20:11 seq crw-rw 1 root audio 116, 33 Oct 14 20:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Oct 14 23:05:26 2016 HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91 InstallationDate: Installed on 2016-10-08 (6 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU PRIMERGY TX1310 M1 PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on iommu=pt pci=assign-busses quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x dmi.board.name: D3219-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3219-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: TX1310M1 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1: dmi.product.name: PRIMERGY TX1310 M1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 64, failed: 1
tests ran: 64, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_19-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635721] Re: Add a driver for Amazon Elastic Network Adapters (ENA)
** 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/1635721 Title: Add a driver for Amazon Elastic Network Adapters (ENA) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Back-porting this driver to Ubuntu LTS generic kernels would be beneficial. commit 1738cd3ed342294360d6a74d4e5884bff854 linux-next "net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_19-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 141, failed: 140
tests ran: 141, failed: 140; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_19-00-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** No longer affects: linux (Ubuntu Zesty) ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Vivid) Status: New => Triaged ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu Precise) Status: New => Triaged ** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Tags added: kernel-da-key kernel-hyper-v ** Tags added: bot-stop-nagging precise trusty vivid xenial yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636656 Title: [Hyper-V] netvsc: fix incorrect receive checksum offloading Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: The Hyper-V netvsc driver was looking at the incorrect status bits in the checksum info. It was setting the receive checksum unnecessary flag based on the IP header checksum being correct. The checksum flag is skb is about TCP and UDP checksum status. Because of this bug, any packet received with bad TCP checksum would be passed up the stack and to the application causing data corruption. The problem is reproducible via netcat and netem. This had a side effect of not doing receive checksum offload on IPv6. The driver was also also always doing checksum offload independent of the checksum setting done via ethtool. Signed-off-by: Stephen Hemminger https://patchwork.ozlabs.org/patch/685660/ When this patch is committed I will include the commit ID in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 19, failed: 8
tests ran: 19, failed: 8; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_18-47-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
I built another Trusty test kernel. However, this kernel is with a cherry pick of commit 9ecf07a1d8f7 and without the reverts. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1634892/ Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect
I also run into this "HcDoneHead not written back; disabled" problem with the latest self compiled kernel 4.8.4 on debian 8. And the disappearing device is an "Eaton 5S 700" ups. It works with the last 4.7.10 without problems. So for the moment i will stick to 4.7.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 33, failed: 1
tests ran: 33, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-50-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
I built the another test kernel, up to the same commit: 7afd16f882887c9adc69cd1794f5e5723217 This kernel also has the two patches. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1626436 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636941] Packages available
Derivative packages from packages here can be worked on, the following tracking bugs were opened for them: linux-raspi2 - bug 1636946 linux-snapdragon - bug 1636948 Backport packages from packages here can be worked on, the following tracking bugs were opened for them: linux-lts-xenial (14.04.1) - bug 1636951 ** Description changed: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC ** Description changed: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC + + -- swm properties -- + derivative-trackers-created: true + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work
It does not have the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: Confirmed Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed 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/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Wednesday, 26. October 2016 18:02 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-38-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636940] [NEW] linux: 4.4.0-46.67 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed-xenial kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636940 Title: linux: 4.4.0-46.67 -proposed tracker Status in linux package in Ubuntu: New Bug description: This bug is for tracking the 4.4.0-46.67 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636941] [NEW] linux: 4.4.0-47.68 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-p
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_17-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1562778] Re: I2C touchscreen init failed on HP X360
** Changed in: linux (Ubuntu Wily) Assignee: Phidias (phidias-chiang) => (unassigned) ** Changed in: linux (Ubuntu Wily) Status: In Progress => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1562778 Title: I2C touchscreen init failed on HP X360 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Won't Fix Status in linux source package in Xenial: Fix Released Bug description: [Impact] As title, after upgrading to latest Vivid kernel the touchscreen failed. After bisecting shows this revert cause the regression: commit 95df597989f6f297db63dd8669656d10f5f48eb1 Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" [Fix] The reverted patch has had a revised version upstreamed: commit de16d55206c5ce82ad44590b01718fbe2323853c Author: Andy Shevchenko Date: Fri Dec 4 23:49:19 2015 +0200 ACPI / LPSS: allow to use specific PM domain during ->probe() For Vivid it depends on a patch to device core for adding BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick. For Xenial the touchscreen still works because the original patch is not reverted, and with the patch reverted the I2C touchscreen still works fine, so I'll skip Xenial for this patch. For Wily it also contains the revert patch as Vivid, but the I2C on X360 still works. [Test] 3.19.0-56 -> Failed 3.19.0-56 + patches -> OK (Including suspend) 4.2.0-34 (with revert patch already) -> OK 4.4.0-15 -> OK 4.4.0-15 + revert patch -> OK 4.4.0-15 + patches -> N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1562778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_16-17-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: linux (Ubuntu Zesty) Importance: Medium Assignee: Colin Ian King (colin-king) Status: 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 EDT--- Debian kernel package with genwqe-bad-page.patch applied. ** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/bugs/1559194/+attachment/4767763/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel
[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
Broadcom found root cause and proposed the following fix: https://marc.info/?l=linux-block&m=147731657127810&w=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Incomplete Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
Can you give 4.5-rc1 a test? It is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
@bitgandtter Intel added driver support for hardware that is not released yet, so there are no available firmware. The only affect it has on any actual system is these warnings, it's nothing to worry about. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1611124 Title: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 Status in xen: Unknown Status in linux-firmware package in Ubuntu: Invalid Bug description: $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency [...] update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.159 Uname: Linux 4.8.0-040800rc1-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 Date: Mon Aug 8 17:50:38 2016 Dependencies: InstallationDate: Installed on 2015-07-26 (379 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/1611124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1632786
Title:
[Hyper-V] do not lose pending heartbeat vmbus packets
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Precise:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Bug description:
Hyper-V hosts can continue sending heartbeat packets to guests
independent of whether earlier packets have responses, which led to a
potential issue of these packets being dropped when responses took too
long to process. Lost heartbeats will lead to the host diagnosing that
the guest is dead and should be shut down and restarted.
The following patch was submitted upstream but has not yet been
accepted. I will add the upstream commit ID once the patch goes into
linux-next:
From: Long Li
The host keeps sending heartbeat packets independent of the
guest responding to them. Even though we respond to the heartbeat messages at
interrupt level, we can have situations where there maybe multiple heartbeat
messages pending that have not been responded to. For instance this occurs
when the
VM is paused and the host continues to send the heartbeat messages.
Address this issue by draining and responding to all
the heartbeat messages that maybe pending.
Signed-off-by: Long Li
Signed-off-by: K. Y. Srinivasan
CC: Stable
---
V2: Submit the patch to stable as well - Joshua R. Poulson
drivers/hv/hv_util.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
index 4aa3cb6..bcd0630 100644
--- a/drivers/hv/hv_util.c
+++ b/drivers/hv/hv_util.c
@@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
struct icmsg_negotiate *negop = NULL;
- vmbus_recvpacket(channel, hbeat_txf_buf,
-PAGE_SIZE, &recvlen, &requestid);
+ while (1) {
+
+ vmbus_recvpacket(channel, hbeat_txf_buf,
+PAGE_SIZE, &recvlen, &requestid);
+
+ if (!recvlen)
+ break;
- if (recvlen > 0) {
icmsghdrp = (struct icmsg_hdr *)&hbeat_txf_buf[
sizeof(struct vmbuspipe_hdr)];
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1588479] Re: dkms_packages.py supported kernel check is not working
Verified for Trusty too: Setting up dkms (2.2.0.3-1.1ubuntu5.14.04.9) ... bdmurray@upgrade-trusty-amd64:~$ python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.7 -k 4.6.1-01234-lowlatency ERROR (dkms apport): kernel package linux-headers-4.6.1-01234-lowlatency is not supported ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1588479 Title: dkms_packages.py supported kernel check is not working Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Committed Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Yakkety: Fix Released Bug description: Test Case - 1) Look for some dkms package in /usr/src e.g. bbswitch-0.8 2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency 3) Observe a crash report dialog from apport for bbswitch With the version of apport from -proposed you will instead receive: ERROR (dkms apport): kernel package linux- headers-4.6.1-01234-lowlatency is not supported The apport package hook for dkms packages seems to have an error in its supported kernel check. If the kernel is an unsupported one, the hook should exit with a return code of 1. However, in the Ubuntu Error Tracker we can see some crashes with unsupported kernel versions e.g.: https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11 DKMSKernelVersion: 4.6.1-040601-lowlatency https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766 DKMSKernelVersion: 4.6.0-040600-lowlatency If the intent really is to block creation of these reports, then let's do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1588479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1588479] Re: dkms_packages.py supported kernel check is not working
Done for xenial: [ 9:26AM 17170 ] [ bdmurray@impulse:~ ] $ sudo apt-get install dkms Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-34 linux-headers-4.4.0-34-generic linux-image-4.4.0-34-generic linux-image-extra-4.4.0-34-generic linux-tools-4.4.0-34 linux-tools-4.4.0-34-generic python3-requests-oauthlib Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: dkms 1 upgraded, 0 newly installed, 0 to remove and 190 not upgraded. Need to get 66.1 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 dkms all 2.2.0.3-2ubuntu11.3 [66.1 kB] Fetched 66.1 kB in 0s (104 kB/s) Sorry, your system lacks support for the snapshot feature Reading changelogs... Done (Reading database ... 918737 files and directories currently installed.) Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.3_all.deb ... Unpacking dkms (2.2.0.3-2ubuntu11.3) over (2.2.0.3-2ubuntu11.2) ... Processing triggers for man-db (2.7.5-1) ... Setting up dkms (2.2.0.3-2ubuntu11.3) ... [ 9:26AM 17171 ] [ bdmurray@impulse:~ ] $ python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency ERROR (dkms apport): kernel package linux-headers-4.6.1-01234-lowlatency is not supported -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1588479 Title: dkms_packages.py supported kernel check is not working Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Committed Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Yakkety: Fix Released Bug description: Test Case - 1) Look for some dkms package in /usr/src e.g. bbswitch-0.8 2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency 3) Observe a crash report dialog from apport for bbswitch With the version of apport from -proposed you will instead receive: ERROR (dkms apport): kernel package linux- headers-4.6.1-01234-lowlatency is not supported The apport package hook for dkms packages seems to have an error in its supported kernel check. If the kernel is an unsupported one, the hook should exit with a return code of 1. However, in the Ubuntu Error Tracker we can see some crashes with unsupported kernel versions e.g.: https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11 DKMSKernelVersion: 4.6.1-040601-lowlatency https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766 DKMSKernelVersion: 4.6.0-040600-lowlatency If the intent really is to block creation of these reports, then let's do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1588479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
After using the CONFING_SQUASHFS_DECOMP_SINGLE=y option in an experimental kernel the memory usage dropped significantly. The traces below are for -45 and the experimental -46 kernel. The 1 and 4 are the number of CPUs on the system. A single CPU system used to consumer 131MB per mounted snap, this is now reduced to just 4MB/snap. A four-CPU system has less dramatic improvement where the numbers are 7MB -> 4MB. This suggests some kind of bug in the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU option perhaps + echo Ubuntu 16.04 Ubuntu 16.04 + ./analyze.py ubuntu 16.04 4.4.0-45-generic 1 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 142.60MB 1: 274.71MB (delta: 132.11MB) 2: 406.55MB (delta: 131.84MB) 3: 538.36MB (delta: 131.81MB) 4: 670.19MB (delta: 131.82MB) + ./analyze.py ubuntu 16.04 4.4.0-46-generic 1 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 62.28MB 1: 66.99MB (delta: 4.71MB) 2: 71.05MB (delta: 4.07MB) 3: 75.12MB (delta: 4.06MB) 4: 79.19MB (delta: 4.07MB) + ./analyze.py ubuntu 16.04 4.4.0-45-generic 4 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 235.43MB 1: 242.38MB (delta: 6.96MB) 2: 249.38MB (delta: 7.00MB) 3: 256.45MB (delta: 7.06MB) 4: 263.42MB (delta: 6.97MB) + ./analyze.py ubuntu 16.04 4.4.0-46-generic 4 size-1m.squashfs.xz.heavy # num-mounted extra-memory delta 0: 72.79MB 1: 75.90MB (delta: 3.11MB) 2: 79.96MB (delta: 4.06MB) 3: 83.93MB (delta: 3.97MB) 4: 88.00MB (delta: 4.07MB) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...
Currently blocked on a grub SRU in xenial-proposed that isn't completely verified. -- 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/1527727 Title: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/... Status in grub: Unknown Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Confirmed Bug description: [Impact] Installs over ZFS where a ZFS disk is expected to be used as a root device. [Test case] - Run update-grub on a system with a ZFS root filesystem. [Regression Potential] Installs relying on the current broken behavior to avoid listing other operating systems in grub menu may find that new entries are added. --- update-grub runs /usr/sbin/grub-probe Without libzfslinux support compiled in, /usr/sbin/grub-probe runs ["zpool", "status", poolname] to find out ZFS info. zpool responds with device names as used at (I think!) pool creation time. Often, this is /dev/disk/by-id/... names, without the path. grub-probe then parses the output, and takes the names of devices, and if they do not start with a "/", it prepends "/dev/". It then tests the existence of the path name of the device. it fails. grub-probe then returns something like /usr/sbin/grub-probe: error: failed to get canonical path of `/dev /ata-ST31000333AS_-part1'. The actual path is of course /dev/disk/by- id/ST31000333AS_-part1 It can prepend smarter than "/dev" or it can understand ZFS natively, to fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1621088] Re: Fix bugs under virtual scsi server driver for Power
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1621088 Title: Fix bugs under virtual scsi server driver for Power Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - BRYANT G. LY - 2016-09-06 12:16:14 == All three of these have been accepted into the 4.9/scsi-queue and scsi tree under misc ibmvscsis: Properly deregister target sessions - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=712db3eb2c35e79986268bcd694ba8075445737d ibmvscsis: Code cleanup of print statements - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=812902159d4174df9a82948c0445becb865dabec ibmvscsis: Fixed a bug reported by Dan Carpenter - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=f6dbe38edf1ef4929847c90e244204ef4c6b3ce7 Still pending Review in target-devel mailing list: target/user: Return TCMU-generated sense data to fabric module - Is still under review under scsi and target-devel mailing list. http://www.spinics.net/lists/target-devel/msg13449.html TCM-User fixes and cleanups - http://www.spinics.net/lists/target-devel/msg13444.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-26.28/kernel02__4.8.0-26.28__2016-10-26_16-07-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] dwalin (amd64) - tests ran: 6, failed: 3
tests ran: 6, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-27.29/dwalin__4.8.0-27.29__2016-10-26_14-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker
*** This bug is a duplicate of bug 1635424 *** https://bugs.launchpad.net/bugs/1635424 ** This bug has been marked a duplicate of bug 1635424 linux: 3.19.0-74.82 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632368 Title: linux: 3.19.0-72.80 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-72.80 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632844] Re: linux: 3.13.0-99.146 -proposed tracker
*** This bug is a duplicate of bug 1635430 *** https://bugs.launchpad.net/bugs/1635430 ** This bug has been marked a duplicate of bug 1635430 linux: 3.13.0-101.148 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632844 Title: linux: 3.13.0-99.146 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** 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/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
In Progress
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634271] Re: arm64: kprobes disabled
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634271 Title: arm64: kprobes disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] kprobes is currently enabled for all Ubuntu architectures except arm64. This excludes a useful debug feature, which is required by certain userspace provided by Ubuntu, such as perf's probe command. I failed to notice this in my yakkety config review because it is a new feature in v4.8. [Test Case] = Failure case = ubuntu@arm64:~$ sudo perf probe schedule kprobe_events file does not exist - please rebuild kernel with CONFIG_KPROBE_EVENTS. Error: Failed to add events. = Success case = ubuntu@arm64:~$ sudo perf probe schedule Added new event: probe:schedule (on schedule) You can now use it in all perf tools, such as: perf record -e probe:schedule -aR sleep 1 ubuntu@arm64:~$ sudo perf record -e probe:schedule -aR sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.185 MB perf.data (61 samples) ] [Regression Risk] The proposed fix enables a config for an already-upstream feature, so regressions will have upstream support. The config change mostly results in building new code vs. modifying existing code. The notable exception is that arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - but only in the case that this newly enabled feature is being used (if kprobe_running()). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620979] Re: Hotkey doesn't work on HP x360
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1620979 Title: Hotkey doesn't work on HP x360 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When pinctrl-cherryview probing gpio device it clear interrupt mask and status, and in the later procedures the interrupt mask isn't set back correctly, leads to hotkeys fail. [Fix] Upstream fixes this in 4.8-rc3 by not clearing interrupt masks: commit bcb48cca23ec9852739e4a464307fa29515bbe48 Author: Mika Westerberg Date: Mon Aug 22 14:42:52 2016 +0300 pinctrl: cherryview: Do not mask all interrupts in probe To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1620979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
Ok test kernels at the URL below, please report testing results back here: people.canonical.com/~apw/lp1636847-xenial/ Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634753] Re: srcname from mount rule corrupted under load
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => 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/1634753
Title:
srcname from mount rule corrupted under load
Status in AppArmor:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Precise:
Invalid
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Invalid
Bug description:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
$ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap install hello-world || true
count=0
while /bin/true ; do
count=$((count+1))
if [ `echo "$count % 100" | bc` -eq 0 ]; then
echo "$count runs"
fi
hello-world > /dev/null || {
tail -100 /var/log/syslog | grep DEN && exit
}
sudo cat /run/snapd/ns/hello-world.mnt 2>/dev/null || sudo
/usr/lib/snapd/snap-discard-ns hello-world
done
2. in another terminal run:
$ while do /bin/true ; sudo apparmor_parser -r /etc/apparmor.d/* >/dev/null
2>&1 ; done
3. In another terminal:
$ tail -f /var/log/syslog|grep DEN
This is not limited to i386.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1634753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634705] Re: Add ipvlan module to 16.04 kernel
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634705 Title: Add ipvlan module to 16.04 kernel 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 Committed Status in linux source package in Zesty: Fix Released Bug description: Currently, ipvlan is included in the linux-image-extra package however users have requested that it be included as a module in the primary kernel package. Users running docker with mesos require ipvlan for container networking to function (and likely other container use cases). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635428] modoc (ppc64el) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/modoc__3.16.0-78.101~14.04.1__2016-10-26_14-13-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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug is for tracking the 3.19.0-74.82~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 -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4
Was the attached patch accepted upstream? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: New Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
Evidence suggests this is triggered by the parallel decompressor. Will spin a kernel with that switched out: CONFIG_SQUASHFS_DECOMP_SINGLE=y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635177] Re: mfd: intel-lpss: Add default I2C device properties for Apollo Lake
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635177 Title: mfd: intel-lpss: Add default I2C device properties for Apollo Lake Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: We need this patch for all Apollo Lake platforms for enabling the touchpad. This patch was cherry-picked from c50cdd62dda3f885c1e6ca8b3d5a0851c911ec54. And later backported to 4.4 kernel. It is because for Apollo Lake, the default freq/falling-time is incorrect. So it makes the i2c acts weird. Please consider SRU this commit. Impact: All touchpad on Apollo Lake work unstable on i2c mode. Sometimes it will fallback to PS/2 mode and lost some functionality. Fix: touchpad works good on i2c mode. Tested: The patch is tested on many Dell ApolloLake laptops and works good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1635177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635594] Re: [yakkety] hio driver missing
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed ** Also affects: linux (Ubuntu Zesty) Importance: Critical Assignee: Andy Whitcroft (apw) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635594 Title: [yakkety] hio driver missing Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Bug description: == SRU Justification == Huawei servers, including Huawei PCIe SSD's require the hio driver which is currently not included in our kernels. We would like to carry this driver in our kernels for Xenial and newer in order to support platforms with these drives. This was original ported to Xenial and is now missing in Yakkety creating a regression in that release. == Source == http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC == Testing == The reporter has hardware to test these kernels. == Regression potential == The driver does not exist currently, so no regression potential exists in Yakkety. Upgrades from Xenial are currently regressing and will need to be tested. --- The hio ubuntu driver in Xenial seems to be MIA in yakkety. Reported to us by Elmo. --- Kernel-Description: hio Ubuntu sauce driver needs porting to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-56-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
https://lists.ubuntu.com/archives/kernel-team/2016-October/080576.html ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
https://lists.ubuntu.com/archives/kernel-team/2016-October/080575.html ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
Marking as 'confirmed' so the bot doesn't auto-close it. ** 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_13-20-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1636847 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625232] Re: xgene i2c slimpro driver fails to load
** Summary changed: - [SRU] [xenial] xgene i2c slimpro driver fails to load + xgene i2c slimpro driver fails to load -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625232 Title: xgene i2c slimpro driver fails to load Status in linux package in Ubuntu: In Progress Bug description: [Impact] The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to communicate with the bmc, locally. [Test Case] Ensure the slimpro driver loads and that ipmitool can communicate with the bmc. [Regression Risk] The slimpro driver is a standalone, xgene driver, so any issues with it will only affect that platform. The patches were specified by APM as needed for local bmc access to work. Outside of the driver causing a crash, a regression in the driver itself would leave us in the same state we currently are, the driver not loading or no access to the bmc locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] onza (amd64) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/onza__4.8.0-27.29__2016-10-26_12-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_11-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] [NEW] unexpectedly large memory usage of mounted snaps
Public bug reported: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker ** Affects: snappy Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also 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/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: New Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635428] modoc (ppc64el) - tests ran: 10, failed: 0
tests ran: 10, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-78.101~14.04.1/modoc__3.16.0-78.101~14.04.1__2016-10-26_12-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/1635428 Title: linux-lts-vivid: 3.19.0-74.82~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug is for tracking the 3.19.0-74.82~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 -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635424 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635242] s2lp3 (s390x.LPAR) - tests ran: 33, failed: 0
tests ran: 33, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-46.67/s2lp3__4.4.0-46.67__2016-10-26_10-50-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/1635242 Title: linux: 4.4.0-46.67 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 18, failed: 0
tests ran: 18, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_11-03-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
Bah, typo:
test kernels at:
http://kernel.ubuntu.com/~cking/zfs-lp-1636517
** Description changed:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
- Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
+ zfsutils-linux:
+
+ Zesty: https://launchpadlibrarian.net/290907232/zfs-
+ linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
+
+ Sync'd fixes into kernel repos, patches in:
+ http://kernel.ubuntu.com/~cking/zfs-lp-1636517
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
-
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged in
4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed by
"zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16
[Kernel-packages] [Bug 1635242] Re: linux: 4.4.0-46.67 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-46.67 /xenial-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635242 Title: linux: 4.4.0-46.67 -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: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
** Description changed:
+ [SRU Request][Xenial][Yakkety]
+
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
- I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
- in 4.4.0-6.21), which added a second parameter to lookup_bdev without
+ [Fix]
+ Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
+
+ Yakkety, likewise
+ Xenial, likewise
+
+ [Regression Potential]
+
+ Minimal. This just touched one line in the zfs module
+ module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
+
+ Tested and passes with the ubuntu kernel team autotest client zfs
+ regression tests.
+
+
+ =
+
+ I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged in
+ 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed by
"zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
- crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
+ crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
-
+
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
- linux-restricted-modules-4.4.0-45-generic N/A
- linux-backports-modules-4.4.0-45-generic N/A
- linux-firmware1.157.4
+ linux-restricted-modules-4.4.0-45-generic N/A
+ linux-backports-modules-4.4.0-45-generic N/A
+ linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
Thanks Hajo, I was working the fix last night with a detection of the
two different lookup_bdev calls and been regression testing during the
night for Zesty, Yakkety and Xenial. I've got my fix already prepared...
So the way this kind of fix works with Ubuntu is as follows:
1. Change goes into zfsutils-linux
2. Sync the delta into the kernel package
I've put the zfsutils updates in ppa:
https://launchpad.net/~colin-king/+archive/ubuntu/zfs-lp-1636517
sudo add-apt-repository ppa:colin-king/zfs-lp-1636517
sudo apt-get update && sudo apt-get upgrade
And the fix in some test kernels:
http://kernel.ubuntu.com/~cking/zfs-lp-163651
These have been tested against our internal zfs regression tests and
pass.
@Fabian can you test these and if they are OK I'll SRU these. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
Zesty:
https://launchpadlibrarian.net/290907232/zfs-linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Po
[Kernel-packages] [Bug 1635430] modoc (ppc64el) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-101.148/modoc__3.13.0-101.148__2016-10-26_10-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635430 Title: linux: 3.13.0-101.148 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-101.148 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
New
Bug description:
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] s2lp4 (s390x.LPAR) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-27.29/s2lp4__4.8.0-27.29__2016-10-26_10-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/1635377 Title: linux: 4.8.0-27.29 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
