linux-kernel - Re: bad DMAR interaction with iwlagn and SATA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1222441833.3798.10.camel@johannes.berg>
Date:	Fri, 26 Sep 2008 17:10:33 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Andres Freund <andres@...razel.de>
Cc:	linux-kernel@...r.kernel.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Tomas Winkler <tomasw@...il.com>
Subject: Re: bad DMAR interaction with iwlagn and SATA

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


Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)