From: Sven Schnelle <svens@stackframe.org>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, Jon Mason <mason@myri.com>,
Jordan_Hargrave@dell.com
Subject: Re: [3.1-rc4] Bus Fatal Error caused by "PCI: Set PCI-E Max Payload Size on fabric"
Date: Wed, 07 Sep 2011 18:22:19 +0200 [thread overview]
Message-ID: <87aaag9vb8.fsf@begreifnix.stackframe.org> (raw)
In-Reply-To: <20110906173605.GA12577@hostway.ca> (Simon Kirby's message of "Tue\, 6 Sep 2011 10\:36\:05 -0700")
Simon Kirby <sim@hostway.ca> writes:
> Hello!
>
> Since trying 3.1-rc4 on a few Dell servers, all of them have booted up
> with the amber error LED lit. "ipmitool sel list" shows:
>
> 1 | 09/06/2011 | 17:21:56 | Event Logging Disabled #0x72 | Log area reset/cleared | Asserted
> 2 | 09/06/2011 | 17:25:38 | Critical Interrupt #0x18 | Bus Fatal Error | Asserted
> 3 | 09/06/2011 | 17:25:38 | Unknown #0x1a |
> 4 | 09/06/2011 | 17:25:38 | Unknown #0x1a |
I'm seeing exact the same issue on a Dell 1950 Server. If anyone wants
me to try additional debugging/patches, feel free to do
so. Unfortunately i don't have the time/knowledge to debug that by myself.
Sven
next prev parent reply other threads:[~2011-09-07 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 17:36 [3.1-rc4] Bus Fatal Error caused by "PCI: Set PCI-E Max Payload Size on fabric" Simon Kirby
2011-09-07 16:22 ` Sven Schnelle [this message]
2011-09-07 16:52 ` Josh Boyer
2011-09-07 17:44 ` Jesse Barnes
2011-09-07 19:18 ` Simon Kirby
2011-09-07 20:47 ` Simon Kirby
2011-09-07 20:57 ` Jon Mason
2011-09-07 20:58 ` Simon Kirby
2011-09-07 21:10 ` Jon Mason
2011-09-07 21:33 ` Simon Kirby
2011-09-08 6:42 ` Sven Schnelle
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=87aaag9vb8.fsf@begreifnix.stackframe.org \
--to=svens@stackframe.org \
--cc=Jordan_Hargrave@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@myri.com \
--cc=sim@hostway.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.