From: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
Date: Wed, 2 Jul 2003 18:00:12 -0300 [thread overview]
Message-ID: <01b101c340dc$ede386c0$3300a8c0@Slepetys> (raw)
In-Reply-To: 1083830000.1057158848@aslan.scsiguy.com
Hi,
I upgraded it for the 6.2.36, using RPM and I am making some heavy tests.
Until now, it's ok, and for this kind of tests, the old configuration gave
some trouble.
Thanks
Slepetys
----- Original Message -----
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>;
<linux-kernel@vger.kernel.org>
Sent: Wednesday, July 02, 2003 12:14 PM
Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
> > The system halts easily if I do a large I/O, like reindexing a database,
> > giving me some messages like: (scsi0:A:1:0): Locking max tag count at
128...
>
> The "Locking max tag count" messages are normal. It means the SCSI
> driver was able to determine the maximum queue depth of your drive.
>
> 6.2.8 is rather old. I don't know that upgrading the aic7xxx driver
> will solve your problem, but it might be worth a shot. The latest
> is available here:
>
> http://people.FreeBSD.org/~gibbs/linux/SRC/
>
> After upgrading, you should be at 6.2.36.
>
> --
> Justin
>
> -
> 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/
>
next prev parent reply other threads:[~2003-07-02 20:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 14:44 Probably 2.4 kernel or AIC7xxx module trouble Roberto Slepetys Ferreira
2003-07-02 15:14 ` Justin T. Gibbs
2003-07-02 21:00 ` Roberto Slepetys Ferreira [this message]
2003-07-03 18:29 ` Roberto Slepetys Ferreira
[not found] ` <13e101c3419d$f62f9410$3400a8c0@W2RZ8L4S02>
2003-07-03 20:15 ` Roberto Slepetys Ferreira
2003-07-03 21:20 ` Justin T. Gibbs
2003-07-03 23:04 ` Jim Gifford
2003-07-05 20:15 ` Justin T. Gibbs
2003-07-05 20:28 ` Jim Gifford
2003-07-03 22:49 ` Matthias Andree
2003-07-03 23:09 ` Jim Gifford
[not found] <4R5X.8bo.19@gated-at.bofh.it>
[not found] ` <4Rzh.h8.25@gated-at.bofh.it>
[not found] ` <4WSg.5H7.21@gated-at.bofh.it>
[not found] ` <5h0y.5ht.25@gated-at.bofh.it>
[not found] ` <5iIR.7Cp.11@gated-at.bofh.it>
[not found] ` <5iIQ.7Cp.9@gated-at.bofh.it>
[not found] ` <5jOA.14o.9@gated-at.bofh.it>
[not found] ` <5lnu.2l7.13@gated-at.bofh.it>
2003-07-04 17:36 ` Roberto Slepetys Ferreira
2003-07-05 20:27 ` Justin T. Gibbs
[not found] ` <5ldB.2cK.1@gated-at.bofh.it>
2003-07-04 17:38 ` Roberto Slepetys Ferreira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01b101c340dc$ede386c0$3300a8c0@Slepetys' \
--to=slepetys@homeworks.com.br \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.