linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: Christoph Hellwig <hch@infradead.org>,
	sal@agora.pl, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18/2.4.20 filemap.c pmd bug (was Re: Problem with mm in 2.4.19 and 2.4.20)
Date: Mon, 11 Aug 2003 12:21:01 +0200	[thread overview]
Message-ID: <20030811102101.GG8953@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030811104823.A15144@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hi Christian.  First of all, thanks for your quick reply.

On Mon, Aug 11, 2003 at 10:48:23AM +0100, Christoph Hellwig wrote:
 
> Well, qlogic + lvm is vert prone of stack overflows.  

In my case, we use neither of them.

> You're using aic7xxx I assume?  

yes.  The device is reported as

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
        <Adaptec aic7890/91 Ultra2 SCSI adapter>
        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs


> Some other interesting drivers?

Well, there's a tulip based network board and one symbios SCSI controller
(ncr53c8xx driver) in the system.  But since the '(scsi0:A:9:0): Locking
max tag count at 64' message always indicates 'scsi0', I think it has to
do with aic7xxx.

-- 
- Harald Welte <laforge@gnumonks.org>               http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-08-11 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 12:16 Problem with mm in 2.4.19 and 2.4.20 Przemysław Maciuszko
2003-08-11  7:34 ` 2.4.18/2.4.20 filemap.c pmd bug (was Re: Problem with mm in 2.4.19 and 2.4.20) Harald Welte
2003-08-11  9:48   ` Christoph Hellwig
2003-08-11 10:21     ` Harald Welte [this message]

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=20030811102101.GG8953@sunbeam.de.gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sal@agora.pl \
    /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;
as well as URLs for NNTP newsgroup(s).