Date: Sun, 03 Dec 2017 22:03:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224064] [nvme][hang][resume] nvme_ctrlr_wait_for_ready called with desired_val = 0 but cc.en =1 Message-ID: <bug-224064-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224064 Bug ID: 224064 Summary: [nvme][hang][resume] nvme_ctrlr_wait_for_ready called with desired_val =3D 0 but cc.en =3D1 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dch@freebsd.org Created attachment 188501 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188501&action= =3Dedit nvme info on resuming from suspend the system stalls on any disk i/o, after console shows: freebsd nvme_ctrlr_wait_for_ready called with desired_val =3D 0 but cc.en = =3D 1 - issue occurs frequently but not 100%, some resumes work fine - easily reproducible - X is running, as are any open terminals, until disk is required system is a dell xps13 laptop with a TOSHIBA NVMe. https://wiki.freebsd.org/Laptops/Dell_XPS13_9360 for full specs & dmesg/devinfo/diskinfo etc. https://s3.amazonaws.com/uploads.hipchat.com/8784/2508819/N0PyBJEhSHX3jKu/I= MG_2693.JPG https://s3.amazonaws.com/uploads.hipchat.com/8784/2508819/eLtZ9caTMR7B6eb/I= MG_2677.JPG # dmesg nvme0: <Generic NVMe Device> mem 0xdc000000-0xdc003fff at device 0.0 on pci4 nvd0: <THNSN5512GPUK NVMe TOSHIBA 512GB> NVMe namespace nvd0: 488386MB (1000215216 512 byte sectors) # nvmcontrol info nvme0: THNSN5512GPUK NVMe TOSHIBA 512GB nvme0ns1 (488386MB) Controller Capabilities/Features =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D Vendor ID: 1179 Subsystem Vendor ID: 1179 Serial Number: 376B508IKSJU Model Number: THNSN5512GPUK NVMe TOSHIBA 512GB Firmware Version: 5KDA4103 Recommended Arb Burst: 1 IEEE OUI Identifier: 0d 08 00 Multi-Interface Cap: 00 Max Data Transfer Size: Unlimited Controller ID: 0x00 Admin Command Set Attributes =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Security Send/Receive: Supported Format NVM: Supported Firmware Activate/Download: Supported Namespace Managment: Not Supported Abort Command Limit: 4 Async Event Request Limit: 4 Number of Firmware Slots: 1 Firmware Slot 1 Read-Only: No Per-Namespace SMART Log: No Error Log Page Entries: 128 Number of Power States: 5 NVM Command Set Attributes =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Submission Queue Entry Size Max: 64 Min: 64 Completion Queue Entry Size Max: 16 Min: 16 Number of Namespaces: 1 Compare Command: Not Supported Write Uncorrectable Command: Supported Dataset Management Command: Supported Volatile Write Cache: Present Size (in LBAs): 1000215216 (953M) Capacity (in LBAs): 1000215216 (953M) Utilization (in LBAs): 1000215216 (953M) Thin Provisioning: Not Supported Number of LBA Formats: 2 Current LBA Format: LBA Format #00 LBA Format #00: Data Size: 512 Metadata Size: 0 LBA Format #01: Data Size: 4096 Metadata Size: 0 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224064-8>