linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22pre8 hangs too (Re: 2.4.21-jam1 solid hangs)
Date: Thu, 28 Aug 2003 09:10:00 +0300	[thread overview]
Message-ID: <20030828061000.GG150921@niksula.cs.hut.fi> (raw)
In-Reply-To: <Pine.LNX.4.55L.0308272020461.23236@freak.distro.conectiva>

On Wed, Aug 27, 2003 at 08:22:07PM -0300, you [Marcelo Tosatti] wrote:
> 
> Ville,
> 
> Which kernel doesnt hang on your box? 2.4 something ? 

2.4.20pre7 ran for over 9 months before it suddenly begun locking up (I
_suppose_ it could just mean the bug/problem is hard to trigger.) Nothing
had been changed: the box had been up for that nine month period, and the
same oracle dump cron job had been running each night.

Earlier 2.4's had too many problems with aic7xxx (crashes and so on), so I
can't comment on them.

After 2.4.20pre7, I tried 2.4.21-jam1 (based on -aa patchset) and
2.4.22-pre8. I also tried compiling 2.4.21-jam1 with gcc-3.2.1 instead of
2.96. All of those locked up eventually, sometimes within a day from
reboot, some times it takes weeks. At one point, 2.4.21-jam1 seemed to
reliably lock up when compiling kernel, but it no longer happens no matter
how hard I try. Usually the lock up happens during nightly oracle backup
dump.

> 2.2?

2.2.22 and 2.2.22-secure1 never locked up, but I didn't run them for more
than a couple of months.

I realize I should try to change all pieces of hardware one at the time and
try various different kernels, but it all seem tedious and shooting in the
dark: the lock up can take weeks to trigger. I would love to get some kind
of lead or theory on what causes the problem before resorting to brute force
search.

I think I'll try 2.4.22-final + a kernel debugger next. Or is there a better
way of getting information on hard lock ups than kdb? (Tried nmi watchdog
and sysrq already).


-- v --

v@iki.fi

  reply	other threads:[~2003-08-28  6:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 23:22 2.4.22pre8 hangs too (Re: 2.4.21-jam1 solid hangs) Marcelo Tosatti
2003-08-28  6:10 ` Ville Herva [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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-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
2003-08-28  5:57                     ` Tejun Huh

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=20030828061000.GG150921@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=skraw@ithnet.com \
    /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).