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.ba...@canonical.com> Tue, 15 May 2018 07:39:26
+0200
--
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/1758507
Title:
sky2 gigabit ethernet driver sometimes stops working after lid-open
resume from sleep (88E8055)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
===SRU Justification===
[Impact]
sky2 ethernet stops working after system resume from suspend.
[Fix]
Increase the PCI D3 delay can workaround the issue.
[Test]
User responded that the D3 delay increase can solve the issue.
[Regression Potential]
Low. It only affects one device. The fix only increase the delay timer,
without any functional change.
===Original Bug Report===
After resuming from sleep using the lid-open event, OFTEN (60% replicable,
usually after 2nd or later resume) the NIC is not functional, and reloading the
sky2 module does not help. Relevant parts from dmesg:
[ 582.852065] sky2 0000:04:00.0: Refused to change power state, currently in
D3
...<after another suspend-resume>
[ 827.613729] sky2 0000:04:00.0: ignoring stuck error report bit
[ 827.613748] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613750] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613752] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613754] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613756] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613759] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613761] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613763] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613765] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613767] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613769] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613772] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613774] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613776] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613778] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613780] sky2 0000:04:00.0: enp4s0: phy I/O error
[ 827.613782] sky2 0000:04:00.0: enp4s0: phy I/O error
And after reloading the module:
[ 1421.781480] sky2: driver version 1.30
[ 1421.781533] sky2 0000:04:00.0: enabling device (0000 -> 0003)
[ 1421.781667] sky2 0000:04:00.0: unsupported chip type 0xff
[ 1421.782292] sky2: probe of 0000:04:00.0 failed with error -95
Possibly relevant:
[ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID.
Replicability: When it happens once, further suspend-resume cycles (tried ~5)
don't fix it. Reboot fixes the NIC, and it often survives first resume after
that, but 1-2 suspend-resume cycles later the issue WILL occur again.
Per-boot chance of encountering the issue - so far 2/5.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-12-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Date: Sat Mar 24 09:54:10 2018
HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
InstallationDate: Installed on 2018-03-21 (3 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64
(20180319)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d
consoleblank=300
RelatedPackageVersions:
linux-restricted-modules-4.15.0-12-generic N/A
linux-backports-modules-4.15.0-12-generic N/A
linux-firmware 1.173
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.11 - 067 - 1566
dmi.board.name: S11D
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 1.0
dmi.chassis.asset.tag: FSC
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0:
dmi.product.name: ESPRIMO Mobile U9200
dmi.product.version: 1.0
dmi.sys.vendor: FUJITSU SIEMENS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758507/+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
