From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jordan_Hargrave@dell.com, Jon Mason <mason@myri.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-3.1-0-rc4 bus error ... MPS configured higher than maximum supported by the device. If a bus issue occurs, try running with pci=pcie_bus_safe.
Date: Tue, 06 Sep 2011 08:25:13 +0200 [thread overview]
Message-ID: <1315290313.2565.0.camel@edumazet-laptop> (raw)
In-Reply-To: <CAAJw_ZvP6m=3T0YoYq6VJdOKMxzm3fDcdJoDY8wqqDV8GZB+Dg@mail.gmail.com>
Le mardi 06 septembre 2011 à 14:09 +0800, Jeff Chua a écrit :
> On Mon, Sep 5, 2011 at 10:55 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> > Got the following error after upgrading from linux-2.6.36 to
> > linux-3.1.0-rc4 on a Dell PowerEdge 2950 that has a PCIe fax card, and
> > the system LED panel shows "Bus Fatal Error".
> >
> >
> > Is is normal or should I try out "pci=pcie_bus_safe" or "pci=pci" as
> > suggested in the dmesg?
> >
> > There was another error that also showed up on 2.6.36 but I'm ignoring
> > that for now ( ... disabling ASPM on pre-1.1 PCIe device. You can
> > enable it with 'pcie_aspm=force')
> >
> > pci 0000:07:00.0: Dev MPS 128 MPSS 256 MRRS 4096
> > pci 0000:07:00.0: Dev MPS 256 MPSS 256 MRRS 128
> > pci 0000:08:00.0: Dev MPS 128 MPSS 128 MRRS 128
> > pci 0000:08:00.0: MPS configured higher than maximum supported by the
> > device. If a bus issue occurs, try running with pci=pcie_bus_safe.
> > pci 0000:08:00.0: Dev MPS 256 MPSS 256 MRRS 128
> > Uhhuh. NMI received for unknown reason 31 on CPU 0.
> > Do you have a strange power saving mode enabled?
> > Dazed and confused, but trying to continue
> > pci 0000:07:01.0: Dev MPS 128 MPSS 256 MRRS 4096
> > pci 0000:07:01.0: Dev MPS 256 MPSS 256 MRRS 128
> > pci 0000:00:06.0: Dev MPS 256 MPSS 256 MRRS 128
> > pci 0000:0e:00.0: Dev MPS 128 MPSS 128 MRRS 512
> > pci 0000:0e:00.0: MPS configured higher than maximum supported by the
> > device. If a bus issue occurs, try running with pci=pci
>
> The above aspm and bus error went away after I added pcie_aspm=force
> and pci=pcie_bus_safe.
>
> Instead of default to pcie_bus_perf that caused problems, why not
> default to the formal behavior (see commit
> b03e7495a862b028294f59fc87286d6d78ee7fa1).
I believe a revert is in progress anyway, see my other thread (scsi:
hpsa: how to destroy your files)
next prev parent reply other threads:[~2011-09-06 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 14:55 Jeff Chua
2011-09-06 6:09 ` Jeff Chua
2011-09-06 6:25 ` Eric Dumazet [this message]
2011-09-06 8:39 ` Jeff Chua
2011-09-10 2:55 ` Linus Torvalds
2011-09-10 4:49 ` Eric Dumazet
2011-09-10 5:55 ` Jeff Chua
2011-09-10 7:57 ` Eric Dumazet
2011-09-10 11:28 ` Jeff Chua
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=1315290313.2565.0.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=Jordan_Hargrave@dell.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@myri.com \
--cc=torvalds@linux-foundation.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®