mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Karol Olechowskii <karol_olechowski@acn.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon XP 1800+ segemntation fault
Date: 22 Jul 2002 13:44:10 +0100	[thread overview]
Message-ID: <1027341850.31782.16.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020722133259.A1226@acc69-67.acn.pl>

On Mon, 2002-07-22 at 14:32, Karol Olechowskii wrote:
> Hello 
> 
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?

> nvidia: loading NVIDIA NVdriver Kernel Module  1.0-2960  Tue May 14 07:41:42 PDT 2002
> devfs_register(nvidiactl): could not append to parent, err: -17
> devfs_register(nvidia0): could not append to parent, err: -17

Please duplicate the problem without ever loading the NVidia nvdriver
from a clean boot. If you can't do that then talk to Nvidia, if you can
then post new crash data here


  parent reply	other threads:[~2002-07-22 11:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 13:32 Karol Olechowskii
2002-07-22 11:34 ` Dave Jones
2002-07-22 12:44 ` Alan Cox [this message]
2002-07-22 15:46   ` Karol Olechowski
2002-07-22 16:10     ` metf28
2002-07-22 16:30     ` venom
2002-07-22 16:53       ` Giro
2002-07-22 16:59       ` Richard B. Johnson
2002-07-22 22:49     ` Diego Calleja
2002-07-22 14:28 ` Kurt Garloff
2002-07-22 14:49 ` Olivier Galibert
2002-07-22 16:43   ` Alan Cox
2002-07-22 17:39 ` Steven J. Hill
2002-07-23  0:04   ` [OT] " J Sloan

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=1027341850.31782.16.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=karol_olechowski@acn.waw.pl \
    --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

all inboxes | Powered by JetHome®