similar to: [Bug 82714] [G84] nouveau fails to properly initialize GPU

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #10 from Bruno <bonbons at sysophe.eu> --- (In reply to Bruno from comment #9) > Created attachment 114735 [details] > 4.0-rc6 dmesg of nouveau loading (debug, runpm=0) The first BUG happens in evo_wait() at line 420 of nv50_display.c Seems like dmac->ptr[put] is bad. 413: evo_wait(void *evoc, int nr) 414: { 415:

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #7 from Bruno <bonbons at sysophe.eu> --- Created attachment 114730 --> https://bugs.freedesktop.org/attachment.cgi?id=114730&action=edit dmesg with 3.19 Sorry for rather late reply, so no issue you being slow too. (In reply to Pierre Moreau from comment #6) > Sorry, I didn't had much time to look into it...

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #8 from Bruno <bonbons at sysophe.eu> --- Created attachment 114731 --> https://bugs.freedesktop.org/attachment.cgi?id=114731&action=edit dmesg with 3.19 but runpm=0 Same kernel, kernel log starting at loading nouveau with `modprobe nouveau debug=debug runpm=0` and running Xorg on top of it: Xorg.0.log tail: [

https://bugs.freedesktop.org/show_bug.cgi?id=82714 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nouveau: fails to properly |[G84] nouveau fails to |initialize GPU |properly initialize GPU -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #21 from Pierre Moreau <pierre.morrow at free.fr> --- I tested with latest Nouveau and latest drm-next as of yesterday (4.6-rcX), with the G84 alongside a GM206; the GM206 was the one driving the screen. Launching weston or kmscon works, but starting X makes the whole computer freeze (no responce on key presses, power button

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #22 from Pierre Moreau <pierre.morrow at free.fr> --- And using the G84 for driving the screen results in the display receiving no signal from the GPU (over VGA (using a VGA->DVI adapter) or HDMI). In the logs, the card did found the screen and initialised a fb of the correct resolution; they are no errors to be found.

https://bugs.freedesktop.org/show_bug.cgi?id=82714 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |FIXED --- Comment #2 from Pierre Moreau

https://bugs.freedesktop.org/show_bug.cgi?id=82714 Bruno <bonbons67 at internet.lu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #3 from Bruno <bonbons67 at

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #4 from Pierre Moreau <pierre.morrow at free.fr> --- (In reply to Bruno from comment #3) > Are you testing on a system where the GeForce 8600 GTS is a secondary GPU > and not initialized by VBIOS? I wasn't, you're right. I'll plug my HD6870 along and see if I can debug this. Does it only go wrong when

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #6 from Pierre Moreau <pierre.morrow at free.fr> --- Sorry, I didn't had much time to look into it... I'm currently tracking some similar problems on my G96, which is a secondary GPU. Hopefully, if I manage to solve it, the patch will help you too. (In reply to Bruno from comment #5) > After fresh boot: > echo 1

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #23 from Pierre Moreau <pierre.morrow at free.fr> --- s/they are no/there are no --" -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=82714 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #25 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #24 from Pierre Moreau <pierre.morrow at free.fr> --- With the GM206 driving the display, no special Nouveau options, I get this upon starting X: [ 545.904188] vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=none:owns=none [ 548.670462] nouveau 0000:04:00.0: timeout at

https://bugs.freedesktop.org/show_bug.cgi?id=82714 --- Comment #5 from Bruno <bonbons67 at internet.lu> --- After fresh boot: echo 1 > /sys/bus/pci/devices/0000\:01\:00.0/reset Kernel log for modprobe nouveau debug=0xff: 2014-12-13 18:55:58.978720 +0100 [ 108.870465] nouveau 0000:01:00.0: enabling device (0004 -> 0007) 2014-12-13 18:55:58.981262 +0100 [ 108.873035] nouveau [

https://bugs.freedesktop.org/show_bug.cgi?id=82714 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|DRM/other |Driver/nouveau Version|XOrg git

https://bugs.freedesktop.org/show_bug.cgi?id=87552 Bug ID: 87552 Summary: [NV1A] 3.18.1 BUG on modprobe nouveau in drivers/gpu/drm/nouveau/core/core/event.c:42 Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium

On Mon, Nov 25, 2019 at 9:08 AM Bruno Prémont <bonbons at sysophe.eu> wrote: > > Hi, > > Trying a new kernel on old [NV04] system I get tons of > nouveau 0000:01:00.0: gr: intr 00000001 [NOTIFY] nsource 00000040 > [ILLEGAL_MTHD] nstatus 00004000 [PROTECTION_FAULT] ch 0 > [DRM] subc 3 class 004a mthd 02fc data 00000003 > errors when operating on console. >

https://bugs.freedesktop.org/show_bug.cgi?id=94725 --- Comment #13 from Karol Herbst <freedesktop at karolherbst.de> --- (In reply to Rashed Abdel-Tawab from comment #10) > Created attachment 122654 [details] > dmesg using tentative fix > > Alexandre, using the tentative fix you uploaded it switches GPUs properly > now. Here is the dmesg from that since there are still some

This is not a known issue. No GPU support has been dropped from nouveau (thus far, nor ever, I expect). Did you update anything other than the kernel? Cheers, -ilia On Thu, Jan 30, 2020 at 7:27 AM Dave <daveh1960 at gmail.com> wrote: > Not sure if this is the correct forum for this question / issue so please > feel free to redirect me to an appropriate list. > > My driver

Thanks for replying, below are the only items I installed when I had the problem last time The sequence of events were: I took an LVM snap I initially installed all the pending packages and had the issue I reverted back to before the lvm snap, made sure I didn't have the issue I installed everything but the kernel, made sure I didn't have the issue and removed the snap Then