> "Bart" == Bart Van Assche writes:
Bart> On Mon, 2018-01-29 at 16:44 -0500, Mike Snitzer wrote:
>> But regardless of which wins the race, the queue will have been run.
>> Which is all we care about right?
Bart> Running the queue is not sufficient. With this patch
Hi,
I've got an LSI MPT2SAS controller in my home system, great board,
running well. When I try to use kernels newer than approximately
4.3.0, the default Kconfig entry goes away because of what looks like
a merge of the mpt2sas and mpt3sas drivers.
In my hand made 4.2.6 config I have:
>>>>> "Martin" == Martin K Petersen <martin.peter...@oracle.com> writes:
>>>>> "John" == John Stoffel <j...@stoffel.org> writes:
John> I've got an LSI MPT2SAS controller in my home system, great board,
John> running w
Andrew == Andrew Morton [EMAIL PROTECTED] writes:
Andrew On Mon, 17 Dec 2007 11:25:51 +0900 FUJITA Tomonori [EMAIL PROTECTED]
wrote:
On Sun, 16 Dec 2007 20:05:51 -0500
John Stoffel [EMAIL PROTECTED] wrote:
[ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128
SBCL=ae
Andrew == Andrew Morton [EMAIL PROTECTED] writes:
Andrew On Mon, 17 Dec 2007 11:25:51 +0900 FUJITA Tomonori [EMAIL PROTECTED]
wrote:
On Sun, 16 Dec 2007 20:05:51 -0500
John Stoffel [EMAIL PROTECTED] wrote:
[ 273.382057] sd 12:0:0:3: Attached scsi generic sg13 type 0
[ 276.244872
Just to confirm, the propsed patch to st.c fixes the issue with
2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access to my DLT tape
drives.
Thanks!
John
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
James == James Bottomley [EMAIL PROTECTED] writes:
James On Mon, 2007-12-17 at 13:43 -0800, Andrew Morton wrote:
On Mon, 17 Dec 2007 16:02:02 -0500
John Stoffel [EMAIL PROTECTED] wrote:
Just to confirm, the propsed patch to st.c fixes the issue with
2.6.24-rc5 as well at 2.6.24-rc5
Hi,
This looks to be a regression between 2.6.23 and 2.6.24-rc5, I'll try
to bi-sect this and report more on it. Basically, when I bootup, I
get a ton of errors in the dmesg log along the lines of:
[ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
[ 215.008145]
John Just fired up 2.6.24-rc5-mm1 on a Dual CPU PIII 550mhz system
John with 2gb of RAM. Got the following error. Let me know if you
John need more details or want me to run tests or make changes.
John Looks like something in the SCSI st driver, which makes sense
John since I have a pair of DLT
Hi,
Just fired up 2.6.24-rc5-mm1 on a Dual CPU PIII 550mhz system with 2gb
of RAM. Got the following error. Let me know if you need more
details or want me to run tests or make changes. Looks like something
in the SCSI st driver, which makes sense since I have a pair of DLT 7k
drives hooked
Jens A repost of this patchset, which adds support forchaining of sg
Jens tables. This enables much larger IO commands, since we don't
Jens have to allocate large consecutive pieces of memory to represent
Jens the sgtable of a huge command. Right now Linux is limited to
Jens somewhere between
Hi James,
As a test, I dropped back to 2.6.12.1 and the drive hung again last
night while trying to do backups, so I suspect that I might have
controller or tape drive problems of some sort. I'll also try to go
back to 2.6.12-rc6 as well and see how that works out.
My next step is to try and
James Well, I suspect the tape is hanging the bus, from which no card
James can recover.
Blech, not going to be fun to fix this sucker.
James Just to test this, can you try sending a bus reset with sgutils (from
James the debain package sg3-utils):
James sg_reset -b /dev/sg3
James Then remove
Hi James,
Dropped back to 2.6.11.1 and it hung again. I was able to get the
drive back by power cycling it and then doing the scsiadd to drop and
re-add the drive. I then used the bacula 'btape' tool to run some
tests. It seems to be just fine with regular files, but when it hit
EOM, all hell
Hi Linus James,
I've still got problems under 2.6.13-rc6 with my DLT7000 drive on an
AIC7880 builtin controller. Here's the message I got in dmesg. My
system is a heavily upgraded Debian/unstable with dual 550mhz Xeon
processors and 768mb of RAM, dual SCSI busses. The annoying problem
is
James == James Bottomley [EMAIL PROTECTED] writes:
Thank you for looking into this with me, I really appreciate it. I'm
kinda stumped why this suddenly started happening, but it could be
hardware related of course...
James So basically the problem is on scsi1 with the tape device, which
James
16 matches
Mail list logo