similar to: Interesting lockdep message coming out of blktap

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

What is the purpose of the name member? And why is it that it''s being left uninitialized (causing the kernel driver to print garbage [in the 2.6.18 driver''s blktap_validate_params()] or even fail [in pv-ops'' blktap_device_validate_params()]) in tapdisk_control_open_image()? Thanks, Jan

Hi, I use btrfs on most of my volumes on my laptop, and I''ve always felt booting was very slow, but definitely sure is slow, is starting up Google Chrome: encrypted ext4: ~20s btrfs: ~2:11s I have tried different things to find out exactly what is the issue, but haven''t quite found it yet. Here''s some stuff I got from latencytop, not sure if would be helpful:

Hi there, I just found a segfaulting tapdisk2 process which led into a kernel oops. [1527071.169682] tapdisk2[26548]: segfault at 7fffd324cfe8 ip 000000000040837f sp 00007fffd324cff0 error 6 in tapdisk2[400000+38000] [1527071.220104] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 [1527071.220170] IP: [<ffffffff810ce73c>] apply_to_page_range+0x47/0x2f3

Package: blktap-dkms Version: 2.0.93-0.10 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, blktap-dkms fails to build a module for Linux 4.12: Selecting previously unselected package blktap-dkms. (Reading database ... 34976 files and directories currently installed.) Preparing to unpack .../blktap-dkms_2.0.93-0.10_amd64.deb ... Unpacking blktap-dkms (2.0.93-0.10) ...

On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn at prgmr.com> wrote: > I experienced a bug that is likely the same as https://bugs.launchpad.net/ > ubuntu/+source/linux/+bug/1350373 . Commit > b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, > doesn't appear in this kernel and doesn't apply cleanly either. > Is there any point in trying to

I tried to compile currently latest revision 105100 and got errors (below). I tried to get previous revisions, down to 105090, and all of them have the same error. configure was given flags: --enable-assertions --enable-shared --enable-libffi --enable-debug-runtime --enable-debug-symbols --disable-optimized FreeBSD-8.0 2.7 with the same flags builds ok. Yuri --- errors --- llvm[3]:

Hi, I tried very promising btrfs to test it a little and I experienced a little bug in implementation. I''m not sure where the bug lies however this works quite well to reproduce the problem: dd if=/dev/zero of=mountme bs=4k count=100000 dd if=/dev/zero of=mountme2 bs=4k count=100000 mkfs.btrfs mountme mkfs.btrfs mountme2 mkdir loop loop2 mount -o loop mountme loop mount -o loop mountme

I've tried everything I know how (and a lot I don't) to get ices to compile on this beige G3 ppc box. I've got the latest cvs of libshout and ices. Gentoo linux ppc 1.2-r1, from stage3 tarball. gcc 2.95.3 I've made sure that libshout points to libshout.so.2.0.2. Don't know what else to try. I've got the box here, and I've port-forwarded through my firewall to

Move the PAGE_POISON value to page_poison.c and add a function to enable callers from a kernel module to get the poison value if the page poisoning feature is in use. This also avoids callers directly checking PAGE_POISON regardless of whether the feature is enabled. Signed-off-by: Wei Wang <wei.w.wang at intel.com> Cc: Andrew Morton <akpm at linux-foundation.org> Cc: Michal Hocko

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70)

While installing the experemental kernel on a CentOS 7 PV the following happened. After a reboot of the PV the kernel looks to be installed but there is no option for booting it in grub. I attempted to run yum reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but still no entry in grub. No initramfs existed and I found kernel-modules did not install properly so I then ran

https://bugzilla.mindrot.org/show_bug.cgi?id=2390 Bug ID: 2390 Summary: PROTOCOL.key mis-describes private section Product: Portable OpenSSH Version: 6.8p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Documentation Assignee: unassigned-bugs at

Full_Name: Ziying Sherwin Version: 1.3.0 OS: Solaris 2.8 Submission from: (NULL) (130.14.31.32) We tried to install R on our Sun Solaris 2.8 machine using gcc 3.0. During the compilation, we got error messages like: gcc -I. -I../../../src/include -I../../../src/include -I/usr/local/include -DHAVE_CONFIG_H -g -O2 -c sockconn.c -o sockconn.o gcc -shared -o internet.so Rsock.o internet.o

On 10/28/19 4:10 PM, Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > gntdev simply wants to monitor a specific VMA for any notifier events, > this can be done straightforwardly using mmu_range_notifier_insert() over > the VMA's VA range. > > The notifier should be attached until the original VMA is destroyed. > > It is unclear if any of

I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either. Is there any point in trying to backport the patch? The backtrace is as follows: [ 32.304666] ------------[ cut here ]------------ [

This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN --exclude='o.*' --exclude '*~'

This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN --exclude='o.*' --exclude '*~'

https://bugs.freedesktop.org/show_bug.cgi?id=110500 Bug ID: 110500 Summary: X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium