bugzilla-daemon at freedesktop.org
2014-Nov-20 14:50 UTC
[Nouveau] [Bug 86491] New: Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Bug ID: 86491 Summary: Nouveau crash when shutting down Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: jarlgjessing at gmail.com QA Contact: xorg-team at lists.x.org Created attachment 109755 --> https://bugs.freedesktop.org/attachment.cgi?id=109755&action=edit Image showing the screen on shutdown When doing init 0, or shutdown from KDE, I end up with a kernel dump :-( I'm unable to stop this from happening so, I cannot get into Windows either. I tried openSUSE 13.2 just as it came out and thought that this problem was due to the live image, and therefore tried again today, using the DVD image. Same problem :-( Unfortunately there are no longer any /var/log/messages or the like, so I don't know what to attach. And the guides as to where to locate these information (which I could before 13.2) is not as I see, easy to find. I have also tried with openSUSE's HEAD version, which was a 3.18.xx version. Same problem The problem arises when shutting down or sleeping. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/5e9c4d3c/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 14:51 UTC
[Nouveau] [Bug 86491] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Jarl E. Gjessing <jarlgjessing at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|medium |high Hardware|Other |x86-64 (AMD64) OS|All |Linux (All) Severity|normal |critical -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/f90a9a2a/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 14:54 UTC
[Nouveau] [Bug 86491] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #109755|text/plain |image/jpeg mime type| | -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/eee0cc74/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 14:58 UTC
[Nouveau] [Bug 86491] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|high |medium Severity|critical |normal --- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> --- Attach a kernel log (dmesg) after boot, that should contain a lot of important info about your hardware. Also what does 'lspci -nn -d 10de:' produce? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/f8085f3c/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 15:01 UTC
[Nouveau] [Bug 86491] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 --- Comment #2 from Jarl E. Gjessing <jarlgjessing at gmail.com> --- I fully respect that not all issues are critical etc. (we all think it is in our own eyes) But when the machines renders dead on shutdown, I think it is a critical issue? Or at least thats just what I feel. lspci says: 01:00.0 3D controller [0302]: NVIDIA Corporation GK106M [GeForce GTX 765M] [10de:11e2] (rev ff) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/fda9c85c/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 15:08 UTC
[Nouveau] [Bug 86491] [NVE6] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Nouveau crash when shutting |[NVE6] Nouveau crash when |down |shutting down --- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Jarl E. Gjessing from comment #2)> I fully respect that not all issues are critical etc. (we all think it is in > our own eyes) > But when the machines renders dead on shutdown, I think it is a critical > issue? > Or at least thats just what I feel.Yeah, so if you have a real support organization backing a bugtracker, these things have meaning. When you have 1 or 2 people looking at bugs, markers like "critical" are more annoying than useful, amusingly enough making it _harder_ to see things since they become irregular on the giant mega-bug-list. Having separate importance and severity markers is also incredibly confusing. In any case, at this point, this is an issue that affects just you, as far as we know, so unless your thing is literally going up in smoke, there's nothing that can be going on that makes it critical -- I think of critical as like "affects 75%+ of nouveau user base". -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/ff7a6208/attachment-0001.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 15:09 UTC
[Nouveau] [Bug 86491] [NVE6] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 --- Comment #4 from Jarl E. Gjessing <jarlgjessing at gmail.com> --- Created attachment 109758 --> https://bugs.freedesktop.org/attachment.cgi?id=109758&action=edit dmesg output -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/a149fcf6/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 15:24 UTC
[Nouveau] [Bug 86491] [NVE6] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 --- Comment #5 from Takashi Iwai <tiwai at suse.de> --- (In reply to Ilia Mirkin from comment #3)> (In reply to Jarl E. Gjessing from comment #2) > > I fully respect that not all issues are critical etc. (we all think it is in > > our own eyes) > > But when the machines renders dead on shutdown, I think it is a critical > > issue? > > Or at least thats just what I feel. > > Yeah, so if you have a real support organization backing a bugtracker, these > things have meaning. When you have 1 or 2 people looking at bugs, markers > like "critical" are more annoying than useful, amusingly enough making it > _harder_ to see things since they become irregular on the giant > mega-bug-list. > > Having separate importance and severity markers is also incredibly > confusing. In any case, at this point, this is an issue that affects just > you, as far as we know, so unless your thing is literally going up in smoke, > there's nothing that can be going on that makes it critical -- I think of > critical as like "affects 75%+ of nouveau user base".This is getting off-topic and a typical bikeshedding, so let's stop it :) But here, I just give an example how these two fields work on SUSE bugzilla: These two fiedls are seen as "priority" and "severity". The former is the field where only developer or manager touches as the priority of the task, while the latter describes how severe the bug itself. They can be totally decopuled; for example, in this bug, the severity can be critical as a system crashes, but its priotiy can be low as it hits only few people. Of course, the usage of such fields pretty depends and is free for other interpretation. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/1ca65420/attachment.html>
bugzilla-daemon at freedesktop.org
2014-Nov-20 15:37 UTC
[Nouveau] [Bug 86491] [NVE6] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 --- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> --- [ 10.538216] nouveau E[ PGRAPH][0000:01:00.0] grctx template channel unload timeout [ 10.538271] nouveau E[ PGRAPH][0000:01:00.0] failed to construct context [ 10.538273] nouveau E[ PGRAPH][0000:01:00.0] init failed, -16 This doesn't fill me with confidence... [ 33.767942] nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM] [ 36.435207] pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xe0 [nouveau] returns -16 and that's not much better. What happens if you boot with nouveau.runpm=0 Note that this will cause the secondary (nvidia) gpu to no longer auto-suspend when not in use. Oh, btw, are you using something like bumblebee? (You shouldn't be.) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141120/b452cabe/attachment.html>
bugzilla-daemon at freedesktop.org
2019-Dec-04 08:52 UTC
[Nouveau] [Bug 86491] [NVE6] Nouveau crash when shutting down
https://bugs.freedesktop.org/show_bug.cgi?id=86491 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #7 from Martin Peres <martin.peres at free.fr> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/151. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20191204/6b4a87c0/attachment-0001.html>
Maybe Matching Threads
- Setting @request.env["HTTP_REFERER"] in an integration test
- Being strict on differentiating between IEC prefixes and SI prefixes.
- possible bug: using assert_recognizes with extras
- Prepared SQL statements
- Suggestion for improving value_to_boolean column conversion