From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Andi Kleen <ak@muc.de>
Cc: john stultz <johnstul@us.ibm.com>,
Greg Schafer <gschafer@zip.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 Nasty Lockup
Date: Thu, 28 Sep 2006 00:06:00 +0300 [thread overview]
Message-ID: <200609280006.03500.caglar@pardus.org.tr> (raw)
In-Reply-To: <20060927205531.GB36261@muc.de>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
27 Eyl 2006 Çar 23:55 tarihinde, Andi Kleen şunları yazmıştı:
> > Ok. Good to hear you have a workaround. Now to sort out why your TSCs
> > are becoming un-synced. From the dmesg you sent me privately, I noticed
>
> On Intel it seems to happen when people overclock their systems.
This sytem is not overlocked, its a pure 2 x Intel Xeon 3GHz with HT.
> > that while you have 4 cpus, the following message only shows up once:
> >
> > ACPI: Processor [CPU1] (supports 8 throttling states)
> >
> > Does disabling cpufreq change anything?
>
> Throttling has nothing to do with cpufreq
> (at least not until you use the broken P4 throttling cpufreq
> driver, which nobody should). It is normally only used when
> the CPU overheats.
None of them is used on this system also
buildfarm ~ # lsmod
Module Size Used by
i2c_i801 7372 0
i2c_core 19968 1 i2c_i801
serio_raw 7012 0
e752x_edac 11364 0
edac_mc 21424 1 e752x_edac
i6300esb 7096 0
tg3 98116 0
sd_mod 18432 4
uhci_hcd 21900 0
ehci_hcd 29896 0
usbcore 115652 5 uhci_hcd,ehci_hcd
ata_piix 13864 2
libata 93172 1 ata_piix
scsi_mod 127304 2 sd_mod,libata
Also if needed, you can find .config at
http://cekirdek.pardus.org.tr/~caglar/config.2.6.18
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-27 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster
2006-09-26 15:41 ` Ben Duncan
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02 ` Greg Schafer
2006-09-26 22:58 ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50 ` john stultz
2006-09-27 9:45 ` S.Çağlar Onur
2006-09-27 19:14 ` john stultz
2006-09-27 20:55 ` Andi Kleen
2006-09-27 21:06 ` S.Çağlar Onur [this message]
2006-09-28 11:39 ` S.Çağlar Onur
2006-09-29 8:49 ` S.Çağlar Onur
2006-10-06 22:57 ` john stultz
2006-10-07 15:48 ` S.Çağlar Onur
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=200609280006.03500.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@muc.de \
--cc=gschafer@zip.com.au \
--cc=johnstul@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox