public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI processor module with Atom N270 causes DMA errors
Date: Mon, 26 Oct 2009 00:45:49 +0300	[thread overview]
Message-ID: <4AE4C70D.2020600@gmail.com> (raw)
In-Reply-To: <20091025210754.55abdbe6@boulder.homenet>

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.

Regards,
Alex.

Chris Vine пишет:
> Hi,
>
> I have a Levono S-12 netbook which uses an Atom N270 processor.
> Loading the ACPI 'processor' module clobbers my DMA, specifically when
> using the b43 driver for a Broadcom BCM4312 802.11b/g [14e4:4315] low
> power phy wireless device.  The b43 driver works correctly if the
> processor ACPI module is blacklisted.
>
> This is with kernel 2.6.32-rc5, but the same occurs with earlier
> pre-2.6.32 kernels.
>
> Please let me know what further information would be helpful (for
> example, the output of dmesg, lspci or lsmod, or other hardware
> information).
>
> Chris
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-10-25 21:45 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 [this message]
2009-10-25 22:35   ` Rafał Miłecki
2009-10-25 22:35   ` Chris Vine

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=4AE4C70D.2020600@gmail.com \
    --to=aystarik@gmail.com \
    --cc=chris@cvine.freeserve.co.uk \
    --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