Bug#859634: nvidia-driver: 5-8 second freeze
luca.boccassi at gmail.com
Wed Apr 5 23:07:21 UTC 2017
On Wed, 2017-04-05 at 08:24 -0400, Xavier Ortiz wrote:
> Package: nvidia-driver
> Version: 375.39-1
> Severity: important
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where
> appropriate ***
> * What led up to the situation?
> * What exactly did you do (or not do) that was effective (or
> * What was the outcome of this action?
> * What outcome did you expect instead?
> *** End of the template - remove these template lines ***
> was browsing on chrome, whole system froze for a couple of seconds.
> Spotify in
> the background continued with audio.
> This was the journalctl output.
> Apr 05 08:20:53 DebianDesktop /usr/lib/gdm3/gdm-x-session: (WW)
> NVIDIA(0): WAIT (2, 8, 0x8000, 0x00004bfc, 0x00004c04)
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: GPU at PCI:0000:01:00:
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: Xid (PCI:0000:01:00): 8,
> Apr 05 08:21:00 DebianDesktop /usr/lib/gdm3/gdm-x-session: (WW)
> NVIDIA(0): WAIT (1, 8, 0x8000, 0x00004bfc, 0x00004c04)
> Apr 05 08:21:02 DebianDesktop kernel: NVRM: os_schedule: Attempted to
> yield the
> CPU while in atomic or interrupt context
> Apr 05 08:21:04 DebianDesktop /usr/lib/gdm3/gdm-x-session: (II)
> SYN_DROPPED event from "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
> - some
> input events have been lost.
The nvidia kernel module is a binary blob, so there it is most likely
nothing we can do about it.
It was already reported upstream:
So I would recommend reporting this to the upstream developers.
Could you please post your logs on one of those threads?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part
More information about the pkg-nvidia-devel