All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy West <jkwest@gmail.com>
To: Michael Barry <jabbera@gmail.com>,
	Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: reiser4 and reiserfs co-existence?
Date: Tue, 9 Nov 2004 12:53:41 -0500	[thread overview]
Message-ID: <b28a886104110909531ee7d29a@mail.gmail.com> (raw)
In-Reply-To: <662c77ee04110909473d0f6dd3@mail.gmail.com>

Funny thing is I did what you suggested, enabling all the debugging,
but it still freezes.  Not immediately, but it still hangs.  First I
get a segfault on any command I type into the console.  After 10 secs
or so of this, It will freeze up.  How in the world did you save that
stack trace.  I've seen the same thing on my machine, but can't figure
out how to save it, because my filesystem doesn't respond.


On Tue, 9 Nov 2004 12:47:07 -0500, Michael Barry <jabbera@gmail.com> wrote:
> This is the exact same problem I am having. I just bumped the thread
> actually. If you enable debig mode instead of your system freezing you
> will get a stack trace. That trace is available in my thread labeled
> possible bug: clog 0.
> 
> Mike
> 
> 
> 
> 
> On Tue, 9 Nov 2004 10:41:25 -0500, Jeremy West <jkwest@gmail.com> wrote:
> > Yes, I have a source code tarball that can't be built correctly.  You
> > can get this file from other places, but it might be best to test
> > exactly what I'm using.  I'm building php, and applying this patch.
> >
> > www.jeremysplace.org/php-4.3.9.tar.bz2
> > http://www.jeremysplace.org/php-4.3.6-includepath.diff
> >
> > To answer Markus's question.  I'm not having any bus errors .... yet.
> > At least I hope I don't get any.  I like to deal with one problem at a
> > time.  I will reboot my machine into a LiveCD, and debug some reiser4
> > for you.  How's best to do this anyway.  The debug script that you
> > referenced won't find anything unless something odd happens, right?
> > What does the script do?  I guess this is a stupid question, huh?
> >
> >
> >
> > On Tue, 09 Nov 2004 13:55:54 +0300, Vladimir Saveliev <vs@namesys.com> wrote:
> > > Hello
> > >
> > > On Tue, 2004-11-09 at 10:16, Jeremy West wrote:
> > > > Ok.  I think I may have found a glitch in reiser4.  It seems that my
> > > > freezing coincidentally happened every time I tried installing php.
> > > > Each time my system froze, the php build would crap out at the same
> > > > point.  Basically the bulid would say that it was running the
> > > > pear-installer program, then give me a segmentation fault.
> > >
> > > Do i understand correctly that you have a source code tar ball which can
> > > not be built in reiser4 filesystem? Where can i find it?
> > >
> > >
> > >
> > > >
> > > > So ... it seems to me that reiser4 is having some issues handling
> > > > segfault events.  I'm not sure how to tell what caused the segfault.
> > > > I don't think it's memory, because it happens in the same spot of the
> > > > build every time.  I've done this 4 times now.  That is not random.
> > > >
> > > >
> > > > On Mon, 08 Nov 2004 18:09:15 +0100, Redeeman <redeeman@metanurb.dk> wrote:
> > > > > On Mon, 2004-11-08 at 11:55 -0500, Jeremy West wrote:
> > > > >
> > > > >
> > > > > > HI,
> > > > > >
> > > > > > I'm new to the list.  I've taken the plunge and tasted the speed of
> > > > > > reiser4.  Excellent work.  I think I've stumbled upon a bug though.  I
> > > > > > have another partition formatted as reiserfs 3.6.  When I mount this
> > > > > > partition and listen to music from it, my reiser4 / partition stops
> > > > > > responding.  I mean every command I issue to the kernel results in a
> > > > > > segmentation fault.  Has anyone else had this problem?
> > > > > >
> > > > > > I'm using redeeman-sources, based on mm-sources patch set.
> > > > > how old would this happen to be? i mean.. give a uname -a
> > > > > --
> > > > > Redeeman <redeeman@metanurb.dk>
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> > --
> > Jeremy West
> > //---------------------------
> > "I had a life once... now I have a computer and DSL"
> >
> 


-- 
Jeremy West
//---------------------------
"I had a life once... now I have a computer and DSL"

  reply	other threads:[~2004-11-09 17:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 16:55 reiser4 and reiserfs co-existence? Jeremy West
2004-11-08 17:09 ` Redeeman
2004-11-09  7:16   ` Jeremy West
2004-11-09 10:41     ` mjt
2004-11-09 10:55     ` Vladimir Saveliev
2004-11-09 15:41       ` Jeremy West
2004-11-09 17:47         ` Michael Barry
2004-11-09 17:53           ` Jeremy West [this message]
2004-11-09 17:55             ` Michael Barry
2004-11-09 17:57             ` Spam
2004-11-09 18:06               ` Jeremy West
2004-11-09 18:11                 ` mjt
2004-11-09 21:21                   ` Jeremy West
     [not found]                     ` <662c77ee04110913347169a645@mail.gmail.com>
2004-11-09 21:56                       ` Jeremy West
2004-11-09 17:57             ` mjt
2004-11-09 18:08               ` Jeremy West
2004-11-09 19:06           ` Dr. Giovanni A. Orlando
2004-11-09 18:11             ` Jeremy West
2004-11-10  5:51       ` Jeremy West
2004-11-10  6:04         ` Jeremy West
2004-11-10  6:48           ` Jeremy West
     [not found]             ` <1100072902.1381.44.camel@tribesman.namesys.com>
2004-11-10 18:34               ` Jeremy West

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=b28a886104110909531ee7d29a@mail.gmail.com \
    --to=jkwest@gmail.com \
    --cc=jabbera@gmail.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.