All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miek Gieben <miekg@atoom.net>
To: linux-kernel@vger.kernel.org
Subject: hard lockup with 2.6.0-test[789]
Date: Sat, 1 Nov 2003 14:17:33 +0100	[thread overview]
Message-ID: <20031101131733.GA4597@atoom.net> (raw)

Hello,

i'm experiencing hard lockups with the 2.6 kernel running on my firewall.

The machine:
pentium II, 
192 MB memory - did not run memtest though
uses reiserfs as / fs

replaced harddisk - old one had bad blocks
current harddisk: 4.3 maxtor

2.4.22 ran ok - no problem
2.6.0-test6 - ok	( haven't fully tested this though)
      test7 - crash
      test8 - crash
      test9 - crash

Problem:
crash after a warm reboot. Turning the machine off and then booting
it seems to make it run ok. But not always...

There is no oops, no nothing. The only thing I can do is reset the machine.
The role of the machine is to act as firewall.

It crashes after the boot - everything goes ok, until the prompt. Then
after a few seconds: a hard lock.

If it does _not_ crash (i've run crashme on the test9 once) it keeps going for
days and even longer (usally it runs until I update the kernel)

Right now i've switched / to another partition using ext3. It _looks_ like it
doesn't crash anymore, so my suspicion is that it is reiserfs related, but i'm
only guessing here.

My server also has a reiserfs partition (though not as /) and it has no problems
with it...

What can I do to find the cause of it? I've already disabled dma but that seems
to make no difference. 

grtz Miek

             reply	other threads:[~2003-11-01 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01 13:17 Miek Gieben [this message]
2003-11-01 14:15 ` hard lockup with 2.6.0-test[789] Michael Frank

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=20031101131733.GA4597@atoom.net \
    --to=miekg@atoom.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.