Displaying 20 results from an estimated 11000 matches similar to: "[Bug 100423] New: MMIO read of 00000000 FAULT at 022554 [ IBUS ]"
2018 Jan 29
8
[Bug 104835] New: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
https://bugs.freedesktop.org/show_bug.cgi?id=104835
Bug ID: 104835
Summary: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2016 Oct 22
29
[Bug 98386] New: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid
https://bugs.freedesktop.org/show_bug.cgi?id=98386
Bug ID: 98386
Summary: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer
to {TDMS,flat panel) table invalid
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority:
2019 Aug 13
4
[Bug 111392] New: [NV110] bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
https://bugs.freedesktop.org/show_bug.cgi?id=111392
Bug ID: 111392
Summary: [NV110] bus: MMIO read of 00000000 FAULT at 619444 [
IBUS ]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2019 Jan 01
2
Nouveau module results in total lockups without any dmesg trace on a NP900X5N Kaby Lake machine
Hi Ben, David and Daniel ,
First of all happy new year. Based on advice of Greg K-H herewith a mail
about a number of Nouveau issues with my laptop.
I installed various Kali linux versions up to Linux 4.20.0-rc7
(downloaded, compiled and installed) on a Samsung NP900X5N laptop and
have an issue with the driver after loading.
My configuration:
- i7 7500
- 16 gb / 256 gb ssd
- nvidia 940MX
2015 Jan 01
12
[Bug 87942] New: [NVE7] Unable to use nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=87942
Bug ID: 87942
Summary: [NVE7] Unable to use nouveau
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2018 Aug 04
2
[Bug 107479] New: GM108: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
https://bugs.freedesktop.org/show_bug.cgi?id=107479
Bug ID: 107479
Summary: GM108: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2013 Oct 10
97
[Bug 70354] New: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M)
https://bugs.freedesktop.org/show_bug.cgi?id=70354
Priority: medium
Bug ID: 70354
Assignee: nouveau at lists.freedesktop.org
Summary: Failed to initialise context object: 2D_NVC0 (0) (for
my GeForce GT 750M)
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS:
2018 Dec 08
18
[Bug 108980] New: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
https://bugs.freedesktop.org/show_bug.cgi?id=108980
Bug ID: 108980
Summary: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2018 Dec 09
2
new GP107
https://nouveau.freedesktop.org/wiki/CodeNames/
> If you're running a recent version nouveau, you can find your chipset by doing dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate.
# dmesg | grep -i chipset
#
Not true anymore I guess.
What is the 'GP' in 'GP107' if 'NV...' are the code names?
# dmesg | grep -i nouveau
2017 Oct 18
9
[Bug 103351] New: Nouveau fails when booting with a screen connected to displayport since 13a86519202c5d119d83640d6f781f3181205d2c
https://bugs.freedesktop.org/show_bug.cgi?id=103351
Bug ID: 103351
Summary: Nouveau fails when booting with a screen connected to
displayport since
13a86519202c5d119d83640d6f781f3181205d2c
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
2017 Jan 08
2
Erros and warning using kernel 4.10-rc2
Hi guys,
I don't know if it is useful to just post some random kernel warnings/errors, but here they are:
[marcos at xfiles ~]$ journalctl -b -p 3 | grep nouveau
Jan 08 15:37:05 xfiles kernel: nouveau 0000:04:00.0: volt: couldn't find speedo value, volting not possible
Jan 08 15:37:05 xfiles kernel: nouveau 0000:04:00.0: bus: MMIO write of ffff981f FAULT at 6013d4 [ IBUS ]
Jan 08
2014 Oct 27
2
[Bug 85495] New: nouveau: xft fonts not rendered on Dell M4800 (QHD+)
https://bugs.freedesktop.org/show_bug.cgi?id=85495
Bug ID: 85495
Summary: nouveau: xft fonts not rendered on Dell M4800 (QHD+)
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2015 Mar 12
52
[Bug 89558] New: Unknown chipset error for GeForce 840M
https://bugs.freedesktop.org/show_bug.cgi?id=89558
Bug ID: 89558
Summary: Unknown chipset error for GeForce 840M
Product: xorg
Version: unspecified
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2017 Jul 23
19
[Bug 101887] New: gtx 970 black screen
https://bugs.freedesktop.org/show_bug.cgi?id=101887
Bug ID: 101887
Summary: gtx 970 black screen
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2013 Oct 09
2
Panic in nouveau on resume after 5addcf0a
After 5addcf0a (nouveau: add runtime PM support (v0.9)) I'm getting
kernel panics immediately after resuming from suspend. Unfortunately it
happens so early that I don't get any more info than the blinking
keyboard lights...
The nouveau tree still panics up to 2fb9d6c, which fails before I can
test it.
Any ideas?
Martin
$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core
2019 May 30
14
[Bug 110797] New: No video if nomodeset is not set with GTX 460
https://bugs.freedesktop.org/show_bug.cgi?id=110797
Bug ID: 110797
Summary: No video if nomodeset is not set with GTX 460
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2016 Nov 03
17
[Bug 98582] New: A regression with nouveau under wayland+xorg: laptop doesn't resume properly from suspension
https://bugs.freedesktop.org/show_bug.cgi?id=98582
Bug ID: 98582
Summary: A regression with nouveau under wayland+xorg: laptop
doesn't resume properly from suspension
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
2020 Jun 18
2
2dd4d163cd9c ("drm/nouveau: remove open-coded version of remove_conflicting_pci_framebuffers()")
Hi,
my test box won't boot 5.8-rc1 all the way but stops at
...
fb0: switching to nouveaufb from EFI VGA
<-- EOF
I've bisected it to the commit in $Subject, see below. Unfortunately, it
doesn't revert cleanly so I can't really do the final test of reverting
it ontop of 5.8-rc1 to confirm that this one is really causing it.
Any ideas?
GPU is:
[ 5.678614] fb0: switching
2012 Jun 22
1
Problem with GT520 and optimus on Fedora 17
Hello,
I have an Asus laptop, U36SD, with Optimus technology.
The discrete gpu is an NVIDIA GeForce GT 520M with 1GB DDR3 VRAM
Using Fedora 17; up to kernel 3.3.7-1 I was able to use bumblebee and
bbswitch and then running optirun command (as I could do in F16).
No more with kernel 3.4. Tried 3.4.0-1.fc17.x86_64,
3.4.2-4.fc17.x86_64 and 3.4.3-1.fc17.x86_64.
I already opened a bug against F17:
2015 Mar 07
20
[Bug 89484] New: xrandr no output to DisplayPort with GeForce GT 520M.
https://bugs.freedesktop.org/show_bug.cgi?id=89484
Bug ID: 89484
Summary: xrandr no output to DisplayPort with GeForce GT 520M.
Product: xorg
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau