mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Dermot Bradley" <dermot.bradley@sla-mobile.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: "exception Emask: 0x42" errors with 2.6.22.x and SATA drives
Date: Fri, 24 Aug 2007 20:20:02 +0100	[thread overview]
Message-ID: <20070824202002.4d11525c@the-village.bc.nu> (raw)
In-Reply-To: <94439DDF32D7464A916B5068EFF76B3B0225E6AD@bart.tisolutions.biz>

On Fri, 24 Aug 2007 14:39:10 +0100
"Dermot Bradley" <dermot.bradley@sla-mobile.com> wrote:

> I've just built a new machine using a ASUS M2A-VM boardboard (ATI SB600
> chipset), AMD X2 3800+ processor, and 2 Western Digital 2.5" 80Gb drives
> running in RAID-1 using MD. I've had these problems with both 2.6.22.1
> and now 2.6.22.5 kernels.
> 
> I'm getting the following errors on occasion:
> 
> Aug 24 13:19:22 playpbx kernel: APIC error on CPU0: 00(40)
> Aug 24 13:19:33 playpbx kernel: APIC error on CPU0: 40(40)

This is not good.

> Aug 24 13:55:31 playpbx kernel: ata3.00: exception Emask 0x42 SAct
> 0x7fc77 SErr0x800 action 0x6 frozen
> Aug 24 13:55:31 playpbx kernel: ata3.00: (spurious completions during
> NCQ issue=0x0 SAct=0x7fc77 FIS=004040a1:00000008)

Probably not connected - your drive seems to be talking rubbish

Neither are good, the latter is probably a drive firmware problem and the
kernel will give up using NCQ with it if it keeps doing that, which
should be just fine.

  reply	other threads:[~2007-08-24 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 13:39 Dermot Bradley
2007-08-24 19:20 ` Alan Cox [this message]
2007-08-26 12:00   ` Alistair John Strachan
2007-08-24 20:49 Dermot Bradley
2007-08-24 23:18 ` Alan Cox
2007-08-27  9:28 Dermot Bradley
2007-08-27 11:18 ` Alistair John Strachan
2007-08-27 12:14 Dermot Bradley

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=20070824202002.4d11525c@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dermot.bradley@sla-mobile.com \
    --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

all inboxes | Powered by JetHome®