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 <[email protected]> http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
Attachment:
pgpk9qhH9AVPX.pgp
Description: PGP signature
- References:
- 2.6.18 Nasty Lockup
- From: Greg Schafer <[email protected]>
- Re: 2.6.18 Nasty Lockup
- From: john stultz <[email protected]>
- Re: 2.6.18 Nasty Lockup
- From: Andi Kleen <[email protected]>
- 2.6.18 Nasty Lockup
- Prev by Date: RE: GPLv3 Position Statement
- Next by Date: Re: Uses for memory barriers
- Previous by thread: Re: 2.6.18 Nasty Lockup
- Next by thread: Re: 2.6.18 Nasty Lockup
- Index(es):