[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
Unfortunately your patch doesn't work for my rt2800usb, here's the dmesg: [ 117.351403] wlxacf1df0c507b: authenticate with 2c:36:f8:fa:ec:00 [ 117.405386] wlxacf1df0c507b: send auth to 2c:36:f8:fa:ec:00 (try 1/3) [ 117.406182] wlxacf1df0c507b: authenticated [ 117.411923] wlxacf1df0c507b: associate with 2c:36:f8:fa:ec:00 (try 1/3) [ 117.414946] wlxacf1df0c507b: RX AssocResp from 2c:36:f8:fa:ec:00 (capab=0x11 status=0 aid=13) [ 117.422791] wlxacf1df0c507b: associated [ 117.422810] IPv6: ADDRCONF(NETDEV_CHANGE): wlxacf1df0c507b: link becomes ready [ 117.689395] wlxacf1df0c507b: Limiting TX power to 27 (30 - 3) dBm as advertised by 2c:36:f8:fa:ec:00 [ 118.317773] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 17159, forcing to 0 [ 118.317782] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 159.352565] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 21901, forcing to 0 [ 159.352575] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 159.356085] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 32969, forcing to 0 [ 159.356095] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 159.356112] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 26654, forcing to 0 [ 159.356116] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 159.356145] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 31363, forcing to 0 [ 159.356150] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 159.356276] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 44307, forcing to 0 [ 159.356285] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 160.791879] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 22885, forcing to 0 [ 160.791888] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [ 165.425558] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 8650, forcing to 0 [ 165.425569] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/362875 Title: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset Status in linux package in Ubuntu: Confirmed Status in rt2x00 package in Ubuntu: Confirmed Bug description: Binary package hint: linux-firmware Dear friends, [24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. This is an example of the message I'm continually getting. ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter Many blessings. ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux-restricted-modules None [modified: /var/lib/dpkg/info/linux-restricted-modules.list] ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SourcePackage: linux-meta Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/L
[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
The vendor request error message does go away though... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/362875 Title: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset Status in linux package in Ubuntu: Confirmed Status in rt2x00 package in Ubuntu: Confirmed Bug description: Binary package hint: linux-firmware Dear friends, [24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. This is an example of the message I'm continually getting. ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter Many blessings. ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux-restricted-modules None [modified: /var/lib/dpkg/info/linux-restricted-modules.list] ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SourcePackage: linux-meta Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1720092] Re: Won't connect to wifi unless power_save is disabled
"First, if one is using select proprietary or out-of-tree modules (ex. vitualbox, nvidia, fglrx, bcmwl, etc.) unless there is an *extra* package available for the version you are testing, you will need to uninstall the module first, in order to test the mainline kernel." I'm using Virtualbox, but the instructions don't say how to uninstall a module. On Thu, Sep 28, 2017 at 4:31 PM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.14 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/ > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1720092 > > Title: > Won't connect to wifi unless power_save is disabled > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720092 Title: Won't connect to wifi unless power_save is disabled Status in linux package in Ubuntu: Incomplete Bug description: I can connect to most WiFi networks fine, however for one particular WPA/WPA2, EAP-PEAP, MSCHAPV2 network I have to do "sudo iw wlp1s0 set power_save off" before it is able to connect. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: vadi 4472 F...m pulseaudio /dev/snd/pcmC0D0p: vadi 4472 F...m pulseaudio /dev/snd/controlC0: vadi 4472 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Sep 28 10:09:15 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752 InstallationDate: Installed on 2017-02-15 (224 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:5805 Broadcom Corp. Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-24 (126 days ago) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.4 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.4:bd06/02/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
With your patch, The problem only occurs to 5G-an network. 2.4G-g works great. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/362875 Title: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset Status in linux package in Ubuntu: Confirmed Status in rt2x00 package in Ubuntu: Confirmed Bug description: Binary package hint: linux-firmware Dear friends, [24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. This is an example of the message I'm continually getting. ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter Many blessings. ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux-restricted-modules None [modified: /var/lib/dpkg/info/linux-restricted-modules.list] ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SourcePackage: linux-meta Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation
Hello, I still se this issue on Xenial with Kernel 4.4.0-93-generic #116-Ubuntu The server is bare-metal. It is just a cosmetic problem in the log files or I should upgrade as soon as possible ? I noticed the bad entries in my kern.log with my monitoring tool, but I dont see any side effect so far. Could anyone please clarify what is the operational impact of this bug ? 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/1705447 Title: misleading kernel warning skb_warn_bad_offload during checksum calculation Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Even when the packet says checksum calculation is unnecessary the kernel will still check the checksum and display a warning that the checksum is bad. This has been fixed upstream in Kernel 4.11 by commit id: b2504a5dbef3305ef41988ad270b0e8ec289331c We have reports of Ubuntu 16.04 virtual machines (with ip forward enabled) displaying these warnings: [10480.074664] [ cut here ] [10480.074667] WARNING: CPU: 1 PID: 0 at /build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 skb_warn_bad_offload+0xd1/0x120 [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1 [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net pata_acpi floppy [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW O 4.8.0-52-generic #55~16.04.1-Ubuntu [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 04/01/2014 [10480.074697] 0286 ec176c2ae03bc036 8beef5643870 b7a2e7b3 [10480.074699] 8beef56438c0 8beef56438b0 b768314b [10480.074702] 098cb84fba80 8bed61f82000 8bee9915c000 0005 [10480.074704] Call Trace: [10480.074704][] dump_stack+0x63/0x90 [10480.074708] [] __warn+0xcb/0xf0 [10480.074710] [] warn_slowpath_fmt+0x5f/0x80 [10480.074713] [] ? ___ratelimit+0xa2/0xf0 [10480.074714] [] skb_warn_bad_offload+0xd1/0x120 [10480.074716] [] __skb_gso_segment+0xd8/0x140 [10480.074717] [] validate_xmit_skb+0x14f/0x2a0 [10480.074719] [] __dev_queue_xmit+0x322/0x6d0 [10480.074720] [] ? nf_nat_ipv4_fn+0x1a6/0x230 [nf_nat_ipv4] [10480.074723] [] dev_queue_xmit+0x10/0x20 [10480.074725] [] ip_finish_output2+0x292/0x380 [10480.074726] [] ? ipv4_confirm+0x7d/0x100 [nf_conntrack_ipv4] [10480.074728] [] ip_finish_output+0x132/0x1d0 [10480.074729] [] ? nf_hook_slow+0x73/0xd0 [10480.074731] [] ip_output+0x6e/0xf0 [10480.074733] [] ? __ip_flush_pending_frames.isra.40+0x90/0x90 [10480.074736] [] ip_forward_finish+0x43/0x70 [10480.074738] [] ip_forward+0x384/0x480 [10480.074739] [] ? ip_frag_mem+0x50/0x50 [10480.074741] [] ip_rcv_finish+0x11b/0x400 [10480.074743] [] ip_rcv+0x28b/0x3c0 [10480.074744] [] ? inet_del_offload+0x40/0x40 [10480.074746] [] __netif_receive_skb_core+0x524/0xab0 [10480.074747] [] ? kmem_cache_alloc+0xd7/0x1b0 [10480.074749] [] ? __build_skb+0x2a/0xe0 [10480.074751] [] __netif_receive_skb+0x18/0x60 [10480.074753] [] netif_receive_skb_internal+0x32/0xa0 [10480.074754] [] napi_gro_receive+0xcd/0x120 [10480.074756] [] virtnet_receive+0x1c3/0x970 [virtio_net] [10480.074758] [] ? update_cfs_rq_load_avg+0x1f9/0x4c0 [10480.074760] [] virtnet_poll+0x1d/0x80 [virtio_net] [10480.074762] [] net_rx_action+0x238/0x380 [10480.074764] [] __do_softirq+0xf6/0x280 [10480.074765] [] irq_exit+0xa3/0xb0 [10480.074766] [] do_IRQ+0x54/0xd0 [10480.074768] [] common_interrupt+0x82/0x82 [10480.074768][] ? native_safe_halt+0x6/0x10 [10480.074772] [] default_idle+0x1e/0xd0 [10480.074774] [] arch_cpu_idle+0xf/0x20 [10480.074775] [] default_idle_call+0x2a/0x40 [10480.074776] [] cpu_startup_entry+0x2ea/0x350 [10480.074778] [] start_secondary+0x151/0x190 [10480.074781] ---[ end trace 3a9bd18de5564b05 ]--- We have recompiled your latest 16.04.2 kernel with this patch and confirmed that this warning does not happen. Could you please consider including this fix in your next 16.0
[Kernel-packages] [Bug 1719553] Re: sysdig-smoke-test failed on ppc64le with Zesty kernel
Patch applied. ** Changed in: linux (Ubuntu) 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/1719553 Title: sysdig-smoke-test failed on ppc64le with Zesty kernel Status in linux package in Ubuntu: Fix Released Bug description: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.py", line 22, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: /home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig _smoke_test.sh Exit status: 1 Duration: 46.2219159603 stdout: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 2 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 3 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 2 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 185201 sysdig events 0 dd context switches 0 cat context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd FAILED (trace at least 25 context switches involving dd) FAILED (trace at least 25 context switches involving cat) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 0 passed, 4 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720343] [NEW] xfs test in xfstests will eat up all the space on i386 Xenial testing node
Public bug reported: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp /xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected uec-images xenial ** Description changed: The xfs test in xfstests test suite will consume all the HDD space on node rizzo wi
[Kernel-packages] [Bug 1720343] Re: xfs test in xfstests will eat up all the space on i386 Xenial testing node
I will check this with xfstest from 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/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name
[Kernel-packages] [Bug 1720343] Re: xfs test in xfstests will eat up all the space on i386 Xenial testing node
apport information ** Tags added: apport-collected uec-images xenial ** Description changed: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp /xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 29 04:10 seq + crw-rw 1 root audio 116, 33 Sep 29 04:10 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: i386 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CurrentDmesg: + + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub + Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. PowerEdge R310 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro + ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-35-generic N/A + linux-backports-modules-4.10.0-35-generic N/A + linux-firmware 1.157.12 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images + Uname: Linux 4.10.0-35-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 09/06/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.0 + dmi.board.name: 05XKKK + dmi.board.vendor: Dell Inc. + dmi.board.version: A09 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:c
[Kernel-packages] [Bug 1720343] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958577/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkFo
[Kernel-packages] [Bug 1720343] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958576/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True
[Kernel-packages] [Bug 1720343] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958575/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.da
[Kernel-packages] [Bug 1720343] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958579/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True
[Kernel-packages] [Bug 1720343] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958574/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: T
[Kernel-packages] [Bug 1720343] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958578/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload:
[Kernel-packages] [Bug 1720343] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958580/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.
[Kernel-packages] [Bug 1720343] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1720343/+attachment/4958581/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: New Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True
[Kernel-packages] [Bug 1720343] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1720343 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/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: Incomplete Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17
[Kernel-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
Ubuntu 17.10 with all updates. LibreOffice Base is still crashing on 32-bit (kernel is 4.13.0-12-generic). ** Tags added: artful ** Summary changed: - linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing + linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic, linux-image-4.13.0-12-generic Regression: many user-space apps crashing ** Summary changed: - linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic, linux-image-4.13.0-12-generic Regression: many user-space apps crashing + linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regression: many user-space apps crashing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in python-jpype package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/
[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
So will this be in the 17.10 release? The fix is in the Linux kernel since a month. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720359] [NEW] Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
Public bug reported: Deploying ceph osd on Trusty/14.04 (LTS) on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720359 Title: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller Status in linux package in Ubuntu: New Bug description: Deploying ceph osd on Trusty/14.04 (LTS) on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
The above behavior is reproducible using upstream mainline kernel, so not Ubuntu specific. A bisection against upstream kernel revealed : # first bad commit: [a736e9b6a03283a2e0fc8190b748b3a672f289c1] hpsa: correct ioaccel2 sg chain len Note that the behavior also seems to be fix in recent upstream kernel (tested with v4.14-rc2) -- The upstream v4.14-rc2 kernel is using : HPSA_DRIVER_VERSION : "3.4.20-0" while Ubuntu-4.4.0-97.120 is using : HPSA_DRIVER_VERSION : "3.4.14-0" -- Another bisection is in progress to find the first good commit between "a736e9b6a03283a2e0fc8190b748b3a672f289c1]" and "v4.14-rc2" HEAD. - Eric ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720359 Title: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller Status in linux package in Ubuntu: New Bug description: Deploying ceph osd on Trusty/14.04 (LTS) on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
The above behavior is reproducible using upstream mainline kernel, so not Ubuntu specific. A bisection against upstream kernel revealed : # first bad commit: [a736e9b6a03283a2e0fc8190b748b3a672f289c1] hpsa: correct ioaccel2 sg chain len Note that the behavior also seems to be fix in recent upstream kernel (tested with v4.14-rc2) The upstream v4.14-rc2 kernel is using : HPSA_DRIVER_VERSION : "3.4.20-0" while Ubuntu-4.4.0-97.120 is using : HPSA_DRIVER_VERSION : "3.4.14-0" Another bisection is in progress to find the first good commit between "a736e9b6a03283a2e0fc8190b748b3a672f289c1]" and "v4.14-rc2" HEAD. - Eric ** Description changed: - Deploying ceph osd on Trusty/14.04 (LTS) on HP HW[1] system triggers - "Controller lockup"[2] + Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel + on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information - Manufacturer: HP - Product Name: ProLiant DL380 Gen9 + Manufacturer: HP + Product Name: ProLiant DL380 Gen9 BIOS - Vendor: HP - Version: P89 - Release Date: 02/17/2017 + Vendor: HP + Version: P89 + Release Date: 02/17/2017 Smart Array Controller - Smart Array P440 Controller - + Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720359 Title: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller Status in linux package in Ubuntu: New Bug description: Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720359] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1720359 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/1720359 Title: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller Status in linux package in Ubuntu: Incomplete Bug description: Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.
Reproduced here on a x86_64 virtual machine. Will investigate further. Thanks. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1714485 Title: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. Status in The Ubuntu-power-systems project: New Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 == ---Problem Description--- Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. ---Steps to Reproduce--- 1. Install Ubuntu 16.04.03 with / as xfs. 2. Configure kdump. 3. trigger crash. Machine hangs after below log. Attaching console log. [ OK ] Reached target Network is Online. Starting Kernel crash dump capture service... Starting iSCSI initiator daemon (iscsid)... [ 12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator [ OK ] Started Kernel crash dump capture service. [ OK ] Started iSCSI initiator daemon (iscsid). Starting Login to default iSCSI targets... [ OK ] Started Login to default iSCSI targets. [ OK ] Reached target Remote File Systems (Pre). 4. After manual reboot /etc/default/kdump-tools is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635597] kdump boot log on talclp3
--- Comment on attachment From hbath...@in.ibm.com 2017-09-29 09:56 EDT--- (In reply to comment #41) > Hi > > > Its is same config.Both lpars its multipath disks.With that we recreated the > issue > > Hi Lekshmi I am not really convinced it is the same configuration looking at the output of blkid command on the system this was tried (see attachment). The root disk in this case does not seem to be multipath based. Also, the fix package mentioned by Breno or Cascardo doesn't seem to have been used for this validation. Could you please try this on the same system the issue was initially reported, with package at ppa:louis/kdump-tools-multipath. Alternatively, I would be happy to validate, if you can provide access to the system where the issue was initially reported. (In reply to comment #42) > By "recreated the issue", do you mean it fixes the issue? Cause in the > previous message, you mentioned you could create the crash files? Was that > using the proposed package from louis ppa? Can you clarify? > Hello Canonical/Cascardo, The issue was not seen on one of our system with kdump-tools verison 1:1.6.0-2ubuntu1.2. Not sure if the has the fix. Neither I am sure the failure was seen on this system to start with. Our test team will try to setup the failed configuration to validate this again.. Thanks Hari ** Attachment added: "kdump boot log on talclp3" https://bugs.launchpad.net/bugs/1635597/+attachment/4958727/+files/kdump_validation-talclp3.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in makedumpfile source package in Trusty: Confirmed Status in linux source package in Xenial: New Status in makedumpfile source package in Xenial: Confirmed Status in linux source package in Zesty: New Status in makedumpfile source package in Zesty: Confirmed Bug description: Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033 CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6
[Kernel-packages] [Bug 1720378] [NEW] Two processes can bind to the same port
Public bug reported: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug ec2-images uosci 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/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Confirmed Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmware
[Kernel-packages] [Bug 1720378] Re: Two processes can bind to the same port
** Tags added: uosci -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Confirmed Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720378] 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/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Confirmed Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720378] Re: Two processes can bind to the same port
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails
I built the next test kernel, up to the following commit: a4d768e702de224cc85e0c8eac9311763403b368 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1696049 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance Hide -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720359 Title: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller Status in linux package in Ubuntu: Incomplete Bug description: Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel on HP HW[1] system triggers "Controller lockup"[2] [1] - HW System Information Manufacturer: HP Product Name: ProLiant DL380 Gen9 BIOS Vendor: HP Version: P89 Release Date: 02/17/2017 Smart Array Controller Smart Array P440 Controller [2] - /var/log/kern.log ... ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60 ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700 1 heartbeat_map is_healthy 'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60 hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30 hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown abort service response 0x00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720343] Re: xfs test in xfstests will eat up all the space on i386 Xenial testing node
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags removed: uec-images ** Tags added: kernel-da-key uec-image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720343 Title: xfs test in xfstests will eat up all the space on i386 Xenial testing node Status in linux package in Ubuntu: Incomplete Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.
[Kernel-packages] [Bug 1720393] [NEW] kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72!
Public bug reported: Generic manual install procedure on KVM/qemu guest ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4456 F pulseaudio CasperVersion: 1.384 Date: Fri Sep 29 09:59:23 2017 Failure: oops IwConfig: ens3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 cirrusdrmfb 1 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops artful kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720393 Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! Status in linux package in Ubuntu: New Bug description: Generic manual install procedure on KVM/qemu guest ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4456 F pulseaudio CasperVersion: 1.384 Date: Fri Sep 29 09:59:23 2017 Failure: oops IwConfig: ens3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 cirrusdrmfb 1 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720263] Re: BUG: unable to handle kernel paging request at ffffffffffffffe1
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720263 Title: BUG: unable to handle kernel paging request at ffe1 Status in linux package in Ubuntu: Incomplete Bug description: I'm constantly getting random kernel oopses and the machine hangs completely. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 29 02:51:30 2017 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: security_vm_enough_memory_mm+0x38/0x60 RSP: ad63cb35fd90 Failure: oops InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=0f587df5-406f-4a5b-b415-224eac397e66 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at ffe1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720219 Title: Repeated keys stop after a few characters Status in linux package in Ubuntu: Incomplete Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE
[Kernel-packages] [Bug 1720393] 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/1720393 Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! Status in linux package in Ubuntu: Incomplete Bug description: Generic manual install procedure on KVM/qemu guest ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4456 F pulseaudio CasperVersion: 1.384 Date: Fri Sep 29 09:59:23 2017 Failure: oops IwConfig: ens3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 cirrusdrmfb 1 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
We're seeing this on our build servers. These are VMWare virtual machines which run docker containers in privileged mode. Inside the containers are Jenkins agents and a build environment. Part of the build process uses unshare to create these namespaces: ipc uts mount pid net. If you have any questions about this arrangement, I can try to provide more detail and maybe example code. The kernel is 4.4.0-79-generic x86_64. We are using docker 17.05.0-ce. In one case, the whole VM hung when this was encountered. Are there any workarounds for 16.04 users beyond rebooting the host? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: Confirmed Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720393] Re: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72!
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720393 Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! Status in linux package in Ubuntu: Incomplete Bug description: Generic manual install procedure on KVM/qemu guest ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4456 F pulseaudio CasperVersion: 1.384 Date: Fri Sep 29 09:59:23 2017 Failure: oops IwConfig: ens3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 cirrusdrmfb 1 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
If this work, it's probably due to buggy VBIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.4.0-1037.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1716613 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Friday, 29. September 2017 16:14 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the 4.4.0-1037.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1716613 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Friday, 29. September 2017 16:14 UTC - kernel-stable-phase:Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-publish series: Invalid Status in Kernel SRU Workflow snap-qa-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1716613 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-publish series: Invalid Status in Kernel SRU Workflow snap-qa-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1716613 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
Edit the Ubuntu boot entry in Grub menu, change "gfxmode $linux_gfx_mode" to "gfxmode text". I think this can workaround your issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker
** Changed in: kernel-sru-workflow/snap-publish Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-qa-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Tags added: kernel-sru-cycle-2017.09.18-2 ** Tags added: kernel-sru-derivative-of-1718149 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1720042 Title: linux-aws: 4.4.0-1038.47 -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 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 snap-publish series: Invalid Status in Kernel SRU Workflow snap-qa-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-1038.47 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 kernel-stable-master-bug: 1718149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1720042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters
Change to multi-user: $ sudo systemctl isolate multi-user See if the issue also happens. To switch back to GUI, $ sudo systemctl isolate graphical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720219 Title: Repeated keys stop after a few characters Status in linux package in Ubuntu: Incomplete Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubs
[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-publish Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-qa-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1719970 Title: linux-aws: 4.4.0-1037.46 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-publish series: Invalid Status in Kernel SRU Workflow snap-qa-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1716613 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
Yes. In all cases, GRUB itself draws fine. On further experimentation, it seems that it might be the case that the boot after a *failed* boot works. If nothing is visible and I blindly enter my cryptroot password it can boot all the way; rebooting with ctrl-alt-delete after that seems to result in another faliure to display anything on the subsequent boot. Restarting with ctrl-alt-delete from the (unseen) initramfs prompt seems to reliably result in the subsequent boot getting displayed. This does not seem to be related to $VT_HANDOFF in GRUB; whether or not it is enabled in grub.cfg does not appear to make a difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720263] Re: BUG: unable to handle kernel paging request at ffffffffffffffe1
It's a clean install. I barely managed to install it though. There are no other versions of the kernel in the repository. I'm going to try the mainline kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720263 Title: BUG: unable to handle kernel paging request at ffe1 Status in linux package in Ubuntu: Incomplete Bug description: I'm constantly getting random kernel oopses and the machine hangs completely. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 29 02:51:30 2017 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: security_vm_enough_memory_mm+0x38/0x60 RSP: ad63cb35fd90 Failure: oops InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=0f587df5-406f-4a5b-b415-224eac397e66 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at ffe1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720229] Re: arm64: usercopy: kernel memory overwrite attempt detected to (null) () (6 bytes)
** 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/1720229 Title: arm64: usercopy: kernel memory overwrite attempt detected to (null) () (6 bytes) Status in linux package in Ubuntu: Confirmed Bug description: I observed this stack trace when attempting to install the 2017.09.26 daily arm64/artful server ISO: [ 107.816592] usercopy: kernel memory overwrite attempt detected to (null) () (6 bytes) [ 107.818389] Internal error: Oops - BUG: 0 [#1] SMP [ 107.819170] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac virtio_blk virtio_net nls_utf8 isofs usb_storage virtio_scsi [ 107.823033] CPU: 0 PID: 8105 Comm: dmraid Not tainted 4.13.0-12-generic #13-Ubuntu [ 107.824318] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 107.825490] task: 80007cfbe900 task.stack: 80007792c000 [ 107.826498] PC is at __check_object_size+0x114/0x200 [ 107.827349] LR is at __check_object_size+0x114/0x200 [ 107.828192] pc : [] lr : [] pstate: 00400145 [ 107.829458] sp : 80007792fb00 [ 107.830026] x29: 80007792fb00 x28: [ 107.830934] x27: fa066520 x26: 80007ce6c000 [ 107.831840] x25: 0002001d x24: 80007ce6 [ 107.832743] x23: 0006 x22: 0006 [ 107.833657] x21: x20: 0006 [ 107.834564] x19: x18: [ 107.835467] x17: x16: [ 107.836371] x15: 093b8c08 x14: 2820296c6c756e28 [ 107.837273] x13: 2020202020202020 x12: 2020206f74206465 [ 107.838175] x11: 093b9658 x10: 086a7e40 [ 107.839072] x9 : 746972777265766f x8 : 0017 [ 107.839972] x7 : 20293e6c6c756e3c x6 : 80007ffb5dc0 [ 107.840867] x5 : 80007ffb5dc0 x4 : [ 107.841771] x3 : 80007ffbe038 x2 : 00040d00 [ 107.842668] x1 : x0 : 0059 [ 107.843566] Process dmraid (pid: 8105, stack limit = 0x80007792c000) [ 107.844698] Stack: (0x80007792fb00 to 0x80007793) [ 107.845680] fb00: 80007792fb40 084e22c0 80007792fc40 80007735ca08 [ 107.846998] fb20: 80007735c8c0 093b8000 0006 082cd088 [ 107.848319] fb40: 80007792fbf0 084e2da4 093b8000 2285 [ 107.849649] fb60: 80007ce6 fa0664c8 80007ce6c000 0002001d [ 107.850974] fb80: 80007792fc40 80007cfbe900 08a91000 80007cfbe900 [ 107.852295] fba0: 80007792fc10 093b8000 [ 107.853626] fbc0: 80007792fbf0 082d022c 80007cfe9000 [ 107.854944] fbe0: 80007cfe9000 00040d00 80007792fce0 084e2f88 [ 107.856264] fc00: 2285 80007a8d7a80 0002001d fa0664c8 [ 107.857592] fc20: fa0664c8 0009 0124 001d [ 107.858917] fc40: fffd0053 00040006 0ed36f10 fa066520 [ 107.860240] fc60: 1770 [ 107.861568] fc80: 0200 [ 107.862890] fca0: 0ed2ee10 80007792fe30 07ff 0fe4 [ 107.864214] fcc0: 80007792fce0 084e2f6c 2285 00040d00 [ 107.865539] fce0: 80007792fd10 00ae6798 80007c873418 80007a8d7a80 [ 107.866861] fd00: 0002001d 2285 80007792fd50 084d4294 [ 107.868184] fd20: 2285 093b8000 fa0664c8 80007a8d7a80 [ 107.869513] fd40: 0002001d ff9c 80007792fdc0 083057f8 [ 107.870837] fd60: 80007ccac600 2285 fa0664c8 80007ccac600 [ 107.872154] fd80: 80007cea0328 fc00 [ 107.873479] fda0: 1000 59cd5389 00040d00 [ 107.874798] fdc0: 80007792fdf0 082d4b4c 093b8000 2285 [ 107.876115] fde0: fa0664c8 00040d00 80007792fe80 082d530c [ 107.877432] fe00: 80007ccac600 80007ccac600 0009 [ 107.878757] fe20: 2285 fa0664c8 618007ff 1001 [ 107.880075] fe40: 80007792fe80 082d52d0 80007ccac600 [ 107.881398] fe60: 80007ccac600 0009
[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
** Tags added: id-598b6543459f8ccf5dfbc04c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in linux package in Ubuntu: In Progress Status in open-iscsi package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in open-iscsi source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in open-iscsi source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in open-iscsi source package in Artful: In Progress Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: (https://launchpadlibrarian.net/291303059/Screenshot.jpg) This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot
** Tags added: id-5983be8a574a2f44b3cbc1ed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1708409 Title: kdump service does not start after configure/reboot Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: == Comment: #0 - Harish Sriram - 2017-08-02 01:45:01 == kdump service does not start after configure/reboot --Problem Description--- kdump service does not start after configure/reboot. It has to be started/loaded manually, everytime after reboot. # kdump-config status current state : Not ready to kdump ---uname output--- Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type/Model = Power 8/8247-22L Additional Info- # cat /proc/cmdline root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ---Steps to Reproduce--- 1. installed linux-crashdump 2. edited the kdump-tools.cfg crashkernel cmdline to above 3. update-grub 4. reboot Expected: kdump-config to be loaded by default after reboot # kdump-config status current state : Not ready to kdump # service kdump-tools status * kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: inactive (dead) ... https://github.com/systemd/systemd/issues/6334 systemd in artful is not properly picking up the unit files in /etc/systemd/system/default.target.wants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)
** Tags added: id-59721d94f129f71adae65e97 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696102 Title: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in xfsprogs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in xfsprogs source package in Xenial: Fix Released Status in linux source package in Zesty: Invalid Status in xfsprogs source package in Zesty: Fix Released Bug description: Impact == When making multiple copies of a V5 filesystem with xfs_copy those copies will be corrupt due to incorrect UUIDs. Test Case = See the detailed steps to create the test environment in comment #20. Regression Potential From the patch "Most of this patch is changing comments and re-ordering tests to match; the functional change is to simply use the *sb rather than the *ag_hdr to identify the proper metadata UUID." So this seems pretty straightforward and given that copy process is currently broken, because the copies are corrupt, this will be an improvement. Original Description Problem Description xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent. # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530 +++ /root/xfstests-dev/results//xfs/073.out.bad 2017-03-27 11:11:43.023059702 +0530 @@ -59,8 +59,7 @@ comparing new image geometry to old unmounting and removing new image checking new image -mounting new image on loopback -comparing new image files to old -comparing new image directories to old -comparing new image geometry to old -unmounting and removing new image +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c) +(see /root/xfstests-dev/results//xfs/073.full for details) +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r) +(see /root/xfstests-dev/results//xfs/073.full for details) Metadata corruption detected at xfs_agf block 0x1/0x200 # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.conf for running with created loop device 5.. Run xfstests-dev test : ./check tests/xfs/073 Full log is attached. == Comment: #2 - Harish Sriram - 2017-05-31 01:22:11 == (In reply to comment #1) > Hi Harish, > Can you share the steps used in creating the loop device with xfs filesystem > ? > > Thank you. Create loop device: # mkdir /mnt/loop-device /mnt/test /mnt/scratch # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done Create File system: # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
** Tags added: id-597a82ade5d5089d05d20931 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: Confirmed Status in console-setup package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cuase] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
** Tags added: id-597a82bd36308ac7a63cff29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Status in unattended-upgrades source package in Artful: Confirmed Status in update-notifier source package in Artful: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
** Tags added: id-594d1970df3ec53730c0d28c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package in Ubuntu:
Fix Released
Status in nbd package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in systemd source package in Xenial:
Incomplete
Bug description:
When using an nbd root, wait-for-root blocks for 30 seconds before
booting continues successfully.
Using Ubuntu Natty, related packages versions:
nbd-client 1:2.9.16-6ubuntu1
initramfs-tools 0.98.1ubuntu9
The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})
# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop. If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done
I replaced wait-for-root with a sh script that did `set >&2`, here are the
relevant environment variables at the time wait-for-root was called:
ROOT='/dev/nbd0'
ROOTDELAY=''
ROOTFLAGS=''
ROOTFSTYPE=''
nbdroot='192.168.0.1,2011'
It's probably worth noting that "nbd0: unknown partition table" was
displayed asynchronously 1-2 seconds after wait-for-root was invoked
and while it was still waiting. But I tried adding a "sleep 5" as the
last line of local-top/nbd, so that the nbd message was displayed a
lot before wait-for-root was called, and it didn't make a difference.
So I don't think a race condition is involved in this problem.
Temporarily I'm passing rootdelay=1 in the kernel command line to work
around the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700270] Re: Stack Clash fix breaks JVM when launched from C
*** This bug is a duplicate of bug 1699772 *** https://bugs.launchpad.net/bugs/1699772 ** Tags added: id-599af6610f9a304e95fd9796 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700270 Title: Stack Clash fix breaks JVM when launched from C Status in linux package in Ubuntu: Confirmed Bug description: I have tested only with linux 4.10.0-24-generic on amd64. The attached repro case: - compiles a java class - compiles a C program that initialises the JVM and calls a static method from the java class - launch the compiled C program. Expected result: the c program should execute the Java method and print some numbers in the terminal Actual result: the c program segfaults while initialising the JVM reverting to linux 4.10.0-22-generic amd64 fixes the problem. Since the only change in the changelog is the Stack Clash fix and since I remember reading that the JVM does tricky stuff with the stack, this is a natural culprit. It touches any program that initialises a JVM (so for instance Java bindings in Postgresql or Java applets in firefox although the latter have been deprecated and are only supported in firefox ESR now). I attach the repro-case. The issue happens with both openjdk-8-jdk from the repository and the standard jdk 8 from oracle. [note: edited after initial submission to fix some typos] --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kim1928 F pulseaudio /dev/snd/controlC1: kim1928 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4d246142-b56c-4cc6-b9cf-dad9c592bca0 InstallationDate: Installed on 2016-10-19 (248 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP EliteBook 820 G2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=de40f805-aa69-464b-8c59-022276f8b381 ro resume=UUID=4d246142-b56c-4cc6-b9cf-dad9c592bca0 i915.enable_rc6=7 i915.enable_dc=2 i915.enable_psr=1 quiet splash ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to zesty on 2017-06-23 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare src sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/10/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.19 dmi.board.name: 225A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.5B dmi.chassis.asset.tag: 5CG52931PR dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.19:bd04/10/2017:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3008E510003:rvnHewlett-Packard:rn225A:rvrKBCVersion96.5B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 820 G2 dmi.product.version: A3008E510003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio
** Tags added: id-599af6610f9a304e95fd9796 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in python-jpype package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708852] Re: Touchpad not detected
Could someone who's affected by this issue verify the fix with the Xenial and/or Zesty kernel currently in -proposed pocket? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708852 Title: Touchpad not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: SRU Justifications: [Impact] Touchpad on Lenovo ideapad 320-14IKB does not work. [Test Case] After adding the ID to the elan_i2c driver, the touchpad works. [Regression Potential] Very low. It only adds device ID to the driver, no functional changes. --- The touchpad is not working in any linux distribution, but works in Windows. It is not getting detected. Seems like a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matheus1504 F pulseaudio CurrentDesktop: GNOME Date: Sat Aug 5 12:58:21 2017 InstallationDate: Installed on 2017-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:1127 Acer, Inc Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 0101:0007 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-30-generic N/A linux-backports-modules-4.10.0-30-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 4A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB: dmi.product.name: 80YF dmi.product.version: Lenovo ideapad 320-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
You are absolutely correct; forceing “gfxmode text” appears to make booting reliably visible. That's a nice workaround. I guess this is a buggy VBIOS issue, then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708852] Re: Touchpad not detected
Hi @unameuname, The packages with the fix for this bug are scheduled to be released to -updates on the week of 09-Oct. Best. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708852 Title: Touchpad not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: SRU Justifications: [Impact] Touchpad on Lenovo ideapad 320-14IKB does not work. [Test Case] After adding the ID to the elan_i2c driver, the touchpad works. [Regression Potential] Very low. It only adds device ID to the driver, no functional changes. --- The touchpad is not working in any linux distribution, but works in Windows. It is not getting detected. Seems like a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matheus1504 F pulseaudio CurrentDesktop: GNOME Date: Sat Aug 5 12:58:21 2017 InstallationDate: Installed on 2017-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:1127 Acer, Inc Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 0101:0007 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-30-generic N/A linux-backports-modules-4.10.0-30-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 4A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB: dmi.product.name: 80YF dmi.product.version: Lenovo ideapad 320-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug
Hi @jacobi, Thank you very much for verifying the fix! Kleber ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805
[Kernel-packages] [Bug 1720378] Re: Two processes can bind to the same port
Thanks for the suggestions. I will try with an upstream kernel and also add steps for reproducing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720378] Re: Two processes can bind to the same port
Thanks. I can try to reproduce this issue if you list the steps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720378 Title: Two processes can bind to the same port Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: On both xenial and zesty apache and haproxy seem to be able to bind to the same port: # netstat -peanut | grep 8776 tcp0 0 0.0.0.0:87760.0.0.0:* LISTEN 0 76856 26190/haproxy tcp6 0 0 :::8776 :::*LISTEN 0 76749 26254/apache2 tcp6 0 0 :::8776 :::*LISTEN 0 76857 26190/haproxy I thought this should not be possible? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 11:46 seq crw-rw 1 root audio 116, 33 Sep 29 11:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Sep 29 14:15:26 2017 Ec2AMI: ami-0193 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmwareN/A 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: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size
Hi @decui, Could you please verify the fix with the Xenial and/or Zesty kernel current in -proposed pocket? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713884 Title: [CIFS] Fix maximum SMB2 header size Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: In Progress Bug description: Currently the maximum size of SMB2/3 header is set incorrectly which leads to hanging of directory listing operations on encrypted SMB3 connections. Fix this by setting the maximum size to 170 bytes that is calculated as RFC1002 length field size (4) + transform header size (52) + SMB2 header size (64) + create response size (56). https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de This applies across the board 3.16, 4.4, 4.10, artful, and azure. Microsoft would be happy to help test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)
Hello IBM, Could you please verify the fix for this issue with the Zesty kernel that is currently in -proposed pocket? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711251 Title: vhost guest network randomly drops under stress (kvm) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: == SRU Justification == A vhost performance patch was introduced in the 4.10 kernel upstream, and is currently included in the Zesty 4.10 kernel: commit 809ecb9bca6a9424ccd392d67e368160f8b76c92 Author: Jason Wang Date: Mon Dec 12 14:46:49 2016 +0800 vhost: cache used event for better performance -- However I recently hit a functional issue linked to this patch which would cause random guests to lose their network connection under stress. This is not architecture specific and more likely to be hit with high network stress (i.e. lots of uperf instances). The patch author has now reverted this patch upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853 which reads: " Revert "vhost: cache used event for better performance" This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it was reported to break vhost_net. We want to cache used event and use it to check for notification. The assumption was that guest won't move the event idx back, but this could happen in fact when 16 bit index wraps around after 64K entries. Signed-off-by: Jason Wang Acked-by: Michael S. Tsirkin Signed-off-by: David S. Miller " I am requesting this patch to revert the problematic one be pulled into Ubuntu Zesty (anything 4.10+). ---uname output--- Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L ---Steps to Reproduce--- I can recreate the scenario with the following setup: - on a 20core host, start 20 1core VMs - I have a single linux bridge assigned to all guests using virtio - start a uperf benchmark between each guest pair (10 total) using a high number of uperf nprocs (32) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful
I have the same problem with similar symptoms, headset connects and works, after some time, the video stops and the headset stops working, than i can't connect again, have to remove the device, reboot, turn of and on the headphones to get it working again. But the problems doesn't always occur, somtines they work normaly. I never testet ubuntu with kernel 4.12 maybe i should do that -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719210 Title: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful Status in linux package in Ubuntu: Incomplete Bug description: Using artful kernel 4.12.0-13.14, Bluetooth audio works great. Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth audio issues which have manifested in a variety of weird ways: 1) Playback would stall after 10-20 seconds 2) Upon removing the device and attempting to redo pairing, no devices could be found to pair with 3) After the device ended up reverting to low quality mono HSP mode, it could not be switched back to A2DP This is all rather vague - sorry - but it felt better to get notice of this regression into the bugtracker sooner rather than later. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-generic 4.13.0-11.12 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 2091 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 24 21:24:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b InstallationDate: Installed on 2016-08-16 (404 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Spectre Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-11-generic N/A linux-backports-modules-4.13.0-11-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago) dmi.bios.date: 02/21/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A0 dmi.board.vendor: HP dmi.board.version: 48.54 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711251] Comment bridged from LTC Bugzilla
--- Comment From jhop...@us.ibm.com 2017-09-29 14:20 EDT--- I am working to verify now, I updated to artful since the fix is listed in (4.12.0-13.14) artful-proposed. Will post results soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711251 Title: vhost guest network randomly drops under stress (kvm) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: == SRU Justification == A vhost performance patch was introduced in the 4.10 kernel upstream, and is currently included in the Zesty 4.10 kernel: commit 809ecb9bca6a9424ccd392d67e368160f8b76c92 Author: Jason Wang Date: Mon Dec 12 14:46:49 2016 +0800 vhost: cache used event for better performance -- However I recently hit a functional issue linked to this patch which would cause random guests to lose their network connection under stress. This is not architecture specific and more likely to be hit with high network stress (i.e. lots of uperf instances). The patch author has now reverted this patch upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853 which reads: " Revert "vhost: cache used event for better performance" This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it was reported to break vhost_net. We want to cache used event and use it to check for notification. The assumption was that guest won't move the event idx back, but this could happen in fact when 16 bit index wraps around after 64K entries. Signed-off-by: Jason Wang Acked-by: Michael S. Tsirkin Signed-off-by: David S. Miller " I am requesting this patch to revert the problematic one be pulled into Ubuntu Zesty (anything 4.10+). ---uname output--- Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L ---Steps to Reproduce--- I can recreate the scenario with the following setup: - on a 20core host, start 20 1core VMs - I have a single linux bridge assigned to all guests using virtio - start a uperf benchmark between each guest pair (10 total) using a high number of uperf nprocs (32) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver
So I think I can now at least explain the weirdness. Booting from the ISO as well as the first boot in OEM mode seem to be in a way where grub does not use graphics mode and hands that off to a vt. In that case, when the kernels starts there will be no VESA framebuffer which later gets switched over to qxl framebuffer. So what I think broke is the init of the framebuffer drawing context. Which potentially is not needed when it is switched over from VESA to qxl. As soon as there was one successful boot in OEM mode, it looks like graphics handoff is used. So after that both 4.12 and 4.14 (and likely 4.13 as well) will successfully boot as well. One way I was able to make this work immediately was to interrupt the boot and replace $vt_handoff by vt.handoff=7 (or =1). And then boot on with that setting. In the crashed boots this was not set at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711358 Title: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Test Case 1. Boot artful desktop 20170817 under qemu with qxl 2. Wait until ubiquity-dm is displayed Expected result It boots Actual result It hangs on the splash screen and the dots below the Ubuntu logo are not blinking. If the option 'splash' is removed from the boot command line it boots successfully. It also boots successfully with -vga std but in this case the splash screen is in text mode not graphical unlike with the qxl driver. - It started with kernel 4.12. - It is still happening with kernel 4.13. - It only happens when booting from an ISO and not on an installed system. - It works with cirrus/vga, but not qxl - It works if nosplash is set (or splash removed from the boot command line) - It works on Xenial but not on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720444] [NEW] wifi suddenly disconnects
Public bug reported: Once a day my wifi disconnects and there is no way to reconnect to it via network manager. The only solution is to reboot my PC. I have changed my router in the last month but the problem still persists. MY wifi cards is: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection used driver is: iwl3945 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic 4.4.0.96.101 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2077 F pulseaudio Date: Fri Sep 29 22:13:29 2017 HibernationDevice: RESUME=UUID=1a9d7c50-5c59-4d68-bc51-1cf714537d97 InstallationDate: Installed on 2017-01-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer, inc. Aspire 5920 ProcEnviron: LANGUAGE=it TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmware1.157.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3708 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3708:bd08/15/2007:svnAcer,inc.:pnAspire5920:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Attachment added: "debug.txt" https://bugs.launchpad.net/bugs/1720444/+attachment/4958916/+files/debug.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720444 Title: wifi suddenly disconnects Status in linux package in Ubuntu: Confirmed Bug description: Once a day my wifi disconnects and there is no way to reconnect to it via network manager. The only solution is to reboot my PC. I have changed my router in the last month but the problem still persists. MY wifi cards is: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection used driver is: iwl3945 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic 4.4.0.96.101 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2077 F pulseaudio Date: Fri Sep 29 22:13:29 2017 HibernationDevice: RESUME=UUID=1a9d7c50-5c59-4d68-bc51-1cf714537d97 InstallationDate: Installed on 2017-01-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer, inc. Aspire 5920 ProcEnviron: LANGUAGE=it TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmware1.157.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3708 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3708:bd08/15/2007:svnAcer,inc.:pnAspire5920:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 1720444] 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/1720444 Title: wifi suddenly disconnects Status in linux package in Ubuntu: Confirmed Bug description: Once a day my wifi disconnects and there is no way to reconnect to it via network manager. The only solution is to reboot my PC. I have changed my router in the last month but the problem still persists. MY wifi cards is: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection used driver is: iwl3945 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic 4.4.0.96.101 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2077 F pulseaudio Date: Fri Sep 29 22:13:29 2017 HibernationDevice: RESUME=UUID=1a9d7c50-5c59-4d68-bc51-1cf714537d97 InstallationDate: Installed on 2017-01-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer, inc. Aspire 5920 ProcEnviron: LANGUAGE=it TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmware1.157.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3708 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3708:bd08/15/2007:svnAcer,inc.:pnAspire5920:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720444] Re: wifi suddenly disconnects
I forgot to add that with another ubuntu system (different hardware) but same os level I have no issue. Idem (no issue) with an Android and Windows smartphone so the problem is obviously related to my Acer hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720444 Title: wifi suddenly disconnects Status in linux package in Ubuntu: Confirmed Bug description: Once a day my wifi disconnects and there is no way to reconnect to it via network manager. The only solution is to reboot my PC. I have changed my router in the last month but the problem still persists. MY wifi cards is: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection used driver is: iwl3945 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic 4.4.0.96.101 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2077 F pulseaudio Date: Fri Sep 29 22:13:29 2017 HibernationDevice: RESUME=UUID=1a9d7c50-5c59-4d68-bc51-1cf714537d97 InstallationDate: Installed on 2017-01-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer, inc. Aspire 5920 ProcEnviron: LANGUAGE=it TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-96-generic N/A linux-backports-modules-4.4.0-96-generic N/A linux-firmware1.157.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2007 dmi.bios.vendor: Acer dmi.bios.version: v1.3708 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3708:bd08/15/2007:svnAcer,inc.:pnAspire5920:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
I'm looking for specific steps to recreate the problem on an Ubuntu system. What steps do I need to take for dkms to leave to a bunch of .old-dkms files in boot? -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
System76 here. We have also had luck with this grub flag: GRUB_GFXPAYLOAD_LINUX=1920*1080 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
1. Have nvidia-3## and/or virtualbox installed. 2. Update kernel. -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720466] [NEW] Add installer support for Broadcom BCM573xx network drivers.
Public bug reported:
Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.
bnxt_en has been available since upstream Linux 4.4 commit
c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
ethernet driver.").
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: artful xenial zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1720466
Title:
Add installer support for Broadcom BCM573xx network drivers.
Status in linux package in Ubuntu:
New
Bug description:
Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.
bnxt_en has been available since upstream Linux 4.4 commit
c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
ethernet driver.").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720466/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720466] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1720466
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/1720466
Title:
Add installer support for Broadcom BCM573xx network drivers.
Status in linux package in Ubuntu:
Incomplete
Bug description:
Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.
bnxt_en has been available since upstream Linux 4.4 commit
c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
ethernet driver.").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720466/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720466] Re: Add installer support for Broadcom BCM573xx network drivers.
** 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/1720466
Title:
Add installer support for Broadcom BCM573xx network drivers.
Status in linux package in Ubuntu:
Confirmed
Bug description:
Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.
bnxt_en has been available since upstream Linux 4.4 commit
c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
ethernet driver.").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720466/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
The bug didn't happened on test kernel 4.1.0-3. commit: 5f54bebd73a3903514d7ab786085b21ea757f92b -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
** Changed in: linux (Ubuntu Zesty) Status: Fix Committed => In Progress ** Tags removed: verification-needed-zesty ** Tags added: verification-failed-zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]
Can you attach the output of "videoinfo" under GRUB? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720197 Title: Every second(?) boot fails to display anything [MSHYBRID mode] Status in linux package in Ubuntu: Incomplete Bug description: When this laptop's firmware is set to MSHYBRID mode (intel/nvidia switchable graphics) it seems that every second boot it fails to display anything. This appears to be regardless of whether or not I enter the grub menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3020 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 28 13:41:53 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=ZFS=rpool/system ro RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704287] Re: wifi on lenovo ideapad 310 does not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704287 Title: wifi on lenovo ideapad 310 does not work Status in linux package in Ubuntu: Expired Bug description: I'm having the same problem as the issue #1640194 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-28-generic 4.10.0-28.32 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: z-lmutt1319 F...m pulseaudio /dev/snd/controlC0: z-lmutt1319 F pulseaudio CurrentDesktop: KDE Date: Fri Jul 14 08:07:45 2017 InstallationDate: Installed on 2017-06-29 (14 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 5986:06b1 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=41018553-7104-4a7b-bee0-d926fad5969f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 5A2 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 ideapad 310-15ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN36WW:bd08/30/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK: dmi.product.name: 80SM dmi.product.version: Lenovo ideapad 310-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1599599 Title: System beep broken (again) in Xenial Xerus Status in linux package in Ubuntu: Confirmed Bug description: This is my first ever bug report, so bear with me if I make mistakes. System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus. The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does. lsmod shows pcspkr is loaded Note The symptoms are exactly the same as in bug #486154 https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154 Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove. Interestingly, Ubuntu can and does produce the system beep in two other instances: 1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads. 2) Press Backspace without entering your password at login, and you will get the error beep. Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dv430uuyn 1784 F pulseaudio /dev/snd/controlC0: dv430uuyn 1784 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 6 14:00:50 2016 HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711 InstallationDate: Installed on 2016-06-24 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 430 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 054KM3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 430 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus
Thanks bam, You're right, it's not fixed. Whenever I restart Ubuntu it's a gamble as sometimes the system beep works and sometimes it doesn't. The 'beep' command always works, and when using virtual consoles (Ctrl+Alt+F1 to F6) the system beep always works, though the pitch seems higher. I changed the status to 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/1599599 Title: System beep broken (again) in Xenial Xerus Status in linux package in Ubuntu: Confirmed Bug description: This is my first ever bug report, so bear with me if I make mistakes. System bell (aka PC speaker beep) is not working upon installing Ubuntu 16.04 Xenial Xerus. The "beep" command has been installed and works, also "echo foo | wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor does pressing the rubout or other keys in terminal and Gedit like it usually does. lsmod shows pcspkr is loaded Note The symptoms are exactly the same as in bug #486154 https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154 Just for the record, rmmod and reloading the pcspkr module, unblacklisting it, trying in vain to turn up the volume, and all the other usual steps are no longer relevant at this point. We are way beyond that here. Something very, very elusive in this 16.04 distro is blocking the bell. I suspect something new in 16.04 runs after you login which nullifies the standard error beep. Pressing down at the end in Gedit and the terminal also used to make the beep, but something is telling it not to anymore. The PC speaker works of course, as the alternative beep command and "echo foo | wall" prove. Interestingly, Ubuntu can and does produce the system beep in two other instances: 1) Edit the grub menu at /etc/default /grub and remove the # hash at GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads. 2) Press Backspace without entering your password at login, and you will get the error beep. Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dv430uuyn 1784 F pulseaudio /dev/snd/controlC0: dv430uuyn 1784 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 6 14:00:50 2016 HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711 InstallationDate: Installed on 2016-06-24 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 430 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 054KM3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 430 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Still an issue; Ubuntu 17.04; 4.10.0-35-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
