All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mfedyk@matchmail.com, andrea@suse.de, green@namesys.com,
	marcelo@conectiva.com.br, akpm@osdl.org,
	linux-kernel@vger.kernel.org, mason@suse.com
Subject: Re: 2.4.22-pre lockups (now decoded oops for pre10)
Date: Tue, 19 Aug 2003 16:18:32 +0200	[thread overview]
Message-ID: <20030819161832.2a0bae58.skraw@ithnet.com> (raw)
In-Reply-To: <1061298621.30565.31.camel@dhcp23.swansea.linux.org.uk>

On 19 Aug 2003 14:10:22 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Maw, 2003-08-19 at 08:12, Stephan von Krawczynski wrote:
> > > Are you saying that one CPU can't saturate the memory bus?  Or maybe
> > > we're hitting something on the CPU bus, or just that SMP will change the
> > > timings and stress things differently?  Or that if memtest doesn't test
> > > from the second CPU then it could be a faulty cpu/L2?
> > 
> > Well, if memtest does not use a second available CPU then probably we
> > should ask the author about this...
> 
> I'm sure he'd give you a quote for adding SMP support if you asked.

Well, actually I don't want to burn down his time as long as I don't see a need
for it. Since I am pretty confident to make the box work in SMP under 2.4.20 a
memtest will most certainly not give any additional information, be it running
UP or SMP.
Instead I will invest another day and convert the whole system back to
reiserfs, because the ext3 fs cannot be used under 2.4.20 - I don't know why.
Additionally reiserfs is better for testing possible patches because it crashes
in much shorter time than ext3 setup.
2.4.20 setup gives me a simple testcase to prove people right or wrong that are
talking about a hardware issue.

Regards,
Stephan

  reply	other threads:[~2003-08-19 15:56 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 [this message]
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
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=20030819161832.2a0bae58.skraw@ithnet.com \
    --to=skraw@ithnet.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=mfedyk@matchmail.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.