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 111371] New: [NV04] bios OOB on kernel driver initialization
Date: Sun, 11 Aug 2019 15:33:56 +0000	[thread overview]
Message-ID: <bug-111371-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111371
           Summary: [NV04] bios OOB on kernel driver initialization
           Product: xorg
           Version: unspecified
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: jorgenatzdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 145023
  --> https://bugs.freedesktop.org/attachment.cgi?id=145023&action=edit
The non-verbose kernel log

Steps to reproduce:
Boot linux with NV04 card in motherboard AGP slot.
OR
'modprobe nouveau' with NV04 card in motherboard AGP slot.

Actual Results:
2 times during the boot process the screen turns black, only to return back to
the character display. The nouveau module ends up loaded, but the screen
appears to not be using the drm driver.

Platform:
Alpine Linux 3.10.1 Standard, kernel 4.19.58 (non-verbose log)
Tiny Core Linux, kernel 4.19.10 (verbose external module log)

I tried using the kernel parameter nouveau.config=NvMSI=0, but it made no
difference. I also tried using nouveau.config=NvBios=PRAMIN, even though there
were no "checksum invalid" errors in the dmesg output.

I was unable to get a VBIOS dump, as the /sys/kernel/debug/dri folder was
empty.

I was also hesitant to do a git bisection, as compiling the nouveau kernel
module takes upwards of 7 hours on the machine I am using. However, I can try
if you would like.

I have two kernel logs, one is from kernel 4.19.58 and has nouveau compiled as
an in-tree module. The other log is for kernel 4.19.10 and has nouveau compiled
as an out-of-tree module, but I was able to add the kernel parameters
drm.debug=14 and log_buf_len=16M.

I apologize if I left any information out, and thank you for any reply.

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

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

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

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

             reply	other threads:[~2019-08-11 15:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 15:33 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-111371-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-08-11 15:41   ` [Bug 111371] [NV04] bios OOB on kernel driver initialization bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 15:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 16:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 16:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 16:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 20:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 20:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 20:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12  3:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12  3:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12  3:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12  3:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12  6:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 15:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 15:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 15:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 19:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 19:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:51   ` 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-111371-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.