similar to: ACPI Error: No handler for Region [POWS] (0xffffff000994f380) [IPMI] on Cisco UCS C200 M2

Hi, I have updated the firmware for perc raid controller card, network card, IDRAC firmware and the BIOS version on Dell R720 server. I have installed CentOS 6.4 and updated with all the latest packages using yum -y update. # cat /var/log/messages | grep -i error Sep 23 14:09:35 x24 kernel: ERST: Error Record Serialization Table (ERST) support is initialized. Sep 23 14:09:35 x24 kernel: ACPI

Hi, there's a regression going from 6.2 to 6.3, where it will panic upon booting the kernel within vm_fault. This problem has been discussed before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of May. It affects multiple (but identical) systems, here's an verbose boot leading to the panic. Please note that 6.2 was running fine on these machines, they also boot

Hi all, I have written a COM32 module called "acpioff", that, not surprisingly, powers off a machine using ACPI. I have tested it only using pxelinux.0 with a SeaBIOS/Qemu virtual machine. Since the changeset pulls in a "Linux-ized" version of the open source ACPI Component Architecture, it was too big to post as a patches to the list. See the git pull-request output below.

I am running SuSE V8.0, and Samba 2.2.7a on a small network server. I have been having problems relating to sorting out printing from an NT4 workstation to a laser printer on the Samba server. I had to reboot my Windoze PC and am logged in as myself (I have Administrator rights). I can see the shares by looking for the computer from Windows explorer using the ip 192.168.0.5 and can proceed

Bugs item #17742, was opened at 2008-02-03 04:04 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=17742&group_id=35 Category: Incorrect behavior Group: current Status: Open Resolution: None Priority: 3 Submitted By: Dale E. Edmons (linuxfan) Assigned to: Nobody (None) Summary: aui/aui.rb example program exhibits a memory leak Initial Comment:

Hello, I have an Asus laptop, U36SD, with Optimus technology. The discrete gpu is an NVIDIA GeForce GT 520M with 1GB DDR3 VRAM Using Fedora 17; up to kernel 3.3.7-1 I was able to use bumblebee and bbswitch and then running optirun command (as I could do in F16). No more with kernel 3.4. Tried 3.4.0-1.fc17.x86_64, 3.4.2-4.fc17.x86_64 and 3.4.3-1.fc17.x86_64. I already opened a bug against F17:

I''m trying to get Rails up and running on a new port of Ruby to Arm/WinCE devices that I''ve been working on, built using CEGCC tools for ''mostly'' Posix compatability, rather than using the existing Ruby WinCE binaries. Ruby runs and is installed under \ruby in root of the device itself. I''ve edited the following files of a default Rails 2.0.2 *zip*

I''m using ruby 1.8.6 p111. But some people seem to think that version 1.8.5 is better. Should I give it a whirl? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe

Hi all, Ruby 1.8.6-p111 Rails 1.2.6 Windows XP Pro IE 7 Posting this for posterity''s sake, and to see if anyone else hit this issue. I sporadically hit a strange error in IE7 when I hit a submit button on a form within a Rails app. res://ieframe.dll/dnserrordiagoff.htm Further investigation revealed that, when I hit this error, it was never reaching the controller, which I thought

Hi! I''m upgrading existing app from Rails 1.2.6 to 2.1.2. I have encountered following problem with AR objects. Model definition did not change and with 1.2.6: params={} params[:flight] = "1111" params[:airline] = "Air France" params[:luggage] = 0 r=Reservation.new params r.save is working code, new Reservation. With the same dataset, changing only

Tried a bunch of them there (x86-64, haswell, znver2) and they all defaulted to 4-wide - haswell additionally caused some extra loop unrolling but still with 8-wide pows. Cheers, -Neil. On Thu, Jul 16, 2020 at 2:39 PM Roman Lebedev <lebedev.ri at gmail.com> wrote: > Did you specify the target CPU the code should be optimized for? > For clang that is -march=native/znver2/... /

Hi I have been wondering if there one can speed up calculating small powers of numbers such as x^8 using multiplication. In addition, one can be a bit clever and calculate x^8 using only 3 multiplies. look at this: > f1 <- function(x){x*x*x*x*x*x*x*x} > f2 <- function(x){x^8} > f3 <- function(x){x2 <- x*x;x4 <- x2*x2;return(x4*x4)} [so f1() and f2() and f3() are

So for us we use SLEEF to actually implement the libcalls (LLVM intrinsics) that LLVM by default would generate - and since SLEEF has highly optimal 8-wide pow, optimized for AVX and AVX2, we really want to use that. So we would not see 4/8 libcalls and instead see 1 call to something that lights up the ymm registers. I guess the problem then is that the default expectation is that pow would be

https://bugzilla.samba.org/show_bug.cgi?id=10322 Summary: Slow Performance over Network rsync Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: Joerg.Grube at Gmx.De

Hey list, I've recently done the first test run of bumping our Burst compiler from LLVM 10 -> 11 now that the branch has been cut, and have noticed an apparent loop vectorization codegen regression for X86 with AVX or AVX2 enabled. The following IR example is vectorized to 4 wide with LLVM 11 and trunk whereas in LLVM 10 it (correctly as per what we want) vectorized it 8 wide matching the

Hi to all! I have a problem with a nvidia geforce 520mx [NVd0 generation card (0x0d9110a1)] i have on my notebook (samsung 3 series). In practice i'm not able to use it with bumblebee and bbswitch. The dmesg message is: [ 13.507435] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 13.507440] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 13.507448] nouveau

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to