<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git, branch v2.6.34.7</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.34.7</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.34.7'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2010-09-13T16:54:58Z</updated>
<entry>
<title>Linux 2.6.34.7</title>
<updated>2010-09-13T16:54:58Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-09-13T16:54:58Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=f42346985c7721798c577606cb4d0f719940d33e'/>
<id>urn:sha1:f42346985c7721798c577606cb4d0f719940d33e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "USB delay init quirk for logitech Harmony 700-series devices"</title>
<updated>2010-09-13T16:52:55Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-09-13T16:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=bcdc83eb6be6296fbe1bd0819a8ccd9832f559a0'/>
<id>urn:sha1:bcdc83eb6be6296fbe1bd0819a8ccd9832f559a0</id>
<content type='text'>
This reverts commit 631b2d37894bb2a891d8897e1861362a23dde4d9.

It was found to cause a number of USB devices to not work properly
because we call usb_disable_autosuspend too soon.  This is not an issue
with any other kernel version.

Reported-by: Jiri Slaby &lt;jslaby@suse.cz&gt;
Acked-by: Phil Dibowitz &lt;phil@ipom.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>Linux 2.6.34.6</title>
<updated>2010-08-26T23:44:38Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-08-26T23:44:38Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=df50751f61a0e515461fb9309869f04eefd4adef'/>
<id>urn:sha1:df50751f61a0e515461fb9309869f04eefd4adef</id>
<content type='text'>
</content>
</entry>
<entry>
<title>x86, apic: ack all pending irqs when crashed/on kexec</title>
<updated>2010-08-26T23:44:12Z</updated>
<author>
<name>Kerstin Jonsson</name>
<email>kerstin.jonsson@ericsson.com</email>
</author>
<published>2010-05-24T19:13:15Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=cb9a5bc499b8e58b450c63d7c03470ee27c7c878'/>
<id>urn:sha1:cb9a5bc499b8e58b450c63d7c03470ee27c7c878</id>
<content type='text'>
commit 8c3ba8d049247dc06b6dcee1711a11b26647aa44 upstream.

When the SMP kernel decides to crash_kexec() the local APICs may have
pending interrupts in their vector tables.

The setup routine for the local APIC has a deficient mechanism for
clearing these interrupts, it only handles interrupts that has already
been dispatched to the local core for servicing (the ISR register) safely,
it doesn't consider lower prioritized queued interrupts stored in the IRR
register.

If you have more than one pending interrupt within the same 32 bit word in
the LAPIC vector table registers you may find yourself entering the IO
APIC setup with pending interrupts left in the LAPIC.  This is a situation
for wich the IO APIC setup is not prepared.  Depending of what/which
interrupt vector/vectors are stuck in the APIC tables your system may show
various degrees of malfunctioning.  That was the reason why the
check_timer() failed in our system, the timer interrupts was blocked by
pending interrupts from the old kernel when routed trough the IO APIC.

Additional comment from Jiri Bohac:
==============
If this should go into stable release,
I'd add some kind of limit on the number of iterations, just to be safe from
hard to debug lock-ups:

+if (loops++  &gt; MAX_LOOPS) {
+        printk("LAPIC pending clean-up")
+        break;
+}
 while (queued);

with MAX_LOOPS something like 1E9 this would leave plenty of time for the
pending IRQs to be cleared and would and still cause at most a second of delay
if the loop were to lock-up for whatever reason.

[trenn@suse.de:

V2: Use tsc if avail to bail out after 1 sec due to possible virtual
    apic_read calls which may take rather long (suggested by: Avi Kivity
    &lt;avi@redhat.com&gt;) If no tsc is available bail out quickly after
    cpu_khz, if we broke out too early and still have irqs pending (which
    should never happen?) we still get a WARN_ON...

V3: - Fixed indentation -&gt; checkpatch clean
    - max_loops must be signed

V4: - Fix typo, mixed up tsc and ntsc in first rdtscll() call

V5: Adjust WARN_ON() condition to also catch error in cpu_has_tsc case]

Cc: &lt;jbohac@novell.com&gt;
Cc: Yinghai Lu &lt;yinghai@kernel.org&gt;
Cc: Kerstin Jonsson &lt;kerstin.jonsson@ericsson.com&gt;
Cc: Avi Kivity &lt;avi@redhat.com&gt;
Cc: Suresh Siddha &lt;suresh.b.siddha@intel.com&gt;
Tested-by: Eric W. Biederman &lt;ebiederm@xmission.com&gt;
Signed-off-by: Thomas Renninger &lt;trenn@suse.de&gt;
LKML-Reference: &lt;201005241913.o4OJDGWM010865@imap1.linux-foundation.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>tracing: Fix timer tracing</title>
<updated>2010-08-26T23:44:11Z</updated>
<author>
<name>Arjan van de Ven</name>
<email>arjan@linux.intel.com</email>
</author>
<published>2010-08-18T22:33:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=4c0d125b0489ec672e3b967b0f44092de083f0d0'/>
<id>urn:sha1:4c0d125b0489ec672e3b967b0f44092de083f0d0</id>
<content type='text'>
commit ede1b4290781ae82ccf0f2ecc6dada8d3dd35779 upstream.

