search for: 16f

...156 <_Z4fct3Pf+0x76> 156: c5 fa 11 43 18 vmovss %xmm0,0x18(%rbx) 15b: c5 fa 10 43 1c vmovss 0x1c(%rbx),%xmm0 160: e8 00 00 00 00 callq 165 <_Z4fct3Pf+0x85> 165: c5 fa 11 43 1c vmovss %xmm0,0x1c(%rbx) 16a: c5 fa 10 43 20 vmovss 0x20(%rbx),%xmm0 16f: e8 00 00 00 00 callq 174 <_Z4fct3Pf+0x94> 174: c5 fa 11 43 20 vmovss %xmm0,0x20(%rbx) 179: c5 fa 10 43 24 vmovss 0x24(%rbx),%xmm0 17e: e8 00 00 00 00 callq 183 <_Z4fct3Pf+0xa3> 183: c5 fa 11 43 24 vmovss %xmm0,0x24(%rbx) 188: c5 fa 10 43 28...

I am troubled by what appears to be a glitch in the current distribution, or in its installation on our system. I've traced it, and found a work- around. Is this normal? Is there a cleaner solution? The problem: During a package installation, the warning message "WARNING: ignoring environment value of R_HOME" from line 31 of <R_HOME>/bin/R is accidentally spliced into the

...]__ksymtab_journal_ack_err+0/8> Trace; f88b5da0 <[jbd]__kstrtab_journal_enable_debug+811/5be5> Trace; f88c4bc0 <[ext3]ext3_dirty_inode+160/180> Trace; c0157ff5 <__mark_inode_dirty+b5/4e0> Trace; c0131f7a <generic_file_write+2ba/2bb0> Trace; c01de57f <scsi_io_completion+16f/850> Trace; c0138bb5 <free_pages+535/27c0> Trace; f88bf0c9 <[ext3]ext3_file_write+39/d0> Trace; c015e991 <seq_printf+f01/a9c0> Trace; c015ee7c <seq_printf+13ec/a9c0> Trace; c015ff11 <seq_printf+2481/a9c0> Trace; c01586ce <clear_inode+8e/260> Trace; c01587ac &l...

...0 PhysBasePtr: 0x0 LinBytesPerScanLine: 0 BnkNumberOfImagePages: 0 LinNumberOfImagePages: 0 LinRedMaskSize: 0 LinRedFieldPosition: 0 LinGreenMaskSize: 0 LinGreenFieldPosition: 0 LinBlueMaskSize: 0 LinBlueFieldPosition: 0 LinRsvdMaskSize: 0 LinRsvdFieldPosition: 0 MaxPixelClock: 0 Mode: 16f (0x0) ModeAttributes: 0x0 WinAAttributes: 0x0 WinBAttributes: 0x0 WinGranularity: 0 WinSize: 0 WinASegment: 0x0 WinBSegment: 0x0 WinFuncPtr: 0x0 BytesPerScanline: 0 XResolution: 0 YResolution: 0 XCharSize: 0 YCharSize: 0 NumberOfPlanes: 0 BitsPerPixel: 0 NumberOfBanks: 0 MemoryMode...

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking