From: Jim Crilly <noth@noth.is.eleet.ca>
To: Rob Turk <r.turk@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AIC7xxx panic
Date: 07 Oct 2001 07:28:57 -0400 [thread overview]
Message-ID: <1002454137.284.6.camel@warblade> (raw)
In-Reply-To: <9ppc3l$cde$1@ncc1701.cistron.net>
In-Reply-To: <1002451051.3718.20.camel@warblade> <9ppc3l$cde$1@ncc1701.cistron.net>
Both disks on the controller are Seagate Cheetahs, the one being worked
during the panic is a ST39204LW, the other disk is a ST318451LW.
I did have TCQ enabled and I left it at the default of 255, I'll try a
lower value tomorrow, since it's so late.
Jim
On Sun, 2001-10-07 at 06:48, Rob Turk wrote:
> "Jim Crilly" <noth@noth.is.eleet.ca> wrote in message
> news:cistron.1002451051.3718.20.camel@warblade...
> > I got a reproducible panic while running dbench simulating 25+ clients,
> > the new aic7xxx driver panics with "Too few segs for dma mapping.
> > "Increase AHC_NSEG". The partition in question is FAT32 and on a
> > different disk than /, I'm not using HIGHMEM. I am using XFS and the
> > preempt patches, but I don't think they're related to the panic.
> >
> > The odd thing, is if I run dbench in the same manner on my / partition,
> > which is on a different disk on the same controller, it goes fine. It
> > seems, to my untrained eye anyway, to be a bad interaction between the
> > vfat driver and the aic7xxx driver.
> >
> > I'm using the old aic7xxx driver right now and it's fine, has anyone
> > else seen anything like this?
> >
> > Jim
>
> Since this seems to fail on just one disk, it might have to do with one of the
> disk characteristics, like command queue depth. Did you enable Tagged Command
> Queueing, and if so, can you try playing around with the maximum depth?
>
> Rob
>
>
>
>
> -
> 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/
--
Help protect your rights on-line.
Join the Electronic Frontiers Foundation today: http://www.eff.org/join
-----------------------------------------------------------------------
Security: Antonyms: See Microsoft
-----------------------------------------------------------------------
"We are coming after you. God may have mercy on you, but we won't,"
declared Sen. John McCain, R-Arizona.
next prev parent reply other threads:[~2001-10-07 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 10:37 AIC7xxx panic Jim Crilly
2001-10-07 10:48 ` Rob Turk
2001-10-07 11:28 ` Jim Crilly [this message]
2001-10-07 12:21 ` David M. Grimes
2001-10-07 14:48 ` Gérard Roudier
2001-10-08 2:31 ` Jim Crilly
2001-10-09 0:51 ` David M. Grimes
2001-10-09 11:47 ` Alan Cox
2001-10-09 2:21 ` Justin T. Gibbs
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=1002454137.284.6.camel@warblade \
--to=noth@noth.is.eleet.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=r.turk@chello.nl \
/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.