<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.37.3</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.37.3</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.37.3'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-03-07T23:05:26Z</updated>
<entry>
<title>e1000e: disable broken PHY wakeup for ICH10 LOMs, use MAC wakeup instead</title>
<updated>2011-03-07T23:05:26Z</updated>
<author>
<name>Bruce Allan</name>
<email>bruce.w.allan@intel.com</email>
</author>
<published>2011-02-02T09:30:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ef4fba5d0fc816eff781d6dc70d76ebc0ac8909e'/>
<id>urn:sha1:ef4fba5d0fc816eff781d6dc70d76ebc0ac8909e</id>
<content type='text'>
commit 4def99bbfd46e05c5e03b5b282cb4ee30e27ff19 upstream.

When support for 82577/82578 was added[1] in 2.6.31, PHY wakeup was in-
advertently enabled (even though it does not function properly) on ICH10
LOMs.  This patch makes it so that the ICH10 LOMs use MAC wakeup instead
as was done with the initial support for those devices (i.e. 82567LM-3,
82567LF-3 and 82567V-4).

[1] commit a4f58f5455ba0efda36fb33c37074922d1527a10

Reported-by: Aurelien Jarno &lt;aurelien@aurel32.net&gt;
Signed-off-by: Bruce Allan &lt;bruce.w.allan@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>r8169: disable ASPM</title>
<updated>2011-03-07T23:05:26Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-02-22T02:00:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=048882f265645e2258a6d6380622b8a1a3634217'/>
<id>urn:sha1:048882f265645e2258a6d6380622b8a1a3634217</id>
<content type='text'>
commit ba04c7c93bbcb48ce880cf75b6e9dffcd79d4c7b upstream.

For some time is known that ASPM is causing troubles on r8169, i.e. make
device randomly stop working without any errors in dmesg.

Currently Tomi Leppikangas reports that system with r8169 device hangs
with MCE errors when ASPM is enabled:
https://bugzilla.redhat.com/show_bug.cgi?id=642861#c4

Lets disable ASPM for r8169 devices at all, to avoid problems with
r8169 PCIe devices at least for some users.

Reported-by: Tomi Leppikangas &lt;tomi.leppikangas@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>carl9170: add Airlive X.USB a/b/g/n USBID</title>
<updated>2011-03-07T23:05:25Z</updated>
<author>
<name>Jan Puk</name>
<email>janpuk@volny.cz</email>
</author>
<published>2011-02-22T13:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d70c044346d70fb9c4980da7c5c581260f41305'/>
<id>urn:sha1:5d70c044346d70fb9c4980da7c5c581260f41305</id>
<content type='text'>
commit c86664e5a285af1afa06416e450e7c4af04daa7c upstream.

"AirLive X.USB now works perfectly under a Linux
environment!"

Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54usb: add Senao NUB-350 usbid</title>
<updated>2011-03-07T23:05:24Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2011-02-26T11:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cea4131a1d2ae214544678113eac6497ba5299e5'/>
<id>urn:sha1:cea4131a1d2ae214544678113eac6497ba5299e5</id>
<content type='text'>
commit 2b799a6b25bb9f9fbc478782cd9503e8066ab618 upstream.

Reported-by: Mark Davis
Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_htc: Fix an endian issue</title>
<updated>2011-03-07T23:05:24Z</updated>
<author>
<name>Sujith Manoharan</name>
<email>Sujith.Manoharan@atheros.com</email>
</author>
<published>2011-02-27T03:53:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=523e19477be751191853ae6f7bbf32654f7ee9d9'/>
<id>urn:sha1:523e19477be751191853ae6f7bbf32654f7ee9d9</id>
<content type='text'>
commit 2c27392dc4d4f5ee8a3967a520b8f6cac0418031 upstream.

The stream length/tag fields have to be in little endian
format. Fixing this makes the driver work on big-endian
platforms.

Tested-by: raghunathan.kailasanathan@wipro.com
Signed-off-by: Sujith Manoharan &lt;Sujith.Manoharan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>block: kill loop_mutex</title>
<updated>2011-03-07T23:05:24Z</updated>
<author>
<name>Petr Uzel</name>
<email>petr.uzel@suse.cz</email>
</author>
<published>2011-03-03T16:48:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f90b478078ffd8d34a7053d5461d4c4f215f0a12'/>
<id>urn:sha1:f90b478078ffd8d34a7053d5461d4c4f215f0a12</id>
<content type='text'>
commit fd51469fb68b987032e46297e0a4fe9020063c20 upstream.

Following steps lead to deadlock in kernel:

dd if=/dev/zero of=img bs=512 count=1000
losetup -f img
mkfs.ext2 /dev/loop0
mount -t ext2 -o loop /dev/loop0 mnt
umount mnt/

Stacktrace:
[&lt;c102ec04&gt;] irq_exit+0x36/0x59
[&lt;c101502c&gt;] smp_apic_timer_interrupt+0x6b/0x75
[&lt;c127f639&gt;] apic_timer_interrupt+0x31/0x38
[&lt;c101df88&gt;] mutex_spin_on_owner+0x54/0x5b
[&lt;fe2250e9&gt;] lo_release+0x12/0x67 [loop]
[&lt;c10c4eae&gt;] __blkdev_put+0x7c/0x10c
[&lt;c10a4da5&gt;] fput+0xd5/0x1aa
[&lt;fe2250cf&gt;] loop_clr_fd+0x1a9/0x1b1 [loop]
[&lt;fe225110&gt;] lo_release+0x39/0x67 [loop]
[&lt;c10c4eae&gt;] __blkdev_put+0x7c/0x10c
[&lt;c10a59d9&gt;] deactivate_locked_super+0x17/0x36
[&lt;c10b6f37&gt;] sys_umount+0x27e/0x2a5
[&lt;c10b6f69&gt;] sys_oldumount+0xb/0xe
[&lt;c1002897&gt;] sysenter_do_call+0x12/0x26
[&lt;ffffffff&gt;] 0xffffffff

