> On Fri, 10 Jan 2003 20:00:31 +0100, Jochen Hein said: > > > - and I've seen a report it causes an OOPS > > > on 2.5.53. I've not tried it on post-52, but I had a -54 kernel OOPS Guess the report was mine :) note for readers, this is bug 134 in the 2.5 kernel bug database at http://bugme.osdl.org . > > > right around that point in bootup (right after IDE and somewhere in PCI > > > init). Haven't chased that one at all... > if it OOPSes without my patch, then it's somebody else's problem. No, it did oops only with the patch. [snip] > In any case, I've attached a new *UNTESTED* patch, that only tries to > gratuitously > assign resources of MEM class, and disables the ROM once it does so. > No, I don't claim to fully understand this code. And if you're not brave > enough or can't test it yourself, I'll be taking the 2.5.56 plunge sometime > this weekend. ;) And all you other kernel hackers are welcome to jump right > in and tell me what I'm doing wrong.. ;) -ENOPATCH ;) Ciao, --alessandro - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [2.5.55, PCI, PCMCIA, XIRCOM]Valdis.Kletnieks
- Prev by Date: Re: any chance of 2.6.0-test*?
- Next by Date: Coding style - (Was Re: any chance of 2.6.0-test*?)
- Previous by thread: Re: Kernel 2.5.55 failed to boot with ACPI support
- Next by thread: Re: [2.5.55, PCI, PCMCIA, XIRCOM]
- Indexes:[Main][Thread]