linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: me@bobcopeland.com
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Pedro Francisco <pedrogfrancisco@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	mickflemm@gmail.com
Subject: Re: ath5k misbehaving affecting other kernel parts unrelated?
Date: Fri, 23 Apr 2010 09:43:59 -0700	[thread overview]
Message-ID: <v2p55a4f86e1004230943j6b312cacpca585c80096375ea@mail.gmail.com> (raw)
In-Reply-To: <20100423163703.GB11112@hash.localnet>

Do you have more than ~2.5-3.5GB of ram (enough to make some ram
non-32-bit-DMA-accessible) with swiotlb enabled,
if such are you seeing "DMA: Out of SW-IOMMU space" kernel messages?

On Fri, Apr 23, 2010 at 09:37,  <me@bobcopeland.com> wrote:
> On Fri, Apr 23, 2010 at 09:48:23AM -0400, John W. Linville wrote:
>> > a) is it "normal"? I thought modules were somewhat isolated these days.
>> > b) any advices for debugging? I've yet to have two oopses that are similar....
>
> Advice for debugging: turn on slub/slab debug options, and possibly
> kmemcheck.  kmemcheck was very helpful for me last time I had such
> a corruption issue.
>
> --
> Bob Copeland %% www.bobcopeland.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2010-04-23 16:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201004230806.13628.pedrogfrancisco@gmail.com>
2010-04-23 13:48 ` ath5k misbehaving affecting other kernel parts unrelated? John W. Linville
2010-04-23 16:37   ` me
2010-04-23 16:43     ` Maciej Żenczykowski [this message]
2010-04-24  8:59       ` Pedro Francisco
2010-04-24  8:56     ` Pedro Francisco
2010-04-24 12:05       ` me
2010-04-24 12:09       ` Vegard Nossum
2010-04-24 17:28         ` Pedro Francisco
2010-04-25 19:22           ` me
2010-04-25 20:29             ` Jiri Slaby
2010-04-25 21:24               ` Pedro Francisco
2010-04-27 11:04                 ` Pedro Francisco
2010-04-28 21:52           ` Pedro Francisco
2010-04-29  7:17             ` Vegard Nossum

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=v2p55a4f86e1004230943j6b312cacpca585c80096375ea@mail.gmail.com \
    --to=zenczykowski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=pedrogfrancisco@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).