From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI processor module with Atom N270 causes DMA errors
Date: Sun, 25 Oct 2009 22:35:38 +0000 [thread overview]
Message-ID: <20091025223538.6261f9f2@boulder.homenet> (raw)
In-Reply-To: <4AE4C70D.2020600@gmail.com>
On Mon, 26 Oct 2009 00:45:49 +0300
Alexey Starikovskiy <aystarik@gmail.com> wrote:
> Hi Chris,
>
> Please open new bug report against ACPI/Processor in
> bugzilla.kernel.org attach outputs from dmesg, acpidump and
> dmidecode. Kernel config file might appear useful too.
Thanks. This is now the subject of further discussion on the bcm43xx
mailing list, as I am glad to say (from my point of view) that Linux
Torvalds is suffering the same problem, albeit not with an Atom.
I will await the outcome of that before posting a kernel bug for the
processor module (there is some suggestion that the BIOS may be at
fault and that kernel ACPI may just be a side effect).
Chris
prev parent reply other threads:[~2009-10-25 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 21:07 ACPI processor module with Atom N270 causes DMA errors Chris Vine
2009-10-25 21:45 ` Alexey Starikovskiy
2009-10-25 22:35 ` Rafał Miłecki
2009-10-25 22:35 ` Chris Vine [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=20091025223538.6261f9f2@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=aystarik@gmail.com \
--cc=linux-acpi@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