On Wed, 21 Apr 1999, Gavin M. Roy wrote:
> Am running a Dual PII-300MHz 256mem Webserver in production. This box gets
> over 2M hits a day. Base installation was Slackware (3.5 I presume). Runs
> great on 2.0.35, except it locks when the kernel is compiled with SMP
> enabled. I can compile 2.0.36, it error's out in main.c. I can compile any
Can you describe the system configuration in more detail? Which network
device(s) are you running for example? Are there other cards on the
bus? What kind of disk interface are you using? Which
motherboard/memory/chipset?
The lockup problem in 2.0.35 sounds like either a device problem or a
memory problem, but I thought that the latter was more or less fixed in
2.0.36. I'm not sure what problem you are describing in 2.0.36 -- do
you get a clean configure and make, do an install, and then lockup on
boot (UP or SMP)? Or is there some sort of compile/link error?
Finally, how do you handle devices? Built in devices will automatically
"become" SMP when you recompile SMP, but modules compiled for UP will
either not work or break when run SMP.
> 2.2.x kernel, and was running 2.2.6 since Sunday. But like the 2.2.x
> kernels before it, Apache starts acting really funky. The number of
> processes increase, and it stops accepting connections. Not too good for a
> webserver that does 550K to 600K uniques a day. :( Any suggestions or
> information I could provide for better resolution that running 2.0.35 on one
> cpu?
I cannot help you here, but somebody probably can. I do think that if
you work out how to make 2.0.36 run SMP perfectly on your system first
(or at least identify just where it is failing), that you'll have better
luck with 2.2.x.
rgb
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:[EMAIL PROTECTED]
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
