mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James <bjlockie@lockie.ca>
To: linux-kernel@vger.kernel.org
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: nouveau: System crashes with NVIDIA GeForce 8600 GT
Date: Mon, 19 Aug 2019 09:55:20 -0400	[thread overview]
Message-ID: <03ec19b7-0a54-39cc-5bb2-1b09bb8fccc6@lockie.ca> (raw)
In-Reply-To: <201908181727.04076.linux@zary.sk>

On 2019-08-18 11:27 a.m., Ondrej Zary wrote:
> On Saturday 17 August 2019 14:50:33 Alex Dewar wrote:
>> Hi all,
>>
>> I'm getting frequent system crashes (every few hours or so) and it seems
>> that the nouveau driver is causing the issue (dmesg output below). I see it
>> with both v5.2.8 and the v4.19 LTS kernel. Sometimes the system
>> completely freezes and sometimes seemingly just the nouveau driver goes
>> down. The screen freezes and colours stream across it. Often after I
>> reboot the BIOS logo is mangled too until the first modeset. The crash
>> seems to be happening in nv50_fb_intr() in nv50.c.
>>
>> I'm not sure if this is related, but the system now often freezes on
>> suspend or resume since I switched from using the old (recently
>> abandoned) proprietry NVIDIA drivers, again both with 5.2 and 4.19
>> kernels. Blacklisting the nouveau driver doesn't seem to fix it however,
>> though I guess the graphics card could still be causing issues in some
>> other way? I never had problems with suspend and resume before.
>>
>> Any suggestions about how I could debug this further?
> 
> Is it really a software problem (does it still work fine with proprietary
> driver)?
> These nVidia chips are known to fail and corrupt BIOS logo suggests that.
> 

It's interesting the proprietary driver still seems to have support for 
series 6 and series 7 (just series 8 became unsupported).

I would try a live iso with a recent kernel.



      reply	other threads:[~2019-08-19 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-17 12:50 Alex Dewar
2019-08-18 15:27 ` Ondrej Zary
2019-08-19 13:55   ` James [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=03ec19b7-0a54-39cc-5bb2-1b09bb8fccc6@lockie.ca \
    --to=bjlockie@lockie.ca \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.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®