From: Felix Seeger <felix.seeger@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: System very unstable
Date: Sat, 28 Sep 2002 12:31:10 +0200 [thread overview]
Message-ID: <200209281231.11057.felix.seeger@gmx.de> (raw)
In-Reply-To: <20020928122349.60be48b4.gigerstyle@gmx.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Samstag, 28. September 2002 12:23 schrieb Marc Giger:
> On Sat, 28 Sep 2002 11:34:27 +0200
>
> Felix Seeger <felix.seeger@gmx.de> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Am Samstag, 28. September 2002 11:32 schrieb Alan Cox:
> > > > EIP: 0010:[get_new_inode+94/368] Tainted: P
> > > > EFLAGS: 00010206
> > > > eax: f1ec9808 ebx: 00000000 ecx: c1376130 edx: c3761dc8
> > >
> > > You appear to have some non typical modules loaded. If they are binary
> > > ones from people like Nvidia please see if the box is stable without
> > > them ever being loaded.
> >
> > Yes I am using the nvidia module. But I don't think that is the problem,
> > because I never had such problems with it.
> > The only thing I can imagine is that:
> > I installed the new module and I looked very unstable. So I installed the
> > old one again.
>
> Yes and that's the point. You're using the 1.0.3123 Version of nvidia's
> module, right?
> I tried this also, but after 1 hour I removed it again,
> because they are very instable. I don't know what nvidia thinks. Probably
> nothing. Their drivers are unworthy. It won't take a long time, until I
> will buy a graphic-card from another manufacturer. Perhaps Matrox
> Parhelia:-)
No, I installed that module, very unstable and installed the old one again
like you ;)
> > > If its only just begun happening and you didnt change these modules or
> > > the kernel then it may well be worth checking CPU temperature in the
> > > BIOS, the fans and/or running memtest86 to see if it is hardware.
> > >
> > > If you've changed kernel obviously see if the old one works reliably
> > > first
have fun
Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9lYTuS0DOrvdnsewRAuPCAJwIKCT4gQUvRxkjKrPdngM8BaiePQCeM3Ms
vNWRu3N6aGdN+Mkm5z0CXLs=
=fD9/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-28 10:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 9:15 System very unstable Felix Seeger
2002-09-28 9:32 ` Alan Cox
2002-09-28 9:34 ` Felix Seeger
2002-09-28 9:50 ` Thunder from the hill
2002-09-28 9:55 ` Felix Seeger
2002-09-28 9:59 ` David S. Miller
2002-09-28 10:10 ` Thunder from the hill
2002-09-28 10:04 ` David S. Miller
2002-09-28 10:33 ` Felix Seeger
2002-09-28 10:35 ` David S. Miller
2002-09-28 11:02 ` FD Cami
2002-09-28 10:48 ` David S. Miller
2002-09-28 11:13 ` Michael Clark
2002-09-29 0:00 ` Elladan
2002-09-29 5:50 ` Michael Clark
2002-09-29 7:37 ` Elladan
2002-09-29 12:12 ` Simon Fowler
2002-09-28 11:35 ` Thunder from the hill
2002-09-28 11:34 ` David S. Miller
2002-09-29 0:42 ` Kristofer T. Karas
2002-09-28 10:08 ` Alan Cox
2002-09-28 10:36 ` Felix Seeger
2002-09-28 12:46 ` Krzysztof Halasa
2002-09-29 18:06 ` Felix Seeger
2002-09-28 10:23 ` Marc Giger
2002-09-28 10:31 ` Felix Seeger [this message]
2002-09-29 5:41 Dieter Nützel
2002-09-30 6:47 ` Kristofer T. Karas
2002-10-01 12:32 ` Dieter Nützel
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=200209281231.11057.felix.seeger@gmx.de \
--to=felix.seeger@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).