All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 101273] New: [NV108] Random kernel panic
Date: Thu, 01 Jun 2017 17:46:16 +0000	[thread overview]
Message-ID: <bug-101273-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1604 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101273

            Bug ID: 101273
           Summary: [NV108] Random kernel panic
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: mrblooter-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 131646
  --> https://bugs.freedesktop.org/attachment.cgi?id=131646&action=edit
lspci output (from when the kernel panic didn't happen)

I have suddenly started experiencing kernel panics with my Nvidia GT630
(NV108).
It started happening after a system update (kernel was updated, but I am
getting the same with an older kernel).

Shortly after booting, sometimes in the middle of it, it goes into a kernel
panic. It doesn't happen all the time, but it seems to be random, every other
time.
I tested it with the proprietary Nvidia driver and there were no kernel panics
with that one.

Could this be related to bug #101184 ?

Screenshot of the screen when it happens (sorry, I couldn't find a way to get
the text from it):
http://preview.ibb.co/mb2oJF/DSC_0007_1.jpg

Xorg version: 1.19.3
Linux version: 4.11.3
Operating system: Arch Linux
I can provide more information if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3281 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-06-01 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 17:46 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-101273-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-06-01 17:51   ` [Bug 101273] [NV108] Random kernel panic bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-04 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 10:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 12:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-101273-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.