mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Andrea Arcangeli <andrea@suse.de>, Chris Mason <mason@suse.com>,
	riel@redhat.com, lkml <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 16:40:27 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.55L.0307211624410.26518@freak.distro.conectiva> (raw)
In-Reply-To: <20030721212453.4139a217.skraw@ithnet.com>



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

> On Mon, 21 Jul 2003 12:20:33 -0400
> Andrea Arcangeli <andrea@suse.de> wrote:
>
> > > I managed to freeze the pre7 box within these few hours. There was no nfs
> > > involved, only tar-to-tape.
> > > 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) ...
> >
> > is it a scsi tape?
>
> yes.
>
> > Is the tape always involved?
>
> No, I experience both freeze during nfs-only action and freeze during
> tar-to-scsi-tape.
> My feelings are that the freeze does (at least in the nfs case) not happen
> during high load but rather when load seems relatively light. Handwaving one
> could say it looks rather like an I/O sched starvation issue than breakdown
> during high load. Similar to the last issue.
>
> > there are st.c updates
> > between 2.4.21 to 22pre7. you can try to back them out.
>
> Hm, which?
>
> > [...]
> > You should also provide a SYSRQ+P/T of the hang or we can't debug it at
> > all.
>
> Well, I really tried hard to produce something, but failed so far, if I had
> more time I would try a serial console hoping that it survives long enough to
> show at least _something_.
> The only thing I ever could see was the BUG in page-alloc thing from the
> beginning of this thread.

Stephan,

I'm sending you the scsi tape driver changes in 2.4.22-pre so you can
revert them (in private in a few minutes).

If that doesnt make us spot the problem, can you PLEASE find out in which
-pre the problem starts ?

Thank you

  reply	other threads:[~2003-07-21 19:29 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       ` 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 [this message]
2003-07-21 20:12                       ` Stephan von Krawczynski
2003-07-21 21:05                     ` Marcelo Tosatti
2003-07-21 17:23                 ` Marcelo Tosatti
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.0307211624410.26518@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

all inboxes | Powered by JetHome®