linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: mason@suse.com, andrea@suse.de, riel@redhat.com,
	linux-kernel@vger.kernel.org, maillist@jg555.com
Subject: Re: Bug Report: 2.4.22-pre5: BUG in page_alloc (fwd)
Date: Mon, 21 Jul 2003 14:23:53 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.55L.0307211422010.26736@freak.distro.conectiva> (raw)
In-Reply-To: <20030721170517.1dd1f910.skraw@ithnet.com>



On Mon, 21 Jul 2003, Stephan von Krawczynski wrote:

> On Mon, 21 Jul 2003 10:49:06 +0200
> Stephan von Krawczynski <skraw@ithnet.com> wrote:
>
> > On Fri, 18 Jul 2003 11:14:15 -0300 (BRT)
> > Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> >
> > >
> > > I have just started stress testing a 8way OSDL box to see if I can
> > > reproduce the problem. I'm using pre6+axboes BH_Sync patch.
> > >
> > > I'm running 50 dbench clients on aic7xxx (ext2) and 50 dbench clients on
> > > DAC960 (ext3). Lets see what happens.
> > >
> > > After lunch I'll keep looking at the oopses. During the morning I only had
> > > time to setup the OSDL box and start the tests.
> >
> > Hello Marcelo,
> >
> > have you seen anything in your tests? My box just froze again after 3 days
> > during NFS action. This was with pre6, I am switching over to pre7.
>
> I managed to freeze the pre7 box within these few hours. There was no nfs
> involved, only tar-to-tape.

You had NMI on, correct? Sysrq doesnt work, correct?

> I switched back to 2.4.21 to see if it is still stable. Is there a
> possibility that the i/o-scheduler has another flaw somewhere (just like
> during mount previously) ...

It might be a problem in the IO scheduler, yes.

Lets isolate the problems: If 2.4.21 doenst lockup, try 2.4.22-pre7
without drivers/block/ll_rw_blk{.c,.h} changes.


  parent reply	other threads:[~2003-07-21 18:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.55L.0307150859130.5146@freak.distro.conectiva>
     [not found] ` <1058297936.4016.86.camel@tiny.suse.com>
     [not found]   ` <Pine.LNX.4.55L.0307160836270.30825@freak.distro.conectiva>
     [not found]     ` <20030718112758.1da7ab03.skraw@ithnet.com>
2003-07-18 12:23       ` Bug Report: 2.4.22-pre5: BUG in page_alloc (fwd) Marcelo Tosatti
2003-07-18 12:50         ` Stephan von Krawczynski
2003-07-18 14:14           ` Marcelo Tosatti
2003-07-18 15:13             ` Stephan von Krawczynski
2003-07-21  8:49             ` Stephan von Krawczynski
2003-07-21 11:51               ` Marcelo Tosatti
2003-07-21 15:05               ` Stephan von Krawczynski
2003-07-21 16:20                 ` Andrea Arcangeli
2003-07-21 19:24                   ` Stephan von Krawczynski
2003-07-21 19:40                     ` Marcelo Tosatti
2003-07-21 20:12                       ` Stephan von Krawczynski
2003-07-21 21:05                     ` Marcelo Tosatti
2003-07-21 17:23                 ` Marcelo Tosatti [this message]
2003-07-21 19:09                   ` Stephan von Krawczynski
2003-07-18 17:18           ` Andrea Arcangeli

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=Pine.LNX.4.55L.0307211422010.26736@freak.distro.conectiva \
    --to=marcelo@conectiva.com.br \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    --cc=mason@suse.com \
    --cc=riel@redhat.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).