Date: Sat, 6 Nov 2004 23:49:14 -0800 (PST)
From: Chris Stromsoe <cbs@cts.ucla.edu>
To: Chuck Ebbert <76306.1226@compuserve.com>
cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: deadlock with 2.6.9
In-Reply-To: <200411070058_MC3-1-8E27-AAEF@compuserve.com>
Message-ID: <Pine.LNX.4.61.0411062342400.29373@potato.cts.ucla.edu>
References: <200411070058_MC3-1-8E27-AAEF@compuserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1306
Lines: 37

On Sun, 7 Nov 2004, Chuck Ebbert wrote:

> Chris Stromsoe wrote:
>
>> I had a third lockup, this time not related to burning a dvd.  As 
>> before, the bulk of the processes that were hung were cron
>
> Why so many cron processes?  Is this normal on your system, or does it 
> look like cron keeps spawning processes because it gets no response on 
> the sockets?

I'm guessing so many processes because every time one gets started, it 
ends up getting stuck in schedule_timeout(), until the system stops 
spawning new processes.  There are many of them because the system was 
running for a day or so before it became unresponsive.

>> The box is P3 SMP
>
> Can you try a uniprocessor kernel?

Boot with nosmp or boot a kernel compiled for up?

>> syslog logs to a stripe of two mirrors, built with mdadm.
>
> Get a real RAID controller (3Ware, not some crappy pseudo-RAID junk.) 
> They are much more reliable than software RAID.

I've had more problems with reliable hardware raid controllers than I have 
with software raid.  Your mileage may vary.


-Chris
-
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/