Ubuntu
nvidia-common package

system locks up or powers down randomly, since 22-14 kernel update

Bug #152202 reported by Ryan Budney
4
Affects Status Importance Assigned to Milestone
nvidia-common (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since installing the 22-14 kernel, my system will randomly either power-down or seize. I've had it power-down 3 times in the past 4 days, and it seized-up once today.

At the time of the power-downs and seizures, I was running ktorrent. I was also running povray for 2 of the 4 episodes.

I asked a question about this earlier, which has no responses. Since it's been persistent and survived a couple dist-upgrades, I think it deserves to be called a bug.

Here is my old question with more details:

https://answers.launchpad.net/ubuntu/+question/14972

See original description
Ryan Budney (delooper)
description: updated
Revision history for this message
Michael Nagel (nailor) wrote :

are you still havubg trouble?

Revision history for this message
Ryan Budney (delooper) wrote : Re: [Bug 152202] Re: system locks up or powers down randomly, since 22-14 kernel update

Hi Michael,

It's still a problem but I have a better understanding of it now. It's
something in the standard screensaver that's been causing the problem. I
disabled the screensaver and all has been well since. It must be some
aspect of NVidia's "native" drivers that is buggy, and this buggy part of
the driver seems to only be called by the screensaver.

-ryan

On Mon, August 4, 2008 10:05 am, Michael Nagel wrote:
> are you still havubg trouble?
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
> Status: New => Incomplete
>
> --
> system locks up or powers down randomly, since 22-14 kernel update
> https://bugs.launchpad.net/bugs/152202
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

Ben Collins (ben-collins)
Changed in linux-restricted-modules:
status: Incomplete → New
Revision history for this message
Ryan Budney (delooper) wrote :

Hey, I've had a recent discovery on this bug. When running ktorrent recently, I noticed that ktorrent spawned instances of mplayer that was using 100% of system resources. My laptop was overheating and it eventually locked-up. I rebooted, loaded up ktorrent again and the process began over again. No amount of kill -9 ### helped, as mplayer was being launched several times a second by the time I knew its process number another one had loaded. A little googling around and I figured out that it's *trackerd* that's spawning mplayer, not ktorrent. So I went into System->Preferences->Indexing Preferences and turned off all tracker features. I killed trackerd too. All is going well now.

So you might want to check to see if your ktorrent download is causing trackerd to strangle your computer.

Alberto Milone (albertomilone)
Changed in nvidia-common:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.