<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> If a user wants to run Linux in a Hyper-V virtual machine (Hyper-V is Microsoft's virtualization solution, included in Windows Server 2008 and higher), Microsoft provides a set of drivers that enable the use of the high-performance synthetic devices (the equivalent of Xen's PV drivers). Maverick includes some of our drivers by default - hv_vmbus, hv_netvsc, and hv_utils. However, that version of the kernel has an bug in the hv_netvsc driver (and the underlying hv_vmbus driver) that results in multiple issues - specifically, you'll see a number of errors in /var/log/messages referring to schedule while atomic. After a while, the synthetic networking device will end up losing its connection. <o:p></o:p> <o:p> </o:p> The issue's been fixed upstream as part of the cleanup we've been doing to exit staging, and we have created a patch set against Maverick that fixes it. The patch set consists of four patches:<o:p></o:p> <o:p> </o:p> <![if !supportLists]>1. <![endif]>Ubuntu-10-10-network-atomic-fix: Change the allocation of memory for the hv_netvsc driver from GFP_KERNEL to GFP_ATOMIC.<o:p></o:p> <![if !supportLists]>2. <![endif]>Ubuntu-10-10-network-stack-print-fix: A wrong check was done when freeing the network device, resulting in a stack trace output which seemed to erroneously indicate that there was a problem.<o:p></o:p> <![if !supportLists]>3. <![endif]>Ubuntu-10-10-vmbus-atomic-fix: Change the allocation of memory for the hv_vmbus driver from GFP_KERNEL to GFP_ATOMIC.<o:p></o:p> <![if !supportLists]>4. <![endif]>Ubuntu-10-10-backport-of-mainline-loss-of-network-fix-for-Hyper-V: Locking is required when tweaking bits located in a shared page, usethe sync_version of bitops. Without this change vmbus_on_event() will miss events and as a result, vmbus_isr() will not schedule the receive tasklet.<o:p></o:p> <o:p> </o:p> This does not hit Natty, as we’ve fixed the issue in later kernels. However, given the large install base of Maverick, we’d like to get this included so customers can use the synthetic devices.<o:p></o:p> <o:p> </o:p> Symptoms: <o:p></o:p> <o:p> </o:p> [ 807.276091] BUG: scheduling while atomic: swapper/0/0x10000100 <o:p></o:p> [ 807.277476] Modules linked in: parport_pc ppdev binfmt_misc hv_utils(C) hv_netvsc(C) psmouse lp serio_raw hv_vmbus(C) i2c_piix4 parport floppy tulip <o:p></o:p> [ 807.294414] Modules linked in: parport_pc ppdev binfmt_misc hv_utils(C) hv_netvsc(C) psmouse lp serio_raw hv_vmbus(C) i2c_piix4 parport floppy tulip <o:p></o:p> [ 807.337981] Pid: 0, comm: swapper Tainted: G D C 2.6.35-22-generic #33-Ubuntu Virtual Machine/Virtual Machine<o:p></o:p> [ 807.339352] EIP: 0060:[<c012c21a>] EFLAGS: 00000246 CPU: 0 <o:p></o:p> [ 807.340699] EIP is at native_safe_halt+0xa/0x10<o:p></o:p> <o:p> </o:p> This has also been logged on Launchpad at <a href="https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/752064">https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/752064</a><o:p></o:p> <o:p> </o:p> Please let me know if you have any questions on this. <o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> -M<o:p></o:p> <o:p> </o:p> mike sterling | program manager open source technology center<o:p></o:p> <a href="http://www.microsoft.com/opensource/">http://www.microsoft.com/opensource/</a> <o:p></o:p> t: +1 425 707 7730<o:p></o:p> f: +1 425 708 1799<o:p></o:p> e: <a href="mailto:mike.sterling@microsoft.com">mike.sterling@microsoft.com</a> <o:p></o:p> t: <a href="http://twitter.com/mikester01">http://twitter.com/mikester01</a> <o:p></o:p> <o:p> </o:p> </div> </body> </html>