From: Vladimir Saveliev <vs@namesys.com>
To: Jake Maciejewski <maciejej@msoe.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: making reiser4/AMD64 hardlock
Date: Thu, 04 Nov 2004 12:52:45 +0300 [thread overview]
Message-ID: <1099561964.1492.20.camel@tribesman.namesys.com> (raw)
In-Reply-To: <20041103201825.GY30438@hvs.envisage.co.za>
Hello
On Wed, 2004-11-03 at 23:18, Hendrik Visage wrote:
> On Wed, Nov 03, 2004 at 02:59:19AM -0600, Jake Maciejewski wrote:
> > I've been testing reiser4 on 2.6.9 (patches from 2.6.9-mm1 and fixes
> > from reiser4-for-2.6.9.diff). I have reiser4progs and libaal 1.0.1.
> > Syslog doesn't catch any errors when I get hardlocks (haven't tried
> > SysRq). I figured I could at least give you guys a hint about what kind
> > of usage pattern kills reiser4.
>
Please try to get as much debugging information as you can.
sysrq+t's output may help to understand the problem. Do you have "File
systems" -> "Reiser4" -> "Enable reiser4 debug options" -> "Assertions"
turned on? If no, please turn it, it may also help. Try to catch its
output, via serial console if it will not be stored in logs.
I will try your test in x86.
> I recall the last response about this issue:
>
> We need an AMD64 cpu...
>
well, yes.
>
next prev parent reply other threads:[~2004-11-04 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 8:59 making reiser4/AMD64 hardlock Jake Maciejewski
2004-11-03 20:18 ` Hendrik Visage
2004-11-04 9:52 ` Vladimir Saveliev [this message]
2004-11-04 10:39 ` Vladimir Saveliev
2004-11-05 5:41 ` Jake Maciejewski
2004-11-10 8:01 ` Jake Maciejewski
2004-11-10 16:08 ` Vladimir Saveliev
2004-11-10 19:45 ` Jake Maciejewski
2004-12-07 12:20 ` Alex Zarochentsev
2004-12-07 21:46 ` Jake Maciejewski
2004-12-08 16:24 ` Alex Zarochentsev
2004-12-08 17:26 ` Jake Maciejewski
2004-12-08 19:47 ` Jake Maciejewski
2004-11-12 18:17 ` Vitaly Fertman
2004-11-12 20:03 ` Jake Maciejewski
2004-11-20 5:35 ` Julia Wolf
2004-11-04 21:53 ` Julia Wolf
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=1099561964.1492.20.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=maciejej@msoe.edu \
--cc=reiserfs-list@namesys.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 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.