Displaying 20 results from an estimated 200 matches similar to: "Kernel BUG: __tree_mod_log_rewind"
2013 Mar 06
1
Difficulty in caper: Error in phy$node.label[which(newNb > 0) - Ntip]
Hello,
I'm doing a comparative analysis of mammal brain and body size data.
I'm following Charlie Nunn and Natalie Cooper's instructions for
"Running PGLS in R using caper".
I run into the following error when I create my comparative dataset,
combining my phylogenetic tree (mammaltree) and taxon measures
(mammaldata):
"Error in phy$node.label[which(newNb > 0) -
2013 Feb 06
1
CAPER pgls() anova not working with variable as factor
Hi there,
>
> I am using the function pgls in the CAPER package, everything seems to run
> fine except for one of my variables.
> When using this variable as continuous the anova works without problem,
> but if using the same variable as factor (in fact, this is what it is), the
> program returns this answer:
>
> Error in terms.formula(formula, data = data) :
>
2013 Feb 13
1
[PATCH] Btrfs: fix crash in log replay with qgroups enabled
When replaying a log tree with qgroups enabled, tree_mod_log_rewind does a
sanity-check of the number of items against the maximum possible number.
It calculates that number with the nodesize of fs_root. Unfortunately
fs_root is not yet set at this stage. So instead use the nodesize from
tree_root, which is already initialized.
Signed-off-by: Arne Jansen <sensille@gmx.net>
---
2013 Apr 09
0
Simple GLS regression with CAPER
Dear R experts,
I hope this is the right list for my question.
As a newcomer in R, I am testing the R CAPER package, applying a simple
regression on a phylogeny tree with three binary traits: (t1, t2, t3).
My goal is to test the sensitivity to a correlation between t1 and t3. But
if a correlation of 100% is considered (i.e. t3 = t1). The pgls method of
CAPER seems to crash:
You can find there
2013 Aug 27
7
[PATCH] Btrfs: fix deadlock in uuid scan kthread
If there''s an ongoing transaction when the uuid scan kthread attempts
to create one, the kthread will block, waiting for that transaction to
finish while it''s keeping locks on the tree root, and in turn the existing
transaction is waiting for those locks to be free.
The stack trace reported by the kernel follows.
[36700.671601] INFO: task btrfs-uuid:15480 blocked for more than
2011 Aug 04
0
phyres function in caper package
## I clicked the send-button too quickly, before changing the title of the message etc... Sorry.##
I am running following phylogenetic analyses with the caper package:
data=read.table(file="data.txt",header=T,sep="\t")
tree = read.nexus("Tree.nex")
primate = comparative.data(phy=tree, data=data,
names.col=Species, vcv=TRUE, na.omit=FALSE,
2012 Aug 24
4
[PATCH] Btrfs: pass lockdep rwsem metadata to async commit transaction
The freeze rwsem is taken by sb_start_intwrite() and dropped during the
commit_ or end_transaction(). In the async case, that happens in a worker
thread. Tell lockdep the calling thread is releasing ownership of the
rwsem and the async thread is picking it up.
Josef and I worked out a more complicated solution that made the async
commit thread join and potentially get a later transaction, but
2013 Jan 31
4
[RFC][PATCH 2/2] Btrfs: implement unlocked dio write
This idea is from ext4. By this patch, we can make the dio write parallel,
and improve the performance.
We needn''t worry about the race between dio write and truncate, because the
truncate need wait untill all the dio write end.
And we also needn''t worry about the race between dio write and punch hole,
because we have extent lock to protect our operation.
I ran fio to test the
2012 Sep 12
2
Deadlock in btrfs-cleaner, related to snapshot deletion
Hello,
(this is a recap of yesterday''s discussion on BTRFS IRC, also to save relevant pastes before pastebins expire)
I have my /home on btrfs; a cronjob makes one snapshot every 30 minutes; these
snapshots are kept for 24-48 hours, then deleted in batches.
This is a 16K Leaf/Node BTRFS on top of mdadm RAID1.
As system uptime approached 2 weeks, I started noticing that the free space
2003 Jan 20
1
LDAP PDC, net rpc vampire
still digging at this:
[2003/01/20 14:26:38, 2] passdb/pdb_ldap.c:ldapsam_connect_system(421)
ldap_connect_system: succesful connection to the LDAP server
[2003/01/20 14:26:38, 4] passdb/pdb_ldap.c:ldapsam_open(472)
The LDAP server is succesful connected
[2003/01/20 14:26:38, 4] passdb/pdb_ldap.c:ldapsam_getsampwnam(1573)
We don't find this user [Administrator] count=0
[2003/01/20
2024 May 22
1
confint Attempts to Use All Server CPUs by Default
Following up on this -- on my system, I have 69 packages installed
that appear to provide something like a confint() method:
h <- help.search("confint", agrep = FALSE)
p <- sort(unique(h$matches$Package))
length(p)
## [1] 69
p
[1] "bamlss" "bbmle" "binom" "brglm2"
[5] "broom"
2011 Sep 10
12
WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]()
Hi
I am hitting this Warning reproducible, the workload is a ceph osd,
kernel ist 3.1.0-rc5.
Best Regards,
martin
[ 5472.099766] ------------[ cut here ]------------
[ 5472.099833] WARNING: at fs/btrfs/inode.c:2193
btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]()
[ 5472.099838] Hardware name: MS-96B3
[ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm
i2c_algo_bit psmouse sp5100_tco
2024 May 21
1
confint Attempts to Use All Server CPUs by Default
? Tue, 21 May 2024 08:00:11 +0000
Dario Strbenac via R-devel <r-devel at r-project.org> ?????:
> Would a less resource-intensive value, such as 1, be a safer default
> CPU value for confint?
Which confint() method do you have in mind? There is at least four of
them by default in R, and many additional classes could make use of
stats:::confint.default by implementing vcov().
>
2014 Aug 24
1
Kernel crash in 3.17-rc1 when loading nouveau on (non-POSTed) NV1A
System was booted with PCI graphics card first in VGA text mode.
Loading nouveau from there on causes the following BUG, after what
kernel produces trace over trace until overflowing its stack.
(trace captured via netconsole)
[ 154.323717] wmi: Mapper loaded
[ 154.735793] nouveau 0000:02:00.0: enabling device (0004 -> 0006)
[ 154.743189] ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 16
[
2012 Dec 12
1
kernel BUG at fs/btrfs/extent_io.c:4052 (kernel 3.5.3)
Hi all,
Last week we had 2 times an "uncorrectable ecc memory error" crash on
our server on the same memory module.
After removing the faulty module and restarting the server, everything
was working again.
However, yesterday we had a soft lockup and had to restart the server
again. No warning or ecc error this time. Everything is working now,
but we want to avoid this in the future
2013 Apr 28
2
Is it one issue. Do you have some good ideas, thanks a lot.
Hi, everyone
I have some questions with the OCFS2 when using it as vm-store.
With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4.
As the network configure change, there are some issues as the log below.
Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog?
Why the host ZHJD-VM6 is blocked until it reboot
2013 Apr 28
2
Is it one issue. Do you have some good ideas, thanks a lot.
Hi, everyone
I have some questions with the OCFS2 when using it as vm-store.
With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4.
As the network configure change, there are some issues as the log below.
Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog?
Why the host ZHJD-VM6 is blocked until it reboot
2007 Oct 22
4
Centos 5.0 Intel G33/P35 Chipset Support (Asus P5K-VM, P5KC)
I have 2 new boxes that I cannot use yet because of
problems supporting these newer chipsets in 5.1. Does
anyone know when the CD version of 5.0 x86-64 that has
support for these chipsets be available on any on a
Centos mirror?
Has the support for these chipsets been added to yum
yet?
Here are my latest results with these chipsets and
Centos 5.1
1. Asus P5K, E6850, P35 Chipset: Does not
2010 Nov 16
7
[Bug 31644] New: Nouveau driver with "Gigabyte nVidia 9600GT" - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=31644
Summary: Nouveau driver with "Gigabyte nVidia 9600GT" - black
screen
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2013 Aug 04
2
Unable to unmount filesystem (bug in kernel reported in kern.log)
I tried to unmount a btrfs filesystem located in a external usb hard
drive. This belonged to a raid1 data and metadata filesystem mounted
in degraded mode.
Unfortunately, I couldn''t save the image of filesystem but I could see
this error in kern.log:
Aug 4 02:23:55 rohan kernel: [ 3747.840027] usb 1-3: new high-speed
USB device number 8 using ehci_hcd
Aug 4 02:23:55 rohan kernel: [