From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from HansenPartnership.com (adsl-64-109-89-108.dsl.chcgil.ameritech.net [64.109.89.108]) by dsl2.external.hp.com (Postfix) with ESMTP id 0367A4831 for ; Wed, 10 Sep 2003 09:45:28 -0600 (MDT) Subject: Re: [parisc-linux] HP B132L hangs From: James Bottomley To: Sebastian Brueckner Cc: debian-hppa@lists.debian.org, parisc-linux@parisc-linux.org In-Reply-To: <3F5F24D9.7030800@epost.de> References: <3F5F24D9.7030800@epost.de> Content-Type: text/plain Date: 10 Sep 2003 11:45:09 -0400 Message-Id: <1063208722.1984.10.camel@mulgrave> Mime-Version: 1.0 Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: On Wed, 2003-09-10 at 09:19, Sebastian Brueckner wrote: > scsi0: (2:0) Synchronous at offset 8, period 100ns > scsi0: (2:0), UNEXPECTED PHASE after command phase (CD BSY REQ CMD_OUT) > len = 6, cmd =Read (10) 00 00 35 e2 00 00 00 18 00 That's a residue of an incorrect lasi700 driver. Notice it thinks the length is six for a ten byte command. This has long been fixed in the linux-2.4 PA tree (er, I think---I've been concentrating on 2.6 mainly). However, something higher up in the trace you don't attach caused the actual problem that this is a response to (It's caused by the SCSI mid layer putting the wrong command length back *after* error recovery, so your true root cause is the error that first started this). James