search for: mrq

...arket Cap (intraday)? ? ? ? ? ? ? <span id="yfs_j10_ibm">132.36B Enterprise Value (27-Apr-09)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 150.79B Trailing PE (ttm intraday)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 11.13 Fiscal Year Ends ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 31-Dec Most Recent Quarter (mrq) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 31-Mar-09 Profit Margin (ttm)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 12.21% Operating Margin (ttm) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 17.40% Return on Assets (ttm)? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 9.80% Return on Equity (ttm) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 5...

I get the above panic after nfs clients attach to this nfs server and being read/write ops on it after an unclean shutdown. I've fsck'ed the fs, and it marks it as clean, but I get this every time. It's an NFS share of a GEOM stripe (about 2TB). mode = 0100600, inum = 58456203, fs = /mnt panic: ffs_valloc: dup alloc I do have dumps from two crashes so far. This is

...er retry, so this this didn't happen. This is unfortunate as the retry is unnecessary, but at this time I can't think of a good way to separate an ignorable synchronous invalidation caused by hmm_range_fault from an async one that cannot be ignored.. A basic fix would be to not update the mrq seq in the notifier if the invalidate is triggered by hmm_range_fault, but that seems difficult to determine.. Any thoughts Jerome? Jason

...> DqvLnR39MrL808IK7WhVgvePJWhZGAMVG7/+mTRFW3kkmcSeZOtbB8iyA2ppZ46fRv3t6GwQ > gV9wNEStCBTFBJuHiUAJ2cP0nyj5/+Xf+O3R35TcM3hP/PwfNAikAVa0qt3WMzu/4BJjwwpx > imESu5vJkr5OB/vybKb8pZRE7bSaJudUZrl3+sxeAm83C/YkXTDHrzXgqegKOsGRFcHwEUb1 > AaYSxe2h/OUVdsgJllxqhmqAC5lHtxhEXfMPES8t5BeaPGy++9bMuW8AXvZGmrqrP0Rd30EX > dLB3x/x4XHZNGTuX7+zAd+3Q8PEOOAuaHiX/TSFLOyVFZC5OY3EQ7/ufeUNHuoiRpTmgaetT > +/nw2xuz+CWN3W6eMDoveH6cJ/vyz2EAv41TRlq//DLoh94SJDskp6/PTb+CscsJw0aYdzzw > Mjqkke+Qh6CAm+Z68vxbk8v2GU/m49M04Iu9EP7PP4hyW0ocvVP5e05/Poc6ti3i0eBUgV1U > wVg4h5gtCdmPxVsq92t9Yq35lcgz1RNQt0FrvMN6LYrLv4XgE8T...

...d=8192, seqcount=5, bpp=0x4) at /usr/src/sys/kern/vfs_cluster.c:118 #10 0xc081213b in ffs_read (ap=0x4) at /usr/src/sys/ufs/ffs/ffs_vnops.c:503 #11 0xc09368a0 in VOP_READ_APV (vop=0x4, a=0xc0a9a254) at vnode_if.c:643 #12 0xc07ad086 in nfsrv_read (nfsd=0xc69b3800, slp=0xc520d900, td=0xc532f900, mrq=0xe78e7c98) at vnode_if.h:343 #13 0xc07bd329 in nfssvc_nfsd (td=0x4) at /usr/src/sys/nfsserver/nfs_syscalls.c:474 #14 0xc07bcb08 in nfssvc (td=0xc532f900, uap=0xe78e7d04) at /usr/src/sys/nfsserver/nfs_syscalls.c:181 #15 0xc0924fcb in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi...

On Tue, Oct 29, 2019 at 07:22:37PM +0000, Yang, Philip wrote: > Hi Jason, > > I did quick test after merging amd-staging-drm-next with the > mmu_notifier branch, which includes this set changes. The test result > has different failures, app stuck intermittently, GUI no display etc. I > am understanding the changes and will try to figure out the cause. Thanks! I'm not

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

Hi, We're running Samba 3.0.26a on AIX 5.3 using security=ads. Users get access denied when ADS user token size gets over an unknow limit even though the ACL settings on JFS2 files/directories should give them access. To demonstrate and based on "id userid" output, user1 AD user token size is over 9k in size since it belongs to about 400 AD groups while user2 AD user token size