RE: Problems running Tux w/ 2.4.19 generic

[joshua.schnee@amd.com]

Currently the server will either hard lock (not respond to anything, keyboard or network), or it will drop all of the tux threads, which leaves it responsive to keyboard and pinging, but without the web server running to respond to requests.  When asked the tux status, it replies something like "Tux is dead, but subsys is active", or close to it.

Thanks again, Joshua

-----Original Message-----
From: Alex Kramarov [mailto:alex@incredimail.com]
Sent: Friday, January 10, 2003 4:20 PM
To: tux-list@redhat.com
Subject: Re: Problems running Tux w/ 2.4.19 generic


logging in general causes hangs of the server at high load - i have wrote
about this to the list. generally, it's freely reproducible by applying high
io load on the machine during high load on the tux server . it have never
been described as "tux drops threads" though, since people had this on
remote servers only, and noone had been present at the console to see what
is going on - the server was simply rebooted to solve the problem. could you
provide detailed info about the state of the server after the freese (it
will not help to solve the problem at the moment, but is still useful)

Alex.

----- Original Message -----
From: <joshua.schnee@amd.com>
To: <tux-list@redhat.com>
Sent: Friday, January 10, 2003 10:34 PM
Subject: RE: Problems running Tux w/ 2.4.19 generic


> Thanks for the help,
>
> This did in fact stop the hunks from failing when patching the generic
2.4.19 kernel.  However, I am still seeing Tux drop threads for no reason
that I can see.
>
> Has anyone had a problem with Tux dropping threads, and such, no longer
responding to requests?
>
>
>
> -----Original Message-----
> From: Shane Allen [mailto:shane@sell.com]
> Sent: Thursday, January 09, 2003 1:37 PM
> To: tux-list@redhat.com
> Subject: Re: Problems running Tux w/ 2.4.19 generic
>
>
> On Thu, Jan 09, 2003 at 08:49:54AM -0600, joshua.schnee@amd.com wrote:
> > Thank you for responding,
> >
> > I am unaware of any patch that has been ported to 2.4.19.  Is there a
ported patch available somewhere?
>
> I thought someone had made one...
>
> > Yes I had several hunks fail, but as this is not my area of expertise, I
am unable to create a work around.
>
> Then that is likely the source of your problem...
>
> > Only Logging, and redirect_logging are enabled, from reading past
archive messages I had thought that referer_logging was causing the errors.
Should I disable all logging?
>
> I wouldn't worry about it at this point, hunks failing is in my best
> guess the source of the problem. Check the archives for the link to my
> patch against 2.4.21-pre2. Download and unpack it, and change the
following:
> -at line 1674, delete the three lines reading:
>  EXPORT_SYMBOL(yield);
>  EXPORT_SYMBOL(__cond_resched);
>  EXPORT_SYMBOL(jiffies);
> and add three lines reading:
>  EXPORT_SYMBOL(sys_sched_yield);
>  EXPORT_SYMBOL(jiffies);
>  EXPORT_SYMBOL(xtime);
>
> Then run the modified patch against vanilla 2.4.19. It should patch
> without any hunks failing.
>
> The previous suggestion of 2.4.19-aa may work, I have not tried it
> myself, and do not run SuSE, so I cannot say.
>
> --
> Shane Allen <shane@sell.com>
>
>
>
> _______________________________________________
> 
> tux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/tux-list
>
>
>
> _______________________________________________
> 
> tux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/tux-list
>



_______________________________________________

tux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/tux-list