linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jim Gifford" <maillist@jg555.com>
To: "Marcelo Tosatti" <marcelo@conectiva.com.br>,
	"Stephan von Krawczynski" <skraw@ithnet.com>
Cc: akpm@osdl.org, andrea@suse.de, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org, mason@suse.com, green@namesys.com
Subject: Re: 2.4.22-pre lockups (now decoded oops for pre10)
Date: Wed, 13 Aug 2003 08:21:42 -0700	[thread overview]
Message-ID: <076901c361ae$9a105030$3400a8c0@W2RZ8L4S02> (raw)
In-Reply-To: Pine.LNX.4.44.0308131143570.4279-100000@localhost.localdomain


----- Original Message ----- 
From: "Marcelo Tosatti" <marcelo@conectiva.com.br>
To: "Stephan von Krawczynski" <skraw@ithnet.com>
Cc: <akpm@osdl.org>; <andrea@suse.de>; <alan@lxorguk.ukuu.org.uk>;
<linux-kernel@vger.kernel.org>; <mason@suse.com>; <green@namesys.com>
Sent: Wednesday, August 13, 2003 7:53 AM
Subject: Re: 2.4.22-pre lockups (now decoded oops for pre10)


>
>
> On Wed, 13 Aug 2003, Stephan von Krawczynski wrote:
>
> > On Fri, 8 Aug 2003 12:33:28 -0300 (BRT)
> > Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> >
> > > That will provide further information yes. We can then know if the
problem
> > > is reiserfs specific or not, which is VERY useful.
> > >
> > > Again, thanks for your efforts helping us track down the problem.
> >
> > Status update:
> >
> > uptime:
> >  12:45pm  up 2 days 19:39,  18 users,  load average: 2.02, 2.05, 2.06
> >
> > Running SMP. So far no crash happened under ext3.
> > Still I see the tar-verification errors. None on the first day, 2 on the
second
> > and 2 today so far.
> > I see a growing possibility that the formerly crashes are directly
linked to a
> > reiserfs problem, maybe broken SMP-locking.
> > If it survives until sunday I will revert all ext3 back to reiserfs to
be sure
> > it still crashes, then ideas for patches will be welcome :-)
>
> Great you tracked it down. Your previous traces almost always involved
> reiserfs calls, which is another indicator that reiserfs is probably the
> problem here.
>
> Chris, Oleg, it might be nice if you guys could look at previous oops
> reports by Stephan.
>
Marcelo,
    Could this be related to the issues I was having. Since rc1 I have not
had any problems, and I have all the iptables stuff running again. My
machine is smp and is using ext3.



  parent reply	other threads:[~2003-08-13 15:21 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030808002918.723abb08.skraw@ithnet.com>
2003-08-08 14:54 ` 2.4.22-pre lockups (now decoded oops for pre10) Marcelo Tosatti
2003-08-08 15:05   ` Stephan von Krawczynski
2003-08-08 15:33     ` Marcelo Tosatti
2003-08-10 21:35       ` Stephan von Krawczynski
2003-08-10 23:23         ` Neil Brown
2003-08-11  9:33           ` Stephan von Krawczynski
2003-08-18 20:43             ` Mike Fedyk
2003-08-13 10:55       ` Stephan von Krawczynski
2003-08-13 14:53         ` Marcelo Tosatti
2003-08-13 14:59           ` Oleg Drokin
2003-08-13 15:12             ` Stephan von Krawczynski
2003-08-13 15:30               ` Oleg Drokin
2003-08-13 16:04                 ` Stephan von Krawczynski
2003-08-13 16:34                   ` Oleg Drokin
2003-08-13 22:19                     ` Stephan von Krawczynski
2003-08-14  8:45                       ` Oleg Drokin
2003-08-14 17:26                         ` Marcelo Tosatti
2003-08-14 17:42                           ` Stephan von Krawczynski
2003-08-15  2:08                             ` Chris Mason
2003-08-15  9:40                               ` Stephan von Krawczynski
2003-08-15 10:28                               ` Stephan von Krawczynski
2003-08-15 12:55                                 ` Chris Mason
2003-08-20 14:21                                   ` 2.4.22-pre lockups (yet another oops for rc2) Stephan von Krawczynski
2003-09-05  9:24                                   ` 2.4.22-pre lockups (case closed) Stephan von Krawczynski
2003-09-05 13:37                                     ` Andrea Arcangeli
2003-08-15 10:13                         ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-15 10:31                           ` Oleg Drokin
2003-08-18 15:06                   ` Andrea Arcangeli
2003-08-18 20:19                     ` Stephan von Krawczynski
2003-08-18 20:58                       ` Mike Fedyk
2003-08-18 22:31                       ` Andrea Arcangeli
2003-08-19  1:12                         ` Mike Fedyk
2003-08-19  7:12                           ` Stephan von Krawczynski
2003-08-19 13:10                             ` Alan Cox
2003-08-19 14:18                               ` Stephan von Krawczynski
2003-08-19 18:00                                 ` Mike Fedyk
2003-08-19 21:58                                   ` Stephan von Krawczynski
2003-08-19 13:27                             ` Andrea Arcangeli
2003-08-13 15:21           ` Jim Gifford [this message]
2003-08-13 17:08             ` Marcelo Tosatti
2003-08-10 14:23     ` Keith Owens
2003-08-02 12:27 2.4.22-pre lockups (decoded oops for pre8) Stephan von Krawczynski
2003-08-05 16:40 ` Marcelo Tosatti
2003-08-06  7:41   ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-06  8:58     ` Oleg Drokin
2003-08-06  9:09     ` Willy Tarreau
2003-08-06  9:36       ` Stephan von Krawczynski
2003-08-06 12:45         ` Willy Tarreau
2003-08-18 14:23       ` Andrea Arcangeli
2003-08-06 18:15     ` Marcelo Tosatti
2003-08-07  2:14       ` Stephan von Krawczynski
2003-08-07  5:35         ` Oleg Drokin
2003-08-07 12:45         ` Marcelo Tosatti
     [not found]           ` <3F325198.2010301@namesys.com>
2003-08-07 13:32             ` Stephan von Krawczynski
2003-08-18 20:29               ` Mike Fedyk
2003-08-18 20:39                 ` Stephan von Krawczynski
2003-08-18 21:09                   ` Mike Fedyk
2003-08-07 15:52           ` Stephan von Krawczynski

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='076901c361ae$9a105030$3400a8c0@W2RZ8L4S02' \
    --to=maillist@jg555.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.com \
    --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).