Bug#696554: System freezes and lockups
----- Original Message -----
> From: Steven Chamberlain <steven@pyro.eu.org>
> To: Mar Mel <marmel6942@yahoo.com>
> Cc: Sven Joachim <svenjoac@gmx.de>; "696554@bugs.debian.org" <696554@bugs.debian.org>
> Sent: Thursday, December 27, 2012 1:10 PM
> Subject: Re: Bug#696554: System freezes and lockups
>
> On 27/12/12 17:48, Mar Mel wrote:
>> One issue I have is I can't seem to install the headers I need for
> Virtualbox to
>> run.
>
> Even if you had the headers, I'm not sure VBox as packaged right now can
> compile against them. See http://bugs.debian.org/696011
I have virtualbox 4.1.24 installed locally. On my laptop (arch linux), the vbox kernel modules build
successfully against all kernel series thus far, though I'm still at 3.6.10 there, so haven't tried 3.7.x.
series yet.
Is there something obvious I'm overlooking in installing the headers for 3.7.1 from experimental?
One of my vm's is a critical need.
> This raises a new question though:
>
> Besides the kernel, what else is different about your setup now since
> yesterday? It seems the virtualbox modules will not be loaded now.
The kernel is the only change since yesterday. I'm not aware of any other non-free modules other
than virtualbox and truecrypt.
The vbox modules were loaded yesterday with the stock wheezy 3.2.0-4 and vanilla 3.4.23.
They are not loaded now since I can't build them due to the header installation issue.
> Also you mentioned truecrypt before - that has non-free kernel modules I
> think? Were those modules loaded yesterday; are they loaded now?
Truecrypt module has been loaded in all instances, including the current
3.7.1 kernel running now.
> Anything else in the kernel yesterday, especially non-free modules? I'm
> not sure how to show the kernel taint status, or get the list of modules
> (as seen in a kernel Oops) where non-free modules are tagged...
Not that I know of.
I do have a serious _new_ problem though. One of the first things I tested with this new kernel
is the suspen/resume function. When the system resumes, the GPU fan runs at full speed! I've
verified after multiple reboots and suspend/resume cycles.
Any thoughts on how to remedy this problem?
In summary:
1) the 3.7.1 kernel from experimental seems to solve this bug. I won't be able to confirm this
until at least several days of nouveaux-problem-free uptime.
2) I need to install the matching kernel headers. Help please?
3) After resume, GPU fan runs 100% speed. Help please?
Thanks Steven and Sven for followuping up on this so diligently.
Reply to: