search for: 0x12345

Hi, FreeBSD/amd64 8-STABLE, Dovecot 2.0.6, stops in random times with: Nov 14 18:42:14 be dovecot: master: Fatal: kevent(): Invalid argument Any ideas? Thanks,

Hi *, are there some special settings except of "load_rails: true" to make ActiveRecord models accessible within my workers? I''ve just installed the latest version of this great plugin, but I keep getting undefined method [] for #<DRb::DRbUnknown:0x12345> (line 105 in backgroundrb.rb) when one of the arguments for the worker is an ActiveRecord object. I assume that the MiddleMan somehow doesn''t see my models. I have already tried to put model :blabla, :foo, :bar in application.rb, but this didn''t help. Any ideas? Regards...

...t with the optimized outputs. The neon_helper.c testcase is clearly misoptimized by gcc-head here: http://embed.cs.utah.edu/embarrassing/jan_10/harvest/compare_clang-head_gcc-head/compare_23BD1620_disasm.shtml Try calling it like this: int main() { printf("%d\n", helper_neon_rshl_s8(0x12345, 15)); return 0; } Prints 74496 here, and not 0 (gcc-head optimized it to a function returning 0). Best regards, --Edwin

I built and install Dovecot 2.0Beta4 on my NetBSD/amd64-current system, and am seeing the user-owned imap processes busy-looping. In Dovecot 1.2.x (and 1.x and 0.x..) I force ionotify and ioloop to kqueue, so I suspected that was the problem. Turns out it's not: Using poll or none also causes the same problem. This did not happen in 1.2.8 (didn't try anything later than that).

Hi folks, I've posted an updated code size comparison between LLVM, GCC, and others here: http://embed.cs.utah.edu/embarrassing/ New in this version: - much larger collection of harvested functions: more than 360,000 - bug fixes and UI improvements - added the x86 Open64 compiler John

...` @@ -98,7 +124,10 @@ Increase the verbosity of the APIC code ### badpage > `= List of [ <integer> | <integer>-<integer> ]` -Specify that certain pages, or certain ranges of pages contain bad bytes and should not be used. For example, if your memory tester says that byte `0x12345678` is bad, you would place `badpage=0x12345` on Xen''s command line. +Specify that certain pages, or certain ranges of pages contain bad +bytes and should not be used. For example, if your memory tester says +that byte `0x12345678` is bad, you would place `badpage=0x12345` on +Xen'...

...original code that was interrupted by the original NMI. Debug: ===== We've added lots of debugging features to make it easier to debug. hypervisor.S is loaded with print to serial code. Be careful, the output of hex numbers are backwards. So if you do a PRINT_QUAD(%rax), and %rax has in it 0x12345, you will get 54321 out of the serial. It's just easier that way (code wise). The macros with a 'S_' prefix will store the regs used on the stack, but that's not always good, since most of the hypervisor code, does not have a usable stack. Page tables. There's functions in lgue...

...original code that was interrupted by the original NMI. Debug: ===== We've added lots of debugging features to make it easier to debug. hypervisor.S is loaded with print to serial code. Be careful, the output of hex numbers are backwards. So if you do a PRINT_QUAD(%rax), and %rax has in it 0x12345, you will get 54321 out of the serial. It's just easier that way (code wise). The macros with a 'S_' prefix will store the regs used on the stack, but that's not always good, since most of the hypervisor code, does not have a usable stack. Page tables. There's functions in lgue...

I''m having trouble switching into user mode with my domU kernel -- everytime I call __HYPERVISOR_iret, the hypervisor calls into my kernel via the registered callback handler. None of the bits in the event channel pending arrays are set. If I return via the iret call, the hypervisor immediately calls back into the handler. The user RIP never changes, so it is clearly not making forward