<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/kernel, branch v2.6.21-rc5</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/kernel?h=v2.6.21-rc5</id>
<link rel='self' href='https://git.amat.us/linux/atom/kernel?h=v2.6.21-rc5'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2007-03-25T21:57:34Z</updated>
<entry>
<title>[PATCH] clocksource: Fix thinko in watchdog selection</title>
<updated>2007-03-25T21:57:34Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2007-03-25T12:42:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=948ac6d71cf868b431adb3139d8dfbd9c4e4a6ca'/>
<id>urn:sha1:948ac6d71cf868b431adb3139d8dfbd9c4e4a6ca</id>
<content type='text'>
The watchdog implementation excludes low res / non continuous
clocksources from being selected as a watchdog reference
unintentionally.

Allow using jiffies/PIT as a watchdog reference as long as no better
clocksource is available. This is necessary to detect TSC breakage on
systems, which have no pmtimer/hpet.

The main goal of the initial patch (preventing to switch to highres/nohz
when no reliable fallback clocksource is available) is still guaranteed
by the checks in clocksource_watchdog().

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] dynticks: fix hrtimer rounding error in next_timer_interrupt</title>
<updated>2007-03-25T21:57:34Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2007-03-25T12:31:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9501b6cf5541f0d576d566a463f1e7d3eaaab4eb'/>
<id>urn:sha1:9501b6cf5541f0d576d566a463f1e7d3eaaab4eb</id>
<content type='text'>
The rework of next_timer_interrupt() fixed the timer wheel bugs, but
invented a rounding error versus the next hrtimer event. This is caused
by the conversion of the hrtimer internal representation to relative
jiffies.

This causes bug #8100:
http://bugzilla.kernel.org/show_bug.cgi?id=8100

next_timer_interrupt() returns "now" in such a case and causes the code
in tick_nohz_stop_sched_tick() to trigger the timer softirq, which is
bogus as no timer is due for expiry. This results in an endless context
switching between idle and ksoftirqd until a timer is due for expiry.

Modify the hrtimer evaluation so that, it returns now + 1, when the
conversion results in a delta &lt; 1 jiffie.

It's confirmed to resolve bug #8100

Reported-by: Emil Karlson &lt;jkarlson@cc.hut.fi&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] time: fix formatting in /proc/timer_list</title>
<updated>2007-03-23T18:01:21Z</updated>
<author>
<name>James Morris</name>
<email>jmorris@namei.org</email>
</author>
<published>2007-03-23T07:09:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0444b3035e5f4981f4d1d96f9f0c3cbada1e6d69'/>
<id>urn:sha1:0444b3035e5f4981f4d1d96f9f0c3cbada1e6d69</id>
<content type='text'>
Fix the print formatting of three unsigned long fields in /proc/timer_list,
which are currently being formatted as signed long.

Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] lockdep: debug_show_all_locks &amp; debug_show_held_locks vs. debug_locks</title>
<updated>2007-03-23T02:39:06Z</updated>
<author>
<name>Jarek Poplawski</name>
<email>jarkao2@o2.pl</email>
</author>
<published>2007-03-22T08:11:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9c35dd7f8bda1849dcb430be99325504221048df'/>
<id>urn:sha1:9c35dd7f8bda1849dcb430be99325504221048df</id>
<content type='text'>
lockdep's data shouldn't be used when debug_locks == 0 because it's not
updated after this, so it's more misleading than helpful.

PS: probably lockdep's current-&gt; fields should be reset after it turns
debug_locks off: so, after printing a bug report, but before return from
exported functions, but there are really a lot of these possibilities (e.g.
 after DEBUG_LOCKS_WARN_ON), so, something could be missed.  (Of course
direct use of this fields isn't recommended either.)

Reported-by: Folkert van Heusden &lt;folkert@vanheusden.com&gt;
Inspired-by: Oleg Nesterov &lt;oleg@tv-sign.ru&gt;
Signed-off-by: Jarek Poplawski &lt;jarkao2@o2.pl&gt;
Acked-by: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Cc: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] fix extra BIOS invocation during resume</title>
<updated>2007-03-23T02:39:06Z</updated>
<author>
<name>Pavel Machek</name>
<email>pavel@ucw.cz</email>
</author>
<published>2007-03-22T08:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=058560fbd70190ea6b50b5df4d814bc30911d06b'/>
<id>urn:sha1:058560fbd70190ea6b50b5df4d814bc30911d06b</id>
<content type='text'>
It causes extra moon icons blinking on x60, and breaks at least two other
systems.

