Comment # 36 on bug 1161238 from Takashi Iwai

(In reply to Thomas Blume from comment #35)
> (In reply to Thomas Blume from comment #33)
> > Sorry, that one went out of my focus.
> > Looking at the rdsosreport in comment#29, it still shows the issue analyzed
> > in comment#22, e.g. the nvme device is not present and the kernel shows:
> > 
> > -->
> > [    1.383508] ab250 kernel: nvme nvme0: missing or invalid SUBNQN field.
> > [    1.386620] ab250 kernel: nvme nvme0: allocated 64 MiB host memory buffer.
> > [    1.398337] ab250 kernel: nvme nvme0: 4/0/0 default/read/poll queues
> > [    1.406485] ab250 kernel: nvme nvme0: Identify Descriptors failed (2)
> > --<
> > 
> > Martin, that looks like another driver issue.
> > Any idea what could be missing?
> 
> Takashi, since you were already involved in the bug.
> Does the aboe driver message tells you anything?

I'm no storage expert, but AFAIK, the first message about SUBNQN field is
usually due to a crappy firmware and mostly harmless.  The last message is the
regression and this likely came from the backport of the commit
538af88ea7d9de24
  nvme: make nvme_report_ns_ids propagate error back
and the regression got fixed later by the backport commit 22802bf742c2
  nvme: Namepace identification descriptor list is optional

And that was merged in April 9.  So likely already addressed in the latest Leap
15.2 kernel.