All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: bunk@fs.tum.de (Adrian Bunk)
Cc: alexh@ihatent.com (Alexander Hoogerhuis),
	hpj@urpla.net (Hans-Peter Jansen), alan@redhat.com (Alan Cox),
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20-pre5-ac4
Date: Sun, 8 Sep 2002 08:55:17 -0400 (EDT)	[thread overview]
Message-ID: <200209081255.g88CtHJ31280@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0209081321200.7218-100000@mimas.fachschaften.tu-muenchen.de> from "Adrian Bunk" at Sep 08, 2002 01:23:10 PM

> Which non-free modues (NVidia?) were loaded on your computer? Is the
> problem reproducible without any non-free module loaded _ever_ since the
> last reboot?

I've seen this trace without nvidia etc loaded too. Right now the problem
I have is that I can't duplicate it. If my box would jut blow up the same
way all would be well 8)

What compilers are being used by the folks who see the problem ?

  parent reply	other threads:[~2002-09-08 12:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 15:00 Linux 2.4.20-pre5-ac4 Alan Cox
2002-09-06 15:40 ` Adrian Bunk
2002-09-06 16:11   ` Steven Cole
2002-09-06 18:40 ` Hans-Peter Jansen
2002-09-07 21:28 ` Hans-Peter Jansen
2002-09-07 21:42   ` Adrian Bunk
2002-09-08 11:01   ` Alexander Hoogerhuis
2002-09-08 11:23     ` Adrian Bunk
2002-09-08 11:14       ` Alexander Hoogerhuis
2002-09-08 12:32         ` Hans-Peter Jansen
2002-09-08 12:55       ` Alan Cox [this message]
2002-09-08 13:36         ` Hans-Peter Jansen
2002-09-08 15:12           ` Zwane Mwaikambo
2002-09-08 15:23         ` Alexander Hoogerhuis
2002-09-08 17:10           ` Alan Cox
2002-09-08 18:02             ` Rudmer van Dijk
2002-09-08 17:03         ` Alexander Hoogerhuis
2002-09-16 22:12         ` Alexander Hoogerhuis
2002-09-17  7:29           ` Jens Axboe
2002-09-09 14:40     ` Scott Henson

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=200209081255.g88CtHJ31280@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=alexh@ihatent.com \
    --cc=bunk@fs.tum.de \
    --cc=hpj@urpla.net \
    --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 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.