All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Briggs <jbriggs@esoft.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Reiser4 panic at fs/reiser4/lock.c:434
Date: Thu, 25 Mar 2004 12:41:54 -0700	[thread overview]
Message-ID: <1080243714.31969.6.camel@localhost.localdomain> (raw)
In-Reply-To: <16482.50006.976095.680498@laputa.namesys.com>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On Thu, 2004-03-25 at 04:32, Nikita Danilov wrote:
> Jonathan Briggs writes:
>  > The system is running Linux kernel 2.6.5-rc2.  It's tainted by Nvidia
>  > drivers.
>  > 
>  > The system was compiling the kernel, and Reiser4 panicked.
> 
> Was compilation multi-threaded (make -j)?

No, it was just plain make.  There were other programs using the disk at
the same time, though.  Evolution, rhythmbox, other desktop stuff.

[snip]
> Please try following patch:
[patch snipped]

I tried to apply the patch, but it must be against a newer version of
Reiser4.  I haven't been following the internal-testing snapshots. 
Should I have been?  I'm still using the 2004-02-25 snapshot.  What
should I be using to apply your patch to?

Thanks.
-- 
Jonathan Briggs
jbriggs@esoft.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-03-25 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25  0:50 Reiser4 panic at fs/reiser4/lock.c:434 Jonathan Briggs
2004-03-25 11:32 ` Nikita Danilov
2004-03-25 19:41   ` Jonathan Briggs [this message]
2004-03-29 13:08     ` Hans Reiser

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=1080243714.31969.6.camel@localhost.localdomain \
    --to=jbriggs@esoft.com \
    --cc=Nikita@Namesys.COM \
    --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.