Mushishi. Very serious, well-told stories told in single episodes. Occasionally a younger character will come along, but it's mostly adults, and the cast outside of the MC rotates episode to episode.
"Please stop making isekai."
"OK, how about a show where a man's wife becomes an elementary school student?"
"Forget I said anything. Go make more isekai"
Thanks for digging that up. Steve's got an eye for comments, that's for sure.
Yes, all new.
The last arc was excellent. I trust they'll do just as good with this one.
Invincible build. Not mine - found it on YT or Overframe.
Armed with a Kuva Nukor running Cascadia Flare. Great weapon as-is, but add in the Furax w/ Amalgam Furax Body Count to boost your fire rate. It's a "stat stick" of sorts.
Merulina Guardian also boosts fire rate for your secondary. With such high fire rate the Nukor turns into a rapid-fire microwave capable of doing enough damage to nuke just about anything on the regular star chart and all of SP. The build is great is for solo Netracells, too. You do need to practice just tapping the fire button and not holding it, as ammo becomes a real concern (I use Carrier to mitigate this, but I still run out.)
What trips me up are the persistent Yareli-specific bugs that randomly lock out weapons and entering/exiting spoiler mode. It seems like every major update has fixes for her (they just fixed her not getting affinity while using Merulina) but there's still more. I'm hoping they can wrap it all up by the time her Prime releases.
I'd say around half of the games I play on Linux require some kind of special launch script, specific Wine version, or even different versions of Steam to run properly. It's nowhere near as simple as people make it out to be.
Hmm, good question. I'd imagine they're very similar (if not identical.) Don't know, however. Mine is self-compiled from source, but when I tried Arch's LTS package it didn't crash either.
I believe 6.6 is the current LTS version. A similar crash to the one you describe in the OP started happening to me in the 6.7 kernel. If you check my posts, I have a writeup on it.
Try the LTS kernel. Fixed a similar crash for me.
Calm before the storm. I love this arc. Dedicating so many episodes to it just like the original was the right move.
Warframe at 28 is nice. The devs acknowledge Proton and even accept bug reports for those using it. Very cool chart overall.
Spice and Wolf is a masterpiece. Excellent adaptation of the LNs. Incredible VA work on both the Japanese and English versions. Excellent writing, and some of the scene direction during the last few episodes was stunning. Really hope this hangs around to adapt the entire story.
Unlikely to help, but while you're experimenting: PROTON_LOG=1 PROTON_LOG_DIR="/tmp/" WINEDEBUG="-all" fixed some extremely annoying hangs during loading screens for me. Probably a 1 in a million chance it helps in your case, but who knows.
Picked up my tickets. Love this movie so much.
Edit: See update at end of post for more details (no solutions, but things to consider.)
As of Linux 6.7 I'm getting hard freezes that require a power cut to reset (sysrq doesn't work.) Happens at both idle and load anywhere from 5 minutes in to an hour. Running journalctl --follow and dmesg -w (both as root) reveal nothing at the time of the crash. Kernel version 6.6 continues to be 100% stable.
System:
- Distro/Kernel: Arch Linux 6.7.arch3-1
- CPU: AMD Ryzen 5 2600X
- GPU: AMD RX580 8GB via AMDGPU
- RAM: Some configuration of 16GB at 2667 MT/s.
- WM: SwayWM
I'm unsure how to go about properly reporting a bug if no errors are being generated.
Any advice?
I'm not alone on this apparently (warning, it's reddit.)
Update (01-27-2024)
I've spent the last 5 days or so bisecting the kernel from stable 6.6 to 6.7 while also touching on linux-next and 6.8rc1. I've experienced hangs on each kernel after 6.6 but under different conditions. In some cases sys-rq can rescue the system, but other times it's a hard (still errorless) crash. I believe all of these crashes can be blamed on AMDGPU given all other user reports (see: reddit thread above) mention having an AMD card.
List of similar issues
Note: Some of these are from earlier Kernel versions, but they're included since they present the same way.
- https://reddit.com/19e0y0b
- https://reddit.com/196tz6v
- https://bugzilla.kernel.org/show_bug.cgi?id=218413
- https://gitlab.freedesktop.org/drm/amd/-/issues/3124#note_2252559
Patched/Unpatched 6.8rc1 attempts
This bug report is the closest I can find on the issue. which links off to this report, which includes a patch. The patch in question is for 6.8rc1 and allows the system to stay up longer, but frequently "trips," meaning the system begins to stumble and halt for tenths of a second with accelerated video playback in my browser (qutebrowser) has to contend with load elsewhere on the system (gaming, etc.) Hangs under this patch and kernel can be rescued. However, with video acceleration disabled in the browser (and the browser not even running,) hard crashes can still occur. So either there's two new issues being brought into the fold (one to do with video accel. and the original issue mentioned in this post), or the original issue is just manifesting in different ways.
Bisecting 6.6 to 6.7
This process was taking forever because there's no reproducible situation in which the system halts. My method was to build the kernel (8 minutes) then reboot and let the system idle on a Sway session while I'm off doing something else (2 to 4 hours.) If I come back to a hard lock, then I mark the version as failed and repeat. This method let me try 2 versions of the kernel a day, not nearly enough to have this fixed quickly or easily. Due to the amount of time it takes to detect a crash, it's also possible to mark a bad commit as good (meaning it didn't crash in 2 hours, but would have in 4 or 5, etc.) I won't be continuing this.
The state of AMDGPU in general
It seems I'm lucky to have not had these issues before. A little bit of time reading issues like this show that people have been encountering problems for a while now (pre-kernel 6.7.) There are issues that have been open for years that still appear to be problems on modern systems and hardware. I'm not passing blame to anyone here, just stating that it's a miracle any of this stuff works at all given how complex the hardware is that even those who appear to be spending huge amounts of time dealing directly with it can't properly untangle what causes these faults.
TL;DR: PROTON_LOG=1 drastically improves performance in Warframe.
I've been dealing with persistent stuttering and general slowdown in Warframe, particularly when assets were loading in upon startup and especially during loading screens. Generally, once I would get into actual gameplay things would be smooth (according to both myself and Mangohud,) but going from a hub to an open world area would completely tank performance or even outright halt rendering for 30 to 40 seconds in the worst-case scenario.
I decided to start poking into what was happening and immediately found out that PROTON_LOG=1 completely solves all of these problems. The longest loading time (30 seconds or so) is now 5 seconds. Missions load almost instantaneously.
The generated log is extremely verbose at around 1MB a minute. I don't see anything obviously wrong, but then again the game is working as it should.
Why is this? Wouldn't not generating the log be faster?