Created attachment 164522 [details]
when the kernel mode switches to radeonkms, I get a reboot. If I comment out radeonkms, and the FW, we stay up. If I kldload the fw and the radeonkms module, we get a failed to initialize cp(-22). message, but we switch.
loader.conf attached (with the 2 radeon lines commented out.
This had been working just fine....
Created attachment 164523 [details]
I had been running @r292000 before this.
I'm running r292448 and don't see this behavior. Next week, I will update to a more recent kernel to try to reproduce the problem.
On your side, could you please try to isolte which commit causes the regression?
I'll try tonight when I am home again.
I updated to r292665 tonight and everything is working fine.
Hrm. Updated to latest (292675) and am compiling -- will check back.
Assuming it still fails, what can I get to help here?
Can you lookup the first commit that fails?
You could use "git bisect" for that purpose, it helps a lot.
Still Failing for me. I do NOT have a git checkout either.
I also don't see anything in a quick search of this months commits for drm or kms.
You could lookup the failing commit by dichotomy with Subversion too; this is what "git bisect" does.
The problem is in the kernel, so you can prepare the initial list of commits to test using "svn log" in sys/ to get all the revisions between r292000 and r292637 (the commits known to be good and bad).
Now, test the commit in the middle of this list, let's say r292xxx. If it fails, test the next commit in the middle between r292000 and r292xxx, otherwise, test the commit in the middle between r292xxx and 292637, and so on.
Between those two revisions, there were two changes to TTM, the memory manager for Radeon (r292373 and r292469). I don't know if they could be the culprit. If you want to test them first, try those and the revisions before.
I'm not sure what to suggest otherwise.
we're heading out of town for Christmas, I'll try to do this when we get back on Saturday.
Thank you very much! Merry Christmas!