PowerTOP would like to be able to trace timers.

Unfortunately, the current timer tracing is not very useful: the
actual timer function is not recorded in the trace at the start
of timer execution.

Although this is recorded for timer "start" time (when it gets
armed), this is not useful; most timers get started early, and a
tracer like PowerTOP will never see this event, but will only
see the actual running of the  timer.

This patch just adds the function to the timer tracing; I've
verified with PowerTOP that now it can get useful information
about timers.

Signed-off-by: Arjan van de Ven &lt;arjan@linux.intel.com&gt;
Cc: xiaoguangrong@cn.fujitsu.com
Cc: Steven Rostedt &lt;rostedt@goodmis.org&gt;
Cc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;
Cc: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
LKML-Reference: &lt;4C6C5FA9.3000405@linux.intel.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: add product ID for Lenz LI-USB</title>
<updated>2010-08-26T23:44:10Z</updated>
<author>
<name>Galen Seitz</name>
<email>galens@seitzassoc.com</email>
</author>
<published>2010-08-19T18:15:20Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=44325f6b0db56842da96a35ae0263b143a5cb205'/>
<id>urn:sha1:44325f6b0db56842da96a35ae0263b143a5cb205</id>
<content type='text'>
commit ea233f805537f5da16c2b34d85b6c5cf88a0f9aa upstream.

Add ftdi product ID for Lenz LI-USB, a model train interface.  This
was NOT tested against 2.6.35, but a similar patch was tested with the
CentOS 2.6.18-194.11.1.el5 kernel.  It wasn't clear to me what
ordering is being used in ftdi_sio.c, so I inserted the ID after another
model train entry(SPROG_II).

Signed-off-by: Galen Seitz &lt;galens@seitzassoc.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: Add ID for Ionics PlugComputer</title>
<updated>2010-08-26T23:44:10Z</updated>
<author>
<name>Martin Michlmayr</name>
<email>tbm@cyrius.com</email>
</author>
<published>2010-08-10T19:31:21Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=173e878e3e699c8920338e5d09ce2ffa74a3f8bb'/>
<id>urn:sha1:173e878e3e699c8920338e5d09ce2ffa74a3f8bb</id>
<content type='text'>
commit 666cc076d284e32d11bfc5ea2fbfc50434cff051 upstream.

Add the ID for the Ionics PlugComputer (&lt;http://ionicsplug.com/&gt;).

Signed-off-by: Martin Michlmayr &lt;tbm@cyrius.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: xhci: Remove buggy assignment in next_trb()</title>
<updated>2010-08-26T23:44:09Z</updated>
<author>
<name>John Youn</name>
<email>John.Youn@synopsys.com</email>
</author>
<published>2010-08-09T20:56:11Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=b9b1463afe574c5ce6d824305ea2fe817d8ccc02'/>
<id>urn:sha1:b9b1463afe574c5ce6d824305ea2fe817d8ccc02</id>
<content type='text'>
commit a1669b2c64a9c8b031e0ac5cbf2692337a577f7c upstream.

The code to increment the TRB pointer has a slight ambiguity that could
lead to a bug on different compilers.  The ANSI C specification does not
specify the precedence of the assignment operator over the postfix
operator.  gcc 4.4 produced the correct code (increment the pointer and
assign the value), but a MIPS compiler that one of John's clients used
assigned the old (unincremented) value.

Remove the unnecessary assignment to make all compilers produce the
correct assembly.

Signed-off-by: John Youn &lt;johnyoun@synopsys.com&gt;
Signed-off-by: Sarah Sharp &lt;sarah.a.sharp@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: io_ti: check firmware version before updating</title>
<updated>2010-08-26T23:44:08Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@suse.de</email>
</author>
<published>2010-08-17T22:15:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=aced8781afb05d5d0d9ce6304c24ac34861585b7'/>
<id>urn:sha1:aced8781afb05d5d0d9ce6304c24ac34861585b7</id>
<content type='text'>
commit 0827a9ff2bbcbb03c33f1a6eb283fe051059482c upstream.

If we can't read the firmware for a device from the disk, and yet the
device already has a valid firmware image in it, we don't want to
replace the firmware with something invalid.  So check the version
number to be less than the current one to verify this is the correct
thing to do.


Reported-by: Chris Beauchamp &lt;chris@chillibean.tv&gt;
Tested-by: Chris Beauchamp &lt;chris@chillibean.tv&gt;
Cc: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: fix endianess of max packet size</title>
<updated>2010-08-26T23:44:07Z</updated>
<author>
<name>Michael Wileczka</name>
<email>mikewileczka@yahoo.com</email>
</author>
<published>2010-08-18T14:14:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=233f104353ab7df00dad8a2137c3665d615098ee'/>
<id>urn:sha1:233f104353ab7df00dad8a2137c3665d615098ee</id>
<content type='text'>
commit d1ab903d2552b2362339b19203c7f01c797cb316 upstream.

The USB max packet size (always little-endian) was not being byte
swapped on big-endian systems.

Applicable since [USB: ftdi_sio: fix hi-speed device packet size calculation] approx 2.6.31

Signed-off-by: Michael Wileczka &lt;mikewileczka@yahoo.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
