On Mon, Jun 15, 2020 at 08:03:40PM +0200, Janne Johansson wrote: > Den m??n 15 juni 2020 kl 19:59 skrev Kenneth R Westerback < > kwesterb...@gmail.com>: > > > On Mon, Jun 15, 2020 at 07:15:36PM +0200, Janne Johansson wrote: > > > Recent AMD box with a bunch of nvme drives, never booted anything, > > crashes > > The line > > > > scsibus2 at nvme1: 33 targets, initiator 0 > > > > is also weird. I have never seen anything but 1 or 2 targets on nvme. > > > > > My bad. It has four or five nvmes and there is some .. reflection going on. > I seem to recall similar things in the old scsi1 days if you had bad > termination, long since I saw mirrored devices like this on the bus. > > > > Running a kernel with SCSIDEBUG will produce more information on the > > negotiation/discovery interactions. > > Clarification of "bunch of nvme drives" and a complete dmesg would > > also help. > > > > If it would help, I could screenshot one page at a time, that seems to be > the best I can do today.
Works for me, though I don't recommend sending all those pics to bugs@. > > -- > May the most significant bit of your life be positive. The other random thing to try is to find the line sc->sc_link.adapter_buswidth = sc->sc_nn + 1; in /usr/src/sys/dev/ic/nvme.c and replace the "sc->sc_nn + 1" with 1 or 2. Perhaps the nvme controller is returning interesting values for the namespace count in the identify message. I see there is already some weird code to deal with Apple oddities. :-) .... Ken
