search for: kmem_alloc

...CentOS 4.4 system (x86_64). We are running kernel 2.6.9-42.0.2.ELsmp along with kernel-module-xfs-2.6.9-42.0.2.ELsmp-0.1-3. The issue we are having is that while the copy is running (using rsync) the system will log these message periodically: kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250) kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x2d0) Eventually the system will panic. This looks similar to this bug: http://oss.sgi.com/bugzilla/show_bug.cgi?id=410 which was apparently fixed in April. Is there any chance that the fix will make it into the c...

I just had a quick play with gzip compression on a filesystem and the result was the machine grinding to a halt while copying some large (.wav) files to it from another filesystem in the same pool. The system became very unresponsive, taking several seconds to echo keystrokes. The box is a maxed out AMD QuadFX, so it should have plenty of grunt for this. Comments? Ian

...y) busy imap server with external scsi hardware raid, dual Xeon CPUs, and 8GB of RAM (it runs the hugemem kernel). Twice now in the last few weeks we've seen it hang with the follow log message repeated many times in the logs at the time of the hang: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250) I see this error discussed in: http://oss.sgi.com/bugzilla/show_bug.cgi?id=410 ...and I'm wondering if the fixes mentioned in that bug are present in the 0.2-1 centosplus xfs drivers, or if it could get included in an xfs update for CentOS 4. Can anyone comment? Thanks for the...

...s_znode_cache: 356 * 11547 = 4110732 bytes zil_lwb_cache: 176 * 43 = 7568 bytes arc_buf_t: 20 * 7060 = 141200 bytes arc_buf_hdr_t: 188 * 7060 = 1327280 bytes dnode_t: 756 * 162311 = 122707116 bytes !! dmu_buf_impl_t: 332 * 18649 = 6191468 other: 14432256 bytes (regular kmem_alloc()) There is 1GB of RAM, 320MB is for the kernel. 1/3 if kernel memory is configured as ARC''s maximum. When it panics, debugger statistics show that there is around 2/3 of this actually allocated, but probably due memory fragmentation. The most important part is dnode_t probably as it loo...

Hi, Following "anonymous tracing" chapter, I wanna trace kmem_init(), but after reboot, I can''t get anything, why? Here is my short script kmem_init.d: #!/usr/sbin/dtrace -s fbt::kmem_init:entry { stack(); } then I just use: #dtrace -AFs kmem_init.d #reboot #dtrace -ae < got nothing here> Thanks, -Alex This message posted from opensolaris.org

...mem_getpages+0x1f/0xd0 Aug 27 19:27:38 sauron kernel: [<c01387da>] cache_grow+0xba/0x180 Aug 27 19:27:38 sauron kernel: [<c0138a0a>] cache_alloc_refill+0x16a/0x220 Aug 27 19:27:38 sauron kernel: [<c0138eb4>] __kmalloc+0x74/0x80 Aug 27 19:27:38 sauron kernel: [<c891d239>] kmem_alloc+0x59/0xc0 [xfs] Aug 27 19:27:38 sauron kernel: [<c88f92a0>] xfs_iread_extents+0x50/0x110 [xfs] Aug 27 19:27:38 sauron kernel: [<c0223949>] dev_queue_xmit+0x249/0x300 Aug 27 19:27:38 sauron kernel: [<c88d1a5e>] xfs_bmapi+0x1fe/0x1460 [xfs] Aug 27 19:27:38 sauron kernel: [<c...

Hi, is it somehow possible to use Dtrace for error injection in a kernel module? Something like changing: - function return value - value of a register If not, can it be implemented? I can do that via kmdb, but I need Dtrace for the time synchronization - chill() action. I can not combine Dtrace & kmdb: dtrace: failed to initialize dtrace: DTrace cannot be used when kernel debugger

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org