RE: mysterious 2.0.33 crashes

Thomas Schenk (tschenk@dejanews.com)
Tue, 17 Feb 1998 17:11:06 -0600 (CST)


On 17-Feb-98 Ken Jordan wrote:
>
>
> On Mon, 16 Feb 1998, Alfredo Sanjuan wrote:
>
>>
>> >FWIW (as I already told in another mail): I'm having the same type
>> >of problems on a system that happened to run for years without any
>> >unexpected crashes with 1.2.13. After upgrading to 2.0.32/33 (and
>> >with a complete new distribution, not based on glibc), the system
>> >mysteriously halts 1 or 2 times a week without _any_ message.
>>
>>
>> With kernel 2.0.29 my machine got an uptime of 80 days with no problems at
>> all.
>> Since I upgrade to
>> 2.0.3[0,1,2,3] I'm getting several Oops every day, several processes in D
>> state,
>> several zombies... :-(
>>
> I have to chime in also, 2.0.33 seems like it has some bad problem(s). I
> have on average a mysterious crash, panic or oops, "D" state in net apps
> every day or so. At first I though it might be hardware related so I
> switched from a 486-133 to a Pentium-133 but the same types of problems
> persist (and I have ran diagnostics on both systems and can find no real
> hardware problem). These same systems ran 2.0.29 with unbounded uptimes
> (I had been using the 486-133 for well over a year as a 24/7 server).
>
>
> I am running RH 4.2+updates with stock 2.0.33. More details available
> upon request.
>

I had a problem with processes stuck in "D" state and multiple zombies
using RedHat 4.2 with stock 2.0.33 until I disabled the automount daemon,
amd. Once I got rid of that, my problem went away.

Tom

---
+-----------------------+-------------------------+------------------------+
| Tom Schenk            | Use Linux!              | All opinions expressed |
| tschenk@dejanews.com  |    Friends don't let    | are mine and not those |
| tschenk@theoffice.net |     friends do Windows! | of my employer.        |
+-----------------------+-------------------------+------------------------+

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu