From: Borislav Petkov <bbpetkov@yahoo.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc4-mm1: acpi reboots machine... solved
Date: Thu, 13 Dec 2007 08:09:23 +0100 [thread overview]
Message-ID: <20071213070923.GA3951@gollum.tnic> (raw)
In-Reply-To: <200712120921.42430.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]
On Wed, Dec 12, 2007 at 09:21:41AM -0700, Bjorn Helgaas wrote:
> On Wednesday 12 December 2007 03:11:23 am Borislav Petkov wrote:
> > On Tue, Dec 11, 2007 at 05:08:59PM -0700, Bjorn Helgaas wrote:
> > > On Tuesday 11 December 2007 01:52:55 pm Borislav Petkov wrote:
> > > > From what i can roughly tell so far it seems like an resource conflict between acpi and
> > > > the pnp requested regions in your patch which result in the acpi_thermal code
> > > > to read the wrong (0xff) temperature value and halt the machine, but i might be
> > > > wrong on the details since acpi is such a big code chunk to swallow.
> > >
> > > I don't see any obvious conflict from the log you posted. For the sake
> > > of comparison, can you post the corresponding dmesg log after you removed
> > > the patch?
> >
> > The only difference i see is that ACPI finds EC in DSDT in the working kernel
> > and in the broken case something silently fails. Please find attached the 2 bootlogs
> > and a disassembled DSDT.
>
> Thanks very much!
>
> "ACPI: EC: Look up EC in DSDT" appears in the working log, but not
> in the broken one. But I think we *do* find the EC in both cases,
> because we see "ACPI: EC: non-query interrupt received" even before
> acpi_ec_add() (which prints the "ACPI: EC: GPE = 0x1c, ...". Maybe
> the logs were collected with different log levels?
Well, hm, actually no, the only difference is that the broken log was taken over
netconsole so the lines might appear in a different order. I'll capture that
log again on the weekend to see whether something is missing..
> I think Alexey is on the right track with the PCI resource allocation
> failure.
Then it should be the SMBus controller, PCI id 00:1f:3, which is having problems
registering its io ports region 4, AFAICT.
> On your working kernel, can you collect this:
>
> lspci -vv > lspci
> cat /proc/ioports > ioports
> cat /proc/iomem > iomem
> grep . /sys/devices/pnp*/*/resources > pnp
> tar -jcf resources.tar.bz2 lspci ioports iomem pnp
attached.
--
Regards/Gruß,
Boris.
[-- Attachment #2: resources.tar.bz2 --]
[-- Type: application/octet-stream, Size: 3941 bytes --]
next prev parent reply other threads:[~2007-12-13 7:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 7:50 2.6.24-rc4-mm1: acpi reboots machine Borislav Petkov
2007-12-09 9:19 ` Borislav Petkov
2007-12-11 17:44 ` 2.6.24-rc4-mm1: acpi reboots machine... solved Borislav Petkov
2007-12-11 20:00 ` Bjorn Helgaas
2007-12-11 20:52 ` Borislav Petkov
2007-12-12 0:08 ` Bjorn Helgaas
2007-12-12 10:11 ` Borislav Petkov
2007-12-12 10:38 ` Alexey Starikovskiy
2007-12-12 16:21 ` Bjorn Helgaas
2007-12-13 7:09 ` Borislav Petkov [this message]
2007-12-13 16:17 ` Bjorn Helgaas
2007-12-13 21:29 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071213070923.GA3951@gollum.tnic \
--to=bbpetkov@yahoo.de \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox