[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#515125: marked as done (general: cpu frequency scalling crashes my system)

Your message dated Mon, 17 Aug 2009 19:01:55 +0200
with message-id <20090817170155.GD21492@inutil.org>
and subject line Re: Bug#515125: general: cpu frequency scalling crashes my system
has caused the Debian Bug report #515125,
regarding general: cpu frequency scalling crashes my system
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
515125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515125
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: general
Severity: important

i am not sure what exacly causes the problem. it maight be cpufreq, or kernel
or maybe something else (or CPU Frequency Scalling Monitor applet in GNOME
which is rather in doubt).

when enabled "AMD Quiet'n'cool" in BIOS (the CPU frequency scalling) and have
installed CPUFreq package, it very often happens that system crashes totally.

it happens estimatelly 0.5-3 times per a day (0.5 means once per two days) that
my machine freezez (and the only way left is hard reset), or resets suddenly,
or my X server crashed (that happen once) and some stack-trace was in console.
one moment later machine had 'self-reset', so i couldn't note that stack.

i am observing the problem for year or even longer (on few different kernels),
but reporting now because i have just discovered that crashes are caused by
frequency-scalling. when "AMD Quiet'n'cool" is disabled in BIOS, nothing
bad happens to the system, i.e. no crashes are occuring.

crashes happen when doing some suddenly actions which need to
rise-up cpu-frequency, such as compiling, or starting application that
needs much of cpu-resources at a time. when system is just up, but has
no any user action, or when watching movie, nothing bad happens.

cheers.


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Mon, Aug 17, 2009 at 09:48:26AM +0200, Mark Poks wrote:
> On Tue, Jul 28, 2009 at 8:30 PM, Mark Poks <markpoks@gmail.com> wrote:
> 
> > >Mark, does the issue still manifest itself with more recent kernel
> > >versions?
> > >
> > >Cheers,
> > >       Moritz
> >
> > when i reduced memory speed from 800 to 667 MHz it seem to not suspending
> > any longer. maybe it's hardware fault in fact?
> >
> > but i have just updated my kernel today, raised memory speed to 800 MHz
> > again and i will try to suspend machine and report observations in a few
> > days.
> >
> > cheers,
> > Mark
> >
> > After kernel updated, problem still occurs - once per few days machine
> hangs-up. when reduced memory speed to 667 MHz every is ok. i'm starting to
> believe this is mainboard problem, not the kernel.

This indeed sounds like a hardware problem, either in your mainboard
or in your RAM chips. Since it might be a mainboard-related timing problem
you could try to upgrade the firmware or your mainboard (if the device allows
it).

I'm closing the bug, if further testing indicates that this really is a
kernel problem, please reopen.

Cheers,
        Moritz

--- End Message ---
Reply to: