* 2.6.19-rc4-mm1: noidlehz problems
@ 2006-11-01 12:23 Pavel Machek
2006-11-01 12:55 ` Pavel Machek
2006-11-01 13:02 ` Arjan van de Ven
0 siblings, 2 replies; 6+ messages in thread
From: Pavel Machek @ 2006-11-01 12:23 UTC (permalink / raw)
To: kernel list, mingo; +Cc: Andrew Morton
Hi!
First, it would be nice if we had someone listed as a maintainer of
noidlehz stuff...
Then... I'm getting strange messages from noidlehz each time I
unplug/replug AC power (perhaps due to interrupt latency?).
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
Adding 987988k swap on /dev/sda1. Priority:-1 extents:1
across:987988k
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
EXT2-fs warning (device sda2): ext2_fill_super: mounting ext3
filesystem as ext2
pcmcia: Detected deprecated PCMCIA ioctl usage from process: cardmgr.
pcmcia: This interface will soon be removed from the kernel; please
expect breakage unless you upgrade to new tools.
pcmcia: see
http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
details.
cs: IO port probe 0x310-0x380: clean.
cs: IO port probe 0xa00-0xaff: clean.
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
coda_read_super: Bad mount data
coda_read_super: device index: 0
coda_read_super: rootfid is (01234567.ffffffff.080519b0.00000000)
coda_upcall: Venus dead on (op,un) (7.2) flags 10
Failure of coda_cnode_make for root: error -19
acpiphp_glue: cannot get bridge info
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
Disabling NO_HZ and high resolution timers due to timer broadcasting
(C3 stops local apic)
...I'd expect one such message, not many of them. Something seems
seriously wrong there...
Plus, suspend to RAM and disk is broken in -rc4-mm1. Suspend to RAM
dies with screaming speaker, suspend to disk returns but machine is
mostly toast (and screaming, looks like timer problem, beeps never
end). I'll disable NO_HZ and try again.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.19-rc4-mm1: noidlehz problems
2006-11-01 12:23 2.6.19-rc4-mm1: noidlehz problems Pavel Machek
@ 2006-11-01 12:55 ` Pavel Machek
2006-11-01 13:02 ` Arjan van de Ven
1 sibling, 0 replies; 6+ messages in thread
From: Pavel Machek @ 2006-11-01 12:55 UTC (permalink / raw)
To: kernel list, mingo; +Cc: Andrew Morton
Hi!
> First, it would be nice if we had someone listed as a maintainer of
> noidlehz stuff...
>
> Then... I'm getting strange messages from noidlehz each time I
> unplug/replug AC power (perhaps due to interrupt latency?).
>
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> Adding 987988k swap on /dev/sda1. Priority:-1 extents:1
> across:987988k
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> EXT2-fs warning (device sda2): ext2_fill_super: mounting ext3
> filesystem as ext2
...
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
>
> ...I'd expect one such message, not many of them. Something seems
> seriously wrong there...
>
> Plus, suspend to RAM and disk is broken in -rc4-mm1. Suspend to RAM
> dies with screaming speaker, suspend to disk returns but machine is
> mostly toast (and screaming, looks like timer problem, beeps never
> end). I'll disable NO_HZ and try again.
Disabling NO_HZ did not help, but I disabled high resolution timers,
and s2ram now works. s2disk also started working.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.19-rc4-mm1: noidlehz problems
2006-11-01 12:23 2.6.19-rc4-mm1: noidlehz problems Pavel Machek
2006-11-01 12:55 ` Pavel Machek
@ 2006-11-01 13:02 ` Arjan van de Ven
2006-11-01 13:20 ` Pavel Machek
2006-11-01 15:22 ` Matthew Garrett
1 sibling, 2 replies; 6+ messages in thread
From: Arjan van de Ven @ 2006-11-01 13:02 UTC (permalink / raw)
To: Pavel Machek; +Cc: kernel list, mingo, Andrew Morton
On Wed, 2006-11-01 at 13:23 +0100, Pavel Machek wrote:
> Hi!
>
> First, it would be nice if we had someone listed as a maintainer of
> noidlehz stuff...
>
> Then... I'm getting strange messages from noidlehz each time I
> unplug/replug AC power (perhaps due to interrupt latency?).
there probably is a different story going on.
When you unplug/replug AC power, several bioses change the meaning of
the software C-states in your system.
(there is a mapping between software visible C states and the hardware
C-states)
In some (hardware) C-states, the local apic timer stops (as does the
TSC), while in others it keeps running. If you change from AC to
battery, the bios can change the meaning of a software C-state from one
where local apic timer keeps going to one where it stops. This obviously
upsets the hrtimers/tickless code since that uses local apic timer for
event generation....
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.19-rc4-mm1: noidlehz problems
2006-11-01 13:02 ` Arjan van de Ven
@ 2006-11-01 13:20 ` Pavel Machek
2006-11-01 15:22 ` Matthew Garrett
1 sibling, 0 replies; 6+ messages in thread
From: Pavel Machek @ 2006-11-01 13:20 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: kernel list, mingo, Andrew Morton
On Wed 2006-11-01 14:02:57, Arjan van de Ven wrote:
> On Wed, 2006-11-01 at 13:23 +0100, Pavel Machek wrote:
> > Hi!
> >
> > First, it would be nice if we had someone listed as a maintainer of
> > noidlehz stuff...
> >
> > Then... I'm getting strange messages from noidlehz each time I
> > unplug/replug AC power (perhaps due to interrupt latency?).
>
> there probably is a different story going on.
> When you unplug/replug AC power, several bioses change the meaning of
> the software C-states in your system.
> (there is a mapping between software visible C states and the hardware
> C-states)
Yep, my notebook is one of such machines, so your theory looks very plausible.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.19-rc4-mm1: noidlehz problems
2006-11-01 13:02 ` Arjan van de Ven
2006-11-01 13:20 ` Pavel Machek
@ 2006-11-01 15:22 ` Matthew Garrett
2006-11-01 20:55 ` Thomas Gleixner
1 sibling, 1 reply; 6+ messages in thread
From: Matthew Garrett @ 2006-11-01 15:22 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: Pavel Machek, kernel list, mingo, Andrew Morton
On Wed, Nov 01, 2006 at 02:02:57PM +0100, Arjan van de Ven wrote:
> In some (hardware) C-states, the local apic timer stops (as does the
> TSC), while in others it keeps running. If you change from AC to
> battery, the bios can change the meaning of a software C-state from one
> where local apic timer keeps going to one where it stops. This obviously
> upsets the hrtimers/tickless code since that uses local apic timer for
> event generation....
Is there any hope of working around this? I'd have expected that the
most useful case for the tickless code was also the case where we want
to be using C3/C4...
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.19-rc4-mm1: noidlehz problems
2006-11-01 15:22 ` Matthew Garrett
@ 2006-11-01 20:55 ` Thomas Gleixner
0 siblings, 0 replies; 6+ messages in thread
From: Thomas Gleixner @ 2006-11-01 20:55 UTC (permalink / raw)
To: Matthew Garrett
Cc: Arjan van de Ven, Pavel Machek, kernel list, mingo, Andrew Morton
On Wed, 2006-11-01 at 15:22 +0000, Matthew Garrett wrote:
> On Wed, Nov 01, 2006 at 02:02:57PM +0100, Arjan van de Ven wrote:
>
> > In some (hardware) C-states, the local apic timer stops (as does the
> > TSC), while in others it keeps running. If you change from AC to
> > battery, the bios can change the meaning of a software C-state from one
> > where local apic timer keeps going to one where it stops. This obviously
> > upsets the hrtimers/tickless code since that uses local apic timer for
> > event generation....
>
> Is there any hope of working around this? I'd have expected that the
> most useful case for the tickless code was also the case where we want
> to be using C3/C4...
Can you try the following patches please ?
http://tglx.de/projects/hrtimers/2.6.19-rc4-mm1/patch-2.6.19-rc4-mm1-hrt-dyntick1.patch
This addresses the C34/C4 issue
tglx
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-11-01 20:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-01 12:23 2.6.19-rc4-mm1: noidlehz problems Pavel Machek
2006-11-01 12:55 ` Pavel Machek
2006-11-01 13:02 ` Arjan van de Ven
2006-11-01 13:20 ` Pavel Machek
2006-11-01 15:22 ` Matthew Garrett
2006-11-01 20:55 ` Thomas Gleixner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox