-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
radeonkms panic on 12.2-RELEASE: Fatal trap 12: page fault while in kernel mode #256
Comments
On 12.x, you have to build from ports |
ok, rebuilt
|
I had another panic, but this time it was BUG_ON assertion failed.
Not sure why there's this warning Parts of
|
Recompiled
|
Is such contents of |
How do I build |
Just so everyone knows, this bug still occurs even with FreeBSD 12.3-RELEASE. I'm not sure exactly how to provoke it, but in my case it tends to happen once I start KDE5 and then use Firefox to do a little browsing for a while. Usually within a few minutes, it dies. I have the following hardware: vgapci0@pci0:0:1:0: class=0x030000 card=0x168b103c chip=0x96481002 rev=0x00 hdr=0x00 [drm] initializing kernel modesetting (SUMO 0x1002:0x9648 0x103C:0x168B 0x00). However I've also observed the same problem with other Radeon cards such as this one: vgapci1@pci0:131:0:0: class=0x030000 card=0x90b8103c chip=0x67711002 rev=0x00 hdr=0x00 The crashes are not consistent but always seem to happen somewhere in the drm_ioctl() path. Furthermore, I have another system with Intel HD Graphics 4000 which is also running FreeBSD 12.3 and using the same drm-fbsd12.0-kmod package, and it does not exhibit this problem. Based on a hint from here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237544 I created a new drm-fbsd11.2-kmod port from the ashes of the old one (which has been removed from the ports repo as obsolete), massaged it a little to make it compile on FreeBSD 12.3, and the driver from that package works without any panics. (I'm using it right now.) Given that the i915kms.ko driver does not crash, as an experiment I took the drm-fbsd12.0-kmod port and replaced the radeon driver directory with the older driver code from the drm-fbsd11.2-kmod directory (that is, I replaced the 4.16 radeon code with the 4.11 radeon code). However this did not fix the problem. Unfortunately there are extensive changes in both the drm and ttm modules between 4.11 and 4.16. I suspect that there is a bug in the memory management code and for some reason only the Radeon driver triggers it. (I noticed that the i915 driver does not use the ttm APIs.) But because there are so many changes it's hard to say just what's broken. My guess is that there is a locking problem somewhere. If anyone cares, they can download my hacked drm-fbsd11.2-kmod port here: https://people.freebsd.org/~wpaul/radeon/ Unpack the drm-fbsd11.2-kmod.tar.gz tarball under /usr/ports/graphics and copy the 4.11 source to /usr/ports/distfiles, then to to drm-fbsd11.2-kmod and type make. Once the build is done, remove the drm-fbsd12.0.kmod package, then do a make install to install the fbsd11.2 one instead. I hope somebody tracks this bug down eventually. It's apparently been there for a very long time. |
After upgrading FreeBSD to 12.2-RELEASE I got a random panic related to radeon:
It seems similar to #130
current process was qutebrowser
freebsd-version
12.2-RELEASE-p2My video card is Radeon HD 5450
I'm using official packages, maybe that's why sources are newer.
kldstat
The text was updated successfully, but these errors were encountered: