[Kernel-packages] [Bug 1640856] Re: eth0: Reset adapter
we activated the susuggested kernel cat /proc/version Linux version 4.9.0-040900rc5-generic (kernel@tangerine) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #201611131431 SMP Sun Nov 13 19:33:15 UTC 2016 however, same issue reappeared: Dec 11 21:58:00 puno01 kernel: [2306342.662457] [ cut here ] Dec 11 21:58:00 puno01 kernel: [2306342.662470] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/net/sched/sch_generic.c:316 dev_watchdog+0x22c/0x230 Dec 11 21:58:00 puno01 kernel: [2306342.662472] NETDEV WATCHDOG: eth0 (igb): transmit queue 7 timed out Dec 11 21:58:00 puno01 kernel: [2306342.662474] Modules linked in: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs dm_snapshot dm_bufio xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd bridge stp llc intel_rapl sb_edac edac_core x86_pkg_temp_thermal ast ttm drm_kms_helper coretemp drm ipmi_ssif crct10dif_pclmul crc32_pclmul ghash_clmulni_intel fb_sys_fops syscopyarea aesni_intel sysfillrect sysimgblt aes_x86_64 lrw glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds ipmi_si ipmi_msghandler shpchp wmi lpc_ich ioatdma mac_hid acpi_power_meter raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear raid10 igb i2c_algo_bit dca ahci ptp libahci pps_core hid_generic mpt3sas raid_class fjes mptsas mptscsih mptbase scsi_transport_sas usbhid hid Dec 11 21:58:00 puno01 kernel: [2306342.662555] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.9.0-040900rc5-generic #201611131431 Dec 11 21:58:00 puno01 kernel: [2306342.662557] Hardware name: Supermicro X10DRi/X10DRi, BIOS 1.1 04/14/2015 Dec 11 21:58:00 puno01 kernel: [2306342.662561] 88200e403da0 81416e32 88200e403df0 Dec 11 21:58:00 puno01 kernel: [2306342.662565] 88200e403de0 8108364b 013c 0007 Dec 11 21:58:00 puno01 kernel: [2306342.662569] 0008 881ff433c000 881ff6413940 Dec 11 21:58:00 puno01 kernel: [2306342.662574] Call Trace: Dec 11 21:58:00 puno01 kernel: [2306342.662577] Dec 11 21:58:00 puno01 kernel: [2306342.662586] [] dump_stack+0x63/0x81 Dec 11 21:58:00 puno01 kernel: [2306342.662594] [] __warn+0xcb/0xf0 Dec 11 21:58:00 puno01 kernel: [2306342.662598] [] warn_slowpath_fmt+0x5f/0x80 Dec 11 21:58:00 puno01 kernel: [2306342.662603] [] ? hrtimer_interrupt+0xc2/0x180 Dec 11 21:58:00 puno01 kernel: [2306342.662606] [] dev_watchdog+0x22c/0x230 Dec 11 21:58:00 puno01 kernel: [2306342.662609] [] ? qdisc_rcu_free+0x40/0x40 Dec 11 21:58:00 puno01 kernel: [2306342.662616] [] call_timer_fn+0x35/0x120 Dec 11 21:58:00 puno01 kernel: [2306342.662619] [] run_timer_softirq+0x215/0x4b0 Dec 11 21:58:00 puno01 kernel: [2306342.662624] [] ? handle_percpu_irq+0x3a/0x50 Dec 11 21:58:00 puno01 kernel: [2306342.662631] [] __do_softirq+0x104/0x28c Dec 11 21:58:00 puno01 kernel: [2306342.662634] [] irq_exit+0xb6/0xc0 Dec 11 21:58:00 puno01 kernel: [2306342.662639] [] xen_evtchn_do_upcall+0x35/0x40 Dec 11 21:58:00 puno01 kernel: [2306342.662642] [] xen_do_hypervisor_callback+0x1e/0x40 Dec 11 21:58:00 puno01 kernel: [2306342.662643] Dec 11 21:58:00 puno01 kernel: [2306342.662649] [] ? xen_hypercall_sched_op+0xa/0x20 Dec 11 21:58:00 puno01 kernel: [2306342.662651] [] ? xen_hypercall_sched_op+0xa/0x20 Dec 11 21:58:00 puno01 kernel: [2306342.662657] [] ? xen_safe_halt+0x10/0x20 Dec 11 21:58:00 puno01 kernel: [2306342.662663] [] ? default_idle+0x20/0xd0 Dec 11 21:58:00 puno01 kernel: [2306342.662668] [] ? arch_cpu_idle+0xf/0x20 Dec 11 21:58:00 puno01 kernel: [2306342.662671] [] ? default_idle_call+0x23/0x30 Dec 11 21:58:00 puno01 kernel: [2306342.662676] [] ? cpu_startup_entry+0x1d0/0x240 Dec 11 21:58:00 puno01 kernel: [2306342.662679] [] ? rest_init+0x77/0x80 Dec 11 21:58:00 puno01 kernel: [2306342.662685] [] ? start_kernel+0x448/0x469 Dec 11 21:58:00 puno01 kernel: [2306342.662689] [] ? x86_64_start_reservations+0x24/0x26 Dec 11 21:58:00 puno01 kernel: [2306342.662691] [] ? xen_start_kernel+0x52f/0x53b Dec 11 21:58:00 puno01 kernel: [2306342.662694] ---[ end trace 14b3343d2dd3515f ]--- Dec 11 21:58:00 puno01 kernel: [2306342.662741] igb :04:00.0 eth0: Reset adapter Dec 11 21:58:00 puno01 kernel: [2306342.663187] xenbr0: port 1(eth0) entered disabled state Dec 11 21:58:00 puno01 kernel: [2306342.685493] igb :04:00.1 eth1: Reset adapter Dec 11 21:58:00 puno01 kernel: [2306342.699077] igb :04:00.1 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Dec 11 21:58:02 puno01 kernel: [2306344.857683] igb :04:00.1: exceed max 2 second Dec 11 21:58:02 puno01 kernel: [2306344.859914] igb :04:00.1 eth1: igb: eth1 NIC Link is Down Dec 11 21:58:03 puno01 kernel: [2306346.074702] igb :04:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX ** Changed in: linux
[Kernel-packages] [Bug 1649213] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1649213 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/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649213] [NEW] Support rootfs on xhci-plat-hcd attached storage
Public bug reported: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647749] onza (i386) - tests ran: 19, failed: 1
tests ran: 19, failed: 1; http://kernel.ubuntu.com/testing/3.13.0-106.153-generic/onza__3.13.0-106.153__2016-12-12_06-59-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647749 Title: linux: 3.13.0-106.153 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-106.153 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649207] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1649207 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/1649207 Title: mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory Status in linux package in Ubuntu: Incomplete Bug description: Failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory Scenario ubuntu@cto-netsim3:~$ sudo ethtool -g ens6f0 [sudo] password for ubuntu: Ring parameters for ens6f0: Pre-set maximums: RX: 4096 RX Mini: 0 RX Jumbo: 0 TX: 8192 Current hardware settings: RX: 1024 RX Mini: 0 RX Jumbo: 0 TX: 1024 ubuntu@cto-netsim3:~$ sudo ethtool -G ens6f0 rx 4096 Cannot set device ring parameters: Cannot allocate memory After brinding the interface down with: ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 down I can not bring it back up !!! ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up SIOCSIFFLAGS: Cannot allocate memory ubuntu@cto-netsim3:~$ dmsg: [ 774.935067] mlx5_core :81:00.0: swiotlb buffer is full (sz: 8388608 bytes) [ 774.935070] swiotlb: coherent allocation failed for device :81:00.0 size=8388608 [ 774.935074] CPU: 38 PID: 6042 Comm: ethtool Not tainted 4.8.0-22-generic #24 [ 774.935075] Hardware name: Quanta Computer Inc D51B-1U (dual 1G LoM)/S2B-MB (dual 1G LoM), BIOS S2B_3A19 05/15/2015 [ 774.935078] 0286 65a68699 8d946b1db9a0 8502f5d2 [ 774.935083] 007f 8d946b1db9e8 8505a280 [ 774.935087] 8d946b1dba80 8d94000b 024082c0 8db471b0e0a0 [ 774.935091] Call Trace: [ 774.935104] [] dump_stack+0x63/0x81 [ 774.935108] [] swiotlb_alloc_coherent+0x140/0x160 [ 774.935115] [] x86_swiotlb_alloc_coherent+0x43/0x50 [ 774.935150] [] mlx5_dma_zalloc_coherent_node+0xa4/0x100 [mlx5_core] [ 774.935164] [] mlx5_buf_alloc_node+0x4d/0xc0 [mlx5_core] [ 774.935181] [] mlx5_cqwq_create+0x7e/0x160 [mlx5_core] [ 774.935199] [] mlx5e_open_cq+0x9e/0x1f0 [mlx5_core] [ 774.935214] [] mlx5e_open_channels+0x715/0xf30 [mlx5_core] [ 774.935229] [] mlx5e_open_locked+0xda/0x1e0 [mlx5_core] [ 774.935245] [] mlx5e_set_ringparam+0x21e/0x350 [mlx5_core] [ 774.935252] [] dev_ethtool+0x59f/0x1fc0 [ 774.935255] [] ? new_slab+0x300/0x6e0 [ 774.935259] [] ? __rtnl_unlock+0x2a/0x50 [ 774.935262] [] ? netdev_run_todo+0x60/0x330 [ 774.935266] [] ? alloc_set_pte+0x4ec/0x610 [ 774.935268] [] ? dev_get_by_name_rcu+0x61/0x80 [ 774.935272] [] dev_ioctl+0x180/0x5a0 [ 774.935277] [] sock_do_ioctl+0x42/0x50 [ 774.935280] [] sock_ioctl+0x1d2/0x290 [ 774.935283] [] do_vfs_ioctl+0xa3/0x610 [ 774.935287] [] ? __do_page_fault+0x203/0x4d0 [ 774.935289] [] SyS_ioctl+0x79/0x90 [ 774.935307] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 774.935312] mlx5_core :81:00.0: :81:00.0:mlx5_cqwq_create:121:(pid 6042): mlx5_buf_alloc_node() failed, -12 [ 774.935537] mlx5_core :81:00.0 ens6f0: mlx5e_open_locked: mlx5e_open_channels failed, -12 This is the upstream patches that fix this issue ec8b9981ad3f net/mlx5e: Create UMR MKey per RQ 3608ae77c098 net/mlx5e: Move function mlx5e_create_umr_mkey 1c1b522808a1 net/mlx5e: Implement
