Re: [Kernel-packages] [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

This is old, but I found the issue was related to avahi autoip and
disabled it, problem solved.

On 7/31/21 10:06 AM, Norbert wrote:
> ** Tags removed: disco
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828666

Title:
  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
  X99A motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
  kernels neworking does not work.  This is true whether I use the
  internal network card which is an Intel E1000 based chipset or a add
  on card that uses a Broadcomm chip.  The same kernels work fine on
  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
  machine for networking to work.  I have determined the problem is
  upstream as I built a 5.1.0 mainstream kernel and it behaves
  identically.  I can't report from a machine that doesn't work since
  networking is what is broken that is why this machine is running
  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-14-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
  Uname: Linux 4.18.0-18-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Sat May 11 03:20:29 2019
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (735 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-lowlatency N/A
   linux-backports-modules-4.18.0-18-lowlatency  N/A
   linux-firmware1.178.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E
  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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828666/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire

[Robert Dinse]

CubicSDR still triggers it for me even in 5.4.0-42.46, further a 5.8.0 mainline 
kernel also suffers
the same.  This was working for me until just a few days ago now it's not.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1868551

Title:
  Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
  i915_active_acquire

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]
  Users are experiencing a frequent NULL pointer dereference crash in 
i915_active_acquire when using kms, which is used by default.

  [Fix]
  The fix is a cherry pick from upstream which was supposed to be backported to 
5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to 
resolve some uninitialized pointer usage.

  [Test]
  Verified by multiple bug reporters.

  [Regression Potential]
  Medium. Although there are a lot of lines added, they're mostly boilerplate, 
and this patch is confirmed by multiple users to fix a crash.
  ---
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter 

Re: [Kernel-packages] [Bug 1766377] Re: Intel Ethernet I218-V [8086:15a1] Subsystem [1043:85c4] detected Hardware Unit Hang

[Robert Dinse]

I can't tell you what performance hit, that depends upon your
application, it will hit TCP apps harder than UDP because UDP can't take
advantage of it at all.  The performance hit will be highest in net
centric apps like routers.

  apt install ethtool
  ethtool --offload eth0  rx off  tx off

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 7 Jul 2020, Ted Gerold wrote:

> Date: Tue, 07 Jul 2020 16:26:22 -
> From: Ted Gerold <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Intel Ethernet I218-V [8086:15a1] Subsystem
> [1043:85c4] detected Hardware Unit Hang
> 
> Unfortunately I cant just install another card in an NUC.  What
> performance hit does turning hardware offloading off have?  How is it
> done and how is it reverted?
>
> Wish they would just fix the problem.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Intel Ethernet I218-V [8086:15a1] Subsystem [1043:85c4] detected
>  Hardware Unit Hang
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Confirmed
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I gave up on this ever being fixed since it's existed since 2.6 and
went and bought some Realtek ethernet cards, no problems since.  But, you
can work around this bug by turning hardware offloading off if efficiency
isn't an issue.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Mon, 6 Jul 2020, Ted Gerold wrote:

> Date: Mon, 06 Jul 2020 22:41:11 -
> From: Ted Gerold <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> I am also experiencing this issue.
>
> Distribution: Ubuntu 20.04 LTS
> Kernel: 5.4.0-26-generic
> Hardware: NUC10i7FNH - 2TB SSD - 64GB RAM
>
> [128476.886034] e1000e :00:1f.6 eno1: Detected Hardware Unit Hang:
>  TDH  
>  TDT  
>  next_to_use  
>  next_to_clean
>buffer_info[next_to_clean]:
>  time_stamp   <101e8eb91>
>  next_to_watch
>  jiffies  <101e8f598>
>  next_to_watch.status <0>
>MAC Status <40080083>
>PHY Status <796d>
>PHY 1000BASE-T Status  <3800>
>PHY Extended Status<3000>
>PCI Status <10>
> [128478.069750] e1000e :00:1f.6 eno1: Reset adapter unexpectedly
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Confirmed
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] 

[Kernel-packages] [Bug 1843511] [NEW] i915 enable_rc6=0 not respected

[Robert Dinse]

Public bug reported:

 i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
be able to walk by the monitor and see what is going on without having to go up 
and wiggle the mouse
and wait for it to wake up and my monitor to sync.

 I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
/etc/modprobe.d/i915.conf I have:

 options i915 enable_guc=3 enable_dc=0 enable_rc6=0

 In /etc/default/grub I have:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

 I have done update-grub2 and update-initramfs -u -k all and
rebooted, but still:

cat /sys/class/drm/card0/power/rc6_enable
1

 The kernel totally ignores my instructions and enables the damned
thing anyway.  ARRGGH!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-lowlatency 5.0.0.28.29
ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
Uname: Linux 5.0.0-28-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nanook 4342 F pulseaudio
CurrentDesktop: MATE
Date: Tue Sep 10 16:14:06 2019
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-28-lowlatency N/A
 linux-backports-modules-5.0.0-28-lowlatency  N/A
 linux-firmware   1.178.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1105
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
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.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug disco package-from-proposed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1843511

Title:
  i915 enable_rc6=0 not respected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
  machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
  want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
  be able to walk by the monitor and see what is going on without having to go 
up and wiggle the mouse
  and wait for it to wake up and my monitor to sync.

   I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
  enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
  /etc/modprobe.d/i915.conf I have:

   options i915 enable_guc=3 enable_dc=0 enable_rc6=0

   In /etc/default/grub I have:

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
  modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

   I have done update-grub2 and update-initramfs -u -k all and
  rebooted, but still:

  cat /sys/class/drm/card0/power/rc6_enable
  1

   The kernel totally ignores my instructions and enables the damned
  thing anyway.  ARRGGH!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-lowlatency 5.0.0.28.29
  ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
  Uname: Linux 5.0.0-28-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 4342 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep 10 16:14:06 2019
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
  RelatedPackageVersions:
   

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I am no longer using E1000 based cards.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 5 Sep 2019, Kai-Heng Feng wrote:

> Date: Thu, 05 Sep 2019 09:13:13 -
> From: Kai-Heng Feng 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Please test latest mainline kernel:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc7/
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Confirmed
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
> '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
> '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
> 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I gave up any hope it ever would be fixed, bought some NIC cards with a
different chipset, and moved on.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 5 Sep 2019, Chris Puttick wrote:

