Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

Bug #1491654 reported by Samantha Jian-Pielak on 2015-09-02
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Joseph Salisbury
Trusty
High
Joseph Salisbury
Xenial
High
Joseph Salisbury
Yakkety
High
Joseph Salisbury
Zesty
High
Joseph Salisbury

Bug Description

Current Behavior
==============================
1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

Reference Verification
==============================
1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
2. Which similar project/product passed/failed? NA

Steps to reproduce the problem
==============================
1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
2. Power on system and install Ubuntu 14.04.
3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

Expected Behavior
==============================
1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 install.

Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

Copied from private bug: https://bugs.launchpad.net/quantatw/+bug/1454965

modalias: pci:v00008086d00000953sv00008086sd00003703bc01sc08i02

udev properties:

P: /devices/pci0000:00/0000:00:03.0/0000:01:00.0/block/nvme0n1
N: nvme0n1
S: disk/by-uuid/4d7a5a96-e306-4a40-8fb7-d49c5ad2ee25
E: DEVLINKS=/dev/disk/by-uuid/4d7a5a96-e306-4a40-8fb7-d49c5ad2ee25
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci0000:00/0000:00:03.0/0000:01:00.0/block/nvme0n1
E: DEVTYPE=disk
E: ID_FS_TYPE=ext2
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=4d7a5a96-e306-4a40-8fb7-d49c5ad2ee25
E: ID_FS_UUID_ENC=4d7a5a96-e306-4a40-8fb7-d49c5ad2ee25
E: ID_FS_VERSION=1.0
E: MAJOR=259
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=650392

sysfs attributes:

  looking at device '/devices/pci0000:00/0000:00:03.0/0000:01:00.0/block/nvme0n1':
    KERNEL=="nvme0n1"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{ro}=="0"
    ATTR{size}=="3125627568"
    ATTR{stat}==" 1338 0 10620 244 0 0 0 0 0 56 244"
    ATTR{range}=="0"
    ATTR{discard_alignment}=="512"
    ATTR{ext_range}=="256"
    ATTR{alignment_offset}=="0"
    ATTR{inflight}==" 0 0"
    ATTR{removable}=="0"
    ATTR{capability}=="50"

  looking at parent device '/devices/pci0000:00/0000:00:03.0/0000:01:00.0':
    KERNELS=="0000:01:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="nvme"
    ATTRS{irq}=="40"
    ATTRS{subsystem_vendor}=="0x8086"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x010802"
    ATTRS{enabled}=="1"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,0fff0000,00000fff"
    ATTRS{device}=="0x0953"
    ATTRS{msi_bus}==""
    ATTRS{local_cpulist}=="0-11,48-59"
    ATTRS{vendor}=="0x8086"
    ATTRS{subsystem_device}=="0x3703"
    ATTRS{numa_node}=="0"
    ATTRS{d3cold_allowed}=="1"

There is no model file in /sys/block/nvme0n1/device/

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1491654

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: trusty
Changed in linux (Ubuntu):
importance: Undecided → Medium
AaronLan (aaron-lan) wrote :

commend "apport-collect 1491654" doesn't work.

Can't collect the log with apport-collect in the installer.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
AaronLan (aaron-lan) wrote :

Hi, Brad Figg

Did you have any update about this issue?

AaronLan (aaron-lan) wrote :

Retest install P3700 to install ubuntu 15.10 via PXE.
NVMe device name still show unknown when partition disk page.
This issue still occur.
Intel P3700 model:SSDPE2MD400G4 FW:8V010171

AaronLan (aaron-lan) wrote :

This symptom still exist in Ubuntu 16.04.1

Leo-Chen (leo-chen) wrote :

Hi
Any update about this issue ?.We're waiting for long time ,Please give we a positive reply.Thk

Changed in linux (Ubuntu Trusty):
status: New → In Progress
Changed in linux (Ubuntu Xenial):
status: New → In Progress
Changed in linux (Ubuntu Yakkety):
status: New → In Progress
Changed in linux (Ubuntu Zesty):
status: Confirmed → In Progress
Changed in linux (Ubuntu Yakkety):
importance: Undecided → High
Changed in linux (Ubuntu Zesty):
importance: Medium → High
Changed in linux (Ubuntu Xenial):
importance: Undecided → High
Changed in linux (Ubuntu Trusty):
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Yakkety):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Zesty):
assignee: nobody → Joseph Salisbury (jsalisbury)
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2