Regression since 2a48fc0ab24241755dc9, which introduced the private
loop_mutex as part of the BKL removal process.

As per [1], the mutex can be safely removed.

[1] http://www.gossamer-threads.com/lists/linux/kernel/1341930

Addresses: https://bugzilla.novell.com/show_bug.cgi?id=669394
Addresses: https://bugzilla.kernel.org/show_bug.cgi?id=29172

Signed-off-by: Petr Uzel &lt;petr.uzel@suse.cz&gt;
Reviewed-by: Nikanth Karthikesan &lt;knikanth@suse.de&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Jens Axboe &lt;jaxboe@fusionio.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>block: add @force_kblockd to __blk_run_queue()</title>
<updated>2011-03-07T23:05:23Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2011-03-02T13:48:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=02d63a7def32bb4a58ea6e24f0edfce0aa653aaa'/>
<id>urn:sha1:02d63a7def32bb4a58ea6e24f0edfce0aa653aaa</id>
<content type='text'>
commit 1654e7411a1ad4999fe7890ef51d2a2bbb1fcf76 upstream.

__blk_run_queue() automatically either calls q-&gt;request_fn() directly
or schedules kblockd depending on whether the function is recursed.
blk-flush implementation needs to be able to explicitly choose
kblockd.  Add @force_kblockd.

All the current users are converted to specify %false for the
parameter and this patch doesn't introduce any behavior change.

stable: This is prerequisite for fixing ide oops caused by the new
        blk-flush implementation.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Cc: Jan Beulich &lt;JBeulich@novell.com&gt;
Cc: James Bottomley &lt;James.Bottomley@HansenPartnership.com&gt;
Signed-off-by: Jens Axboe &lt;jaxboe@fusionio.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: fix memory corruption with GM965 and &gt;4GB RAM</title>
<updated>2011-03-07T23:05:23Z</updated>
<author>
<name>Jan Niehusmann</name>
<email>jan@gondor.com</email>
</author>
<published>2011-03-03T23:28:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c5a3ef83c9b4cd3eb38b4c33ef4aed89eb790d53'/>
<id>urn:sha1:c5a3ef83c9b4cd3eb38b4c33ef4aed89eb790d53</id>
<content type='text'>
commit 6927faf30920b8c03dfa007e732642a1f1f20089 upstream.

On a Thinkpad x61s, I noticed some memory corruption when
plugging/unplugging the external VGA connection. The symptoms are that
4 bytes at the beginning of a page get overwritten by zeroes.
The address of the corruption varies when rebooting the machine, but
stays constant while it's running (so it's possible to repeatedly write
some data and then corrupt it again by plugging the cable).

Further investigation revealed that the corrupted address is
(dev_priv-&gt;status_page_dmah-&gt;busaddr &amp; 0xffffffff), ie. the beginning of
the hardware status page of the i965 graphics card, cut to 32 bits.

So it seems that for some memory access, the hardware uses only 32 bit
addressing. If the hardware status page is located &gt;4GB, this
corrupts unrelated memory.

Signed-off-by: Jan Niehusmann &lt;jan@gondor.com&gt;
Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>tg3: Restrict phy ioctl access</title>
<updated>2011-03-07T23:05:23Z</updated>
<author>
<name>Matt Carlson</name>
<email>mcarlson@broadcom.com</email>
</author>
<published>2011-02-15T12:51:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e8d5b85f2cce50980de6d36dad4e81ab44f53bd0'/>
<id>urn:sha1:e8d5b85f2cce50980de6d36dad4e81ab44f53bd0</id>
<content type='text'>
commit ed199facd070f8e551dc16a2ae1baa01d8d28ed4 upstream.

If management firmware is present and the device is down, the firmware
will assume control of the phy.  If a phy access were allowed from the
host, it will collide with firmware phy accesses, resulting in
unpredictable behavior.  This patch fixes the problem by disallowing phy
accesses during the problematic condition.

Signed-off-by: Matt Carlson &lt;mcarlson@broadcom.com&gt;
Reviewed-by: Michael Chan &lt;mchan@broadcom.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Staging: comedi: Add MODULE_LICENSE and similar to NI modules</title>
<updated>2011-03-07T23:05:22Z</updated>
<author>
<name>Ian Abbott</name>
<email>abbotti@mev.co.uk</email>
</author>
<published>2011-02-07T13:39:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=adbbc36af2a36f1998404e56b27f3933d0cc8afd'/>
<id>urn:sha1:adbbc36af2a36f1998404e56b27f3933d0cc8afd</id>
<content type='text'>
commit 3c323c01b6bd5fd01be21a8f0cdc11e55997aa06 upstream.

As mentioned by W. Trevor King on the devel@linuxdriverproject.org list
on "Thu, 27 Jan 2011 18:52:15 -0500", "Message-ID:
&lt;20110127235214.GA5107@thialfi.dhcp.drexel.edu&gt;", the ni_pcimio module
is missing module metadata, including a license.

This patch adds module metadata to all the NI comedi driver modules.  It
also removes a duplicate MODULE_LICENSE("GPL") line from the "mite"
module.

Signed-off-by: Ian Abbott &lt;abbotti@mev.co.uk&gt;
Cc: W. Trevor King &lt;wking@drexel.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

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