From: David Johnson <dj@david-web.co.uk>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: Hardware bug or kernel bug?
Date: Mon, 16 Oct 2006 15:32:38 +0100 [thread overview]
Message-ID: <200610161532.38663.dj@david-web.co.uk> (raw)
In-Reply-To: <20061016102500.GA1709@ff.dom.local>
On Monday 16 October 2006 11:25, Jarek Poplawski wrote:
>
> Was this lock-up effect visible during above 2.6.19-rc1 tests?
No, I've not seen anything in Linux other than the reboots, which are instant
without any preceding lock-up.
> If not I'd try to continue linux debbuging:
> - is 2.6.19-rc1 working with "normal" config (use make oldconfig
> to "upgrade" .config),
With 2.6.19-rc1 and a normal config, I get the reboots as usual.
> - is 2.6.17 working with "minimal" config (use make oldconfig),
Yes.
> - changing one or two options at a time try to find which one makes
> the effect returns (acpi, smp...).
I've found the culprit - CPU Frequency Scaling.
With it enabled I get the reboots, with it disabled I don't. That's the same
with every kernel version I've tried (2.6.19-rc1+rc2, 2.6.17.13 & Centos'
2.6.9) The system was using the p4-clockmod driver and the ondemand governor.
I'm still not sure exactly what the problem is - the reboots only happen in
the circumstances I've mentioned and are not triggered by changes in clock
speed alone - but disabling cpufreq seems to make it go away...
Thanks for your help,
David.
next prev parent reply other threads:[~2006-10-16 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:53 Hardware bug or kernel bug? David Johnson
2006-10-12 17:20 ` Arjan van de Ven
2006-10-12 19:13 ` Linus Torvalds
2006-10-13 9:20 ` David Johnson
2006-10-13 8:56 ` Jarek Poplawski
2006-10-13 9:20 ` David Johnson
2006-10-13 10:58 ` Jarek Poplawski
2006-10-13 11:56 ` David Johnson
2006-10-13 13:06 ` Jarek Poplawski
2006-10-13 16:24 ` David Johnson
2006-10-13 17:11 ` Alan Cox
2006-10-16 10:25 ` Jarek Poplawski
2006-10-16 14:32 ` David Johnson [this message]
2006-10-17 7:10 ` Jarek Poplawski
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=200610161532.38663.dj@david-web.co.uk \
--to=dj@david-web.co.uk \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox