From: Peter Simons <simons@cryp.to>
To: Bjorn Helgaas <bjorn.helgaas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: ACPI 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 1 (20120320/utaddress-251)
Date: Fri, 14 Sep 2012 17:45:11 +0200 [thread overview]
Message-ID: <87ipbgip6g.fsf@write-only.cryp.to> (raw)
In-Reply-To: <CABhMZUXH0cZSmjW_5oW1+XQZhR84S8LwWxk16Nuert4s3yo0xQ@mail.gmail.com> (Bjorn Helgaas's message of "Thu, 13 Sep 2012 22:07:47 -0600")
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
Hi Bjorn,
> The panic is the real problem, not the warning message. It's possible
> that they're related, but certainly not obvious. Can you capture any
> information about the panic with a serial console, netconsole, or
> even a digital photo or movie?
right, I have attached picture of the kernel messages displayed when the
machine crashes. I hope this helps.
> It sounds like this is a regression, so it will be useful to know the
> newest kernel that works correctly and the oldest one that fails.
Yes, I understand why that information would be very helpful.
Unfortunately, I don't know exactly when these errors began to occur. I
cannot easily find out either, because these kernel panics more or less
randomly -- I don't know how to trigger such the event. Sometimes, the
machine works just fine for a day or two, and then it crashes 4 or 5
times in a row for no apparent reason. I'm sorry for not being any more
specific, but I just don't know more.
Take care,
Peter
[-- Attachment #2: picture of kernel panic --]
[-- Type: image/jpeg, Size: 197145 bytes --]
prev parent reply other threads:[~2012-09-14 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 18:11 PROBLEM: ACPI 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 1 (20120320/utaddress-251) Peter Simons
2012-09-14 4:07 ` Bjorn Helgaas
2012-09-14 15:45 ` Peter Simons [this message]
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=87ipbgip6g.fsf@write-only.cryp.to \
--to=simons@cryp.to \
--cc=bjorn.helgaas@gmail.com \
--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