search for: phsyical

Hi all! I'm having problems no end on my 4.8-STABLE box, and I hope you can help me. My processes get lots of signals (mostly 6, 10 and 11), and my kernel dumps core very often. I have the core dumps from the 4 latest crashes. See attachment for more info. Notice the common values for IdlePTD and initial pcb. Does this mean anything? There are other problems as well: 1) Some time ago KDE

Hi all, Virtual ISAs such as WebAssembly and NVPTX use infinite virtual register sets instead of traditional phsyical registers. PrologEpilogInserter is run after register allocation and asserts that all virtuals have been allocated but doesn't otherwise depend on this if scavenging is not needed. We'd like to use the target-independent PEI code for WebAssembly, so we're proposing a TargetRegisterInfo...

...o compiling techniques so I'm sorry for the stupid questions. Question 1: My idea is to lower the select SDNode as follows: %res1 = %falseVal %res2 = setc %trueVal, %condition Where setc is conditional mov. The question is how can I make sure that %res1 and %res2 are assigned to the same phsyical register? (I'm assuming you can only define virtual register once, is this correct assumption?) Question 2: What kind of information if any the front end needs about the target architecture? Am I able to use gcc front end to compile for the new architecture and what if there are 32- an...

...rg > > Sent: Wednesday, December 9, 2015 4:31:31 PM > > Subject: [llvm-dev] Allowing virtual registers after register allocation > > > > > > Hi all, > > Virtual ISAs such as WebAssembly and NVPTX use infinite virtual > > register sets instead of traditional phsyical registers. > > PrologEpilogInserter is run after register allocation and asserts > > that all virtuals have been allocated but doesn't otherwise depend > > on this if scavenging is not needed. We'd like to use the > > target-independent PEI code for WebAssembly, so w...

...me detail... Please mail me if there is more I'm ment to do. Thanks in advance :) ultraviolet@tulip:~ %> uname -a FreeBSD tulip.epweb.co.za 4.8-STABLE FreeBSD 4.8-STABLE #0: Wed Jun 11 10:09:55 SAST 2003 root@tulip.epweb.co.za:/usr/src/sys/compile/TULIP i386 Panic message: IdlePTD at phsyical address 0x0042a000 initial pcb at physical address 0x0036e460 panicstr: vm_map_entry_create: kernel resources exhausted initial pcb at physical address 0x0036e460 panicstr: vm_map_entry_create: kernel resources exhausted panic messages: --- panic: vm_map_entry_create: kernel resources exhausted sy...

...sday, December 9, 2015 4:31:31 PM >> > Subject: [llvm-dev] Allowing virtual registers after register allocation >> > >> > >> > Hi all, >> > Virtual ISAs such as WebAssembly and NVPTX use infinite virtual >> > register sets instead of traditional phsyical registers. >> > PrologEpilogInserter is run after register allocation and asserts >> > that all virtuals have been allocated but doesn't otherwise depend >> > on this if scavenging is not needed. We'd like to use the >> > target-independent PEI code for W...

...unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x00352000 initial pcb at physical address 0x002bf8e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xaaae fault code = supervisor write, page not present instruction pointer = 0x8:0xc0193de9 stack pointer...

And then I should be ready to roll with my project.. I have some fine tuning of the looks to do after, but funtionality first! This is probably a rails question.. but I''m not sure where to sign up for the rails questions email group? (I guess I turned this into a 2 question email). I''ll ask here and then if someone will send me the url of where I go to sign up for the rails

.../or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x05332000 initial pcb at physical address 0x0029f980 panicstr: page fault panic messages: --- Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc023ceeb stack pointer = 0x10:0xcf7d9ea4 frame pointer = 0x10:0xcf7d9ec0 code segmen...

...) I have had a number of occerances where the bridge stops forwarding packets from the domUs to the physical interface of the host. The domUs and domU can all communicate amongst themselves but the domUs lose their connectivity to the outside world. The only fix I have found is to reboot the phsyical server, which is a Supermicro 5014. The server has Broadcom NICs and the kernel is using the tg3 driver. I appreciate that fc7 is getting a little old but the server is colocated 600 miles away and hence upgrading the OS isn''t currently an option. ANy clues or even a pointer to a pos...

