linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernie Innocenti <bernie@codewiz.org>
To: Harri Olin <harri.olin@gmail.com>
Cc: Mark Lord <liml@rtr.ca>,
	linux-ide@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	sysadmin <sysadmin@gnu.org>
Subject: Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040
Date: Thu, 08 Oct 2009 12:26:00 -0400	[thread overview]
Message-ID: <1255019160.30440.666.camel@giskard> (raw)
In-Reply-To: <1254852272.1471.172.camel@giskard>

El Tue, 06-10-2009 a las 14:04 -0400, Bernie Innocenti escribió:
> > I have heard same thing happened with same kind of configuration, using 
> > Supermicro H8DME-2 motherboard, Opteron 2378 CPU.
> >
> >Even the controllers were on same slots.
> 
> Close.  Mine is a Supermicro H8DM8-2 with 2x Opteron 2374 HE CPU.

I was wrong (the BIOS DMI block is wrong).  The motherboard is labeled
as H8DME-2.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

  parent reply	other threads:[~2009-10-08 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03  5:10 sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040 Bernie Innocenti
2009-10-05 21:45 ` Mark Lord
2009-10-06  4:16   ` Bernie Innocenti
2009-10-06 12:25   ` Harri Olin
2009-10-06 18:04     ` Bernie Innocenti
2009-10-06 20:06       ` Mark Lord
2009-10-07  0:06         ` Bernie Innocenti
2009-10-07  1:40           ` Bernie Innocenti
2009-10-07  3:13             ` Mark Lord
2009-10-08 16:42               ` Bernie Innocenti
2009-10-08 17:09                 ` Tony Vroon
2009-10-14 15:24                   ` [SOLVED] " Bernie Innocenti
2009-10-09  2:22                 ` Christian Pernegger
2009-10-09  3:07                 ` Mark Lord
2009-10-09  3:16                   ` Mark Lord
2009-10-08 16:26       ` Bernie Innocenti [this message]
2009-10-08 21:51         ` Harri Olin

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=1255019160.30440.666.camel@giskard \
    --to=bernie@codewiz.org \
    --cc=harri.olin@gmail.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sysadmin@gnu.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;
as well as URLs for NNTP newsgroup(s).