On Thu, Mar 24, 2005 at 03:07:51AM -0800, Andrew Morton wrote:
> Peter Baumann <[email protected]> wrote:
> >
> > >
> > > The only PCI change I see is
> > >
> > > --- drivers/pci/pci.c 22 Jan 2005 03:20:37 -0000 1.71
> > > +++ drivers/pci/pci.c 24 Feb 2005 18:02:37 -0000 1.72
> > > @@ -268,7 +268,7 @@
> > > return -EIO;
> > >
> > > pci_read_config_word(dev,pm + PCI_PM_PMC,&pmc);
> > > - if ((pmc & PCI_PM_CAP_VER_MASK) != 2) {
> > > + if ((pmc & PCI_PM_CAP_VER_MASK) > 2) {
> > > printk(KERN_DEBUG
> > > "PCI: %s has unsupported PM cap regs version (%u)\n",
> > > dev->slot_name, pmc & PCI_PM_CAP_VER_MASK);
> > >
> > > and you're not getting that message (are you?)
> > >
> >
> > Reverting the above patch solved it. But _now_ I get the message.
> > (dmesg output with above patch reverted at the end of the mail)
>
> Greg, help!
>
> > > Nothing much in arch/i386..
> > >
> > > There were some ACPI changes, which is always a worry ;) Does that machine
> > > run OK without ACPI support? If so, could you determine whether disabling
> > > ACPI fixes things up?
> > >
> > Hm. I tried it with 2.6.11.5 by appending acpi=off at the cmdline but
> > as I remember it hasn't changed anything. Or do I have to specify
> > someting else at the commandline to deactivate acpi?
>
> We like to change these things so people send us more email.
>
> According to Documentation/kernel-parameters.txt, acpi=off should still work.
>
Yes. That's were I was looking for :-)
Sorry for my bad english but I meant that switching acpi off did not
change anything releated to the bug. Of course it deactivates acpi.
Peter
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
