None of the other setups produce the "..could net get a free page.."
message. This looks like a subtle race condition with this particular scsi
driver. I will try some other scenarios.
Jeff
----- Original Message -----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Merkey <jmerkey@timpanogas.com>
Cc: <jmerkey@timpanogas.com>; <linux-kernel@vger.rutgers.edu>
Sent: Wednesday, June 09, 1999 5:32 PM
Subject: Re: Oops in 2.3.X, 2.2.X, and 2.0.3X with FENRIS and NCR53c875 SCSI
Driver
> > Also shows up single processor (different machine, same chipset 53C875).
=
> > Looks like a possible SCSI Scipts error. FENRIS, unlike UNIX FS's will
=
> > talk to more than one disk or partition concurrently since a volume can
=
> > have multiple segments strip[ed across several drives. May be exposing
=
> > some timing condition with the way I am calling breada abd bread.
>
> The raid code already does that kind of concurrency. Now the important
clue
> is probably
>
> > More on this -- am also getting "..could not get a free page...". =
>
> This indicates a memory allocation failed. That means its more likely
someone
> doesnt check a get_free_page/kmalloc return and continues blissfully into
> oblivion mode.
>
> Could be the driver fs or scsi layer. Are your other test setups producing
> a "free page.." message too ? (ie the working ones)
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/