similar to: RedHat Node Panic Weekly

Hi, I sent an email to Mark Fisheh of Oracle Corp. & posted this issue at OTN under Linux thread this morning. I hope that someone among you might have experienced this and can help. On that basis, I am sending this to you too. I am stuck & will really appreciate if you can shed some light on this. Thanks. Anjan

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other

strange problem!! I think the xen 3.3.1 has been installed successfully.(detail info appended below). when I use "xm create" command, it said"Started domain opensolaris0811". opensolaris0811 is my installed domain name. However, when I use "xm list" command, I cannot find the new build domain opensolaris0811. Only show domain-0 and win2k3 (which is a guest OS

https://bugs.freedesktop.org/show_bug.cgi?id=97021 Bug ID: 97021 Summary: Screen locks up randomly while only mouse pointer moves, system responsive via ssh Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority:

Hello, I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel that it pulls down on its own. I added support for the aacraid driver to the kernel using ''make menuconfig'' from the build-linux-2.6-pvops_x86_64 subdirectory, and then built and installed the whole thing using ''make install'' from the xen-4.0.0 directory. I compiled this

I am trying to extract and combine the various pieces of information found in [1] and its sub-pages and the Xen in-tree documentation in order to make xen boot (potentially non-smp without some later changes). But since I am not familiar enough with Arm I think I am stuck doing something wrong. I compiled the hypervisor with debug and early printk for midway and use the xen.bin file (I could get

Hello all, I am trying to debug an elusive memory corruption bug on my arm64 machine which appears to be in the nouveau driver. I got the following splat from the refcount debugging code: """ refcount_t: underflow; use-after-free. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3366 at lib/refcount.c:128 refcount_sub_and_test+0xe8/0x108 Modules linked in: fuse nouveau

Chris: I''m consistently getting oopses when running fsstress against both single and multiple device compressed btrfs filesystems using kernels built from the current btrfs-unstable. In this report, I''m describing an incident with a single device filesystem. Once the oops occurs, all I/O appears to stop though iowait is still reported, and fsstress does not make apparent

Hi! Recently got a Via VE-900 board from Fry''s. It has a via nano x2 chip on it, and suggests that it has Intel-compatible virtualization extensions. Has anyone worked with this board yet? I thought it would be nice to have a lower-powered, nearly silent Xen machine sitting on my desk. I tried booting into Xen, but it said it didn''t recognize the processor. I can post

Hi! Recently got a Via VE-900 board from Fry''s. It has a via nano x2 chip on it, and suggests that it has Intel-compatible virtualization extensions. Has anyone worked with this board yet? I thought it would be nice to have a lower-powered, nearly silent Xen machine sitting on my desk. I tried booting into Xen, but it said it didn''t recognize the processor. I can post

Hi, this is the next version of quota support for quota tools. I've addressed all the comments of Tao, Joel and others. Sparse feature disabling also correctly updates quota information now and the patch is merged into the tunefs support patch. Honza

https://bugs.freedesktop.org/show_bug.cgi?id=100431 Bug ID: 100431 Summary: nv50: memory corruption due to use-after-free of dma_fence Product: xorg Version: unspecified Hardware: ARM OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

Hi Xen developers, We are hitting a DomU Linux kernel panic and we''d like to find a solution for it. We are porting our virtual appliance to Amazon''s AWS. Our kernel is 2.6.27.57. We know it is old but we have to stay with it for now. The problem is when the kernel (64-bit) boots up in EC2 ( a large instance with 7.5 GB memory), the kernel crashes when hitting the BUG in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am new to XEN. Try to move from vmware and Virtualbox (I use both now). Unfortunately, Debian Squeeze no longer support xen (out of the box no dom0) So I am trying to make it myself. I have installed xen 3.4.2 from source, did make world and installed. Got the kernel source from from the git repository with the xen patches following the xen

I have a single VM (of 11) that has a recurring problem. This image has moved from machine to machine, with the problem following it. This image has been rebuilt from scratch, and the problem recurred. It would appear that there is something in the behaviour of this VM which causes it to crash and causes Xend to become unhappy. The problem presents as: Domain crashes, becomes zombie. xm

Hi, I'm sending a series of patches implementing quota support into ocfs2-tools. It's the same as the original huge patch I've sent but now it's split as Joel asked. I've also realized that when disabling SPARSE feature, we should update quota information. That piece of code is missing, I'll implement it soon. Comments welcome. Honza

Hello Ben, commit (mini) [~/work/linux-2.6] git bisect bad 8777c5c11764d8336d8270f96778158c34c92108 is the first bad commit commit 8777c5c11764d8336d8270f96778158c34c92108 Author: Ben Skeggs <bskeggs at redhat.com> Date: Fri Jun 6 18:09:55 2014 +1000 drm/nouveau/dp: probe dpcd to determine connectedness Signed-off-by: Ben Skeggs <bskeggs at redhat.com> introduces a

Hi, below comes a new version of the series of patches implementing quota support for ocfs2-tools. I've fixed the calls of ocfs2_malloc_blocks() which were given number of bytes instead of number of blocks. Besides that the series should be the same. Honza

On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Ben, > commit Hey Thomas, Are you able to double-check that bisect? I'm not at all sure how that particular commit could trigger the issue you're seeing. Some of the others, certainly. It might be worth trying a couple of times before marking something as "good", in case

Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t