search for: 0xc

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

...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+0x...

...3 0x7ee1423a in rpcrt4 (+0x3423a) (0x0053e968) 4 0x7ee145c0 RPCRT4_ReceiveWithAuth+0x80() in rpcrt4 (0x0053e9f8) 5 0x7ee193f9 in rpcrt4 (+0x393f9) (0x0053ea68) 6 0x7bc6ef74 call_thread_func+0xc() in ntdll (0x0053ea78) 7 0x7bc6f140 call_thread_entry_point+0x70() in ntdll (0x0053eb48) 8 0x7bc778a5 in ntdll (+0x678a5) (0x0053f398) 9 0xb76b680e start_thread+0xbe() in libpthread.so.0 (0x0053f498) 10 0xb76378de...

...Input: AX 000Ch DX derivative-specific flags (0000h = clean up all) Output: None Apparently, device is not shut down based on the description of the problem. I am looking at int22() routine in comboot_call.c. I don't see it processes this request (AX=0xc) at all. Can someone help to clarify this? Thanks! Kevin

...000Ch > DX derivative-specific flags (0000h = clean up all) > Output: None > > Apparently, device is not shut down based on the description of the problem. I am looking at int22() routine in comboot_call.c. I don't see it processes this request (AX=0xc) at all. > > Can someone help to clarify this? comboot_call.c is part of gPXE/iPXE, which only supports a subset of the COMBOOT API. However, even if you are running on top of PXELINUX proper, the INT 22h interface is obsoleted in Syslinux 5+. Its direct replacement is the syslinux_final_...

...zfs`zio_dva_allocate+0x4c zfs`zio_write_compress+0x1ec zfs`arc_write+0xe4 zfs`dbuf_sync+0x6c0 zfs`dnode_sync+0x35c zfs`dmu_objset_sync_dnodes+0x6c zfs`dmu_objset_sync+0x54 zfs`dsl_dataset_sync+0xc zfs`dsl_pool_sync+0x64 zfs`spa_sync+0x1b0 zfs`txg_sync_thread+0x134 unix`thread_start+0x4 82 genunix`avl_walk+0xa0 zfs`metaslab_ff_alloc+0x9c zfs`space_map_alloc+0x10 zfs`...

...0c 0x0031e71c: 00000000 0031eb28 7369642f 3273306b 0x0031e72c: 00000000 00000000 00000000 00000000 0200: sel=1007 base=7ffc0000 limit=00000fff 32-bit rw- Backtrace: =>0 0x20736e69 (0x0031e708) fixme:winedbg:print_value ---error fixme:winedbg:print_value ---error 1 0x4403366b call_window_proc+0xcc(hwnd=, msg=0x10076, wp=0xc, lp=0, result=, arg=0x7369642f) in user32 (0x0031e748) fixme:winedbg:print_value ---error fixme:winedbg:print_value ---error 2 0x44036464 CallWindowProcW+0x80(func=, hwnd=, msg=0x10076, wParam=0xc, lParam=0) in user32 (0x0031e798) fixme:winedbg:print_value ---error 3...

...ng: http://rubyforge.org/tracker/?func=detail&atid=218&aid=26918&group_id=35 Category: Installer problems Group: current Status: Open Resolution: None Priority: 3 Submitted By: lasse fabisch (lassef) Assigned to: Nobody (None) Summary: ruby1.9 gem: wxruby2.so: [BUG] unknown type 0x22 (0xc given) Initial Comment: Hi, i downloaded: http://rubyforge.org/frs/download.php/52503/wxruby-ruby19-2.0.0-x86_64-linux.gem Installation was successfull. But when i do: [code] ruby -e "require ''wx''" [/code] I get: [result] <main>:422: [BUG] Segmentation fault r...

...000Ch > DX derivative-specific flags (0000h = clean up all) > Output: None > > Apparently, device is not shut down based on the description of the problem. I am looking at int22() routine in comboot_call.c. I don't see it processes this request (AX=0xc) at all. > > Can someone help to clarify this? comboot_call.c is part of gPXE/iPXE, which only supports a subset of the COMBOOT API. However, even if you are running on top of PXELINUX proper, the INT 22h interface is obsoleted in Syslinux 5+. Its direct replacement is the syslinux_final_...

...write over PCIe bus anymore. What am I missing? Thanks! Kevin -----Original Message----- From: H. Peter Anvin [mailto:hpa at zytor.com] Sent: Wednesday, February 12, 2014 10:07 PM To: Kevin Tran Cc: For discussion of Syslinux and tftp-hpa Subject: Re: [syslinux] SYSLINUX API call INT 22h/AX=0xC On 02/12/2014 08:31 PM, Kevin Tran wrote: > Hi Peter, > They use PXELINUX to download the OS deployment bootstrap. When this is completed, they want to shutdown the stack including the UNDI driver before jumping to the kernel. > > Thanks! > Kevin > That is better done by usi...

...onment that runs under qemu-kvm. For this I had to use OVMF so the nodes would boot in EFI mode (or should I say "UEFI mode" ?). This setup uses ipxe roms? to boot over the network. The short story is that I never got further than syslinux proclaiming "Failed to read blocks: 0xC" before even getting to the stage where it tries to load ldlinux.e64. Searching for answers I found a thread on the qemu-devel list discussing this problem. The user mjt (Michael Tokarev, also on this list) found a branch of ipxe that contains two patches that should solve this problem...

