Messages in this thread | | | From | Roger Larsson <> | Subject | Re: Errors in the VM - detailed (or is it Tux? or rmap? or those together...) | Date | Sat, 2 Feb 2002 16:31:59 +0100 |
| |
On Saturdayen den 2 February 2002 16.22, Roy Sigurd Karlsbakk wrote: > > > Problem #2 is _the_ worst problem, as it makes the server more-or-less > > > unusable > > > > Please send sysrq-t traces for such stuck processes. It's _impossible_ > > to guess whats going on from here, the crystal ball just isn't good > > enough :-) > > Decoded sysrq+t is attached. > > I've found only the first 60 wget processes started from the remote > machine is being serviced. After they are done, Tux hangs, using 100% > system time, still open on port ## (80), but doesn't do anything. > > I don't understand anything...
I have reread the first mail in this series - I would say that Bug#2 is much worse than Bug#1. This since Bug#1 is "only" a performance problem, but Bug#2 is about correctness...
Are you 100% sure that tux works with rmap?
I would suggest testing the simplest possible case. * Standard kernel * concurrent dd:s
What can your problem be: * something to do with the VM - but the problem is in several different VMs... * something to do with read ahead? you got some patch suggestions - please use them on a standard kernel, not rmap (for now...)
/RogerL
-- Roger Larsson Skellefteå Sweden - 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/
| |