Bug 90851
Summary: | radeonsi on pitcairn: nine and skyrim - unable to handle kernel paging request | ||
---|---|---|---|
Product: | Drivers | Reporter: | Christoph Haag (haagch.christoph) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.19-rc2 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | full dmesg |
Description
Christoph Haag
2015-01-06 11:10:37 UTC
Can you try decoding the backtrace with scripts/decode_stacktrace.sh from the kernel tree? Does it only happen with a 3.19 kernel, or also with older ones? I'll have to build a kernel with symbols later and replicate it. It sometimes takes even a few hours of gameplay to have this happen, so it could take some time. But I am relatively sure that it did not happen with 3.18. Hm, interesting. I compiled 3.19-rc4 with debug symbols. I'm also testing Tom Stellard's VGPR register spilling llvm and mesa branches. After a while of playing skyrim I got the familiar hang where skyrim just freezes, but I did NOT get "BUG: unable to handle kernel paging request" in the system log. Instead I got this in the terminal from which I started skyrim: radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 I'm not very good with the wine debugger... Attaching to the TESV.exe process and then getting a backtrace shows: Wine-dbg>bt Backtrace: =>0 0xf7702bee __kernel_vsyscall+0xe() in [vdso].so (0x7eada510) 1 0xf7514e02 __lll_lock_wait+0x21() in libpthread.so.0 (0x7eada510) 2 0xf750f5ae __GI___pthread_mutex_lock+0x8d() in libpthread.so.0 (0x7eada510) 3 0xed73ba1d in d3dadapter9.so.1 (+0x128a1c) (0x7eada510) 4 0x0069df9c in tesv (+0x29df9b) (0x7eada510) 5 0xfff0e400 (0x526077e9) I would try to find out where exactly in d3dadapter9.so.1 this happens but I don't get how to properly attach winedbg --gdb and addr2linux didn't give a line with code, so I probably used it wrong. (In reply to Christoph Haag from comment #3) > radeon: mmap failed, errno: 12 That's ENOMEM, so it looks like the kernel runs out of memory. Maybe a leak somewhere. (In reply to Christoph Haag from comment #2) > But I am relatively sure that it did not happen with 3.18. Can you bisect? I didn't answer for a while because I didn't have too much time, but also because it hasn't happened anymore. I think it has meanwhile been fixed, wherever the problem was. |