Displaying 3 results from an estimated 3 matches for "msg00434".
Did you mean:
msg00034
2009 Nov 27
10
[PATCH 0/9] FOR DISCUSSION ONLY: daemon error handling
The more I look at this patch, the less I like it. I would summarise
why I think it's wrong here, but it's better if you look at the
message I posted on the gnulib mailing list here first:
http://lists.gnu.org/archive/html/bug-gnulib/2009-11/msg00434.html
Directly accessing errno on Windows is wrong: you won't see the true
reasons for an error by doing that. However depending on what the
call is and whether it was replaced by gnulib, the alternatives are a
lot more complicated.
This patch series attempts to Do The Right Thing with gnulib...
2011 Dec 02
6
[PATCH] tools/firmware: remove "_PS0/3" Method
tools/firmware: remove "_PS0/3" Method
Do not expose the ACPI power management "_PS0/3" Method to guest firmware. According to section 3.4 of the APCI specification 4.0, PCI device control the device power through its own specification but not through APCI.
Qemu pushes "_PS0/3" to guest will cause a mess between ACPI PM and PCI PM as a result of incorrect ACPI table
2009 Dec 18
3
xen "set encode" (8b2a) problem
Hi my friends,
I am running into a problem with my NIC.
[root@xxxx ~]# ifup eth0
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth0 ; No such device.
SIOCGIFFLAGS: No such device
Failed to bring up eth0.
eth0 is not a wireless device. Below are some information about my host:
[root@xxxx ~]# lspci |grep -i ether
00:04.0 Ethernet controller: Intel Corporation