From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262671AbVCXLIo (ORCPT ); Thu, 24 Mar 2005 06:08:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263096AbVCXLIn (ORCPT ); Thu, 24 Mar 2005 06:08:43 -0500 Received: from fire.osdl.org ([65.172.181.4]:17133 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S262671AbVCXLIT (ORCPT ); Thu, 24 Mar 2005 06:08:19 -0500 Date: Thu, 24 Mar 2005 03:07:51 -0800 From: Andrew Morton To: Peter Baumann Cc: linux-kernel@vger.kernel.org, Greg KH Subject: Re: [Bug] invalid mac address after rebooting (kernel 2.6.11.5) Message-Id: <20050324030751.6e150376.akpm@osdl.org> In-Reply-To: <20050324110102.GA30711@faui00u.informatik.uni-erlangen.de> References: <20050323122423.GA24316@faui00u.informatik.uni-erlangen.de> <20050323185225.11097185.akpm@osdl.org> <20050324110102.GA30711@faui00u.informatik.uni-erlangen.de> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Peter Baumann 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.