Messages in this thread | | | Date | Fri, 23 Apr 2010 09:43:59 -0700 | Subject | Re: ath5k misbehaving affecting other kernel parts unrelated? | From | Maciej Żenczykowski <> |
| |
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/ > -- 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/
| |