This bug is awaiting verification that the linux-azure/6.5.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-mantic-linux-azure-v2 
verification-needed-mantic-linux-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2041495

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2041495

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 10000:e1:00.0
  kernel: [ 1.754595] pcieport 10000:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 10000:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [    1.731760] nvme nvme0: pci function 10000:e1:00.0
  kernel: [    1.731778] pcieport 10000:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [    1.731780] nvme 10000:e1:00.0: PCI INT A: no GSI
  kernel: [    1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [    1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [    1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [    1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [    2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  ========== original bug report ==========

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 10000:e1:00.0
  kernel: [ 1.754595] pcieport 10000:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 10000:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2041495/+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

Reply via email to