mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Andres Freund <andres@anarazel.de>
Cc: linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Tomas Winkler <tomasw@gmail.com>
Subject: Re: bad DMAR interaction with iwlagn and SATA
Date: Fri, 26 Sep 2008 17:10:33 +0200	[thread overview]
Message-ID: <1222441833.3798.10.camel@johannes.berg> (raw)
In-Reply-To: <200809251511.20132.andres@anarazel.de>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

On Thu, 2008-09-25 at 15:11 +0200, Andres Freund wrote:

> I don't know if this is relevant, but I though i better report it.

Thanks. I've also been chasing a DMA corruption issue with iwlagn (on
powerpc).

> This was on fb478da5ba69ecf40729ae8ab37ca406b1e5be48 - sometime after 2.6.27-
> rc7
> 
> I stumbled over two buglets:
> First:
> [ 4184.617392] DMAR:[DMA Read] Request device [03:00.0] fault addr fa946000 
> [ 4184.617393] DMAR:[fault reason 06] PTE Read access is not set
> [ 4184.644081] iwlagn: Microcode HW error detected.  Restarting.
> [ 4186.646000] psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
> [ 4186.683034] Registered led device: iwl-phy0:radio
> [ 4186.683478] Registered led device: iwl-phy0:assoc
> [ 4186.683793] Registered led device: iwl-phy0:RX
> [ 4186.684094] Registered led device: iwl-phy0:TX
> [ 4186.689749] wlan0: authenticate with AP 00:1d:7e:42:fe:42
> [ 4186.691691] wlan0: authenticated
> [ 4186.691705] wlan0: associate with AP 00:1d:7e:42:fe:42
> [ 4186.696380] wlan0: RX ReassocResp from 00:1d:7e:42:fe:42 (capab=0x411 status=0 aid=2)
> [ 4186.696392] wlan0: associated
> 
> Most of the time when this happened, the machine wasnt reacting for 1-3 
> seconds and had audio buffer underruns, but I also had a hard lockup which I 
> couldnt diagnose so far.

I suspect the hard lockup was due to a BUG_ON in the iwlagn driver, if
you can reproduce this either try applying the patch here [1] or going
to a VC to see if it crashes there. It's a BUG_ON in iwl-tx.c.

johannes

[1] http://article.gmane.org/gmane.linux.kernel.wireless.general/21226


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2008-09-26 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 13:11 Andres Freund
2008-09-26  2:11 ` Jeff Garzik
2008-09-26  2:18   ` Andres Freund
2008-09-26  2:41     ` Jeff Garzik
2008-09-26 14:47       ` Muli Ben-Yehuda
2008-09-26 15:12         ` Johannes Berg
2008-09-26 23:30           ` Tomas Winkler
2008-09-29  8:27             ` Andres Freund
2008-09-29  8:40               ` Tomas Winkler
2008-10-06 12:26                 ` Johannes Berg
2008-10-06 14:32                   ` Andres Freund
2008-10-07  8:37                     ` Johannes Berg
2008-10-07 17:04                       ` Kyle McMartin
2008-10-07 17:08                         ` Johannes Berg
2008-09-26 15:10 ` Johannes Berg [this message]
2008-09-29  8:26   ` Andres Freund
2008-10-06 22:11 Boris Fersing

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=1222441833.3798.10.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=andres@anarazel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@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

all inboxes | Powered by JetHome®