From: Cliff Albert <cliff@oisec.net>
To: "Oleg A. Yurlov" <kris@spylog.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.11aa1 and AIC7XXX
Date: Thu, 11 Oct 2001 16:31:05 +0200 [thread overview]
Message-ID: <20011011163105.A18508@oisec.net> (raw)
In-Reply-To: <13522687985.20011011173954@spylog.com>
In-Reply-To: <13522687985.20011011173954@spylog.com>
On Thu, Oct 11, 2001 at 05:39:54PM +0400, Oleg A. Yurlov wrote:
> Oct 10 20:35:31 samson kernel: (scsi0:A:2:0): Locking max tag count at 128
> Oct 10 21:06:31 samson kernel: (scsi1:A:0:0): Locking max tag count at 64
> Oct 11 05:33:09 samson kernel: (scsi0:A:3:0): Locking max tag count at 128
>
> Hardware - SMP 2 CPU, 1GB RAM, M/B Intel L440GX, 5 SCSI HDD, Software
> RAID5 (3 disks) and RAID1.
>
> I found in dmesg:
>
> *** Possibly defective BIOS detected (irqtable)
> *** Many BIOSes matching this signature have incorrect IRQ routing tables.
> *** If you see IRQ problems, in paticular SCSI resets and hangs at boot
> *** contact your vendor and ask about updates.
> *** Building an SMP kernel may evade the bug some of the time.
> Starting kswapd
>
> It's normal or not ? What I can do to fix problem with locking max tag
> count ?
Looks normal, it's that the new aic7xxx driver utilizes a maximum tag queue depth of 255 tags. Your devices are supporting only a maximum tag count of 128, 64 and 128 so it's perfectly normal. Also these 'error' messages should only appear once and no more (until a reboot)
--
Cliff Albert | RIPE: CA3348-RIPE | www.oisec.net
cliff@oisec.net | 6BONE: CA2-6BONE | icq 18461740
next prev parent reply other threads:[~2001-10-11 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 13:39 2.4.11aa1 and AIC7XXX Oleg A. Yurlov
2001-10-11 14:31 ` Cliff Albert [this message]
2001-10-11 15:20 ` Re[2]: " Oleg A. Yurlov
2001-10-11 16:47 ` Andrea Arcangeli
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=20011011163105.A18508@oisec.net \
--to=cliff@oisec.net \
--cc=kris@spylog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox