Marco d'Itri wrote:
On Apr 22, Matthew Lockner <mlockner@iastate.edu> wrote:Since its postinst is my means of demonstrating the problem, then of course removing the package will prevent the problem from appearing, at least in this context.You can remove it and manually run modprobe. Anyway, I am quite sure that there is some crap in your /etc/modprobe.d/, double check everything.
What kind of crap am I looking for?
And be sure to delete /etc/modprobe.conf.
My modprobe.conf still contains a line:install agpgart /sbin/modprobe radeon; /sbin/modprobe --ignore-install agpgart
I don't recall precisely what that is there for, but somehow I remember it may have been needed to make hardware graphics acceleration work properly. If we as users can't expect to be able to use this file anymore, it would be user-friendlier for the package upgrade to tell us so and state the correct alternative.
It is noteworthy that while I was obtaining the output you requested below, I had another hard lockup, and upon rebooting, there were similar problems during startup. The screen displayed the same kinds of warnings at points, and the OOM killer was stepping in at points to kill modprobe and its child processes.The warnings are harmless.
I'll grant that the system still boots up, but the OOM-killer coming up in the process is something that is definitely not supposed to happen. I have a workaround for this personally, so for my part, I'm prepared to drop the matter - but based on this and other bug reports against this package, I find it likely there is an unresolved bug in play here. Left to your discretion, of course.