search for: 0x1cb

...c:smb_panic(1599) PANIC (pid 28277): Security context stack overflow! [2007/08/26 06:01:13, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 63 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c293] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c386] #2 /usr/sbin/smbd(push_sec_ctx+0x1cb) [0x80db8db] #3 /usr/sbin/smbd(become_root+0xb) [0x80d140b] #4 /usr/sbin/smbd(sid_to_gid+0xd8) [0x81eec98] #5 /usr/sbin/smbd(pdb_set_group_sid+0x4d) [0x81e55cd] #6 /usr/sbin/smbd(pdb_set_group_sid_from_rid+0x67) [0x81ee287] #7 /usr/sbin/smbd(init_sam_from_buffer_v3+0x8f1) [0x81e7ed1]...

...56>] lock_acquire+0xce/0x117 > [ 326.168615] [<ffffffff905a367e>] _raw_spin_lock_irqsave+0x3f/0x51 > [ 326.168623] [<ffffffffa00d6a8a>] alarm_timer_callback+0xf1/0x179 [nouveau] > [ 326.168651] [<ffffffffa00da895>] nv04_timer_alarm_trigger+0x1b1/0x1cb [nouveau] > [ 326.168679] [<ffffffffa00daaa0>] nv04_timer_alarm+0xb5/0xbe [nouveau] > [ 326.168708] [<ffffffffa00d54ac>] nouveau_fan_update+0x234/0x252 [nouveau] > [ 326.168735] [<ffffffffa00d54df>] nouveau_fan_alarm+0x15/0x17 [nouveau] > [ 326...

..._generic_alloc_coherent+0x8f/0x140 [Mon Oct 23 16:43:32 2017]? [<ffffffff81065c0d>] gart_alloc_coherent+0x2d/0x40 [Mon Oct 23 16:43:32 2017]? [<ffffffffc012e4d3>] mlx4_buf_direct_alloc.isra.6+0xd3/0x1a0 [mlx4_core] [Mon Oct 23 16:43:32 2017]? [<ffffffffc012e76b>] mlx4_buf_alloc+0x1cb/0x240 [mlx4_core] [Mon Oct 23 16:43:32 2017]? [<ffffffffc04dd85e>] create_qp_common.isra.31+0x62e/0x10d0 [mlx4_ib] [Mon Oct 23 16:43:32 2017]? [<ffffffffc04de44e>] mlx4_ib_create_qp+0x14e/0x480 [mlx4_ib] [Mon Oct 23 16:43:32 2017]? [<ffffffffc06df20c>] ? ipoib_cm_tx_init+0x5c/0...

...;ffffffff81032953>] handle_irq+0x83/0x8c [ 2417.746707] [<ffffffff81031f19>] do_IRQ+0x57/0xbe [ 2417.746711] [<ffffffff8143bf13>] ret_from_intr+0x0/0xf [ 2417.746714] [<ffffffff8102f085>] cpu_idle+0x5c/0xb3 [ 2417.746717] [<ffffffff81434180>] start_secondary+0x1c7/0x1cb [ 2417.746720] [ 2417.746720] to a HARDIRQ-irq-unsafe lock: [ 2417.746722] (&(&mm->unused_lock)->rlock){+.+...} [ 2417.746724] ... which became HARDIRQ-irq-unsafe at: [ 2417.746725] ... [<ffffffff81097418>] __lock_acquire+0x6eb/0x8f4 [ 2417.746729] [<ffffffff81097769>...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 7/29/2014 11:20 AM, Ben Johnson wrote: >> On 7/29/2014 3:13 AM, Steffen Kaiser wrote: >>> On Mon, 28 Jul 2014, Ben Johnson wrote: >>> >>>> I have some debugging output in my pipe script; the output looks >>> >>> How does your script looks like?

...cktrace+0x3b) [0x812d07b] 1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c061e] 2: [0xc1a400] 3: /usr/lib/xorg/modules/drivers//nouveau_drv.so(NvSetupOutputs+0x3b) [0x1f16ab] 4: /usr/lib/xorg/modules/drivers//nouveau_drv.so [0x1e8c4a] 5: /usr/bin/Xorg(InitOutput+0x4e9) [0x80a8e39] 6: /usr/bin/Xorg(main+0x1cb) [0x806b92b] 7: /lib/libc.so.6(__libc_start_main+0xe6) [0xaa5a66] 8: /usr/bin/Xorg [0x806afa1] Fatal server error: Caught signal 11. Server aborting Is there a workaround (special configuration entry, kernel parameter etc.) available? -- Configure bugmail: http://bugs.freedesktop.org/userpref...

https://bugs.freedesktop.org/show_bug.cgi?id=86650 Bug ID: 86650 Summary: (NV44): initrd gpu lockup from 3.12 or 3.13 onwards Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee:

...b/dovecot/libdovecot.so.0(io_add+0x9b) > [0x7f23489f89fb] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_io_listeners_add+0x69) > [0x7f23489a9e49] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_init_finish+0xb0) > [0x7f23489a9f90] -> /usr/lib/dovecot/deliver(main+0x1cb) > [0x7f234939269b] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) > [0x7f23485e6ec5] -> /usr/lib/dovecot/deliver(+0x31de) [0x7f23493931de] > /usr/local/bin/sa-learn-pipe.sh: line 52: 5584 Aborted > (core dumped) /usr/lib/dovecot/deliver -d "sa-training at...

