Date: Thu, 04 Jun 1998 11:34:51 -0600 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: Mark Murray <mark@grondar.za> Cc: gibbs@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Error: "Timedout SCB handled by another timeout" Message-ID: <199806041739.LAA06499@pluto.plutotech.com> In-Reply-To: Your message of "Wed, 03 Jun 1998 08:38:53 %2B0200." <199806030638.IAA00337@greenpeace.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
>Hi > >I am still getting the error "Timedout SCB handled by another timeout", >which only happens in SMP mode. I ran for 8 days in UP mode, and the >machine was rock-steady. Can you change that printf into a panic and poke around the timeout code when it occurs. You'll probably want to have remote GDB setup for this. I really think that the problem has little to do with CAM, but is some kind of race in the processing of clock interrupts that causes the timeout queues to become corrupted. Just going up the stack should bring you into the generic timeout facility code and hopefully something will be obviously corrupted. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806041739.LAA06499>