During resume, we do not know that "reboot"/"shutdown" method was used, so
we assume "plaform" and call BIOS, anyway...

This is 2.6.21 material, and should fix 2 or 3 regressions from 2.6.20.

Signed-off-by: Pavel Machek &lt;pavel@suse.cz&gt;
Acked-by: "Rafael J. Wysocki" &lt;rjw@sisk.pl&gt;
Cc: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] swsusp: Fix SNAPSHOT_S2RAM ioctl</title>
<updated>2007-03-23T02:39:05Z</updated>
<author>
<name>Rafael J. Wysocki</name>
<email>rjw@sisk.pl</email>
</author>
<published>2007-03-22T08:11:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=93c9a7ff50a5b39dbdf80129c5da89e6d6256bea'/>
<id>urn:sha1:93c9a7ff50a5b39dbdf80129c5da89e6d6256bea</id>
<content type='text'>
The SNAPSHOT_S2RAM ioctl does not disable the nonboot CPUs before entering
the suspend, although it should do this.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] clockevents: Fix suspend/resume to disk hangs</title>
<updated>2007-03-17T02:35:25Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2007-03-16T23:25:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cd05a1f818073a623455a58e756c5b419fc98db9'/>
<id>urn:sha1:cd05a1f818073a623455a58e756c5b419fc98db9</id>
<content type='text'>
I finally found a dual core box, which survives suspend/resume without
crashing in the middle of nowhere. Sigh, I never figured out from the
code and the bug reports what's going on.

The observed hangs are caused by a stale state transition of the clock
event devices, which keeps the RCU synchronization away from completion,
when the non boot CPU is brought back up.

The suspend/resume in oneshot mode needs the similar care as the
periodic mode during suspend to RAM. My assumption that the state
transitions during the different shutdown/bringups of s2disk would go
through the periodic boot phase and then switch over to highres resp.
nohz mode were simply wrong.

Add the appropriate suspend / resume handling for the non periodic
modes.

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] initialise pi_lock if CONFIG_RT_MUTEXES=N</title>
<updated>2007-03-17T02:25:06Z</updated>
<author>
<name>Zilvinas Valinskas</name>
<email>zilvinas@wilibox.com</email>
</author>
<published>2007-03-16T21:38:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e29e175b0f40cffc86068156733def14a7a533ab'/>
<id>urn:sha1:e29e175b0f40cffc86068156733def14a7a533ab</id>
<content type='text'>
Fixes a bogus lockdep warning which causes lockdep to disable itself.

Acked-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] futex: PI state locking fix</title>
<updated>2007-03-17T02:25:06Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2007-03-16T21:38:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=21778867b1c8e0feb567addb6dc0a7e2ca6ecdec'/>
<id>urn:sha1:21778867b1c8e0feb567addb6dc0a7e2ca6ecdec</id>
<content type='text'>
Testing of -rt by IBM uncovered a locking bug in wake_futex_pi(): the PI
state needs to be locked before we access it.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] swsusp: fix suspend when console is in VT_AUTO+KD_GRAPHICS mode</title>
<updated>2007-03-17T02:25:05Z</updated>
<author>
<name>Andrew Johnson</name>
<email>ajohnson@intrinsyc.com</email>
</author>
<published>2007-03-16T21:38:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b257bc051f06607beb3004d9a1c297085e728bec'/>
<id>urn:sha1:b257bc051f06607beb3004d9a1c297085e728bec</id>
<content type='text'>
When the console is in VT_AUTO+KD_GRAPHICS mode, switching to the
SUSPEND_CONSOLE fails, resulting in vt_waitactive() waiting indefinitely or
until the task is interrupted.  This patch tests if a console switch can
occur in set_console() and returns early if a console switch is not
possible.

[akpm@linux-foundation.org: cleanup]
Signed-off-by: Andrew Johnson &lt;ajohnson@intrinsyc.com&gt;
Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;
Cc: "Antonino A. Daplas" &lt;adaplas@pol.net&gt;
Cc: "Rafael J. Wysocki" &lt;rjw@sisk.pl&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
