RobinJ1995
commented
9 years ago Possibly related: #200
Closed Takios closed 8 years ago
RobinJ1995
commented
9 years ago Possibly related: #200
Takios
commented
9 years ago Don't think so because I can Alt+Tab in and out just fine.
Takios
commented
9 years ago Got some log output from the X Server after another crash today: https://gist.github.com/Takios/e76fab03b3142a78f5ac
Seems like it is an issue with processing input from the keyboard, if I'm reading the backtrace correctly.
thatarchguy
commented
9 years ago What you described seems to be a GPU overheat problem. This happens to me on various games, not just CS:GO. Even on Windows, Linux, and different hardware. Fractals on the screen usually. On Windows sometimes the game would exit and I'd get a "Driver crash" problem.
I can't change TTY's or anything after the crash. I am forced to reboot and restart the game.
I changed all my settings to Low and i crash 1/10 games now. I used to crash 3 times a game.
Takios
commented
9 years ago I was monitoring the temperature one time when it crashed, was sitting at 60°C.
Had to reinstall my OS due to a btrfs bug corrupting my root filesystem two days ago and have not crashed since, maybe it was related. Switched everything back to ext4 now.
Takios
commented
9 years ago Whelp, crashed again today.
Dez 05 22:10:41 mothership kernel: NVRM: GPU at PCI:0000:01:00: GPU-9dd8f36b-f875-5506-0929-f3691a5dd223 Dez 05 22:10:45 mothership kernel: NVRM: Xid (PCI:0000:01:00): 8, Channel 0000000b Dez 05 22:10:45 mothership kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Dez 05 22:10:45 mothership kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
rgarch
commented
9 years ago I can confirm this happening on my system as well. I am using Arch Linux with i3 as the window manager with AMD Radeon graphics. I'm using the proprietary graphics driver "Catalyst". This is a huge issue for me as I will have so many things running in the background when it happens.
thatarchguy
commented
9 years ago If I manually turn my fan settings to 99 on my GPU I crash way less. Here is an output from my kernel logs. It may be an issue with the drivers?
Jan 21 22:02:33 arch kernel: NVRM: GPU at PCI:0000:01:00: GPU-73086354-a3cd-86b8-7730-79738ffb1312
Jan 21 22:02:33 arch kernel: NVRM: Xid (PCI:0000:01:00): 32, Channel ID 00000007 intr 80064000
Jan 21 22:02:33 arch kernel: NVRM: Xid (PCI:0000:01:00): 32, Channel ID 00000007 intr 80024000
Jan 21 22:02:35 arch kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 21 22:02:37 arch kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 21 22:02:37 arch systemd-logind[328]: Power key pressed.
Jan 21 22:02:37 arch systemd-logind[328]: Powering Off...Yeah this is such a ridiculous problem. I just got banned for 7 days on competitive because my computer froze and I couldn't join the match again. I turned the settings down to low or medium and I don't have any issues. Then suddenly after like hours and hours of gameplay it freezes.
Takios
commented
9 years ago The problem is definately still there. Someone on the Steam forums suggested limiting the maximum fps to 120 (fps_max 120 in console). That worked for me perfectly, no crashes since. Sometimes, I forget to limit them when I start the game and everytime it crashes after some time. At least I can play competitive again with this workaround.
idk
commented
9 years ago Updated this comment April 28, with more information.
"NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context"
Same error here, happens all the time for at least a year, but only seems to happen with some source games, csgo in particular. As of some weeks ago when using the Steam Client Beta I think this issue changed from locking up the game/system (cited in this issue and many others) to now mainly only causing the sound to loop/stop like other issues here like this: https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/310
Now that the current (as of me posting) Steam Client Beta is broken under Linux (https://github.com/ValveSoftware/steam-for-linux/issues/3811) and cs:go is also broken (https://github.com/ValveSoftware/steam-for-linux/issues/3810) I had to opt out of the beta and play cs:go on the regular Steam Client and now I'm getting these crashes/freezes again like I used to instead of the sound looping like it does now in Beta Client.
To sum up, when using the regular Steam Client this issue/freeze/lockup/crash happens much more regularly as it used to in the Steam Client Beta as well until some weeks ago when this issue changed into the audio loop issue which is what happens now when play cs:go using Steam Client Beta (except it is broken currently).
I disable multicore rendering as well as setting it to headphones audio and this issue still happens all the time in Regular Steam Client the only difference is in the Beta Client it now randomly causes sound to loop where in the Regular Client it randomly locks up my system after some time playing. I haven't really tested out changing options to fix the sound issue as the past month of playing cs:go with only sound issues was a God send :+1: compared to the constant crashing and lockups it used to do (and still does in Regular Steam Client).
This issue/bug is always reproducible to me, in Beta client it causes the sound to loop and a generic alsa/ pulse audio related error ("Error: Total static audio channels have been used: 96") is sent to stderr and when using the Regular client it crashes/locks up X I can sometimes switch to another tty and then kill csgo_linux process but often it's unrecoverable, if i can recover it, it shows the "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" error in the systems logs, the sound also loops exactly the same during this crash/freeze as it does using the Beta client, except of course in the Beta client nothing freezes or locks up, only the sound is effected.
Steam Beta Client Info: Processor Information: Vendor: GenuineIntel CPU Family: 0x6 CPU Model: 0x3a CPU Stepping: 0x9 CPU Type: 0x0 Speed: 3800 Mhz 4 logical processors 4 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported
Network Information: Network Speed:
Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 3.19.3-3-ARCH X Server Vendor: The X.Org Foundation X Server Release: 11701000 X Window Manager: JWM Steam Runtime Version: steam-runtime-release_2015-01-06
Video Card: Driver: NVIDIA Corporation GeForce GTX 660 Ti/PCIe/SSE2 Driver Version: 4.5.0 NVIDIA 349.16 OpenGL Version: 4.5 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x10de DeviceID: 0x1183 Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 3840 x 1080 Primary Display Size: 20.91" x 11.77" (23.98" diag) 53.1cm x 29.9cm (60.9cm diag) Primary Bus: PCI Express 16x Primary VRAM: 2048 MB Supported MSAA Modes: 2x 4x 8x 16x
Sound card: Audio device: Realtek ALC887-VD
Memory: RAM: 7941 Mb
Miscellaneous: UI Language: English LANG: en_US.UTF-8 Microphone: Not set Total Hard Disk Space Available: 94679 Mb Largest Free Hard Disk Block: 27784 Mb
Installed software:
Recent Failure Reports:
Takios
commented
9 years ago I recently switched to the rolling release distribution of openSUSE named Tumbleweed and installed the latest beta driver from NVidia 349.16 and had no crashes since.
Tele42
commented
8 years ago The 64 bit client update has significantly changed the general stability of the game. If you are still experiencing this issue, please open a new issue report.
Hello,
I am having a problem with random hangups. They occur in every mode on every map while doing nothing specifically. It happened to me when I died, opened the scoreboard, watched someone get a kill after my death, switching weapons and even when I was just standing still. The hangups manifest as the screen standing still and the last audio in a loop. Furthermore, the system becomes unresponsive even though sound from other sources (such as VLC or Youtube videos) is still fine and input works as well with Teamspeak. Most of the times I have to reboot the PC with SysRQ but now I finally got to close it (with hammering AltF4) and could grab the output from Steam when the hangup occured.
My system: http://pastebin.com/zSN5GW75
Greetings Takios