Date: Fri, 26 Jul 2013 22:01:21 +0000 From: Bob Bawn <Bob.Bawn@nirvanix.com> To: "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Re: Reset Problem with SATA Port Multiplier Message-ID: <94969AC586B81A4BBD2484F9862736A80CDAE9A2@CORPEX001.nirvanix.com> In-Reply-To: <mailman.73.1374580811.89468.freebsd-hardware@freebsd.org> References: <mailman.73.1374580811.89468.freebsd-hardware@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 25, 2013, Dieter BSD <dieterbsd@gmail.com> wrote: > Sounds like FreeBSD is doing something bad to the pm, which Linux isn't > doing. Perhaps log the commands the OS sends to the controller (over the > network to a 2nd machine, or to a local disk not on a pm) and compare > BSD to Linux? Perhaps start logging when you get the first timeout, to > save hours of commands to wade through. Yes, that occurred to me. I was hoping to avoid learning how to build kernels with debug messages but I suppose it's a good skill to have. :-) > Alternately you could stare at the driver sources until enlightenment > occurs. I did a little of this and superficially it does seem like there could be differences between FreeBSD and Linux in the treatment of the mysterious 6th port (SEMB) on the 5-port multiplier. Hopefully, the logging you suggest will clarify the situation. Thanks for your help.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94969AC586B81A4BBD2484F9862736A80CDAE9A2>