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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 25 Sep 2008 22:11:32 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andres Freund <andres@...razel.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: bad DMAR interaction with iwlagn and SATA

Andres Freund wrote:
> Hi,	
> 
> in some accident caused by wanting to create the .config/compile the kernel 
> for my new laptop (thinkpad t500) before the desperately needed sleeping I 
> activated DMAR...
> 
> I don't know if this is relevant, but I though i better report it.
> 
> 
> 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.
> 
> Second:
> [ 2937.484251] DMAR:[DMA Read] Request device [00:1f.2] fault addr fffbf000 
> [ 2937.484255] DMAR:[fault reason 06] PTE Read access is not set
> [ 2937.484297] ata1.00: exception Emask 0x60 SAct 0x1 SErr 0x800 action 0x6 
> frozen
> [ 2937.484303] ata1.00: irq_stat 0x20000000, host bus error
> [ 2937.484309] ata1: SError: { HostInt }
> [ 2937.484319] ata1.00: cmd 61/08:00:c0:1d:6b/00:00:07:00:00/40 tag 0 ncq 4096 
> out
> [ 2937.484321]          res 40/00:00:c0:1d:6b/00:00:07:00:00/40 Emask 0x60 
> (host bus error)

Ouch, a host bus error is serious nastiness...

http://ata.wiki.kernel.org/index.php/Libata_error_messages#Error_classes

That's the ATA controller falling over after some serious machine hiccups.

	Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/