Bug#859634: nvidia-driver: 5-8 second freeze

[Andreas Beckmann]

Control: tag -1 - moreinfo
Control: close -1 390.67-1

On 2018-07-09 15:10, Xavier Ortiz wrote:
> Hello Andreas,
> 
> I've been using the stretch-backports nvidia-driver package, and haven't
> seen this particular issue with my system since reporting in subsequent
> binaries since using at least v390.67 .
> 
> Thanks for the followup!
> 
> Best,
> 
> --Xavier

Thanks for the information, closing the bug now.


Andreas

Bug#859634: nvidia-driver: 5-8 second freeze

[Andreas Beckmann]

Control: tag -1 moreinfo

On Fri, 7 Apr 2017 15:40:47 -0400 Xavier Ortiz  wrote:
> Luca,
> 
> Thank you for the reply. Really appreciate it.
> 
> I will definitely be posting logs there. Will add link information once
> posted.

The forum thread turned out to be a faulty card.


Is this still an issue with the latest driver (390.67) available in sid,
buster, and stretch-backports?


Andreas

Bug#859634: nvidia-driver: 5-8 second freeze

[Xavier Ortiz]

Luca,

Thank you for the reply. Really appreciate it.

I will definitely be posting logs there. Will add link information once
posted.

Best,

--Xavier

On Wed, Apr 5, 2017 at 7:07 PM, Luca Boccassi 
wrote:

> 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
> >  ineffective)?
> >* 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[1469]: (WW)
> > NVIDIA(0): WAIT (2, 8, 0x8000, 0x4bfc, 0x4c04)
> > Apr 05 08:20:59 DebianDesktop kernel: NVRM: GPU at PCI::01:00:
> > GPU-7005a340-d9d1-0a70-4742-2697dbda6882
> > Apr 05 08:20:59 DebianDesktop kernel: NVRM: Xid (PCI::01:00): 8,
> > Channel
> > 0038
> > Apr 05 08:21:00 DebianDesktop /usr/lib/gdm3/gdm-x-session[1469]: (WW)
> > NVIDIA(0): WAIT (1, 8, 0x8000, 0x4bfc, 0x4c04)
> > 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[1469]: (II)
> > SYN_DROPPED event from "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
> > - some
> > input events have been lost.
>
> Hi,
>
> 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:
>
> https://devtalk.nvidia.com/default/topic/903841/linux/nvrm-os_schedule-
> attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-context-/
>
> https://devtalk.nvidia.com/default/topic/912392/-solved-xserver-freezes
> -during-gaming-attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-
> con/
>
> So I would recommend reporting this to the upstream developers.
>
> Could you please post your logs on one of those threads?
>
> Kind regards,
> Luca Boccassi

Bug#859634: nvidia-driver: 5-8 second freeze

[Luca Boccassi]

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
>  ineffective)?
>    * 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[1469]: (WW)
> NVIDIA(0): WAIT (2, 8, 0x8000, 0x4bfc, 0x4c04)
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: GPU at PCI::01:00:
> GPU-7005a340-d9d1-0a70-4742-2697dbda6882
> Apr 05 08:20:59 DebianDesktop kernel: NVRM: Xid (PCI::01:00): 8,
> Channel
> 0038
> Apr 05 08:21:00 DebianDesktop /usr/lib/gdm3/gdm-x-session[1469]: (WW)
> NVIDIA(0): WAIT (1, 8, 0x8000, 0x4bfc, 0x4c04)
> 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[1469]: (II)
> SYN_DROPPED event from "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
> - some
> input events have been lost.

Hi,

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:

https://devtalk.nvidia.com/default/topic/903841/linux/nvrm-os_schedule-
attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-context-/

https://devtalk.nvidia.com/default/topic/912392/-solved-xserver-freezes
-during-gaming-attempted-to-yield-the-cpu-while-in-atomic-or-interrupt-
con/

So I would recommend reporting this to the upstream developers.

Could you please post your logs on one of those threads?

Kind regards,
Luca Boccassi

signature.asc
Description: This is a digitally signed message part