>When I upgraded to 2gigs of ram I was using 2.4.10 then used 2.4.14 and
>2.4.16 each did a kernel panic. however none do it with highmem off.
I am still investigating the cause of this particular problem. In
fact we are building up a new system today in the hope of being able
to reproduce and solve this problem.
>I've also had the error locking at making tag count 64( somebody in the
>archives said that it doing that is normal. I've had that problem for
>years it doesn't hurt anything so I ignore it. so why does it do that?)
Its an informational message, not an error. The system is telling
you that it has dynamically determined the maximum queue depth of
>I've read through the archives somebody posted the if they change the
>#define NSEG from 128 to 512 it goes away. it went away for me too when
>I did that and recomplied the kernel it went away for me too.
>I found this in aic7xxx_osm.h suggesting the 128 setting was only for
> * Number of SG segments we require. So long as the S/G segments for
> * a particular transaction are allocated in a physically contiguous
> * manner and are allocated below 4GB, the number of S/G segments is
> * unrestricted.
This is merely saying that the controller requires that the S/G list is
allocated below 4GB in the PCI bus address space (note that on some platforms
this may not mean the same thing as allocated within the first 4GB of
-- Justin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:18 EST