From: Ville Herva <vherva@niksula.hut.fi>
To: TeJun Huh <tejun@aratech.co.kr>
Cc: Stephan von Krawczynski <skraw@ithnet.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22pre8 hangs too (Re: 2.4.21-jam1 solid hangs)
Date: Thu, 28 Aug 2003 08:40:00 +0300 [thread overview]
Message-ID: <20030828053959.GA83336@niksula.cs.hut.fi> (raw)
In-Reply-To: <20030828011341.GA19622@atj.dyndns.org>
On Thu, Aug 28, 2003 at 10:13:41AM +0900, you [TeJun Huh] wrote:
>
> Your problem sounds very simlar to the problem we were suffering.
> The problem was a spinlock deadlock inside drivers/char/random.c which
> is used by tcp to generate random initial sequence number. The bug
> fix was checked into 2.4 tree on 28th July after the release of pre8
> at 14th July.
Uhh, I tried 2.4.22pre8 a while ago (I think it was Herbert Pötzl's
suggestion), and it locked up too. Shame that the fix didn't make it in
it...
I'll give .22-final a spin.
> This problem can happen on UP machine if the kernel is compiled with
> CONFIG_SMP.
This is UP box and the kernel is _not_ compiled with CONFIG_SMP.
> Because the offending routine is called only every five
> minutes and it should receive a SYN packet while it's connecting, it
> occurs rarely, but it happens when it happens.
In my case, the lock up seems clearly related to disk io: it usually happens
during the nightly oracle backup dump, and at some point it kept happening
while compiling kernel. (It's random, I can no longer reproduce it by just
compiling a kernel.)
Do you still think it could be the same one?
> Please try 2.4.22.
>
> P.S. This bug is a real headache. We had many servers deployed and
> they all randomly locked up about every two or four weeks. I believe
> people should be warned about this one.
What's really strange is that the box kept running with 2.4.20pre7 for
almost a year without problems (with the same oracle dump jub in nightly
cron), and then suddenly begun acting up on my the first day of my summer
vacation...
-- v --
v@iki.fi
next prev parent reply other threads:[~2003-08-28 5:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 7:39 2.4.21-jam1, aic7xxx-6.2.36: solid hangs, crashes on boot Ville Herva
2003-07-30 7:13 ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1, aic7xxx-6.2.36: solid hangs) Ville Herva
2003-07-30 14:50 ` Marcelo Tosatti
2003-07-30 18:10 ` Ville Herva
2003-08-08 12:55 ` Ville Herva
2003-08-09 20:19 ` Adrian Bunk
2003-08-09 22:15 ` Ville Herva
2003-08-27 6:43 ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1 " Ville Herva
2003-08-27 7:03 ` Stephan von Krawczynski
2003-08-27 7:12 ` Ville Herva
2003-08-27 7:21 ` Stephan von Krawczynski
2003-08-27 7:37 ` Ville Herva
2003-08-27 9:30 ` Stephan von Krawczynski
2003-08-27 10:13 ` Ville Herva
2003-08-27 10:56 ` Stephan von Krawczynski
2003-08-27 11:04 ` Ville Herva
2003-08-27 11:30 ` Stephan von Krawczynski
2003-08-28 9:26 ` Ingo Oeser
2003-08-28 19:09 ` Ville Herva
2003-08-28 1:13 ` TeJun Huh
2003-08-28 5:40 ` Ville Herva [this message]
2003-08-28 5:57 ` Tejun Huh
2003-08-27 23:22 Marcelo Tosatti
2003-08-28 6:10 ` Ville Herva
2003-08-29 16:35 Marcelo Tosatti
2003-08-29 19:57 ` Ville Herva
2003-09-09 7:05 ` Ville Herva
2003-09-09 8:48 ` Stephan von Krawczynski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030828053959.GA83336@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=tejun@aratech.co.kr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).