Date: Tue, 5 Jul 2011 23:22:42 +0100 From: Anton Shterenlikht <mexas@bristol.ac.uk> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Matthew Jacob <mj@feral.com>, freebsd-current@freebsd.org, Anton Shterenlikht <mexas@bristol.ac.uk>, freebsd-ia64@freebsd.org Subject: Re: isp(4) timeout Message-ID: <20110705222242.GA27743@mech-cluster241.men.bris.ac.uk> In-Reply-To: <783405F6-2417-4E5B-B1F8-B8EC0113B73A@xcllnt.net> References: <20110630102544.GA97559@mech-cluster241.men.bris.ac.uk> <4E0C67EC.8020609@feral.com> <20110705083935.GA9094@mech-cluster241.men.bris.ac.uk> <783405F6-2417-4E5B-B1F8-B8EC0113B73A@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 05, 2011 at 08:13:02AM -0700, Marcel Moolenaar wrote: > > 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. updated to r223796 (no PREEMPTION in kernel). Had this hang on reboot: KDB: stack backtrace: getenv with the following non-sleepable locks held: exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe000000011587ce8) locked @ /usr/src/sys/fs/devfs/devfs_vnops.c:405 KDB: stack backtrace: getenv with the following non-sleepable locks held: exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe000000011587ce8) locked @ /usr/src/sys/fs/devfs/devfs_vnops.c:405 KDB: stack backtrace: (repeated lots of times) no panic, just hang. Had to reset power via MP. Seems fine after reboot. Anything else I should check? Many thanks Anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110705222242.GA27743>