From: TeJun Huh <tejun@aratech.co.kr>
To: Ville Herva <vherva@niksula.cs.hut.fi>,
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 10:13:41 +0900 [thread overview]
Message-ID: <20030828011341.GA19622@atj.dyndns.org> (raw)
In-Reply-To: <20030827073758.GW83336@niksula.cs.hut.fi>
On Wed, Aug 27, 2003 at 10:37:58AM +0300, Ville Herva wrote:
> On Wed, Aug 27, 2003 at 09:21:39AM +0200, you [Stephan von Krawczynski] wrote:
> >
> > Sorry, then you have to look for another explanation.
>
> Yep, but I don't have any reasonable suspects.
>
> > Did you already try to exchange everything but the harddisks ?
>
> No. Do you suspect faulty hardware?
>
> Apart from perhaps Adaptec 2940 (Adaptecs always give me trouble), I
> believe the hw is pretty solid. It had no problems with 2.2 kernels. Based
> on my experience, the i815 chipset is not that shaky (unlike the Via dung),
> and I would expect the Intel motherboard to be on the better side as well.
>
> I can't completely rule faulty hw out, though.
>
> Exchanging hw will be quite difficult, as the hangs take as much as three
> weeks to trigger (sometimes they happen withing a day after reboot), the box
> is a production server, and I don't have much spare hardware atm.
>
> What I had hoped for is to be able to get some information on where it hangs.
> But sysrq and nmi watchdog don't cut it...
>
Hello Ville. Hello Stephan. :-)
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.
ChangeSet@1.1019.1.7, 2003-07-24 14:21:29-03:00, marcelo@freak.distro.conectiva
Changed EXTRAVERSION to -pre8
TAG: v2.4.22-pre8
ChangeSet@1.1019.3.10, 2003-07-28 17:25:49-07:00, olof@austin.ibm.com
[RANDOM]: Fix SMP deadlock in __check_and_rekey().
This problem can happen on UP machine if the kernel is 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.
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.
--
tejun
next prev parent reply other threads:[~2003-08-28 1:11 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 [this message]
2003-08-28 5:40 ` Ville Herva
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=20030828011341.GA19622@atj.dyndns.org \
--to=tejun@aratech.co.kr \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=vherva@niksula.cs.hut.fi \
/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
all inboxes | Powered by JetHome®