Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
Subject: Bug: SCSI driver hangs in 2.6.6 and 2.6.7
To: linux-kernel@vger.kernel.org
Date: Wed, 16 Jun 2004 17:28:02 -0500
From: "Kai OM" <epimetreus@fastmail.fm>
Message-Id: <1087424882.30041.198581042@webmail.messagingengine.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2034
Lines: 44

It looks like there is some kind of bug in sym 2.1.18j that
prevents booting on some SCSI controllers.

I've tested my SCSI controller (LSIU160) against 2.6.7 and 2.6.6, and
both are proneto this bug. All kernel versions prior to this work
perfectly, as does Windows. The hard drive on that controller is a
Quantum ATLAS10K2-TY734J, in case it's pertinent.

I have no clue what the issue is, precisely, or if there's some obscure
bug in the firmware I'm using(LSI Logic's 4.19 - the latest version I
was able to find). Some Googling returned no results, so I have to
assume otherwise.

[PATCH] sym 2.1.18j sym 2.1.18j: 
- Add SPI
transport attributes (James Bottomley) 
- Use generic code to do Domain Validation (James Bottomley) 
- Stop using scsi_to_pci_dma_dir() (Christoph Hellwig) 
- Change some constants to their symbolic names (Grant Grundler) 
- Handle a race between a postponed command completing and the EH
retrying it (James Bottomley)
- If the auto request sense fails, issue a device reset (James
Bottomley) 

I'm not any fool's expert on SCSI, nor coding, so I can't really guess
what changes that weremade are the culprit, and since I don't know where
to get a copy of the patch that was submitted, I can't try reversing the
changes it made. If someone wants to link me to this patch, I'd be
interested to try that and see if it has any effect. 

I've already posted about this once, but I suspect it might have looked
a little like begging for "tech support", instead of reporting an actual
bug to some people, so I am guessing it was largely ignored. 

Anyway, I'd really like to, you know, use kernel versions after 2.6.5,
because that would rather severely
limit my ability to stay up-to-date in the Linux world after awhile.

 Thanks for any consideration this gets.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/