[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2019-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 Martin Peres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2017-10-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 --- Comment #5 from James --- OK -- I'll try giving that a go some time this week. To be honest I'm no too bothered about actually getting this card working on an Ultra 45... -- You are receiving this mail

[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2017-10-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 --- Comment #4 from Ilia Mirkin --- https://github.com/skeggsb/nouveau/commit/0f6081089699b9f882def35ebe2b1649e77b7688 I believe this patch should fix your crash, but won't help you get the board running. If you want to

[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2017-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 --- Comment #3 from Ilia Mirkin --- OK, so looks like it very successfully creates a GT214_DISP object, and then proceeds to call nv50_display_create. This then does not trigger *any* further traces, and errors out. It

[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2017-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 --- Comment #2 from James --- Created attachment 134875 --> https://bugs.freedesktop.org/attachment.cgi?id=134875=edit debug.trace output from modprobe nouveau Requested info attached -- taken from manually doing

[Nouveau] [Bug 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp

2017-10-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103284 --- Comment #1 from Ilia Mirkin --- Looks like if we error out somewhere we never have before, and the attempt to clean things up ends up using something that hasn't been initialized yet. Can you try booting with