> Date: Thu, 05 Sep 2019 08:35:29 -
> From: Chris Puttick 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> We're seeing this bug consistently (although not consistent per se - the
> error does not occur immediately after boot, and doesn't immediately
> disconnect the server from the network; anything from 3 weeks to 3 hours
> before it starts, and a day or so after is starts before it gets
> permanently disconnected).
>
> # uname -a
> Linux  4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 
> 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
>
> Ubuntu 18.04.3 LTS
>
> Issue occurred on earlier 18.04 and kernel versions. Server was built as
> 18.04.1 and is a fairly minimal install acting as a virtual host with
> KVM/QEMU. It's not heavily loaded and doesn't have a huge amount of
> traffic. It's a co-located rental so we don't have a detailed spec, but
> if it's of interest more details are probably available from the
> provider.
>
> We have other servers with identical hardware from the same provider
> running 16.04 without any issue.
>
>
> ** Changed in: linux (Ubuntu Bionic)
>   Status: Expired => Confirmed
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Confirmed
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> 

Re: [Kernel-packages] [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

I can maybe do this but a 15 step bisection is not something I can do.
This machine needs to be in service 24x7 and it's 21 miles away, I have to
go there to reboot because when it comes up with no network then I'm stuck.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 4 Jun 2019, Connor Kuehl wrote:

> Date: Tue, 04 Jun 2019 23:10:33 -
> From: Connor Kuehl <1828...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on
>  i7-6850k on Asus X99A motherboard
> 
> Hi Robert,
>
> Since the uptime of that machine is important, this might be kind of
> tricky, but we can still collect logs on the troublesome kernel with an
> extra step. Once you've booted into the kernel where networking doesn't
> work, the report can be generated and saved locally. Then you can boot
> back into the 4.18 kernel and submit the report to this bug [1].
>
> My hope is that the logs might contain some clues which will help us
> zero in on the regression without too much kernel testing churn. If
> that's not the case, bisection to find the commit that introduced this
> regression looks like it could take around 15 steps to bisect and drill
> down on the regression.
>
> [1] See step #2 here:
> https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1828666
>
> Title:
>  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
>  X99A motherboard
>
> Status in linux package in Ubuntu:
>  Confirmed
>
> Bug description:
>  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
>  kernels neworking does not work.  This is true whether I use the
>  internal network card which is an Intel E1000 based chipset or a add
>  on card that uses a Broadcomm chip.  The same kernels work fine on
>  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
>  machine for networking to work.  I have determined the problem is
>  upstream as I built a 5.1.0 mainstream kernel and it behaves
>  identically.  I can't report from a machine that doesn't work since
>  networking is what is broken that is why this machine is running
>  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: linux-image-5.0.0-14-lowlatency (not installed)
>  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
>  Uname: Linux 4.18.0-18-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu27
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
> '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
> '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
> '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
> '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
> '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
> failed with exit code 1:
>  CurrentDesktop: MATE
>  Date: Sat May 11 03:20:29 2019
>  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
>  InstallationDate: Installed on 2017-05-05 (735 days ago)
>  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  MachineType: ASUS All Series
>  ProcFB: 0 nouveaufb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
> root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
>  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
> PulseAudio daemon running, or not running as session daemon.
>  RelatedPackageVersions:
>   linux-restricted-modules-4.18.0-18-lowlatency N/A
>   linux-backports-modules-4.18.0-18-lowlatency  N/A
>   linux-firmware1.178.1
>  RfKill:
>
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
>  dmi.bios.date: 08/11/2017
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: 1801
>  dmi.board.asset.tag: Default string
>  dmi.board.name: X99-E
>  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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
>  dmi.product.family: ASUS MB
>  dmi.product.name: All Series
>  dmi.product.sku: All
>  dmi.product.version: System Version
>  dmi.sys.vendor: ASUS
>
> To manage notifications about this bug go to:

[Kernel-packages] [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

Was kind of hoping something severe enough to render the Operating
System unusable on some platforms would get assigned someone and get a
reasonable priority rather that sitting in limbo.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828666

Title:
  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
  X99A motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
  kernels neworking does not work.  This is true whether I use the
  internal network card which is an Intel E1000 based chipset or a add
  on card that uses a Broadcomm chip.  The same kernels work fine on
  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
  machine for networking to work.  I have determined the problem is
  upstream as I built a 5.1.0 mainstream kernel and it behaves
  identically.  I can't report from a machine that doesn't work since
  networking is what is broken that is why this machine is running
  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-14-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
  Uname: Linux 4.18.0-18-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Sat May 11 03:20:29 2019
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (735 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-lowlatency N/A
   linux-backports-modules-4.18.0-18-lowlatency  N/A
   linux-firmware1.178.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E
  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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828666/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

Also, this machine is critical so I can not reboot frequently to test
kernels and I have no other machines with this specific hardware to test
with.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828666

Title:
  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
  X99A motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
  kernels neworking does not work.  This is true whether I use the
  internal network card which is an Intel E1000 based chipset or a add
  on card that uses a Broadcomm chip.  The same kernels work fine on
  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
  machine for networking to work.  I have determined the problem is
  upstream as I built a 5.1.0 mainstream kernel and it behaves
  identically.  I can't report from a machine that doesn't work since
  networking is what is broken that is why this machine is running
  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-14-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
  Uname: Linux 4.18.0-18-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Sat May 11 03:20:29 2019
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (735 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-lowlatency N/A
   linux-backports-modules-4.18.0-18-lowlatency  N/A
   linux-firmware1.178.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E
  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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828666/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1828666] Re: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

The i7-6700k has the same network interface cards as the i7-6850k so not
an issue with the cards.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828666

Title:
  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
  X99A motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
  kernels neworking does not work.  This is true whether I use the
  internal network card which is an Intel E1000 based chipset or a add
  on card that uses a Broadcomm chip.  The same kernels work fine on
  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
  machine for networking to work.  I have determined the problem is
  upstream as I built a 5.1.0 mainstream kernel and it behaves
  identically.  I can't report from a machine that doesn't work since
  networking is what is broken that is why this machine is running
  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-14-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
  Uname: Linux 4.18.0-18-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Sat May 11 03:20:29 2019
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (735 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-lowlatency N/A
   linux-backports-modules-4.18.0-18-lowlatency  N/A
   linux-firmware1.178.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E
  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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828666/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1828666] [NEW] Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard

[Robert Dinse]

Public bug reported:

On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
kernels neworking does not work.  This is true whether I use the
internal network card which is an Intel E1000 based chipset or a add on
card that uses a Broadcomm chip.  The same kernels work fine on X299
motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this machine
for networking to work.  I have determined the problem is upstream as I
built a 5.1.0 mainstream kernel and it behaves identically.  I can't
report from a machine that doesn't work since networking is what is
broken that is why this machine is running 4.18.0 instead of 5.0.0
kernel under Ubuntu 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-14-lowlatency (not installed)
ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
Uname: Linux 4.18.0-18-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: MATE
Date: Sat May 11 03:20:29 2019
HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
InstallationDate: Installed on 2017-05-05 (735 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-18-lowlatency N/A
 linux-backports-modules-4.18.0-18-lowlatency  N/A
 linux-firmware1.178.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-05-05 (6 days ago)
dmi.bios.date: 08/11/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: Default string
dmi.board.name: X99-E
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.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828666

Title:
  Kernels 5.0.0 and later networking does not work on i7-6850k on Asus
  X99A motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Asus x99A platform with an i7-6850k and 128GB RAM, 5.0.0 and later
  kernels neworking does not work.  This is true whether I use the
  internal network card which is an Intel E1000 based chipset or a add
  on card that uses a Broadcomm chip.  The same kernels work fine on
  X299 motherboards and i7-6700k CPUs.  I have to run 4.18.0-x on this
  machine for networking to work.  I have determined the problem is
  upstream as I built a 5.1.0 mainstream kernel and it behaves
  identically.  I can't report from a machine that doesn't work since
  networking is what is broken that is why this machine is running
  4.18.0 instead of 5.0.0 kernel under Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-14-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19-lowlatency 4.18.20
  Uname: Linux 4.18.0-18-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Sat May 11 03:20:29 2019
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (735 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I had a better fix, after becoming convinced Canonical was not going to
fix the drivers in my lifetime, I went and bought some non-Intel NICs.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Wed, 24 Apr 2019, Halvor Lyche Strandvoll wrote:

> Date: Wed, 24 Apr 2019 07:08:36 -
> From: Halvor Lyche Strandvoll 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> I made a workaround for this. That is basically just disable tso.
> This fix persists across boots.
>
> Copy the following script and save it as /etc/systemd/system/disable-
> tso@enp0s25.service
>
> ##
>
> [Unit]
> Description=Disable TSO for %i
> BindsTo=sys-subsystem-net-devices-%i.device
> After=sys-subsystem-net-devices-%i.device
>
> [Service]
> Type=oneshot
> ExecStart=/sbin/ethtool -K %i tso off
>
> [Install]
> WantedBy=sys-subsystem-net-devices-%i.device
>
> ##
>
> Run "systemctl enable disable-tso@enp0s25" with your interface name
> instead of "enp0s25" that is what mine is named.
>
> If you have more problematic interfaces just enable service for those as
> well.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Expired
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] 

Re: [Kernel-packages] [Bug 1824892] Re: Nvidia nouveah does not work in high resolution

[Robert Dinse]

*** This bug is a duplicate of bug 1824677 ***
https://bugs.launchpad.net/bugs/1824677


  This is fixed in 5.0.0-13.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 19 Apr 2019, Timo Aaltonen wrote:

> Date: Fri, 19 Apr 2019 06:27:15 -
> From: Timo Aaltonen 
> Reply-To: Bug 1824892 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824892] Re: Nvidia nouveah does not work in high resolution
> 
> *** This bug is a duplicate of bug 1824677 ***
>https://bugs.launchpad.net/bugs/1824677
>
> ** This bug has been marked a duplicate of bug 1824677
>   Display only has 640x480
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1824892
>
> Title:
>  Nvidia nouveah does not work in high resolution
>
> Status in linux package in Ubuntu:
>  Confirmed
>
> Bug description:
>  I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this 
> card is no longer supported by Nvidia, I use the nouveau drivers.  These work 
> Perfect in kernel 5.0.0-8-lowlatency, which I am
>  using to send this report.  But in 5.0.0-11-lowlatency I can only work in 
> super low resolution mode, I think its 640x480, my normal resolution is 
> 1920x1080.  Although I am including version.log per
>  instructions this is the working kernel, the broken kernel is TOO broken to 
> file a bug report with.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
>  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
>  Uname: Linux 5.0.0-8-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu27
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  nanook 2584 F pulseaudio
>  CurrentDesktop: MATE
>  Date: Mon Apr 15 16:21:10 2019
>  InstallationDate: Installed on 2018-12-06 (130 days ago)
>  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
> (20181017.2)
>  IwConfig:
>   enp5s0f1  no wireless extensions.
>
>   enp5s0f0  no wireless extensions.
>
>   lono wireless extensions.
>  MachineType: Apple Computer, Inc. MacPro2,1
>  ProcFB: 0 nouveaufb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
> root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
>  RelatedPackageVersions:
>   linux-restricted-modules-5.0.0-8-lowlatency N/A
>   linux-backports-modules-5.0.0-8-lowlatency  N/A
>   linux-firmware  1.178
>  RfKill:
>
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824892/+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/1824892

Title:
  Nvidia nouveah does not work in high resolution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this card 
is no longer supported by Nvidia, I use the nouveau drivers.  These work 
Perfect in kernel 5.0.0-8-lowlatency, which I am
  using to send this report.  But in 5.0.0-11-lowlatency I can only work in 
super low resolution mode, I think its 640x480, my normal resolution is 
1920x1080.  Although I am including version.log per
  instructions this is the working kernel, the broken kernel is TOO broken to 
file a bug report with.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 2584 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr 

Re: [Kernel-packages] [Bug 1824892] Status changed to Confirmed

[Robert Dinse]

Fixed in 5.0.0-13

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Mon, 15 Apr 2019, Ubuntu Kernel Bot wrote:

> Date: Mon, 15 Apr 2019 23:30:10 -
> From: Ubuntu Kernel Bot 
> Reply-To: Bug 1824892 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824892] 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 subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1824892
>
> Title:
>  Nvidia nouveah does not work in high resolution
>
> Status in linux package in Ubuntu:
>  Confirmed
>
> Bug description:
>  I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this 
> card is no longer supported by Nvidia, I use the nouveau drivers.  These work 
> Perfect in kernel 5.0.0-8-lowlatency, which I am
>  using to send this report.  But in 5.0.0-11-lowlatency I can only work in 
> super low resolution mode, I think its 640x480, my normal resolution is 
> 1920x1080.  Although I am including version.log per
>  instructions this is the working kernel, the broken kernel is TOO broken to 
> file a bug report with.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
>  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
>  Uname: Linux 5.0.0-8-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu27
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  nanook 2584 F pulseaudio
>  CurrentDesktop: MATE
>  Date: Mon Apr 15 16:21:10 2019
>  InstallationDate: Installed on 2018-12-06 (130 days ago)
>  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
> (20181017.2)
>  IwConfig:
>   enp5s0f1  no wireless extensions.
>
>   enp5s0f0  no wireless extensions.
>
>   lono wireless extensions.
>  MachineType: Apple Computer, Inc. MacPro2,1
>  ProcFB: 0 nouveaufb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
> root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
>  RelatedPackageVersions:
>   linux-restricted-modules-5.0.0-8-lowlatency N/A
>   linux-backports-modules-5.0.0-8-lowlatency  N/A
>   linux-firmware  1.178
>  RfKill:
>
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824892/+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/1824892

Title:
  Nvidia nouveah does not work in high resolution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this card 
is no longer supported by Nvidia, I use the nouveau drivers.  These work 
Perfect in kernel 5.0.0-8-lowlatency, which I am
  using to send this report.  But in 5.0.0-11-lowlatency I can only work in 
super low resolution mode, I think its 640x480, my normal resolution is 
1920x1080.  Although I am including version.log per
  instructions this is the working kernel, the broken kernel is TOO broken to 
file a bug report with.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 2584 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr 15 16:21:10 2019
  InstallationDate: Installed on 2018-12-06 (130 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   enp5s0f1  no wireless 

[Kernel-packages] [Bug 1824892] [NEW] Nvidia nouveah does not work in high resolution

[Robert Dinse]

Public bug reported:

I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this card 
is no longer supported by Nvidia, I use the nouveau drivers.  These work 
Perfect in kernel 5.0.0-8-lowlatency, which I am
using to send this report.  But in 5.0.0-11-lowlatency I can only work in super 
low resolution mode, I think its 640x480, my normal resolution is 1920x1080.  
Although I am including version.log per
instructions this is the working kernel, the broken kernel is TOO broken to 
file a bug report with.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
Uname: Linux 5.0.0-8-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nanook 2584 F pulseaudio
CurrentDesktop: MATE
Date: Mon Apr 15 16:21:10 2019
InstallationDate: Installed on 2018-12-06 (130 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
IwConfig:
 enp5s0f1  no wireless extensions.
 
 enp5s0f0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Apple Computer, Inc. MacPro2,1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-8-lowlatency N/A
 linux-backports-modules-5.0.0-8-lowlatency  N/A
 linux-firmware  1.178
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
dmi.bios.date: 07/02/07
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MP21.88Z.007F.B06.0707021348
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F4208DC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.version: Mac-F4208DC8
dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
dmi.product.family: MacPro
dmi.product.name: MacPro2,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug disco third-party-packages

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1824892/+attachment/5256078/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824892

Title:
  Nvidia nouveah does not work in high resolution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Mac Pro 1,1 with Nvidia GeForce 7300 GT video card.  Since this card 
is no longer supported by Nvidia, I use the nouveau drivers.  These work 
Perfect in kernel 5.0.0-8-lowlatency, which I am
  using to send this report.  But in 5.0.0-11-lowlatency I can only work in 
super low resolution mode, I think its 640x480, my normal resolution is 
1920x1080.  Although I am including version.log per
  instructions this is the working kernel, the broken kernel is TOO broken to 
file a bug report with.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-lowlatency 5.0.0-11.12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 2584 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr 15 16:21:10 2019
  InstallationDate: Installed on 2018-12-06 (130 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   enp5s0f1  no wireless extensions.
   
   enp5s0f0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Computer, Inc. MacPro2,1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-lowlatency N/A
   linux-backports-modules-5.0.0-8-lowlatency  N/A
   linux-firmware  1.178
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I gave up on it every being fixed and bought some broadcom interfaces
for my machines.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 23 Nov 2018, Emlyn Bolton wrote:

> Date: Fri, 23 Nov 2018 17:37:46 -
> From: Emlyn Bolton <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> I'm still seeing this issue on the 4.15.0-39-generic kernel:
>
> [467738.375137] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f70ff8>
>  next_to_watch.status <0>
> [467740.391180] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f711f0>
>  next_to_watch.status <0>
> [467742.407313] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f713e8>
>  next_to_watch.status <0>
> [467744.423373] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f715e0>
>  next_to_watch.status <0>
> [467745.319133] e1000 :05:01.0 enp5s1f0: Reset adapter
>
> 05:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (Copper) (rev 03)
>   Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
>   Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
>   Memory at f722 (64-bit, non-prefetchable) [size=128K]
>   Memory at f71c (64-bit, non-prefetchable) [size=256K]
>   I/O ports at d040 [size=64]
>   Expansion ROM at f718 [disabled] [size=256K]
>   Capabilities: [dc] Power Management version 2
>   Capabilities: [e4] PCI-X non-bridge device
>   Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
>   Kernel driver in use: e1000
>   Kernel modules: e1000
>
> 05:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (Copper) (rev 03)
>   Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
>   Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
>   Memory at f720 (64-bit, non-prefetchable) [size=128K]
>   Memory at f714 (64-bit, non-prefetchable) [size=256K]
>   I/O ports at d000 [size=64]
>   Expansion ROM at f710 [disabled] [size=256K]
>   Capabilities: [dc] Power Management version 2
>   Capabilities: [e4] PCI-X non-bridge device
>   Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
>   Kernel driver in use: e1000
>   Kernel modules: e1000
>
>
> This is a dual-port adapter, but I also saw the issue with the on-board i217 
> chip too.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Expired
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

4.14.0 final crashed hard after running 17 hours.  Not only was the
ethernet not-responsive, neither was the console, not even the magic
sys-req key.  I had to power cycle the machine to get it unhung.  Then
I booted 4.14.0rc1 and it immediately exploded however I had set a 20 second
time out and the machine self booted back into 4.15.0-21 and I turned hardware
offloading back off.

  I can not continue testing this on production machines and the one Intel
machine I have with that interface chip is currently broken.  I'll work on
getting that working and setup a web server on it and use some test software
to put a load on it.

  One thing I found digging in github is that there has been only one
commit against the E1000 driver in the last three years and that was on
February 13th, so might be worth looking at.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 11 May 2018, Joseph Salisbury wrote:

> Date: Fri, 11 May 2018 12:31:14 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Thanks for testing.  We should work backwards towards 4.13 now.  Can you
> test the following:
>
> 4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
> 4.14-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4/
> 4.14-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/
>
>
> You don't have to test every kernel, just up until the kernel that first has 
> this bug.
>
> Thanks in advance!
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

4.14 has the problem.  Do I need to try the 4.15rc0 kernel also since
4.14 isn't well?

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 10 May 2018, Joseph Salisbury wrote:

> Date: Thu, 10 May 2018 19:26:46 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Could you test the following two upstream kernels, so we can narrow down
> the last good and first bad further:
>
> v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
> v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I booted the most problematic machine, that's the i7-6850k machine,
probably because it has the most traffic, on the 4.14.0 kernel, so far so
good.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 10 May 2018, Joseph Salisbury wrote:

> Date: Thu, 10 May 2018 19:26:46 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Could you test the following two upstream kernels, so we can narrow down
> the last good and first bad further:
>
> v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
> v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I did not see this behavior with 4.13.0 and did with 4.15.0.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 10 May 2018, Joseph Salisbury wrote:

> Date: Thu, 10 May 2018 17:25:18 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> We could perform a kernel bisect to identify the commit that introduced
> this regression.  To perform a bisect, we need to identify the last
> kernel that did not have the bug and the first kernel version that did.
>
> Do you recall the last kernel that didn't exhibit the bug?  If not,
> would you be able to test some kernels to narrow it down?  I could post
> a link to the kernels to test.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Just to make sure you got the latest, the 4.17.x kernel did not work well
enoguh to leave it running, it broke kernel-nfs-server among other things.

  I am pressenting running 4.15.0-21 and with this kernel I would still
get these hangs except that I discovered disabling certain hardware offload
functions stops it, so presently in my /etc/rc.local file on the affected
servers I have: /sbin/ethtool -K eno1 gso off gro off tso off

  With this in place no hangs, slight performance penalty but no
hangs.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Mon, 7 May 2018, Joseph Salisbury wrote:

> Date: Mon, 07 May 2018 18:26:12 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> ** Tags removed: kernel-key
> ** Tags added: kernel-da-key
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I read an article here https://serverfault.com/questions/616485/e1000e-
reset-adapter-unexpectedly-detected-hardware-unit-
hang?utm_medium=organic_source=google_rich_qa_campaign=google_rich_qa
which stated some people had had success preventing this by disabling
hardware offloading with ethtool -K eth0 gso off gro off tso off.  With
the 4.15.0-21-lowlatency #22-Ubuntu SMP PREEMPT Tue May 1 15:47:42 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux kernel on the i7-6850 machine which
has been the most problematic, I did this and have not had a hang since.
Obviously this comes with a performance penalty so is undesirable as a
permanent fix but hoping this might help narrow the cause.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766377

Title:
  Ethernet E1000 Controller Hangs

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
motherboard, controller specifications:
  Intel® I218V, 1 x Gigabit LAN Controller(s)
  Intel® I211-AT, 1 x Gigabit LAN
  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
appliance
  Support Teaming Technology
  ASUS Turbo LAN Utility
  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
  This machine has a number of Qemu/KVM virtual guests and is using a software 
bridge to share the interface.
  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
multiple machines here.
  Here are the messages from dmesg:
  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d0880>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d1040>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
  [1016202.413701] bridge0: port 1(eno1) entered disabled state
  [1016202.413732] bridge0: topology change detected, propagating
  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [1016206.666708] bridge0: port 1(eno1) entered blocking state
  [1016206.666712] bridge0: port 1(eno1) entered listening state
  [1016216.750911] bridge0: port 1(eno1) entered learning state
  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [1017834.414792] platform regulatory.0: Direct firmware load for 
regulatory.db failed with error -2
  [1017834.414794] cfg80211: failed to load regulatory.db
  If there is any other information I can provide to aid in resolution, please 
contact me, nan...@eskimo.com.  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

This kernel did make it so I could not reproduce it on demand using
ethtool -G however it broke so many other things I could not leave it running
to see if it fixed spontaneous hangs.

  Strangely it broke nfs-kernel-server on the i7-6850k machine but not the
i7-6700k machine.  I did much stare and compare to make sure they were
configured the same.  This forced me to back out this kernel.

  But in addition to NFS, the nouveau drivers needed on the i7-6850k
machine had some bug that would pixelize much of the screen in a semi-random
fashion.  Also for whatever reason x2goserver would not work properly with
that kernel.

  On the i7-6700k machines, one I had to restart lightdm several times to
get it to actually start, it did not start on boot up.  On another I was unable
to get lightdm to start at all and only console graphics worked, and for some
reason they were in yellow instead of white.  The i7-6700k machines are using
the internal graphics of the i7-6700k processor clocked real slow to minimize
the impact on heat budget.

  So on the kernel-developers's PPA I saw another test kernel, 4.15.0-21,
I installed it, it also made ethtool -G not induce Ethernet hang but on the 
i7-6850 it's already hung once spontaneously:

[ 4112.809034] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <4f>
  TDT  <6f>
  next_to_use  <6f>
  next_to_clean<4e>
buffer_info[next_to_clean]:
  time_stamp   <1003a2221>
  next_to_watch<4f>
  jiffies  <1003a2d80>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[ 4114.793198] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <4f>
  TDT  <6f>
  next_to_use  <6f>
  next_to_clean<4e>
buffer_info[next_to_clean]:
  time_stamp   <1003a2221>
  next_to_watch<4f>
  jiffies  <1003a3540>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[ 4116.008748] [ cut here ]
[ 4116.008750] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out
[ 4116.008765] WARNING: CPU: 8 PID: 59 at 
/build/linux-QLn4bB/linux-4.15.0/net/s
ched/sch_generic.c:323 dev_watchdog+0x21d/0x230
[ 4116.008765] Modules linked in: tcp_diag inet_diag vhost_net vhost tap 
xt_CHEC
KSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv
4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
n
f_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables 
iptab
le_filter devlink rpcsec_gss_krb5 nfsv4 nfs fscache msr bridge stp llc 
binfmt_mi
sc nls_iso8859_1 quota_v2 quota_tree intel_rapl x86_pkg_temp_thermal 
intel_power
clamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
pcbc aesni_intel snd_hda_codec_hdmi aes_x86_64 input_leds crypto_simd 
glue_helper cryptd snd_hda_codec_realtek snd_hda_codec_generic snd_seq_midi 
snd_seq_midi_e
vent snd_hda_intel snd_hda_codec snd_hda_core snd_rawmidi snd_hwdep snd_seq 
snd_
pcm snd_seq_device
[ 4116.008792]  snd_timer intel_cstate eeepc_wmi snd asus_wmi sparse_keymap 
wmi_
bmof lpc_ich intel_rapl_perf intel_wmi_thunderbolt shpchp soundcore mei_me mei 
m
ac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
l
ibiscsi scsi_transport_iscsi nct6775 hwmon_vid coretemp parport_pc ppdev nfsd 
au
th_rpcgss nfs_acl lockd grace sunrpc lp parport ip_tables x_tables autofs4 
btrfs
  zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_t
x xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash 
d
m_log hid_generic usbhid hid raid10 nouveau video i2c_algo_bit ttm 
drm_kms_helpe
r mxm_wmi syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops ahci drm ptp 
liba
hci pps_core wmi
[ 4116.008825] CPU: 8 PID: 59 Comm: ksoftirqd/8 Not tainted 
4.15.0-21-lowlatency
  #22-Ubuntu
[ 4116.008825] Hardware name: ASUS All Series/X99-E, BIOS 1801 08/11/2017
[ 4116.008827] RIP: 0010:dev_watchdog+0x21d/0x230
[ 4116.008827] RSP: 0018:a9b8c64cbd60 EFLAGS: 00010282
[ 4116.008828] RAX:  RBX:  RCX: 
0006
[ 4116.008829] RDX: 0007 RSI: 0096 RDI: 
8e863f416490
[ 4116.008829] RBP: 

[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I discovered a way to cause this instantly, I attempted to change the
size of the ring buffers from 512 bytes to the hardware maximum of 4096
using: ethtool -G eno1 rx 4096 tx 4096, it instantly hung the interface
with the following in dmesg:

[458611.154752] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <48>
  TDT  <73>
  next_to_use  <73>
  next_to_clean<47>
buffer_info[next_to_clean]:
  time_stamp   <11b5117a3>
  next_to_watch<48>
  jiffies  <11b511d40>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[458613.138731] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <48>
  TDT  <73>
  next_to_use  <73>
  next_to_clean<47>
buffer_info[next_to_clean]:
  time_stamp   <11b5117a3>
  next_to_watch<48>
  jiffies  <11b512500>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[458615.122888] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <48>
  TDT  <73>
  next_to_use  <73>
  next_to_clean<47>
buffer_info[next_to_clean]:
  time_stamp   <11b5117a3>
  next_to_watch<48>
  jiffies  <11b512cc0>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[458617.106832] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
  TDH  <48>
  TDT  <73>
  next_to_use  <73>
  next_to_clean<47>
buffer_info[next_to_clean]:
  time_stamp   <11b5117a3>
  next_to_watch<48>
  jiffies  <11b513480>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>[458619.154912] e1000e :00:19.0 
eno1: Detected Hardware Unit Hang:
  TDH  <48>
  TDT  <73>
  next_to_use  <73>
  next_to_clean<47>
buffer_info[next_to_clean]:
  time_stamp   <11b5117a3>
  next_to_watch<48>
  jiffies  <11b513c80>
  next_to_watch.status <0>
MAC Status <80083>
PHY Status <796d>
PHY 1000BASE-T Status  <7c00>
PHY Extended Status<3000>
PCI Status <10>
[458620.562618] e1000e :00:19.0 eno1: Reset adapter unexpectedly
[458620.562761] bridge0: port 1(eno1) entered disabled state
[458620.562789] bridge0: topology change detected, propagating
[458623.880650] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
[458623.880683] bridge0: port 1(eno1) entered blocking state
[458623.880688] bridge0: port 1(eno1) entered listening state
[458638.995031] bridge0: port 1(eno1) entered learning state
[458654.355381] bridge0: port 1(eno1) entered forwarding state
[458654.355385] bridge0: topology change detected, sending tcn bpdu
[476901.384610] bridge0: port 1(eno1) entered disabled state
[476901.384656] bridge0: topology change detected, propagating
[476905.544755] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
[476905.544788] bridge0: port 1(eno1) entered blocking state
[476905.544791] bridge0: port 1(eno1) entered listening state
[476920.887125] bridge0: port 1(eno1) entered learning state
[476936.247478] bridge0: port 1(eno1) entered forwarding state
[476936.247482] bridge0: topology change detected, sending tcn bpdu

-- 
You received this bug notification because you are a member of Kernel
Packages, 

[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Still happening, not sure why but far more frequently on i7-6850k
platform than i7-6700k.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766377

Title:
  Ethernet E1000 Controller Hangs

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
motherboard, controller specifications:
  Intel® I218V, 1 x Gigabit LAN Controller(s)
  Intel® I211-AT, 1 x Gigabit LAN
  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
appliance
  Support Teaming Technology
  ASUS Turbo LAN Utility
  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
  This machine has a number of Qemu/KVM virtual guests and is using a software 
bridge to share the interface.
  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
multiple machines here.
  Here are the messages from dmesg:
  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d0880>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d1040>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
  [1016202.413701] bridge0: port 1(eno1) entered disabled state
  [1016202.413732] bridge0: topology change detected, propagating
  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [1016206.666708] bridge0: port 1(eno1) entered blocking state
  [1016206.666712] bridge0: port 1(eno1) entered listening state
  [1016216.750911] bridge0: port 1(eno1) entered learning state
  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [1017834.414792] platform regulatory.0: Direct firmware load for 
regulatory.db failed with error -2
  [1017834.414794] cfg80211: failed to load regulatory.db
  If there is any other information I can provide to aid in resolution, please 
contact me, nan...@eskimo.com.  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Apr 23 16:45:30 2018
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (353 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Hate to say it but it happened again.  Only once which is a lot better
in terms of frequency but still happening, here are details:

[23144.764734] hrtimer: interrupt took 46767 ns
[41628.563552] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <65>
 next_to_use  <65>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <1027691ea>
 next_to_watch
 jiffies  <102769c40>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <7c00>
   PHY Extended Status<3000>
   PCI Status <10>
[41630.611608] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <65>
 next_to_use  <65>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <1027691ea>
 next_to_watch
 jiffies  <10276a440>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <7c00>
   PHY Extended Status<3000>
   PCI Status <10>
[41632.595800] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <65>
 next_to_use  <65>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <1027691ea>
 next_to_watch
 jiffies  <10276ac00>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <7c00>
   PHY Extended Status<3000>
   PCI Status <10>
[41634.579772] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <65>
 next_to_use  <65>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <1027691ea>
 next_to_watch
 jiffies  <10276b3c0>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <7c00>
   PHY Extended Status<3000>
   PCI Status <10>
[41635.667409] [ cut here ]
[41635.667411] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out
[41635.667424] WARNING: CPU: 9 PID: 65 at 
/build/linux-5s7Xkn/linux-4.15.0/net/sched/sch_generic.c:323 
dev_watchdog+0x21d/0x230
[41635.667424] Modules linked in: tcp_diag inet_diag vhost_net vhost tap 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink rpcsec_gss_krb5 nfsv4 nfs fscache msr bridge 
stp llc binfmt_misc quota_v2 quota_tree nls_iso8859_1 intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_hdmi aesni_intel aes_x86_64 
crypto_simd snd_hda_codec_realtek snd_hda_codec_generic glue_helper 
snd_hda_intel cryptd input_leds snd_hda_codec intel_cstate intel_rapl_perf 
snd_hda_core snd_hwdep snd_seq_midi snd_seq_midi_event snd_rawmidi
[41635.667448]  snd_seq snd_seq_device snd_pcm eeepc_wmi asus_wmi snd_timer 
sparse_keymap wmi_bmof intel_wmi_thunderbolt mei_me snd soundcore lpc_ich 
shpchp mei mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid nfsd coretemp 
auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport ip_tables 
x_tables autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
dm_mirror dm_region_hash dm_log hid_generic usbhid hid raid10 nouveau video 
i2c_algo_bit ttm drm_kms_helper mxm_wmi syscopyarea sysfillrect sysimgblt 
e1000e fb_sys_fops ahci drm libahci ptp pps_core wmi
[41635.667479] CPU: 9 PID: 65 Comm: ksoftirqd/9 Not tainted 
4.15.0-20-lowlatency #21-Ubuntu
[41635.667480] Hardware name: ASUS All Series/X99-E, BIOS 1801 08/11/2017
[41635.667481] RIP: 0010:dev_watchdog+0x21d/0x230
[41635.667482] RSP: 0018:a1a9064fbd60 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Looks like you nailed it.  Three machines running haven't barfed in over 
11 hours, used to several times an hour.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 24 Apr 2018, Joseph Salisbury wrote:

> Date: Tue, 24 Apr 2018 23:59:59 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Yes, that is the correct kernel version.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
> '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
> '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
> 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Ok, will reboot tonight when traffic is low and let you know how it goes.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 24 Apr 2018, Joseph Salisbury wrote:

> Date: Tue, 24 Apr 2018 23:59:59 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Yes, that is the correct kernel version.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
>  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
>  Uname: Linux 4.15.0-15-lowlatency x86_64
>  ApportVersion: 2.20.9-0ubuntu6
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
> '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
> '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

There is a 4.50.0-20.21 in Proposed, is this the correct kernel?

On Tue, April 24, 2018 8:47 am, Joseph Salisbury wrote:
> Would it be possible for you to test the proposed kernel and post back if
> it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed
> for documentation how to enable and use -proposed.
>
> Thank you in advance!
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
>
> ** Also affects: linux (Ubuntu Bionic)
> Importance: High
> Status: Confirmed
>
>
> ** Tags added: kernel-key
>
>
> ** Changed in: linux (Ubuntu Bionic)
> Status: Confirmed => Incomplete
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report. https://bugs.launchpad.net/bugs/1766377
>
>
> Title:
> Ethernet E1000 Controller Hangs
>
>
> Status in linux package in Ubuntu:
> Incomplete
> Status in linux source package in Bionic:
> Incomplete
>
>
> Bug description:
> With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX
> motherboard, controller specifications: Intel® I218V, 1 x Gigabit LAN
> Controller(s)
> Intel® I211-AT, 1 x Gigabit LAN
> Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE)
> appliance Support Teaming Technology
> ASUS Turbo LAN Utility
> The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
> This machine has a number of Qemu/KVM virtual guests and is using a
> software bridge to share the interface. This did not happen with 17.10 and
> 4.13.0 kernel.  It is happening on multiple machines here.
> Here are the messages from dmesg:
> 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d> next_to_clean
> buffer_info[next_to_clean]:
> time_stamp   <13c8d0008> next_to_watch jiffies
> <13c8d0880>
> next_to_watch.status <0> MAC Status <80083>
> PHY Status <796d>
> PHY 1000BASE-T Status  <3c00>
> PHY Extended Status<3000>
> PCI Status <10>
> [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d> next_to_clean
> buffer_info[next_to_clean]:
> time_stamp   <13c8d0008> next_to_watch jiffies
> <13c8d1040>
> next_to_watch.status <0> MAC Status <80083>
> PHY Status <796d>
> PHY 1000BASE-T Status  <3c00>
> PHY Extended Status<3000>
> PCI Status <10>
> [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
> [1016202.413701] bridge0: port 1(eno1) entered disabled state
> [1016202.413732] bridge0: topology change detected, propagating
> [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: Rx/Tx
> [1016206.666708] bridge0: port 1(eno1) entered blocking state
> [1016206.666712] bridge0: port 1(eno1) entered listening state
> [1016216.750911] bridge0: port 1(eno1) entered learning state
> [1016232.110291] bridge0: port 1(eno1) entered forwarding state
> [1016232.110294] bridge0: topology change detected, sending tcn bpdu
> [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for
> regulatory database [1017834.390770] cfg80211: Loaded X.509 cert
> 'sforshee: 00b28ddf47aef9cea7'
> [1017834.414792] platform regulatory.0: Direct firmware load for
> regulatory.db failed with error -2 [1017834.414794] cfg80211: failed to
> load regulatory.db If there is any other information I can provide to aid
> in resolution, please contact me, nan...@eskimo.com.  Thank you!
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
> ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
> Uname: Linux 4.15.0-15-lowlatency x86_64
> ApportVersion: 2.20.9-0ubuntu6
> Architecture: amd64
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3',
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0',
> '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p',
> '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path',
> '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p',
> '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0',
> '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
> CurrentDesktop: MATE
> Date: Mon Apr 23 16:45:30 2018
> HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
> InstallationDate: Installed on 2017-05-05 (353 days ago)
> InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64
> (20170412)
> MachineType: ASUS All Series
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency
> root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash
> vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit
> code 1: No PulseAudio daemon running, or not running as session daemon.
> 

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

Yes though I will need to boot at night when usage is low.  Can you tell
me what the kernel version is so I an be sure to get the correct kernel?

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 24 Apr 2018, Joseph Salisbury wrote:

> Date: Tue, 24 Apr 2018 15:47:57 -
> From: Joseph Salisbury 
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> Would it be possible for you to test the proposed kernel and post back if it 
> resolves this bug?
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
> enable and use -proposed.
>
> Thank you in advance!
>
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => High
>
> ** Also affects: linux (Ubuntu Bionic)
>   Importance: High
>   Status: Confirmed
>
> ** Tags added: kernel-key
>
> ** Changed in: linux (Ubuntu Bionic)
>   Status: Confirmed => Incomplete
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Incomplete
> Status in linux source package in Bionic:
>  Incomplete
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
> appliance
>  Support Teaming Technology
>  ASUS Turbo LAN Utility
>  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
>  This machine has a number of Qemu/KVM virtual guests and is using a software 
> bridge to share the interface.
>  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
> multiple machines here.
>  Here are the messages from dmesg:
>  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d0880>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
> TDH  
> TDT  <2d>
> next_to_use  <2d>
> next_to_clean
>   buffer_info[next_to_clean]:
> time_stamp   <13c8d0008>
> next_to_watch
> jiffies  <13c8d1040>
> next_to_watch.status <0>
>   MAC Status <80083>
>   PHY Status <796d>
>   PHY 1000BASE-T Status  <3c00>
>   PHY Extended Status<3000>
>   PCI Status <10>
>  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
>  [1016202.413701] bridge0: port 1(eno1) entered disabled state
>  [1016202.413732] bridge0: topology change detected, propagating
>  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: Rx/Tx
>  [1016206.666708] bridge0: port 1(eno1) entered blocking state
>  [1016206.666712] bridge0: port 1(eno1) entered listening state
>  [1016216.750911] bridge0: port 1(eno1) entered learning state
>  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
>  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
>  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
>  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  [1017834.414792] platform regulatory.0: Direct firmware load for 
> regulatory.db failed with error -2
>  [1017834.414794] cfg80211: failed to load regulatory.db
>  If there is any other information I can provide to aid in resolution, please 
> contact me, nan...@eskimo.com.  Thank you!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: 

[Kernel-packages] [Bug 1766377] [NEW] Ethernet E1000 Controller Hangs

[Robert Dinse]

Public bug reported:

 With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
motherboard, controller specifications:
Intel® I218V, 1 x Gigabit LAN Controller(s)
Intel® I211-AT, 1 x Gigabit LAN
Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) appliance
Support Teaming Technology
ASUS Turbo LAN Utility
The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
This machine has a number of Qemu/KVM virtual guests and is using a software 
bridge to share the interface.
This did not happen with 17.10 and 4.13.0 kernel.  It is happening on multiple 
machines here.
Here are the messages from dmesg:
1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
   TDH  
   TDT  <2d>
   next_to_use  <2d>
   next_to_clean
 buffer_info[next_to_clean]:
   time_stamp   <13c8d0008>
   next_to_watch
   jiffies  <13c8d0880>
   next_to_watch.status <0>
 MAC Status <80083>
 PHY Status <796d>
 PHY 1000BASE-T Status  <3c00>
 PHY Extended Status<3000>
 PCI Status <10>
[1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
   TDH  
   TDT  <2d>
   next_to_use  <2d>
   next_to_clean
 buffer_info[next_to_clean]:
   time_stamp   <13c8d0008>
   next_to_watch
   jiffies  <13c8d1040>
   next_to_watch.status <0>
 MAC Status <80083>
 PHY Status <796d>
 PHY 1000BASE-T Status  <3c00>
 PHY Extended Status<3000>
 PCI Status <10>
[1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
[1016202.413701] bridge0: port 1(eno1) entered disabled state
[1016202.413732] bridge0: topology change detected, propagating
[1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
[1016206.666708] bridge0: port 1(eno1) entered blocking state
[1016206.666712] bridge0: port 1(eno1) entered listening state
[1016216.750911] bridge0: port 1(eno1) entered learning state
[1016232.110291] bridge0: port 1(eno1) entered forwarding state
[1016232.110294] bridge0: topology change detected, sending tcn bpdu
[1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
[1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[1017834.414792] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[1017834.414794] cfg80211: failed to load regulatory.db
If there is any other information I can provide to aid in resolution, please 
contact me, nan...@eskimo.com.  Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: MATE
Date: Mon Apr 23 16:45:30 2018
HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
InstallationDate: Installed on 2017-05-05 (353 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-15-lowlatency N/A
 linux-backports-modules-4.15.0-15-lowlatency  N/A
 linux-firmware1.173
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-04-12 (11 days ago)
dmi.bios.date: 08/11/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: Default string
dmi.board.name: X99-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string

[Kernel-packages] [Bug 1715609] Re: kernel warning: skb_warn_bad_offload

[Robert Dinse]

This bug also affects the low-latency kernel Linux iglulik
4.10.0-37-lowlatency #41-Ubuntu SMP PREEMPT Fri Oct 6 21:30:07 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux and you can make that four people that
are affected.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715609

Title:
  kernel warning: skb_warn_bad_offload

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp