similar to: 6321768 assertion failed: qprocsareon(rq) in strsubr.c:qattach()

Displaying 20 results from an estimated 200 matches similar to: "6321768 assertion failed: qprocsareon(rq) in strsubr.c:qattach()"

2006 Oct 31
0
6256083 Need a lightweight file page mapping mechanism to substitute segmap
Author: praks Repository: /hg/zfs-crypto/gate Revision: 4c3b7ab574cc73502effa96c11c293e04fd54309 Log message: 6256083 Need a lightweight file page mapping mechanism to substitute segmap 6387639 segkpm segment set to incorrect size for amd64 Files: create: usr/src/uts/common/vm/vpm.c create: usr/src/uts/common/vm/vpm.h update: usr/src/pkgdefs/SUNWhea/prototype_com update:
2006 Oct 31
0
PSARC/2005/625 Greyhound - Solaris Kernel SSL proxy
Author: kais Repository: /hg/zfs-crypto/gate Revision: 4c19f37f44f83def06a8aab4c0e079347eedd284 Log message: PSARC/2005/625 Greyhound - Solaris Kernel SSL proxy 4931229 Kernel-level SSL proxy Files: create: usr/src/cmd/cmd-inet/usr.sbin/kssl/kssladm/Makefile create: usr/src/cmd/cmd-inet/usr.sbin/kssl/kssladm/kssladm.c create: usr/src/cmd/cmd-inet/usr.sbin/kssl/kssladm/kssladm.h create:
2007 Jan 10
2
[DTrace] using C preprocessor in dtrace scripts
Hi Max/DTrace list, > At any rate, without the -C, I can''t use #include <sys/stream.h>. > Without the #include <sys/stream.h>, I can''t use the M_DATA. > As it is, I get the following: > > # ./strrput.d 0xd595a6c0 <-- this is a vnode for a socket > ftp is using (not important here) > dtrace: failed to compile script ./strrput.d: line 7: >
2008 Dec 05
0
resync onnv_105 partial for 6713916
Author: Darren Moffat <Darren.Moffat at Sun.COM> Repository: /hg/zfs-crypto/gate Latest revision: 957d30a3607ed9f3cbe490da5894d1e1b2104033 Total changesets: 28 Log message: resync onnv_105 partial for 6713916 Files: usr/src/Makefile.lint usr/src/Targetdirs usr/src/cmd/Makefile usr/src/cmd/Makefile.cmd usr/src/cmd/acctadm/Makefile usr/src/cmd/acctadm/acctadm.xcl
2014 Jan 16
0
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
From: Rusty Russell <rusty at rustcorp.com.au> Date: Thu, 16 Jan 2014 10:25:26 +1030 > Rusty Russell <rusty at rustcorp.com.au> writes: >> Jason Wang <jasowang at redhat.com> writes: >>> It looks like there's no need for those two fields: >>> >>> - Unless there's a failure for the first refill try, rq->max should be always
2014 Jan 15
0
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
Jason Wang <jasowang at redhat.com> writes: > It looks like there's no need for those two fields: > > - Unless there's a failure for the first refill try, rq->max should be always > equal to the vring size. > - rq->num is only used to determine the condition that we need to do the refill, > we could check vq->num_free instead. > - rq->num was
2014 Jan 15
2
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
Rusty Russell <rusty at rustcorp.com.au> writes: > Jason Wang <jasowang at redhat.com> writes: >> It looks like there's no need for those two fields: >> >> - Unless there's a failure for the first refill try, rq->max should be always >> equal to the vring size. >> - rq->num is only used to determine the condition that we need to do the
2014 Jan 15
2
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
Rusty Russell <rusty at rustcorp.com.au> writes: > Jason Wang <jasowang at redhat.com> writes: >> It looks like there's no need for those two fields: >> >> - Unless there's a failure for the first refill try, rq->max should be always >> equal to the vring size. >> - rq->num is only used to determine the condition that we need to do the
2014 Jan 16
2
[PATCH net-next] virtio-net: drop rq->max and rq->num
It looks like there's no need for those two fields: - Unless there's a failure for the first refill try, rq->max should be always equal to the vring size. - rq->num is only used to determine the condition that we need to do the refill, we could check vq->num_free instead. - rq->num was required to be increased or decreased explicitly after each get/put which results a
2014 Jan 16
2
[PATCH net-next] virtio-net: drop rq->max and rq->num
It looks like there's no need for those two fields: - Unless there's a failure for the first refill try, rq->max should be always equal to the vring size. - rq->num is only used to determine the condition that we need to do the refill, we could check vq->num_free instead. - rq->num was required to be increased or decreased explicitly after each get/put which results a
2013 Dec 27
2
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
It looks like there's no need for those two fields: - Unless there's a failure for the first refill try, rq->max should be always equal to the vring size. - rq->num is only used to determine the condition that we need to do the refill, we could check vq->num_free instead. - rq->num was required to be increased or decreased explicitly after each get/put which results a
2013 Dec 27
2
[PATCH net-next RFC] virtio-net: drop rq->max and rq->num
It looks like there's no need for those two fields: - Unless there's a failure for the first refill try, rq->max should be always equal to the vring size. - rq->num is only used to determine the condition that we need to do the refill, we could check vq->num_free instead. - rq->num was required to be increased or decreased explicitly after each get/put which results a
2012 Jan 10
0
"tau + h > 1: error in summary.rq"
Dear all, I am doing a simulation for my model that works when I use only the rq() command. However, since I need to use the varcov matrix for my Wald test, I need to compute summary(rq(), cov=TRUE). But the simulation does not work because of the error: tau + h > 1: error in summary.rq I tried to use: if (tau + h > 1) stop("tau + h > 1: error in summary.rq") But the
2012 Sep 18
0
Comparing rqpd() and rq()
Dear R users, I am trying to estimate a panel data model using rqpd(). I also estimated the same model using rq() and dummy variables for the groups. The coefficient estimates differ substantially between the two approaches (rqpd() produces substantially larger coefficients). Should the two approaches deliver similar estimates (as for plm() and lm() plus dummies)? I.e. does this indicate a
2012 May 05
0
penalized quantile regression (rq.fit.lasso)
Dear all: I have a question about how to get the optimal estimate of coefficients using the penalized quantile regression (LASSO penalty in quantile regression defined in Koenker 2005). In R, I found both rq(y ~ x, method="lasso",lambda = 30) and rq.fit.lasso(x, y, tau = 0.5, lambda = 1, beta = .9995, eps = 1e-06) can give the estimates. But, I didn't find a way using either of
2008 Jul 10
1
problems with rq.fit.sfn
Dear all, I am running a quantile estimation with Sparse matrix and when I run the procedure rq.fit.sfn I receive the following warning: tiny diagonals replaced with Inf when calling blkfct. Does anyone knows exactly what does it mean? What's this kind of error? Should I get worried about this message? The matrix I use is a full rank matrix (and indeed I do not have any message about
2009 May 06
0
Quantile Regression for Longitudinal Data. Warning message: In rq.fit.sfn
Dear Dimitris, I have exactly the same problem than you, Do you get some solution? Thanks, Lola Lola Gadea Profesora titular de Economía Aplicada/Lecturer in Applied Economics Universidad de Zaragoza/University of Zaragoza (Spain) lgadea@unizar.es <http://estructuraehistoria.unizar.es/personal/lgadea/index.html>http://estructuraehistoria.unizar.es/personal/lgadea/index.html Grupo de
2012 Jan 04
1
plot rq lm
Dear Community, I'd like to plot an rq object the same way I do with a lm one, is it possible? Something like this plot(rqmodel , 1:4, id.labels=rownames(pga1)); where rqmodel <- rq(log(vd) ~ v1 + log(v2) +log(v3) + v4 + v5 ,data =dat) Thanks in advance and apologies, I'm pretty newbie with this, user at host.com -- View this message in context:
2014 Mar 08
0
blazer_usb rqt 33 rq 9 len 8 ret -110
On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > Are the messages a problem? Or could I ignore? Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.
2014 Mar 08
1
blazer_usb rqt 33 rq 9 len 8 ret -110
2014-03-08 14:26 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > >> Are the messages a problem? Or could I ignore? > > Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query. Thanks for the