public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Möller" <andreas-moeller@gmx.net>
To: Felix Braun <Felix.Braun@McGill.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Random lockups with kernels 2.4.6-pre8+
Date: Mon, 9 Jul 2001 19:44:47 +0200	[thread overview]
Message-ID: <20010709174456Z264329-720+528@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0107080056170.833-100000@eressea.in-berlin.de>
In-Reply-To: <Pine.LNX.4.33L2.0107080056170.833-100000@eressea.in-berlin.de>

Am Sonntag, 8. Juli 2001 07:01 schrieb Felix Braun:
> Hi there,
>
> just in case anybody cares: the lockup behaviour that I observed starting
> mozilla 0.9.2 on kernels 2.4.6-pre8 and 2.4.6-final does not occur on
> 2.4.6-ac2 (haven't tried with 2.4.7-preX). Appearently, I was the only one
> experiencing that problem anyway. Ah well, I won't complain now that
> evertything is working.

I also experienced some lockups under 2.4.6-pre, there was an OOPS under 
2.4.6-pre3 and some other lockups under newer 2.4.6-pres but without any 
error message. Each time I was running Mozilla 0.9.1 (respectively Galeon 
0.11.0). Fortunately, there were no more lockups since 2.4.7-pre (I didn't 
test 2.4.6 abundant).

>
> Cheers Felix
>

	Andreas

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2001-07-09 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  0:51 Random lockups with kernels 2.4.6-pre8+ Felix Braun
2001-07-05 20:47 ` Felix Braun
2001-07-08  5:01   ` Felix Braun
2001-07-09 17:44     ` Andreas Möller [this message]

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=20010709174456Z264329-720+528@vger.kernel.org \
    --to=andreas-moeller@gmx.net \
    --cc=Felix.Braun@McGill.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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