All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "MPhil. Emanoil Kotsev" <Emanoil.Kotsev@fincom.at>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: kernel 3.11.6 general protection fault
Date: Sun, 17 Nov 2013 16:06:07 +0100	[thread overview]
Message-ID: <20131117150607.GF27323@pd.tnic> (raw)
In-Reply-To: <201311171545.35217.Emanoil.Kotsev@fincom.at>

On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote:
> this is also true - which makes me sad as the notebook was working
> thgreat in e past 7y

Hmm, maybe it is heading slowly for the eternal hunting fields... :-)

> > What kind of upgrade exactly did you do to a laptop?
> 
> I was using debian squeeze with trinity desktop (KDE 3.5.10) and upgraded to 
> debian wheeze with TDE (3.5.13)

Oh ok, so I thought you were talking about a hw upgrade, like adding
more RAM, hew hdd, etc.

Ok, can you try this: boot without X and try overloading the machine on
the console, i.e. do

while true; do make clean && make -j64; done

or similar in your kernel repository. Does it trigger then?

Although I can't imagine how a software upgrade would cause the
overheating... :-\.

> > Can you revert the upgrade and see whether it still happens?
> This would be hard - no impossible as I have a backup but it will be
> time consuming

You could try booting a distro from a livecd and see any change there...

> $ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:        +47.5°C  (crit = +126.0°C)

That's some ACPI timezone thing. So what happens if you do

$ watch -n 1 sensors

and you incur the load? Do you hit the critical temperature?

> grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:1:ondemand
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:1:10000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1:2000000 1667000 1333000 1000000
> /sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:1:0 1
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:1:acpi-cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:1:ondemand powersave performance conservative userspace
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1:<unsupported>

Yeah, I don't see anything wrong with that output.

> I could try this. I guess this assumes I have to have another machine
> running in paralell, but this can be arranged with a little effort

Yep.

> Thanks for the hints. As I never had to do with overheating or
> similar issues, your help is very precious to me. Unfortunately we
> have a little child on board and time is limitted :) to a couple of
> hours daily, where I can work at home which means even less time for
> debugging. But I never give up. I just want to be sure that it is not
> a hardware issue

No worries, take care of the child first - the laptop and everyone else
can wait :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "MPhil. Emanoil Kotsev" <Emanoil.Kotsev@fincom.at>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Intel-gfx] kernel 3.11.6 general protection fault
Date: Sun, 17 Nov 2013 16:06:07 +0100	[thread overview]
Message-ID: <20131117150607.GF27323@pd.tnic> (raw)
In-Reply-To: <201311171545.35217.Emanoil.Kotsev@fincom.at>

On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote:
> this is also true - which makes me sad as the notebook was working
> thgreat in e past 7y

Hmm, maybe it is heading slowly for the eternal hunting fields... :-)

> > What kind of upgrade exactly did you do to a laptop?
> 
> I was using debian squeeze with trinity desktop (KDE 3.5.10) and upgraded to 
> debian wheeze with TDE (3.5.13)

Oh ok, so I thought you were talking about a hw upgrade, like adding
more RAM, hew hdd, etc.

Ok, can you try this: boot without X and try overloading the machine on
the console, i.e. do

while true; do make clean && make -j64; done

or similar in your kernel repository. Does it trigger then?

Although I can't imagine how a software upgrade would cause the
overheating... :-\.

> > Can you revert the upgrade and see whether it still happens?
> This would be hard - no impossible as I have a backup but it will be
> time consuming

You could try booting a distro from a livecd and see any change there...

> $ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:        +47.5°C  (crit = +126.0°C)

That's some ACPI timezone thing. So what happens if you do

$ watch -n 1 sensors

and you incur the load? Do you hit the critical temperature?

> grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:1:ondemand
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:1:10000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1:2000000 1667000 1333000 1000000
> /sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:1:0 1
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:1:acpi-cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:1:ondemand powersave performance conservative userspace
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1:<unsupported>

Yeah, I don't see anything wrong with that output.

> I could try this. I guess this assumes I have to have another machine
> running in paralell, but this can be arranged with a little effort

Yep.

> Thanks for the hints. As I never had to do with overheating or
> similar issues, your help is very precious to me. Unfortunately we
> have a little child on board and time is limitted :) to a couple of
> hours daily, where I can work at home which means even less time for
> debugging. But I never give up. I just want to be sure that it is not
> a hardware issue

No worries, take care of the child first - the laptop and everyone else
can wait :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-11-17 15:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 19:58 kernel 3.11.6 general protection fault MPhil. Emanoil Kotsev
2013-11-13 19:58 ` MPhil. Emanoil Kotsev
2013-11-13 20:09 ` Daniel Vetter
2013-11-13 20:09   ` [Intel-gfx] " Daniel Vetter
2013-11-13 20:33   ` Borislav Petkov
2013-11-13 20:33     ` [Intel-gfx] " Borislav Petkov
2013-11-13 21:19     ` MPhil. Emanoil Kotsev
2013-11-13 21:19       ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-11-17 11:35     ` MPhil. Emanoil Kotsev
2013-11-17 11:35       ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-11-17 12:07       ` Borislav Petkov
2013-11-17 12:07         ` [Intel-gfx] " Borislav Petkov
2013-11-17 14:45         ` MPhil. Emanoil Kotsev
2013-11-17 14:45           ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-11-17 15:06           ` Borislav Petkov [this message]
2013-11-17 15:06             ` Borislav Petkov
2013-11-17 16:45             ` MPhil. Emanoil Kotsev
2013-11-17 16:45               ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-11-17 20:05               ` Borislav Petkov
2013-11-17 20:05                 ` [Intel-gfx] " Borislav Petkov
2013-11-19  9:21                 ` MPhil. Emanoil Kotsev
2013-11-19  9:21                   ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-12-18 20:59                 ` MPhil. Emanoil Kotsev
2013-12-18 20:59                   ` [Intel-gfx] " MPhil. Emanoil Kotsev
2013-12-18 21:22                   ` Borislav Petkov
2013-12-18 21:22                     ` [Intel-gfx] " Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31 14:00 emanoil.kotsev
2013-10-31 14:37 ` Borislav Petkov
2013-10-31 14:37   ` Borislav Petkov
2013-10-31 15:52   ` emanoil.kotsev
2013-10-31 16:44     ` Borislav Petkov
2013-10-31 16:44       ` Borislav Petkov
     [not found]       ` <201311011018.49670.Emanoil.Kotsev@fincom.at>
2013-11-01 11:27         ` Borislav Petkov
2013-11-01 11:27           ` Borislav Petkov
2013-11-01 18:08           ` MPhil. Emanoil Kotsev
2013-11-01 18:08             ` MPhil. Emanoil Kotsev
2013-10-31 13:34 emanoil.kotsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131117150607.GF27323@pd.tnic \
    --to=bp@alien8.de \
    --cc=Emanoil.Kotsev@fincom.at \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.