0
> [ 2551.528665] kthread+0x121/0x140
> [ 2551.528667] ? xb_read+0x1d0/0x1d0
> [ 2551.528670] ? kthread_park+0x90/0x90
> [ 2551.528673] ret_from_fork+0x35/0x40
>
> Fix this by doing the cleanup via a workqueue instead.
>
> Reported-by: James Dingwall
> Fixes: fd8aa9095a95c
2551.528654] xenbus_dev_queue_reply+0xc4/0x220
> > [ 2551.528657] xenbus_thread+0x7de/0x880
> > [ 2551.528660] ? wait_woken+0x80/0x80
> > [ 2551.528665] kthread+0x121/0x140
> > [ 2551.528667] ? xb_read+0x1d0/0x1d0
> > [ 2551.528670] ? kthread_park+0x90/0x90
> >
Hi,
I have been investigating a problem where xenstore becomes unresponsive
during domain shutdowns. My test script seems to trigger the problem
but without definitively being the same. It is possible to replicate
the issue in dom0 or a domU. If the test script is run in dom0 it seems
that
On Mon, Sep 23, 2019 at 08:41:05PM -0400, Boris Ostrovsky wrote:
> On 9/23/19 6:59 PM, Kees Cook wrote:
> > On Mon, Sep 23, 2019 at 03:42:27PM +0000, James Dingwall wrote:
> >> On Thu, Sep 19, 2019 at 12:37:40PM -0400, Boris Ostrovsky wrote:
> >>> On 9/19/19
On Thu, Sep 19, 2019 at 12:37:40PM -0400, Boris Ostrovsky wrote:
> On 9/19/19 12:14 PM, James Dingwall wrote:
> > On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
> >>> I have been investigating a regression in our environment where pstore
> >>> (efi-
On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
> > I have been investigating a regression in our environment where pstore
> > (efi-pstore specifically but I suspect this would affect all
> > implementations) no longer works after upgrading from a 4.4 to 5.0
> > kernel when running u
Hi,
I have been investigating a regression in our environment where pstore
(efi-pstore specifically but I suspect this would affect all
implementations) no longer works after upgrading from a 4.4 to 5.0
kernel when running under xen. (This is an Ubuntu kernel but I don't
think there are patch
On Fri, Jan 05, 2018 at 09:50:53PM +, James Dingwall wrote:
> Hi,
>
> I have just tried to build 4.4.110 but it failed with following message:
>
> arch/x86/built-in.o: In function `map_vdso':
> vma.c:(.text+0x8a3): undefined reference to `pvclock_pvti_cpu0_va
Hi,
I have just tried to build 4.4.110 but it failed with following message:
arch/x86/built-in.o: In function `map_vdso':
vma.c:(.text+0x8a3): undefined reference to `pvclock_pvti_cpu0_va'
make: *** [Makefile:953: vmlinux] Error 1
I found https://patchwork.kernel.org/patch/7906831/ which has a s
On Thu, Jan 22, 2015 at 04:30:02PM +0100, Borislav Petkov wrote:
> On Thu, Jan 22, 2015 at 09:53:04AM -0500, Boris Ostrovsky wrote:
> > Alternatively, we could return an error (-EINVAL?) from
> > microcode_init() when either of these two conditions is true.
>
> Yeah, this should be the right fix.
Hi,
Since 3.18.2 I am getting the oops below during boot whilst running as a dom0
under xen 4.4.1 / 4.5.0. Is this a known issue or worth bisecting to identify
the exact commit which causes this?
Thanks,
James
[ 173.735541] BUG: unable to handle kernel NULL pointer dereference at
00
Hi,
Since 3.11 I have noticed that the OOM killer quite frequently triggers
in my Xen guest domains which use ballooning to increase/decrease their
memory allocation according to their requirements. One example domain I
have has a maximum memory setting of ~1.5Gb but it usually idles at
~300
12 matches
Mail list logo