...? nouveau_drm_load+0x154/0x565 [nouveau] kernel: [<ffffffffa020c455>] ? drm_get_minor+0x196/0x1e8 [drm] kernel: [<ffffffffa020e08b>] ? drm_get_pci_dev+0x141/0x243 [drm] kernel: [<ffffffff811a762c>] ? __pci_set_master+0x22/0x6d kernel: [<ffffffffa02c9656>] ? nouveau_drm_probe+0x1cb/0x1ee [nouveau] kernel: [<ffffffff811aa8de>] ? local_pci_probe+0x34/0x5b kernel: [<ffffffff8105350e>] ? work_for_cpu_fn+0xb/0x11 kernel: [<ffffffff8105502d>] ? process_one_work+0x1c1/0x2c8 kernel: [<ffffffff8105514c>] ? process_scheduled_works+0x18/0x25 kernel: [<ffffffff...

...2c,13,c0561940,c3a852b8,c3612690,...) at 0xc05623aa = callout_reset+0x14a realitexpire(c3a852b8,2d6100,c3612690,1,dd4f6cbc,...) at 0xc0561ab6 = realitexpire+0x176 softclock(0,0,c0747617,4a1,0,...) at 0xc0562c25 = softclock+0x235 ithread_loop(c35e5a20,dd4f6d38,0,0,0,...) at 0xc053268b = ithread_loop+0x1cb fork_exit(c05324c0,c35e5a20,dd4f6d38) at 0xc052eda1 = fork_exit+0xa1 fork_trampoline() at 0xc06f46b0 = fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xdd4f6d70, ebp = 0 --- Some debugging: (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc05512b3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown...

Hi, I am profiling some workloads for the voluntary and involuntary context switches. I am interested in finding out the reasons causing these two types of context switches. As far as I understand, involuntary context switch happens on expiration of time slice or when a higher priority process comes in. While the voluntary switch generally happens when a process is waiting for I/O etc. So to

I have an application ("The Rosetta Stone" 2.0.7a) which segfaults during the startup splash screen. According to strace() it is trying to munmap() an address (0x7a6b3000) which was never mmap()'d. I get identical behavior with Wine 20050111 and kernels 2.6.9 / 2.6.10 (I use gentoo-sources). I noticed some people had similar issues upgrading from 2.6.9 to 2.6.10.

...3] [<ffffffff8110d665>] filemap_write_and_wait+0x35/0x60 [ 153.920013] [<ffffffffa01cf622>] __btrfs_write_out_cache+0x792/0x9a0 [btrfs] [ 153.920013] [<ffffffffa0175b25>] ? __find_space_info+0x85/0xa0 [btrfs] [ 153.920013] [<ffffffffa017f28b>] ? btrfs_run_delayed_refs+0x1cb/0x450 [btrfs] [ 153.920013] [<ffffffffa01cf8c5>] btrfs_write_out_cache+0x95/0xf0 [btrfs] [ 153.920013] [<ffffffffa017fa2f>] btrfs_write_dirty_block_groups+0x51f/0x5f0 [btrfs] [ 153.920013] [<ffffffffa01e9b2a>] commit_cowonly_roots+0xec/0x1c6 [btrfs] [ 153.920013] [<ffff...

Hi - I''m trying btrfs with kernel 2.6.38.8-32.fc15.x86_64 (a Fedora kernel). I''m just doing a tar-to-tar copy onto the file system with compress- force=zlib. Here are some traces of the stuck processes. flush-btrfs-5 seems to be stuck: Jul 8 11:49:40 xback2 kernel: [74920.681032] flush-btrfs-5 D ffff88003c7bae60 0 11712 2 0x00000080 Jul 8 11:49:40 xback2 kernel:

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

...0 32 0 r . . 8 8 8 8 . . 0 16 0 0 0 0 0 0 0 None 0x1c8 24 tc 0 32 0 r . . 8 8 8 8 . . 0 16 0 16 16 16 16 0 0 Slow 0x1c9 24 tc 0 32 0 r y . 8 8 8 8 . . 0 16 0 0 0 0 0 0 0 None 0x1ca 24 tc 0 32 0 r y . 8 8 8 8 . . 0 16 0 16 16 16 16 0 0 Slow 0x1cb 24 tc 0 32 0 r y . 8 8 8 8 . . 0 16 0 0 0 0 0 0 0 None 0x1cc 24 tc 0 32 0 r y . 8 8 8 8 . . 0 16 0 16 16 16 16 0 0 Slow 0x1cd 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 0 0 0 0 0 0 0 None 0x1ce 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 0 16 16 16 16 0...

...all Trace: Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302453] [<ffffffff817cc037>] schedule+0x37/0x90 Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302454] [<ffffffff817cee2c>] schedule_timeout+0x20c/0x280 Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302457] [<ffffffff811af62b>] ? do_wp_page+0x1cb/0x4c0 Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302459] [<ffffffff817cca64>] wait_for_completion+0xa4/0x170 Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302461] [<ffffffff810a6a80>] ? wake_up_state+0x20/0x20 Jul 21 10:15:06 dioo-XPS kernel: [ 2399.302464] [<ffffffff810de000>] ? __call...

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

Hi, Chris (cc) and I try to get the SGE master monitor work with Apple Leopard dtrace. Unfortunately we are stuck with the error msg below. Anyone having an idea what could be the cause? What I can rule out as cause is function inlining for the reasons explained below. Background information on SGE master monitor implementation is under http://wiki.gridengine.info/wiki/index.php/Dtrace