dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209345] [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80)
Date: Tue, 22 Sep 2020 14:14:14 +0000	[thread overview]
Message-ID: <bug-209345-2300-i7f03DDiov@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209345-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209345

--- Comment #8 from Alexander von Gluck (kallisti5@unixzen.com) ---
rebooted without TB3 enclosure attached. Msnuslly loaded nouveau vis insmod
after the TB3 attachment calmed down, and got something a bit cleaner:


[  176.083524] nouveau: loading out-of-tree module taints kernel.
[  176.084343] nouveau: module verification failed: signature and/or required
key missing - tainting kernel
[  176.124991] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch -
Found [Buffer], ACPI requires [Package] (20200528/nsarguments-59)
[  176.125405] nouveau 0000:08:00.0: NVIDIA GK120 (0f22d0a1)
[  176.406057] nouveau 0000:08:00.0: bios: version 80.21.1f.00.01
[  176.537701] nouveau 0000:08:00.0: fb: 11520 MiB GDDR5
[  176.562278] nouveau 0000:08:00.0: bar: one-time init failed, -12
[  176.562522] nouveau 0000:08:00.0: init failed with -12
[  176.562523] nouveau: DRM-master:00000000:00000080: init failed with -12
[  176.562525] nouveau 0000:08:00.0: DRM-master: Device allocation failed: -12
[  176.563099] nouveau: probe of 0000:08:00.0 failed with error -12
[  176.563387] nouveau 0000:09:00.0: NVIDIA GK120 (0f22d0a1)
[  176.842900] nouveau 0000:09:00.0: bios: version 80.21.1f.00.02
[  176.977507] nouveau 0000:09:00.0: fb: 11520 MiB GDDR5
[  177.002138] nouveau 0000:09:00.0: bar: one-time init failed, -12
[  177.002380] nouveau 0000:09:00.0: init failed with -12
[  177.002382] nouveau: DRM-master:00000000:00000080: init failed with -12
[  177.002384] nouveau 0000:09:00.0: DRM-master: Device allocation failed: -12
[  177.003019] nouveau: probe of 0000:09:00.0 failed with error -12


So, each GK120 gets 11.5 GiB to make up that 24GiB of ram.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-09-22 14:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 23:55 [Bug 209345] New: [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80) bugzilla-daemon
2020-09-22  0:00 ` [Bug 209345] " bugzilla-daemon
2020-09-22  0:01 ` bugzilla-daemon
2020-09-22  1:14 ` bugzilla-daemon
2020-09-22  1:54 ` bugzilla-daemon
2020-09-22  4:05 ` bugzilla-daemon
2020-09-22  4:07 ` bugzilla-daemon
2020-09-22 13:59 ` bugzilla-daemon
2020-09-22 14:14 ` bugzilla-daemon [this message]
2020-09-22 14:15 ` bugzilla-daemon
2020-09-22 14:18 ` bugzilla-daemon
2020-09-22 14:23 ` bugzilla-daemon
2021-04-14 15:00 ` bugzilla-daemon
2021-04-14 15:08 ` bugzilla-daemon
2021-04-14 15:10 ` bugzilla-daemon
2021-04-14 15:35 ` bugzilla-daemon

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-209345-2300-i7f03DDiov@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@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