Date: Thu, 1 Jun 2017 10:29:34 -0500 From: Scott Long <scottl@samsco.org> To: Stephen Mcconnell <stephen.mcconnell@broadcom.com> Cc: Harry Schmalzbauer <freebsd@omnilan.de>, freebsd-scsi@freebsd.org, Scott Long <scottl@freebsd.org> Subject: Re: mps(4) blocks panic-reboot Message-ID: <DC12C54A-5DD6-4C02-96CC-83728E2D5479@samsco.org> In-Reply-To: <ff9342e2e1eb541f347d9f683cfc8214@mail.gmail.com> References: <592FDE8C.1090609@omnilan.de> <ff9342e2e1eb541f347d9f683cfc8214@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Good summary Steve, I forgot about this. I'm traveling today, but if I have= time tonight I'll see if I still have any notes or patches. Scott Sent from my iPhone > On Jun 1, 2017, at 10:25 AM, Stephen Mcconnell <stephen.mcconnell@broadcom= .com> wrote: >=20 > I found a couple of emails between me and Scott a while back and we talked= > about this. The problem is that the SSU handling relies on interrupts, but= > interrupts stop due to the panic, so it hangs. Scott came up with a way > around it but we never decided on a final fix and then it was forgotten > about. If you have a way to reproduce this, I can try to find a fix here. > Or, I might be able to force the system to panic at the right time. >=20 > Steve >=20 >> -----Original Message----- >> From: Stephen Mcconnell [mailto:stephen.mcconnell@broadcom.com] >> Sent: Thursday, June 01, 2017 8:51 AM >> To: 'Harry Schmalzbauer'; 'freebsd-scsi@freebsd.org'; 'Scott Long' >> Subject: RE: mps(4) blocks panic-reboot >>=20 >> Scott, did you have a fix for this some time back? >>=20 >> Steve >>=20 >>> -----Original Message----- >>> From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- >>> scsi@freebsd.org] On Behalf Of Harry Schmalzbauer >>> Sent: Thursday, June 01, 2017 3:30 AM >>> To: freebsd-scsi@freebsd.org >>> Subject: mps(4) blocks panic-reboot >>>=20 >>> Hello, >>>=20 >>> I'm not sure if scsi@ is the correct list, but since my problem seems >>> to be mps(4) related, I thought asking here shouldn't be too wrong. >>>=20 >>> There's not much to add to the topic: If my stable/11 setup panics, >>> the system doesn't reboot (besides IPMI-watchdog takes over this > task). >>> The machine stucks with these last lines: >>> Dumping 1669 out of 15734 >>> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% >>> Dump complete >>> mps0: Sending StopUnit: path (xpt0:mps0:0:2:ffffffff): handle 12 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:3:ffffffff): handle 11 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:4:ffffffff): handle 10 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:5:ffffffff): handle 9 >>> mps0: Incrementing SSU count >>> mps0: Sending StopUnit: path (xpt0:mps0:0:6:ffffffff): handle 13 >>> mps0: Incrementing SSU count >>>=20 >>> Then, nothing happens. On a similar setup without mps(4), the machine >>> reboots after the panic. >>>=20 >>> Is this a known problem/feature? >>>=20 >>> Thanks, >>>=20 >>> -harry >>> _______________________________________________ >>> freebsd-scsi@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi >>> To unsubscribe, send any mail to > "freebsd-scsi-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DC12C54A-5DD6-4C02-96CC-83728E2D5479>