[Bug 1626894] Re: nvme drive probe failure

2017-01-23 Thread Gerd Peter
i does not work with the stock kernel, I work with a patched kernel.
(https://forum.proxmox.com/threads/nvme-storage-issue.31572/page-2#post-159444)

my first results, only Only a few hours old, Are up to now good:
(a skylake Fujitsu D3417-B Mainboard with Intel C236 Chipset)

only one Line in dmesg:
# dmesg | grep -i nvme
[0.893264]  nvme0n1: p1 p2 p3

and up to now no errors

this is the part from lspci -v
...
01:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2260 (rev 
03) (prog-if 02 [NVM Express])
Subsystem: Silicon Motion, Inc. Device 2260
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f701 (64-bit, non-prefetchable) [size=16K]
Expansion ROM at f700 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [158] #19
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: nvme

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894

Title:
  nvme drive probe failure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1626894] Re: nvme drive probe failure

2017-01-15 Thread Gerd Peter
With this Hardware:

a skylake Fujitsu D3417-B Mainboard with Intel C236 Chipset with 64GB DDR4 ECC 
RAM and a
E3-1245-v5 XEON and one ADATA SSD M.2 2280 NVMe 1.2 PCIe Gen3x4 128GB XPG 
SX8000 
 with ext4 and thin LVM

I also get this error:

=> [45512.825928] nvme :01:00.0: Failed status: 0x, reset 
controller.
=> [45513.276990] nvme :01:00.0: Removing after probe failure
=> [45513.276997] nvme0n1: detected capacity change from 128035676160 to 0
[45513.507206] Aborting journal on device dm-0-8.
[45513.507226] Buffer I/O error on dev dm-0, logical block 3702784, lost sync 
page write
[45513.507248] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
[45513.507555] Buffer I/O error on dev dm-0, logical block 0, lost sync page 
write
[45513.507585] EXT4-fs error (device dm-0): ext4_journal_check_start:56: 
Detected aborted journal
[45513.507619] EXT4-fs (dm-0): Remounting filesystem read-only
[45513.507643] EXT4-fs (dm-0): previous I/O error to superblock detected
[45513.507656] Buffer I/O error on dev dm-0, logical block 0, lost sync page 
write
[45519.236744] device-mapper: thin: 251:4: metadata operation 
'dm_pool_commit_metadata' failed: error = -5
[45519.236766] device-mapper: thin: 251:4: aborting current metadata transaction
[45519.236949] device-mapper: thin: 251:4: failed to abort metadata transaction
[45519.236977] device-mapper: thin: 251:4: switching pool to failure mode
[45519.236978] device-mapper: thin metadata: couldn't read superblock
[45519.236989] device-mapper: thin: 251:4: failed to set 'needs_check' flag in 
metadata
[45519.237004] device-mapper: thin: 251:4: dm_pool_get_metadata_transaction_id 
returned -22
[46805.070494] rrdcached[2458]: segfault at c0 ip 7fb12ab3b1ed sp 
7fb126e376b0 error 4 in libc-2.19.so[7fb12aaf5000+1a1000]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626894

Title:
  nvme drive probe failure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs