Support for X553 Intel NIC in Xenial

Bug #1708870 reported by Vincent Bernat
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned
Xenial
Triaged
Medium
Unassigned
Zesty
Triaged
Medium
Unassigned

Bug Description

Hey!

The Intel Atom C3000 platform comes with an integrated X553 Intel NIC. Support was added in Linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=b3eb4e1860f35. PCI IDs are 8086:15E4 and 8086:15E5.

Would it be possible to backport such support into 4.4? Redhat provided support for such chips a few months back (through DKMS): https://access.redhat.com/errata/RHEA-2017:1194.

Thanks.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1708870

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: xenial
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Xenial):
status: New → Triaged
Changed in linux (Ubuntu Zesty):
status: New → Triaged
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
Changed in linux (Ubuntu Zesty):
importance: Undecided → Medium
tags: added: kernel-da-key zesty
Revision history for this message
Leroy Tennison (ltennison) wrote :

I am also needing the updated driver for a firewall appliance.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
Revision history for this message
Leroy Tennison (ltennison) wrote :

I logged in using the elinks browser (since the system has no GUI), allowed the application to have access via my account and nothing apparent happened. I did change the status to confirmed as requested above. If I need to do something after allowing the application to have access then please provide the steps i need to take, thanks.

Revision history for this message
Leroy Tennison (ltennison) wrote : apport information

AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116, 1 Jan 8 13:21 seq
 crw-rw----+ 1 root audio 116, 33 Jan 8 13:21 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=80757df8-19e5-4abd-9cec-f7106619f2b8
InstallationDate: Installed on 2019-01-08 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Supermicro Super Server
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=691a755f-26ff-4bee-bdb0-30c4ef9acf61 ro
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-87-generic N/A
 linux-backports-modules-4.4.0-87-generic N/A
 linux-firmware 1.157.11
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial xenial
Uname: Linux 4.4.0-87-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 08/28/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A2SDi-2C-HLN4F
dmi.board.vendor: Supermicro
dmi.board.version: 1.00
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1:bd08/28/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-2C-HLN4F:rvr1.00:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: Super Server
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

tags: added: apport-collected
Revision history for this message
Leroy Tennison (ltennison) wrote : CRDA.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : JournalErrors.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : Lspci.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : Lsusb.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : ProcModules.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : UdevDb.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote : WifiSyslog.txt

apport information

Revision history for this message
Leroy Tennison (ltennison) wrote :

Good! I had to subscribe to the bug to get apport-collect to work but obviously after doing so (and answering Yes to "... really .. proceed?" then "Send report") it did what it said.

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.