All of lore.kernel.org
 help / color / mirror / Atom feed
From: Athanasios Leontaris <aleontar@ucsd.edu>
To: Thomas Weich <weicht@in.tum.de>
Cc: s0348365@sms.ed.ac.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.6.2 Kernel Badness with 1.0-5336 NVIDIA driver
Date: Tue, 17 Feb 2004 16:40:38 -0800	[thread overview]
Message-ID: <200402171640.39177.aleontar@ucsd.edu> (raw)
In-Reply-To: <200402172131.52993.weicht@in.tum.de>

Indeed it shows up on my /var/log/messages* on two other occasions without 
hanging the system then. _But_ I had 5328 then. At least this badness shows 
up through 5328 and 5336, if that could provide a pointer to somebody (NVIDIA 
are you listening?)...

On Tuesday 17 February 2004 12:31 pm, Thomas Weich wrote:
> I had the same problems with NVidia 1.0-5336 but there was no hint
> in /var/log/* that the NVidia driver caused the freeze. It wasn't necessary
> that X  was running, loading the nvidia Module was sufficient to freeze the
> complete system after an unspecified amount of time.
>
> For me, it worked to use the 1.0-5328 version with patches from
> www.minion.de. Since then, everything is working without problems.
>
> I'm not on the list.
>
> Thomas
>
> > I checked it. "RenderAccel" is not set.
> > Maybe FW and SBA have something to do with it, but that's just a guess.
> > Thanks.
> >
> > On Tuesday 17 February 2004 09:54 am, Alistair John Strachan wrote:
> > > On Tuesday 17 February 2004 16:08, you wrote:
> > > > Hi to all,
> > > >
> > > > Pls cc me as I am not subscribing.
> > > > I know that the kernel is tainted so pls don't flame ;)
> > > > The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP
> > > > (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro.
> > > > The mobo is Abit KG7 and the video card an FX5600.
> > > >
> > > > X stopped responding out of the blue, at a KDE 3.2 desktop, and it
> > > > could not be killed either. The following messages were uncovered in
> > > > my /var/log/messages:
> > >
> > > [snip]
> > >
> > > Please first check to see if /etc/X11/XF86Config or
> > > /etc/X11/XF86Config-4 contains the string:
> > >
> > > Option "RenderAccel" "1"
> > >
> > > If it does, either remove the line or replace it with:
> > >
> > > Option "RenderAccel" "0"
> > >
> > > Render acceleration is still not working with the proprietary driver.
> > > I'm not saying it's definitely this, it just might not be related to
> > > the messages in syslog.
> > >
> > > I occasionally see these badness messages in syslog, but my machine
> > > never locks up. I was under the impression that these were only
> > > warnings.
> >
> > -
> > 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:[~2004-02-18  0:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 16:08 2.6.2 Kernel Badness with 1.0-5336 NVIDIA driver Athanasios Leontaris
2004-02-17 16:56 ` Matt H.
2004-02-17 17:54 ` Alistair John Strachan
2004-02-17 17:57   ` Athanasios Leontaris
2004-02-17 20:31     ` Thomas Weich
2004-02-18  0:40       ` Athanasios Leontaris [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=200402171640.39177.aleontar@ucsd.edu \
    --to=aleontar@ucsd.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=weicht@in.tum.de \
    /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.