RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-29 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Friday, August 29, 2014 19:20 PM > Because this particular return code is overloaded with multiple meanings > that can't necessarily be deduced from its name perhaps this > documentation patch would be helpful: > > diff --git a/arch/x86/

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-29 Thread Sitsofe Wheeler
On Fri, Aug 29, 2014 at 01:24:11PM +0300, Dan Carpenter wrote: > On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote: > > > > Section 4.11.3 of Hypervisor Top Level Functional Specification(available at > > http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/02/17/updated-hypervisor-top-lev

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-29 Thread Dan Carpenter
On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote: > Hi Dan, > > Section 4.11.3 of Hypervisor Top Level Functional Specification(available at > http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/02/17/updated-hypervisor-top-level-functional-specification.aspx) > says HV_STATUS_INVALID_AL

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-29 Thread Dexuan Cui
> -Original Message- > From: Dan Carpenter > Sent: Friday, August 29, 2014 17:50 PM > To: KY Srinivasan > Cc: Sitsofe Wheeler; Dexuan Cui; Greg Kroah-Hartman; Haiyang Zhang; > linux-ker...@vger.kernel.org; de...@linuxdriverproject.org > Subject: Re: [PANIC, hyperv]

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-29 Thread Dan Carpenter
It's sort of weird that this is an alignment issue. The config that was posted earlier was an x86_64 config and on that system then the pointers from kmalloc() should already be aligned correctly at sizeof(u64). Earlier I said I suspected the code is racy, so possibly changing from kmalloc() to g

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-28 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Thursday, August 28, 2014 20:49 PM > > > > The only issue seen on boot now is similar to > > > > https://lkml.org/lkml/2014/8/19/227 ... > > > I don't see this issue. Do you still see the issue for EVERY boot > > after you applied KY's

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-28 Thread Sitsofe Wheeler
Hi Dexuan, On Thu, Aug 28, 2014 at 03:21:59AM +, Dexuan Cui wrote: > > > > First let me thank you guys for looking into this issue. Looking at Feel free to add Reported-by: Sitsofe Wheeler to your patches (it's useful too me because it makes it easier for me to show what I've been doing to

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread KY Srinivasan
> -Original Message- > From: Dexuan Cui > Sent: Wednesday, August 27, 2014 8:22 PM > To: KY Srinivasan; Sitsofe Wheeler > Cc: Greg Kroah-Hartman; Haiyang Zhang; de...@linuxdriverproject.org; > linux-ker...@vger.kernel.org > Subject: RE: [PANIC, hyperv] BUG: unable to

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Dexuan Cui
> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of KY Srinivasan > Sent: Thursday, August 28, 2014 7:14 AM > > > > From: Sitsofe Wheeler [mailto:sits...@gmail.com] > > > > Sent: Wednesday, August 27, 2014 9:19 AM > > >

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread KY Srinivasan
: [PANIC, hyperv] BUG: unable to handle kernel paging request at > 880077800004 (hv_ringbuffer_write) > > On Wed, Aug 27, 2014 at 06:45:55PM +, KY Srinivasan wrote: > > > > > -Original Message- > > > From: Sitsofe Wheeler [mailto:sits...@gma

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Sitsofe Wheeler
On Wed, Aug 27, 2014 at 06:45:55PM +, KY Srinivasan wrote: > > > -Original Message- > > From: Sitsofe Wheeler [mailto:sits...@gmail.com] > > Sent: Wednesday, August 27, 2014 9:19 AM > > > > > BTW, with the patch below, hyperv_fb can work now, BUT, > > > *occasionally*, > > > storvsc_p

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread KY Srinivasan
: [PANIC, hyperv] BUG: unable to handle kernel paging request at > 880077800004 (hv_ringbuffer_write) > > On Wed, Aug 27, 2014 at 02:14:02PM +, Dexuan Cui wrote: > > > -Original Message- > > > From: Sitsofe Wheeler > > > Sent: Wednesday, August

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Sitsofe Wheeler
On Wed, Aug 27, 2014 at 02:14:02PM +, Dexuan Cui wrote: > > -Original Message- > > From: Sitsofe Wheeler > > Sent: Wednesday, August 27, 2014 20:16 PM > > > > I'm making a patch for this. > Please see the end of the mail for the inline patch and try it. > (the patch hasn't been rebased

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Wednesday, August 27, 2014 20:16 PM > > > do_hypercall() fails due to HV_STATUS_INVALID_ALIGNMENT, if "the > > specified input or output GPA pointer is not aligned to 8 bytes", > > or, "the specified input or output parameter lists spans

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Sitsofe Wheeler
On Wed, Aug 27, 2014 at 11:30:54AM +, Dexuan Cui wrote: > > -Original Message- > > From: Sitsofe Wheeler > > On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote: > > > > > Actually I found the direct cause of the panic: sometimes > > > vmbus_post_msg() can return 4 (HV_STATUS_IN

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote: > > > Actually I found the direct cause of the panic: sometimes > > vmbus_post_msg() can return 4 (HV_STATUS_INVALID_ALIGNMENT), but > > vmbus_open() doesn't propagate this error to t

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-27 Thread Sitsofe Wheeler
On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote: > > What is baffles me is the whole UP vs SMP thing - why would UP > > make this show up consistently? Perhaps some assertions could be added > > to check that rbi->ring_buffer still has sane values in it after > > operations on it are f

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-26 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Tuesday, August 26, 2014 1:42 AM > > > [7.645526] hv_vmbus: registering driver hyperv_fb > > > [7.657553] BUG: unable to handle kernel paging request at > > > 88007784 > > > [7.658224] IP: [] hv_ringbuffer_write+0x7c/0

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-25 Thread Sitsofe Wheeler
Hi Dexuan, On Mon, Aug 25, 2014 at 02:02:21PM +, Dexuan Cui wrote: > > -Original Message- > > From: Sitsofe Wheeler > > Sent: Wednesday, August 20, 2014 17:27 PM > > > > While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was > > triggered while registering hyperv_fb whic

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-25 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Wednesday, August 20, 2014 17:27 PM > > While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was > triggered while registering hyperv_fb which in turn caused a panic. > Various kernel debugging options (CONFIG_DEBUG_PAGEALLOC

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-20 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Wednesday, August 20, 2014 19:40 PM > > I suppose you're using the latest mainline v3.17-rc1(7d1311b9). > > That's right - Linux 3.17-rc1 > (7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9). Ok, let me try to reproduce it first. > > Can you p

Re: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-20 Thread Sitsofe Wheeler
Hi, On Wed, Aug 20, 2014 at 11:15:39AM +, Dexuan Cui wrote: > > -Original Message- > > From: Sitsofe Wheeler > > Sent: Wednesday, August 20, 2014 17:27 PM > > To: Dexuan Cui > > Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang; > > de...@linuxdriverproject.org; linux-ker...@vger.ke

RE: [PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-20 Thread Dexuan Cui
> -Original Message- > From: Sitsofe Wheeler > Sent: Wednesday, August 20, 2014 17:27 PM > To: Dexuan Cui > Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang; > de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; Jean-Christophe > Plagniol-Villard; linux-fb...@vger.kernel.org >

[PANIC, hyperv] BUG: unable to handle kernel paging request at ffff880077800004 (hv_ringbuffer_write)

2014-08-20 Thread Sitsofe Wheeler
While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was triggered while registering hyperv_fb which in turn caused a panic. Various kernel debugging options (CONFIG_DEBUG_PAGEALLOC, CONFIG_SLUB_DEBUG=y...) were on at the time. This only seems to happen if the guest is being booted with