tags: added: kernel-da-key xenial yakkety zesty
Leo-Chen (leo-chen) wrote :

I have one question, How to install the v4.10.deb file on OS installation ?

description: updated
Joseph Salisbury (jsalisbury) wrote :

It would required that an installation first succeeds. Then install the .deb with "dpkg -i".

The easiest way to do this would be to try the daily build of Zesty. The iso can be downloaded from:

Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

However, Zesty is still using the 4.9 kernel, so it may fail as well. It would still be a good data point.

Leo-Chen (leo-chen) wrote :

It P3700 PCie-SSD model still show "Unknown " on 4.9 kernel

Joseph Salisbury (jsalisbury) wrote :

Are you able to get any versions of Ubuntu to install on the system?

Maybe you could install Ubuntu on another disk, but still have the SSD drives installed. That will allow us to test various kernels and/or patches to try and get the SSD to be recognized.

Leo-Chen (leo-chen) wrote :

Yes, The system can installed and got version.

Joseph Salisbury (jsalisbury) wrote :

Once the system is installed, can you test the 4.10-rc3 kernel? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3/

Leo-Chen (leo-chen) wrote :

About this issue was happened during OS installation ,As you said install test the 4.10-rc3 kernel under OS.but how to check and identify the SSD modle is correctly?

Joseph Salisbury (jsalisbury) wrote :

You should be able to review dmesg or /var/log/syslog to see if the "Unknown" message still happens.

Is the SSD drive still accessible when the "Unknown" message happens?

Leo-Chen (leo-chen) wrote :

I could not find anything about that "Unknown" message in dmesg or var/log/syslog.

>>It can be accessible,The SSD drive The"Unknown"message just unable to distinguish what are modle(SSD) to used during OS installation.

Joseph Salisbury (jsalisbury) wrote :

Is the SSD working as expected after booting with the 4.10-rc3 kernel? If it is, that may indicate this bug is fixed in mainline. If it is, we can perform a "Reverse" bisect and/or review the git logs to find the commit that fixes the bug.

Leo-Chen (leo-chen) wrote :

Yes, it can working afrer booting with the 4.10-rc3 kernel.

Joseph Salisbury (jsalisbury) wrote :

Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc3. We first need to identify the last bad kernel and first good one.

Can you test the following kernels:

3.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/
4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/
4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/

You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug.

AaronLan (aaron-lan) wrote :

Leo will try the following kernels.

Leo-Chen (leo-chen) wrote :

4.8-rc1 and 4.10-rc1 result as below:
root@192-168-1-5:~# dmesg | grep -i nvme
[ 6.884176] nvme nvme0: pci function 0000:81:00.0
[ 6.885573] nvme nvme1: pci function 0000:82:00.0
[ 10.027726] nvme1n1: p1 p2 p3
[ 10.117900] EXT4-fs (nvme1n1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 11.239349] EXT4-fs (nvme1n1p2): re-mounted. Opts: errors=remount-ro
[ 11.363905] nvme0n1:
[ 12.067057] Adding 33431548k swap on /dev/nvme1n1p3. Priority:-1 extents:1 across:33431548k SSFS

Joseph Salisbury (jsalisbury) wrote :

It sounds like 4.8-rc1 and 4.10-rc1 do not have the bug. Were you able to test the 4.5 final kernel?

Changed in linux (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in linux (Ubuntu Xenial):
status: In Progress → Incomplete
Changed in linux (Ubuntu Yakkety):
status: In Progress → Incomplete
Changed in linux (Ubuntu Zesty):
status: In Progress → Incomplete

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

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

Changed in linux (Ubuntu Yakkety):
status: Incomplete → Won't Fix
Sujith Pandel (sujithpandel) wrote :

I can see this behavior of reporting NVME disks as 'Unknown' by the installer in Ubuntu-16.04.3 (Server) with HWE kernel 4.10 during installation.
I do see that the sysfs has 'model' attribute, so I think its the installer who is not reading it, now.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers