Re: kern/52126 (mvsata Marvell 88SX6081 panics on boot)

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

The following reply was made to PR kern/52126; it has been noted by GNATS.

From: Patrick Welche <prlw1%cam.ac.uk@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/52126 (mvsata Marvell 88SX6081 panics on boot)
Date: Mon, 20 May 2019 10:45:39 +0100

 An update - in the meantime jdolecek-ncq was merged, and I'm sure I saw
 something about DMA...
 
 >  and then machine apparently hangs
 
 I still see the hang
 
 >  kernel with MVSATA_WITHOUTDMA etc.
 
 but don't need the MVSATA_WITHOUTDMA. No more panics!
 
 GENERIC 8.9941/amd64 kernel, with LOCKDEBUG, DIAGNOSTIC and KUBSAN,
 booted with -1 just in case (no difference in multiprocessor), and:
 
 cpu0: package 0, core 0, smt 0
 cpu1 at mainbus0 apid 1: multiprocessor boot disabled
 ...
 mvsata0 at pci5 dev 1 function 0: vendor 11ab product 6081 (rev. 0x09)
 mvsata0: interrupting at ioapic1 pin 1
 mvsata0: GenII, 2hc, 4port/hc
 atabus0 at mvsata0 channel 0
 atabus1 at mvsata0 channel 1
 ...
 mvsata0 port 0: device present, speed: 1.5Gb/s
 mvsata0 port 6: device present, speed: 1.5Gb/s
 ahcisata0 port 0: device present, speed: 1.5Gb/s
 ahcisata0 port 1: device present, speed: 1.5Gb/s
 wd0 at atabus0 drive 0
 wd0: <ST3200822AS>
 wd0: 186 GB, 387621 cyl, 16 head, 63 sec, 512 bytes/sect x 390721968 sectors
 mvsata0:0:0: lost interrupt
  type: ata tc_bcount: 16384 tc_skip: 0
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0), xfer 38, retry 0
 mvsata0:0:0: lost interrupt
  type: ata tc_bcount: 16384 tc_skip: 0
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0), xfer 38, retry 1
 ipmi0: ID 32.1 IPMI 2.0 Available
 mvsata0: channel 0: drive 0 not ready, st=0xd0, err=0x00
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0), xfer 38, retry 2
 mvsata0: channel 0: drive 0 not ready, st=0xd0, err=0x00
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0), xfer 38, retry 3
 mvsata0: channel 0: drive 0 not ready, st=0xd0, err=0x00
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0), xfer 38, retry 4
 mvsata0: channel 0: drive 0 not ready, st=0xd0, err=0x00
 wd0d: device timeout reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0)
 wd0d: error reading fsbn 0 of 0-31 (wd0 bn 0; cn 0 tn 0 sn 0)
 
 hang
 
 break into ddb:
 
 --- interrupt ---
 x86_stihlt() at netbsd:x86_stihlt+0x6
 acpicpu_cstate_idle_enter() at netbsd:acpicpu_cstate_idle_enter+0x18d
 acpicpu_cstate_idle() at netbsd:acpicpu_cstate_idle+0x1b3
 idle_loop() at netbsd:idle_loop+0x19a
 
 Lost in idle_loop?
 
 Extracts from ps:
 
 PID    LID S CPU     FLAGS       STRUCT LWP *               NAME WAIT
 0       65 3   0       204   ffffbddd0279f200         mvsata0cnf biowait
 0       21 3   0       204   ffffbddd0248b540            atabus0 atath
 0    >   2 7   0       201   ffffbddf4b803040             idle/0