From: Jeff Garzik <jeff@garzik.org>
To: Andres Freund <andres@anarazel.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad DMAR interaction with iwlagn and SATA
Date: Thu, 25 Sep 2008 22:11:32 -0400 [thread overview]
Message-ID: <48DC44D4.8000103@garzik.org> (raw)
In-Reply-To: <200809251511.20132.andres@anarazel.de>
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
next prev parent reply other threads:[~2008-09-26 2:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 13:11 bad DMAR interaction with iwlagn and SATA Andres Freund
2008-09-26 2:11 ` Jeff Garzik [this message]
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
2008-09-29 8:26 ` Andres Freund
-- strict thread matches above, loose matches on Subject: below --
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=48DC44D4.8000103@garzik.org \
--to=jeff@garzik.org \
--cc=andres@anarazel.de \
--cc=linux-kernel@vger.kernel.org \
/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