...der qemu-kvm. For this I had to use OVMF so the nodes > would boot in EFI mode (or should I say "UEFI mode" ?). This setup uses ipxe > roms to boot over the network. > > The short story is that I never got further than syslinux proclaiming "Failed > to read blocks: 0xC" before even getting to the stage where it tries to load > ldlinux.e64. Searching for answers I found a thread on the qemu-devel list This is happening if you are trying to boot syslinux.efi from iPXE that was not patched. In my understanding iPXE patches some UEFI network services in o...

...#39;t help with the problems on real hardware but have come across the > qemu problems before and maybe I can give some hints on that. Thank you, your help is much appreciated! >> The short story is that I never got further than syslinux proclaiming >> "Failed to read blocks: 0xC" before even getting to the stage where it >> tries to load ldlinux.e64. Searching for answers I found a thread on >> the qemu-devel list > > This is happening if you are trying to boot syslinux.efi from iPXE that > was not patched. I was using commit 87981bb from the bra...

...003621660: 2a1038c7021 [ 000002a1038c7021 cv_wait+0x3c() ] 000002a1038c70d1 exitlwps+0x10c(0, 100000, 42100002, 6000a729068, 6000a72912e, 42000002) 000002a1038c7181 proc_exit+0x1c(1, 0, ff000000, 1, 0, e965) 000002a1038c7231 exit+8(1, 0, ffbff9d0, 1, ff164770, 16419) 000002a1038c72e1 syscall_trap32+0xcc(0, 0, ffbff9d0, 1, ff164770, 16419) stack pointer for thread 3000351b620: 2a101f864b1 Which is ok. However all the other threads (650 of them) were in cv_wait: bash-3.00# cat nfsd.txt | grep -c "nfssys+" 650 bash-3.00# cat nfsd.txt | grep -c "cv_wait+" 651 bash-3.00# bash-3...

...ypt -lnsl -lm -lc -lnss_files -lnss_dns -lresolv -lc -lnss_files -lnss_dns -lresolv >&5 /usr/lib/mysql/libmysqlclient.a(ssl.o)(.gnu.linkonce.d.__vt_Q25yaSSL7Message+0x8): undefined reference to `__pure_virtual' /usr/lib/mysql/libmysqlclient.a(ssl.o)(.gnu.linkonce.d.__vt_Q25yaSSL7Message+0xc): undefined reference to `__pure_virtual' /usr/lib/mysql/libmysqlclient.a(ssl.o)(.gnu.linkonce.d.__vt_Q25yaSSL7Message+0x10): undefined reference to `__pure_virtual' /usr/lib/mysql/libmysqlclient.a(ssl.o)(.gnu.linkonce.d.__vt_Q25yaSSL7Message+0x14): undefined reference to `__pure_virtual...

...azer_usb RET ioctl 0 67611 blazer_usb CALL close(0x5) 67611 blazer_usb RET close 0 67611 blazer_usb CALL close(0x4) 67611 blazer_usb RET close 0 67611 blazer_usb CALL gettimeofday(0x7fffffffcb80,0) 67611 blazer_usb RET gettimeofday 0 67611 blazer_usb CALL write(0x2,0x7fffffffc0f0,0xc) 67611 blazer_usb GIO fd 2 wrote 12 bytes " 0.002761 " 67611 blazer_usb RET write 12/0xc 67611 blazer_usb CALL write(0x2,0x7fffffffc0f0,0x34) 67611 blazer_usb GIO fd 2 wrote 52 bytes "Checking device (06DA/0201) (/dev/usb//dev/ugen0.2) " 67...

>>> > OK I got lost. > are you saying you finally were able to chainload syslinux.efi on the HP?? > by doing what? Some magic in dhcpd.conf: ? ? ???if option architecture-type = 00:09 { ? ? ? ???filename "efi64/syslinux-87020-or.efi"; ? ? ???option pxelinux.pathprefix "http://bla/efi64/"; ? ? ???} elsif option architecture-type = 00:07 { ? ? ?

>>> Is this possible? Are you saying the FW is stealing the DHCP response away before iPXE gets it?? I haven't thought of this possibility. Or am I misunderstanding you? <<< I'm saying that "probably" iPXE is trigerring a new PXE sequence with a different arch but the one that finally loads the new NBP is really the FW. >>> Since I'm

On 02/12/2014 08:31 PM, Kevin Tran wrote: > Hi Peter, > They use PXELINUX to download the OS deployment bootstrap. When this is completed, they want to shutdown the stack including the UNDI driver before jumping to the kernel. > > Thanks! > Kevin > That is better done by using syslinux_shuffle_boot_pm() or syslinux_shuffle_boot_rm() as appropriate; they shut down the stack

...n to get a CallerID to work? In addition iax -codec are not compatible with earlier asterisk (1.4); I have selected ulaw / alaw but Asterisk 1.4 wants GSM: chan_iax2.c:9541 socket_process: Rejected connect attempt from 192.168.141.8, requested/capability 0x2/0x703 incompatible with our capability 0xc. -- Joseph