← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

 

This bug was fixed in the package linux - 4.13.0-43.48

---------------
linux (4.13.0-43.48) artful; urgency=medium

  * CVE-2018-3639 (powerpc)
    - SAUCE: rfi-flush: update H_CPU_* macro names to upstream
    - SAUCE: rfi-flush: update plpar_get_cpu_characteristics() signature to
      upstream
    - SAUCE: update pseries_setup_rfi_flush() capitalization to upstream
    - powerpc/pseries: Support firmware disable of RFI flush
    - powerpc/powernv: Support firmware disable of RFI flush
    - powerpc/64s: Allow control of RFI flush via debugfs
    - powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code
    - powerpc/rfi-flush: Always enable fallback flush on pseries
    - powerpc/rfi-flush: Differentiate enabled and patched flush types
    - powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
    - powerpc: Add security feature flags for Spectre/Meltdown
    - powerpc/powernv: Set or clear security feature flags
    - powerpc/pseries: Set or clear security feature flags
    - powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()
    - powerpc/pseries: Use the security flags in pseries_setup_rfi_flush()
    - powerpc/pseries: Fix clearing of security feature flags
    - powerpc: Move default security feature flags
    - powerpc/pseries: Restore default security feature flags on setup
    - powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit

  * CVE-2018-3639 (x86)
    - SAUCE: Add X86_FEATURE_ARCH_CAPABILITIES
    - SAUCE: x86: Add alternative_msr_write
    - x86/nospec: Simplify alternative_msr_write()
    - x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
    - x86/bugs: Concentrate bug detection into a separate function
    - x86/bugs: Concentrate bug reporting into a separate function
    - x86/msr: Add definitions for new speculation control MSRs
    - x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits
    - x86/bugs, KVM: Support the combination of guest and host IBRS
    - x86/bugs: Expose /sys/../spec_store_bypass
    - x86/cpufeatures: Add X86_FEATURE_RDS
    - x86/bugs: Provide boot parameters for the spec_store_bypass_disable
      mitigation
    - x86/bugs/intel: Set proper CPU features and setup RDS
    - x86/bugs: Whitelist allowed SPEC_CTRL MSR values
    - x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested
    - x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
    - x86/speculation: Create spec-ctrl.h to avoid include hell
    - prctl: Add speculation control prctls
    - x86/process: Allow runtime control of Speculative Store Bypass
    - x86/speculation: Add prctl for Speculative Store Bypass mitigation
    - nospec: Allow getting/setting on non-current task
    - proc: Provide details on speculation flaw mitigations
    - seccomp: Enable speculation flaw mitigations
    - SAUCE: x86/bugs: Honour SPEC_CTRL default
    - x86/bugs: Make boot modes __ro_after_init
    - prctl: Add force disable speculation
    - seccomp: Use PR_SPEC_FORCE_DISABLE
    - seccomp: Add filter flag to opt-out of SSB mitigation
    - seccomp: Move speculation migitation control to arch code
    - x86/speculation: Make "seccomp" the default mode for Speculative Store
      Bypass
    - x86/bugs: Rename _RDS to _SSBD
    - proc: Use underscores for SSBD in 'status'
    - Documentation/spec_ctrl: Do some minor cleanups
    - x86/bugs: Fix __ssb_select_mitigation() return type
    - x86/bugs: Make cpu_show_common() static

  * LSM Stacking prctl values should be redefined as to not collide with
    upstream prctls (LP: #1769263) // CVE-2018-3639
    - SAUCE: LSM stacking: adjust prctl values

linux (4.13.0-42.47) artful; urgency=medium

  * linux: 4.13.0-42.47 -proposed tracker (LP: #1769993)

  * arm64: fix CONFIG_DEBUG_WX address reporting (LP: #1765850)
    - arm64: fix CONFIG_DEBUG_WX address reporting

  * HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
    - net: hns: Avoid action name truncation

  * CVE-2017-18208
    - mm/madvise.c: fix madvise() infinite loop under special circumstances

  * CVE-2018-8822
    - staging: ncpfs: memory corruption in ncp_read_kernel()

  * CVE-2017-18203
    - dm: fix race between dm_get_from_kobject() and __dm_destroy()

  * CVE-2017-17449
    - netlink: Add netns check on taps

  * CVE-2017-17975
    - media: usbtv: prevent double free in error case

  * [8086:3e92] display becomes blank after S3 (LP: #1763271)
    - drm/i915/edp: Allow alternate fixed mode for eDP if available.
    - drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp
    - drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
    - drm/i915/edp: Do not do link training fallback or prune modes on EDP

  * sky2 gigabit ethernet driver sometimes stops working after lid-open resume
    from sleep (88E8055) (LP: #1758507)
    - sky2: Increase D3 delay to sky2 stops working after suspend

  * perf vendor events arm64: Enable JSON events for ThunderX2 B0 (LP: #1760712)
    - perf vendor events arm64: Enable JSON events for ThunderX2 B0

  * No network with e1000e driver on 4.13.0-38-generic (LP: #1762693)
    - e1000e: Fix e1000_check_for_copper_link_ich8lan return value.

  * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812)
    - i2c: xlp9xx: return ENXIO on slave address NACK
    - i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly
    - i2c: xlp9xx: Check for Bus state before every transfer
    - i2c: xlp9xx: Handle NACK on DATA properly

  * "ip a" command on a guest VM shows UNKNOWN status (LP: #1761534)
    - virtio-net: Fix operstate for virtio when no VIRTIO_NET_F_STATUS

  * fix regression in mm/hotplug, allows NVIDIA driver to work (LP: #1761104)
    - SAUCE: Fix revert "mm, memory_hotplug: do not associate hotadded memory to
      zones until online"

  * ibrs/ibpb fixes result in excessive kernel logging  (LP: #1755627)
    - SAUCE: remove ibrs_dump sysctl interface

 -- Stefan Bader <stefan.bader@xxxxxxxxxxxxx>  Tue, 15 May 2018 07:39:26
+0200

** Changed in: linux (Ubuntu Artful)
       Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17449

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17975

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18203

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18208

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-8822

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1762693

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't have a working network connection. ethtool reports that my network interface doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
          Supported ports: [ TP ]
          Supported link modes:   10baseT/Half 10baseT/Full
                                  100baseT/Half 100baseT/Full
                                  1000baseT/Full
          Supported pause frame use: No
          Supports auto-negotiation: Yes
          Advertised link modes:  10baseT/Half 10baseT/Full
                                  100baseT/Half 100baseT/Full
                                  1000baseT/Full
          Advertised pause frame use: No
          Advertised auto-negotiation: Yes
          Speed: Unknown!
          Duplex: Unknown! (255)
          Port: Twisted Pair
          PHYAD: 2
          Transceiver: internal
          Auto-negotiation: on
          MDI-X: Unknown (auto)
          Supports Wake-on: pumbg
          Wake-on: g
          Current message level: 0x00000007 (7)
                                 drv probe link
          Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = [-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   25.969587] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   35.939670] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   46.263237] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci 0000:00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   56.935347] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   67.199669] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   78.170825] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   88.938939] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [   99.163603] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [  110.191137] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [  115.022823] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [  120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [  120.910537] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [  125.019509] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [  131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [  131.164741] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [  136.039268] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500
  [  142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  [  142.186891] e1000e 0000:00:1f.6 eth0: changing MTU from 1500 to 1492
  [  147.038361] e1000e 0000:00:1f.6 eth0: changing MTU from 1492 to 1500

  Everything works fine when I boot Linux 4.13.0-37-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  martin     2756 F.... pulseaudio
  CurrentDesktop: MATE
  Date: Tue Apr 10 11:34:19 2018
  EcryptfsInUse: Yes
  IwConfig:
   lo        no wireless extensions.

   eth0      no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=8ee32f29-87ea-4229-8807-35171b6dfeed ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware                             1.169.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-23 (76 days ago)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2002
  dmi.board.asset.tag: Default string
  dmi.board.name: H170-PRO/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd09/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170-PRO/USB3.1:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1762693/+subscriptions