Date: Tue, 5 Jul 2011 08:13:02 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-current@freebsd.org, Matthew Jacob <mj@feral.com>, freebsd-ia64@freebsd.org Subject: Re: isp(4) timeout Message-ID: <783405F6-2417-4E5B-B1F8-B8EC0113B73A@xcllnt.net> In-Reply-To: <20110705083935.GA9094@mech-cluster241.men.bris.ac.uk> References: <20110630102544.GA97559@mech-cluster241.men.bris.ac.uk> <4E0C67EC.8020609@feral.com> <20110705083935.GA9094@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 5, 2011, at 1:39 AM, Anton Shterenlikht wrote: > On Thu, Jun 30, 2011 at 05:11:24AM -0700, Matthew Jacob wrote: >> On 6/30/2011 3:25 AM, Anton Shterenlikht wrote: >>> I see in my logs: >>> >>> isp0: Polled Mailbox Command (0x54) Timeout (500000us) (started @ >>> isp_plogx:2122) >>> isp0: Mailbox Command 'EXECUTE IOCB A64' failed (TIMEOUT) >>> isp0: Chan 0 PLOGI 0x010500 failed >>> isp0: Polled Mailbox Command (0x64) Timeout (250000us) (started @ >>> isp_getpdb:2307) >>> isp0: Mailbox Command 'GET PORT DATABASE' failed (TIMEOUT) >> >> More details please. >> >> These errors indicate failures to execute commands that try and figure >> out what's on a fabric and then log into devices on the fabric. Knowing >> what hardware you have (QLogic card version), what FreeBSD release you >> are running, would help. A verbose dmesg would be useful. > > I got it again. But this time the network seems fine. If you haven't updated to the latest sources, please do so. If you did already, please make sure you don't have PREEMPTION configured. FYI, -- Marcel Moolenaar marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?783405F6-2417-4E5B-B1F8-B8EC0113B73A>