<div dir="ltr">Luca,<div><br></div><div>Thank you for the reply. Really appreciate it.<br><br>I will definitely be posting logs there. Will add link information once posted.</div><div><br></div><div>Best,</div><div><br></div><div>--Xavier</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 7:07 PM, Luca Boccassi <span dir="ltr"><<a href="mailto:luca.boccassi@gmail.com" target="_blank">luca.boccassi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 2017-04-05 at 08:24 -0400, Xavier Ortiz wrote:<br>
> Package: nvidia-driver<br>
> Version: 375.39-1<br>
> Severity: important<br>
><br>
> Dear Maintainer,<br>
><br>
> *** Reporter, please consider answering these questions, where<br>
> appropriate ***<br>
><br>
>    * What led up to the situation?<br>
>    * What exactly did you do (or not do) that was effective (or<br>
>      ineffective)?<br>
>    * What was the outcome of this action?<br>
>    * What outcome did you expect instead?<br>
><br>
> *** End of the template - remove these template lines ***<br>
><br>
> was browsing on chrome, whole system froze for a couple of seconds.<br>
> Spotify in<br>
> the background continued with audio.<br>
><br>
> This was the journalctl output.<br>
><br>
> Apr 05 08:20:53 DebianDesktop /usr/lib/gdm3/gdm-x-session[<wbr>1469]: (WW)<br>
> NVIDIA(0): WAIT (2, 8, 0x8000, 0x00004bfc, 0x00004c04)<br>
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: GPU at PCI:0000:01:00:<br>
> GPU-7005a340-d9d1-0a70-4742-<wbr>2697dbda6882<br>
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: Xid (PCI:0000:01:00): 8,<br>
> Channel<br>
> 00000038<br>
> Apr 05 08:21:00 DebianDesktop /usr/lib/gdm3/gdm-x-session[<wbr>1469]: (WW)<br>
> NVIDIA(0): WAIT (1, 8, 0x8000, 0x00004bfc, 0x00004c04)<br>
> Apr 05 08:21:02 DebianDesktop kernel: NVRM: os_schedule: Attempted to<br>
> yield the<br>
> CPU while in atomic or interrupt context<br>
> Apr 05 08:21:04 DebianDesktop /usr/lib/gdm3/gdm-x-session[<wbr>1469]: (II)<br>
> SYN_DROPPED event from "Microsoft Microsoft® 2.4GHz Transceiver v9.0"<br>
> - some<br>
> input events have been lost.<br>
<br>
Hi,<br>
<br>
The nvidia kernel module is a binary blob, so there it is most likely<br>
nothing we can do about it.<br>
<br>
It was already reported upstream:<br>
<br>
<a href="https://devtalk.nvidia.com/default/topic/903841/linux/nvrm-os_schedule-
attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-context-/" rel="noreferrer" target="_blank">https://devtalk.nvidia.com/<wbr>default/topic/903841/linux/<wbr>nvrm-os_schedule-<br>
attempted-to-yield-the-cpu-<wbr>while-in-atomic-or-interrupt-<wbr>context-/</a><br>
<br>
<a href="https://devtalk.nvidia.com/default/topic/912392/-solved-xserver-freezes
-during-gaming-attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-
con/" rel="noreferrer" target="_blank">https://devtalk.nvidia.com/<wbr>default/topic/912392/-solved-<wbr>xserver-freezes<br>
-during-gaming-attempted-to-<wbr>yield-the-cpu-while-in-atomic-<wbr>or-interrupt-<br>
con/</a><br>
<br>
So I would recommend reporting this to the upstream developers.<br>
<br>
Could you please post your logs on one of those threads?<br>
<br>
Kind regards,<br>
Luca Boccassi</blockquote></div><br></div>