search for: 0xc9

...live traffic somewhere else but before I did I managed to get the below: # dtrace -n profile-997''{@[stack()]=count();}'' [...] unix`default_lock_delay+0x48 unix`mutex_vector_enter+0x99 zfs`dmu_zfetch_find+0x1f9 zfs`dmu_zfetch+0xc9 zfs`dbuf_read+0x27a zfs`dmu_buf_hold_array_by_dnode+0x287 zfs`dmu_buf_hold_array+0x81 zfs`dmu_read_uio+0x49 zfs`zfs_read+0x15e zfs`zfs_shim_read+0xc genunix`fop_read+0x31 genunix`read+0x1...

...xt+0x1da9): undefined reference to `__guard' sio.o(.text+0x1db9): undefined reference to `__stack_smash_handler' vga_isa.o: In function `isavga_probe': vga_isa.o(.text+0x10): undefined reference to `__guard' vga_isa.o(.text+0xb9): undefined reference to `__guard' vga_isa.o(.text+0xc9): undefined reference to `__stack_smash_handler' vga_isa.o(.text+0xc9): undefined reference to `__stack_smash_handler' *** Error code 1 Stop in /usr/obj/usr/src/sys/FJUTTSI. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. anyone succesfully compiled 4.8p3 with fsta...

...t;MCInst #1545 GSLBGT                                         #  <MCOperand Reg:23>                                         #  <MCOperand Reg:24>                                         #  <MCOperand Reg:25>>     gslhle    $8, $9, $10             # encoding: [0x12,0x50,0x28,0xc9]                                         # <MCInst #1553 GSLHLE                                         #  <MCOperand Reg:311>                                         #  <MCOperand Reg:312>                                         #  <MCOperand Reg:313>>     gslhgt    $1...

...bc, 0xbd, 0xbf }, { 0xbc, 0xbd, 0xbe, 0xc0 }, { 0xbd, 0xbe, 0xbf, 0xc1 }, { 0xbe, 0xbf, 0xc0, 0xc2 }, { 0xbf, 0xc0, 0xc1, 0xc3 }, { 0xc0, 0xc1, 0xc2, 0xc4 }, { 0xc1, 0xc2, 0xc3, 0xc5 }, { 0xc2, 0xc3, 0xc4, 0xc6 }, { 0xc3, 0xc4, 0xc5, 0xc7 }, { 0xc4, 0xc5, 0xc6, 0xc8 }, { 0xc5, 0xc6, 0xc7, 0xc9 }, { 0xc6, 0xc7, 0xc8, 0xca }, { 0xc7, 0xc8, 0xc9, 0xcb }, { 0xc8, 0xc9, 0xca, 0xcc }, { 0xc9, 0xca, 0xcb, 0xcd }, { 0xca, 0xcb, 0xcc, 0xce }, { 0xcb, 0xcc, 0xcd, 0xcf }, { 0xcc, 0xcd, 0xce, 0xd0 }, { 0xcd, 0xce, 0xcf, 0xd1 }, { 0xce, 0xcf, 0xd0, 0xd2 }, { 0xcf, 0xd0, 0xd1, 0xd3 }, { 0xd...

...f80490268 at kdb_backtrace+0x68 #1 0xffffffff8045630a at panic+0x21a #2 0xffffffff8068bbc2 at vm_page_unwire+0x102 #3 0xffffffff80678702 at vm_fault_unwire+0xd2 #4 0xffffffff80680841 at vm_map_delete+0x171 #5 0xffffffff80680abf at vm_map_remove+0x5f #6 0xffffffff80683ee9 at vmspace_exit+0xc9 #7 0xffffffff8041f3ad at exit1+0x72d #8 0xffffffff804203ae at sys_sys_exit+0xe #9 0xffffffff806afd6f at amd64_syscall+0x3bf #10 0xffffffff8069a817 at Xfast_syscall+0xf7 Uptime: 2d0h35m3s Fri Sep 20 17:49:57 2013 +1000 ozsrv04# kgdb kernel.debug /var/crash/vmcore.1 ... panic: vm_pa...

...950. However, a trouble blocked me during the machines run after two days. The machines crashed and the syslog said it got the following messages: ------------------ part dump of /var/log/messages ---------------------- ..... Jul 25 02:15:02 vega2008 kernel: [<c045bc58>] ? exit_mmap+0x93/0xc9 Jul 25 02:15:02 vega2008 kernel: [<c04214c2>] ? mmput+0x25/0x68 Jul 25 02:15:02 vega2008 kernel: [<c046e9c9>] ? flush_old_exec+0x4f8/0x777 Jul 25 02:15:02 vega2008 kernel: [<c046dfcf>] ? kernel_read+0x32/0x43 Jul 25 02:15:02 vega2008 kernel: [<c0490e60>] ? load_elf_binar...

...8) [/build/buildd/wine1.3-1.4/dlls/ntdll/signal_i386.c:2532] in ntdll (0x00a4eb28) 12 0x7bc72f3e RtlRaiseException+0x21() in ntdll (0x00a4eb48) 13 0x7bc7b9e8 start_thread+0xf7(info=0x7ffbcfb8) [/build/buildd/wine1.3-1.4/dlls/ntdll/thread.c:405] in ntdll (0x00a4f398) 14 0xf75dcd1a start_thread+0xc9() in libpthread.so.0 (0x00a4f498) Backtracing for thread 001e in process 000e (C:\windows\system32\services.exe): Backtrace: =>0 0xf778342e __kernel_vsyscall+0xe() in [vdso].so (0x0053e7f8) 1 0xf75e3bcb __libc_read+0x4a() in libpthread.so.0 (0x0053e7f8) 2 0x7bc41bff NtReadFile+0x34e(hFile=0...

Hi Konrad I encountered a bug when trying to bring offline a cpu then online it again in HVM. As I''m not very familiar with HVM stuffs I cannot come up with a quick fix. The HVM DomU is configured with 4 vcpus. After booting into command prompt, I do following operations. # echo 0 > /sys/devices/system/cpu/cpu3/online # echo 1 > /sys/devices/system/cpu/cpu3/online With

...bc, 0xbd, 0xbf }, { 0xbc, 0xbd, 0xbe, 0xc0 }, { 0xbd, 0xbe, 0xbf, 0xc1 }, { 0xbe, 0xbf, 0xc0, 0xc2 }, { 0xbf, 0xc0, 0xc1, 0xc3 }, { 0xc0, 0xc1, 0xc2, 0xc4 }, { 0xc1, 0xc2, 0xc3, 0xc5 }, { 0xc2, 0xc3, 0xc4, 0xc6 }, { 0xc3, 0xc4, 0xc5, 0xc7 }, { 0xc4, 0xc5, 0xc6, 0xc8 }, { 0xc5, 0xc6, 0xc7, 0xc9 }, { 0xc6, 0xc7, 0xc8, 0xca }, { 0xc7, 0xc8, 0xc9, 0xcb }, { 0xc8, 0xc9, 0xca, 0xcc }, { 0xc9, 0xca, 0xcb, 0xcd }, { 0xca, 0xcb, 0xcc, 0xce }, { 0xcb, 0xcc, 0xcd, 0xcf }, { 0xcc, 0xcd, 0xce, 0xd0 }, { 0xcd, 0xce, 0xcf, 0xd1 }, { 0xce, 0xcf, 0xd0, 0xd2 }, { 0xcf, 0xd0, 0xd1, 0xd3 }, { 0xd...

...d one This resulted in hot-plug being unsuccessful, as a port with the same name already exists (even though it was unplugged). This behaviour resulted in a warning message like this one: -------------------8<--------------------------------------- WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) Hardware name: KVM sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' Call Trace: [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff8106b6f6>] ? warn_slowpath_fmt+0x46/0x50 [<fffffff...

...d one This resulted in hot-plug being unsuccessful, as a port with the same name already exists (even though it was unplugged). This behaviour resulted in a warning message like this one: -------------------8<--------------------------------------- WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) Hardware name: KVM sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' Call Trace: [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff8106b6f6>] ? warn_slowpath_fmt+0x46/0x50 [<fffffff...

I have an OCFS2 filesystem on a coraid AOE device. It mounts fine, but with heavy I/O the server self fences claiming a write timeout: (16,2):o2hb_write_timeout:164 ERROR: Heartbeat write timeout to device etherd/e0.1p1 after 12000 milliseconds (16,2):o2hb_stop_all_regions:1789 ERROR: stopping heartbeat on all active regions. Kernel panic - not syncing: ocfs2 is very sorry to be fencing this

I''m not sure if this is a problem with the iscsitarget or zfs. I''d greatly appreciate it if it gets moved to the proper list. Well I''m just about out of ideas on what might be wrong.. Quick history: I installed OS 2008.05 when it was SNV_86 to try out ZFS with VMWare. Found out that multilun''s were being treated as multipaths so waited till SNV_94 came out to

...0x6e, 0xff, 0x7f, 0xff, 0x64, 0xff, 0x87, 0xff, 0x5b, 0xff, 0x71, 0xff, 0x4c, 0xff, 0x76, 0xff, 0x58, 0xff, 0x90, 0xff, 0x7a, 0xff, 0xa2, 0xff, 0xa7, 0xff, 0xd3, 0xff, 0xe3, 0xff, 0xf7, 0xff, 0xfb, 0xff, 0x04, 0x00, 0xe2, 0xff, 0xef, 0xff, 0xc2, 0xff, 0xbc, 0xff, 0xcd, 0xff, 0xc9, 0xff, 0xc8, 0xff, 0xbc, 0xff, 0x8f, 0xff, 0x7d, 0xff, 0x51, 0xff, 0x42, 0xff, 0x72, 0xff, 0x5a, 0xff, 0xb9, 0xff, 0x9f, 0xff, 0xea, 0xff, 0xc3, 0xff, 0xea, 0xff, 0xca, 0xff, 0xf9, 0xff, 0xc8, 0xff, 0x20, 0x00, 0xf3, 0xff, 0x26, 0x00, 0xf7, 0xff, 0xd6, 0xff, 0xa2, 0xff, 0xa3...

...plug being unsuccessful, as a port with the same > name already exists (even though it was unplugged). > > This behaviour resulted in a warning message like this one: > > -------------------8<--------------------------------------- > WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) > Hardware name: KVM > sysfs: cannot create duplicate filename > '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' > > Call Trace: > [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 > [<ffffffff8106b6f6>] ? warn_sl...

...plug being unsuccessful, as a port with the same > name already exists (even though it was unplugged). > > This behaviour resulted in a warning message like this one: > > -------------------8<--------------------------------------- > WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) > Hardware name: KVM > sysfs: cannot create duplicate filename > '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' > > Call Trace: > [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 > [<ffffffff8106b6f6>] ? warn_sl...

...eserve_inode_write+0x33/0x89 [<c016aac1>] ext3_mark_inode_dirty+0x18/0x31 [<c017082b>] journal_start+0x7f/0xa9 [<c016ab26>] ext3_dirty_inode+0x4c/0x5f [<c0156c20>] __mark_inode_dirty+0x24/0xce [<c01527d2>] inode_setattr+0x118/0x123 [<c016a951>] ext3_setattr+0xc9/0x104 [<c0152903>] notify_change+0xda/0x143 [<c013c6b9>] sys_utime+0xec/0x110 [<c013e5ad>] __fput+0xc2/0xde [<c013d251>] filp_close+0x5a/0x63 [<c013d2b2>] sys_close+0x58/0x7a [<c0108807>] syscall_call+0x7/0xb Code: 0f 0b 8f 06 52 3d 22 c0 83 c4 14 85 f6 75...

....log It starts like this: Oct 30 22:42:36 localhost kernel: btrfs bad mapping eb start 982689189888 len 4096, wanted 4424 17 Oct 30 22:42:36 localhost kernel: ------------[ cut here ]------------ Oct 30 22:42:36 localhost kernel: WARNING: at fs/btrfs/extent_io.c:4661 map_private_extent_buffer+0x83/0xc9() Oct 30 22:42:36 localhost kernel: Hardware name: A780L3L Oct 30 22:42:36 localhost kernel: Modules linked in: hwmon_vid snd_hda_codec_hdmi nvidia(PO) snd_hda_codec_realtek snd_hda_intel snd_hda_codec i2c_piix4 k10temp Oct 30 22:42:36 localhost kernel: Pid: 7143, comm: btrfs-endio-wri Tainted: P...

Hello, This series fixes a few races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches for

Hello, This series fixes a few races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches for