Can't kill chrome pid

D

drhowarddrfine

Code: 
PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU COMMAND
 2841 xxx           2 141    0   820M   363M CPU4     4   4:28  99.98% chrome

I tried kill 2841 from top but it does nothing. I tried killall chrome which killed all the other pids that aren't shown above. Also kill -9 2841 and all the other numbers there to no avail.
 
When I restart the system, I get a constant scroll of
Code: 
lkpi_vmf_insert_pfn_prot_locked page rename failed:page is mapped

It continues a fast scroll for maybe 10 seconds before it shuts down. This is 15.0r4-RELEASE intel onboard graphics driver AMD64
 
drhowarddrfine said:
It appears that drm-612-kmod was either upgraded (most likely) or installed on my system (I lost track) which has caused my issue. I removed it and installed
drm-66-kmod and all my issues went away. There is a bug report from a few weeks ago about this same or similar issue.
Click to expand...
drhowarddrfine, thanks for linking the post.
Yes, there was an update on latest/current branches. You can switch to quarterly to use the previous version in the meantime and see if that helps.
As for the issue, there were changes done due to some code that moved from the driver to linuxkpi, it is supposed to work with both the old interfaces and the new ones but maybe not.
Open a ticket on github ( https://github.com/freebsd/drm-kmod/issues ) and link the bugzilla bug report. From experience I've noticed that the people working on drm are more likely to pay attention to github issues than bugzilla issues.

Edited to add that the 6.6 package was also updated.

So, question, which version are you running and what 6.12 package was actually installed? (drm-612-kmod-6.12.110.1501000_3 or drm-612-kmod-6.12.110.1501503_3)
 
I'm kind of hazy about what was installed cause I went on vacation at that time and rushed to get the upgrade done but it happened after a pkg upgrade. I don't recall install 6.12, and I'm sure upgrade didn't do that on its own, but I remember hesitating before upgrading it.

drm-66-kmod version: 6.6.25.1501000_11
 
drhowarddrfine said:
I'm kind of hazy about what was installed cause I went on vacation at that time and rushed to get the upgrade done but it happened after a pkg upgrade. I don't recall install 6.12, and I'm sure upgrade didn't do that on its own, but I remember hesitating before upgrading it.

drm-66-kmod version: 6.6.25.1501000_11
Click to expand...
if you had drm-kmod installed instead of the specific version, that could have been the cause of the installation of 6.12 (as the default changed from 6.6 to 6.12).

As for the specific bug, no ideia really, that package should have the linuxkpi changes also so that makes it an issue specific to the 6.12 branch. Can you try with the quarterly branch install drm-612-kmod? If that works the issue is in the new upgrade to the 110 upstream patch version (and needs addressing).
 
You must log in or register to reply here.
Back
Top