Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

2.4.18 highmem smp freeze

1 view
Skip to first unread message

Thomas Michael Wanka

unread,
Mar 31, 2002, 8:10:07 PM3/31/02
to
Hi,

here are some people (including me) with smp and more than 1GB Ram
(most Serverworks chipsets, have not jet seen it with AMDs MPX) where
after some time (from hours to weeks probably load dependent) it
seems there is nothing written to disk anymore and in the end the
system completely freezes. This with several 2.4.x kernels (2.4.4,
2.4.10, 2.4.16, 2.4.17 and 2.4.18).

I think this has been discussed here, but I am too stupid to
understand it and/or find the solution.

I browsed the archives of the last year, and I think it was suggested
to use 2.4.17rc2aa1 or aa2. Is this correct and will it solve the
problem (IIRC there was no success message)? Will the later 2.2
kernels show this behavior too (like 2.2.20)?

Thank you in advance and please cc me,

Thomas Michael Wanka
1080 Vienna, Austria
Please treat my personal data confidential

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Marcelo Tosatti

unread,
Apr 1, 2002, 7:30:07 PM4/1/02
to

On Mon, 1 Apr 2002, Thomas Michael Wanka wrote:

> Hi,
>
> here are some people (including me) with smp and more than 1GB Ram
> (most Serverworks chipsets, have not jet seen it with AMDs MPX) where
> after some time (from hours to weeks probably load dependent) it
> seems there is nothing written to disk anymore and in the end the
> system completely freezes. This with several 2.4.x kernels (2.4.4,
> 2.4.10, 2.4.16, 2.4.17 and 2.4.18).
>
> I think this has been discussed here, but I am too stupid to
> understand it and/or find the solution.
>
> I browsed the archives of the last year, and I think it was suggested
> to use 2.4.17rc2aa1 or aa2. Is this correct and will it solve the
> problem (IIRC there was no success message)? Will the later 2.2
> kernels show this behavior too (like 2.2.20)?

The ServerWorks chipsets are problematic. Use the "noapic" boot option.

0 new messages