-mm release schedule?
I didn't really know of a better place to ask this question, bus is there any rhyme or reason to when -mm kernels are released? Is there a -git repo that I can get work in progress for -mm? -Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ACPI: EC: Handler for query 0x80 is not found!
Ever since 2.6.22-rc6-mm1 I have been seeing these messages in dmesg: ACPI: EC: Handler for query 0x80 is not found! ACPI: EC: Handler for query 0x81 is not found! This did not happen in 2.6.22-rc4-mm1. Does anyone have any clue what this is about? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ACPI: EC: Handler for query 0x80 is not found!
I noticed that this message goes away if I reboot my computer... So a fresh boot it errors, on reboot it does not error. On 7/10/07, Ryan Hope <[EMAIL PROTECTED]> wrote: Ever since 2.6.22-rc6-mm1 I have been seeing these messages in dmesg: ACPI: EC: Handler for query 0x80 is not found! ACPI: EC: Handler for query 0x81 is not found! This did not happen in 2.6.22-rc4-mm1. Does anyone have any clue what this is about? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Pluggable Schedulers (was: [ANNOUNCE] RSDL completely fair starvation free interactive cpu scheduler)
from what I understood, there is a performance loss in plugsched schedulers because they have to share code even if pluggable schedulers is not a viable option, being able to choose which one was built into the kernel would be easy (only takes a few ifdefs), i too think competition would be good On 3/9/07, Al Boldi <[EMAIL PROTECTED]> wrote: William Lee Irwin III wrote: > William Lee Irwin III wrote: > >> I consider policy issues to be hopeless political quagmires and > >> therefore stick to mechanism. So even though I may have started the > >> code in question, I have little or nothing to say about that sort of > >> use for it. > >> There's my longwinded excuse for having originated that tidbit of code. > > On Fri, Mar 09, 2007 at 04:25:55PM +0300, Al Boldi wrote: > > I've no idea what both of you are talking about. > > The short translation of my message for you is "Linus, please don't > LART me too hard." Right. > On Fri, Mar 09, 2007 at 04:25:55PM +0300, Al Boldi wrote: > > How can giving people the freedom of choice be in any way > > counter-productive? > > This sort of concern is too subjective for me to have an opinion on it. How diplomatic. > My preferred sphere of operation is the Manichean domain of faster vs. > slower, functionality vs. non-functionality, and the like. For me, such > design concerns are like the need for a kernel to format pagetables so > the x86 MMU decodes what was intended, or for a compiler to emit valid > assembly instructions, or for a programmer to write C the compiler > won't reject with parse errors. Sure, but I think, even from a technical point of view, competition is a good thing to have. Pluggable schedulers give us this kind of competition, that forces each scheduler to refine or become obsolete. Think evolution. > If Linus, akpm, et al object to the > design, then invalid output was produced. Please refer to Linus, akpm, > et al for these sorts of design concerns. Point taken. Linus Torvalds wrote: > And hey, you can try to prove me wrong. Code talks. So far, nobody has > really ever come close. > > So go and code it up, and show the end result. So far, nobody who actually > *does* CPU schedulers have really wanted to do it, because they all want > to muck around with their own private versions of the data structures. What about PlugSched? Thanks! -- Al - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
pciehp: Cannot get control of hotplug hardware
Ever since I started playing with suspend I started turning on PCI Hot Plug support since then I have been seeing messages like whats below from dmesg I'm not exactly sure how this actually impacts me if it does at all. I just thought it didn't look exactly right so I wanted to inquire about it. Does anyone know what is going on here? -Ryan pci_hotplug: PCI Hot Plug PCI Core version: 0.5 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 decode_hpp: Could not get hotplug parameters. Use defaults pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.0 pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.1 pciehp: HPC vendor_id 8086 device_id 27d4 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.2 pciehp: HPC vendor_id 8086 device_id 27d6 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.3 pciehp: HPC vendor_id 8086 device_id 27e0 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.4 pciehp: HPC vendor_id 8086 device_id 27e2 ss_vid 0 ss_did 0 Evaluate _OSC Set fails. Status = 0x0005 Evaluate _OSC Set fails. Status = 0x0005 pciehp: Cannot get control of hotplug hardware for pci :00:1c.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