Morning all ... 'K, this one is a first for me ... server crashed this aft and savecore wouldn't dump the resultant core: pluto# savecore -v /vm/crash dumplo = 4362141696 (8519808 * 512) savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #1: Sat May 31 22:57:04 ADT 2003 " and " #(#(#(" savecore: reboot savecore: dump time is zero

...e-based forwarding enabled, default to deny, unlimited logging ad0: 6204MB <ST36531A> [13446/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ==================================================================================== IdlePTD at phsyical address 0x002b4000 initial pcb at physical address 0x00237ea0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xe37e0000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0142ffa stack point...

...-RELEASE). I gather she made a few attempts to get mozilla to start and then the system panic'd. According to the crashdump, p->p_leader is NULL but according to the code, this can never happen. This is a UP Athlon XP-1800 with the kernel built for a K7. Anyone got any ideas? IdlePTD at phsyical address 0x003a3000 initial pcb at physical address 0x00302ac0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x184 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015c0dd stack pointer...

...un more debug commands or whatever is helpful. Thanks in advance. Ben debuging information follows... # uname -a FreeBSD digitalpimp.princenet 4.8-STABLE FreeBSD 4.8-STABLE #1: Thu Jun 12 14:13:23 EDT 2003 root@digitalpimp.princenet:/usr/src/sys/compile/PIMPIN48 i386 panic message: IdlePTD at phsyical address 0x0040c000 initial pcb at physical address 0x00353c40 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffff000a fault code = supervisor read, page not present instruction pointer = 0x8:0xc02639dc stack pointer = 0x...

...unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x0040f000 initial pcb at physical address 0x003618e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x121a2673 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0283ad3 stack point...

...there was a bright white message: issignal. This shows up at X11 startup. Then the system coredumped. Below is more information. Is this a serious problem? Please help me, I'm an inexperienced programmer and I can't do this alone. Daniela # gdb -k kernel.debug vmcore.0 ... IdlePTD at phsyical address 0x005ba000 initial pcb at physical address 0x004d3100 panicstr: ufsdirhash_lookup: bad offset in hash array panic messages: --- panic: ufsdirhash_lookup: bad offset in hash array syncing disks... 80 2 1 done Uptime: 1d21h53m1s /dev/vmmon: Module vmmon: unloaded dumping to dev #ad/0x30001,...

...e and thought I would route a /24 to ds0 instead of to the IP on ds0 (which I had done for a number of other aggregate routes). The only other "strange" thing about the box is that ds0 is loaded via kld. I will see if I can reproduce it on a non production box. ---Mike IdlePTD at phsyical address 0x0032e000 initial pcb at physical address 0x002a3d80 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc019a569 stack pointer...

...unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x005bf000 initial pcb at physical address 0x004dbb00 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 145 111 102 41 37 31 31 31 31 31 31 31 panic: lockmgr: locking against myself Uptime: 2d9h18m37s dumping to dev #ad/0x3003...

...ember 9, 2015 4:31:31 PM >>> Subject: [llvm-dev] Allowing virtual registers after register >>> allocation >>> >>> >>> Hi all, >>> Virtual ISAs such as WebAssembly and NVPTX use infinite virtual >>> register sets instead of traditional phsyical registers. >>> PrologEpilogInserter is run after register allocation and asserts >>> that all virtuals have been allocated but doesn't otherwise depend >>> on this if scavenging is not needed. We'd like to use the >>> target-independent PEI code for WebAs...

The following 5 patches are re-submissions of the vt-d patch. This set of patches has been tested against cs# 15080 and is now much more mature and tested against more environments than the original patch. Specifically, we have successfully tested the patch with following environements: - 32/64-bit Linux HVM guest - 32-bit Windows XP/Vista (64-bit should work but did not test) -