From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
Jordan_Hargrave@dell.com, Jon Mason <mason@myri.com>,
Jesse Barnes <jbarnes@virtuousgeek.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: Sat, 10 Sep 2011 09:57:50 +0200 [thread overview]
Message-ID: <1315641470.2606.26.camel@edumazet-laptop> (raw)
In-Reply-To: <CAAJw_Zt7dWh_=DHOevxmudyS8wzn7dY4NJozwCMW0kpJGcaBSQ@mail.gmail.com>
Le samedi 10 septembre 2011 à 13:55 +0800, Jeff Chua a écrit :
> On Sat, Sep 10, 2011 at 12:49 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > Le vendredi 09 septembre 2011 à 19:55 -0700, Linus Torvalds a écrit :
> >> On Tue, Sep 6, 2011 at 1:39 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> >> >
> >> > Thanks. I saw that. And the system nearly got trashed even though I've
> >> > no hpsa. Grub went into rescue mode after reboot, and I had to rebuild
> >> > the grub boot sector.
> >> >
> >> > Now, it's all ok with pcie_aspm=force and pci=pcie_bus_safe.
> >>
> >> Jeff, Eric,
> >> Is the current -git state ok for you guys? I just pushed out commit
> >> ed2888e906b5 ("PCI: Remove MRRS modification from MPS setting code")
> >> which should default to safe pcie behavior.
> >>
> >> I just wanted to verify that that was all sufficient for this thread..
> >>
> >
> > Hi Linus
> >
> > I pulled your last changes, and did some tests on my HP BL460c G6,
> > including several stress sessions (make -j128 and various benches)
> >
> > So far, everything seems fine, thanks.
>
> Couldn't pulled anything for the past few days. Still stuck at commit
> 9e79e3e9dd9672b37ac9412e9a926714306551fe.
>
> fatal: Unable to look up git.kernel.org (port 9418) (Name or service not known)
> failed
>
>
Hmm, you probably miss something ;)
http://lwn.net/Articles/457142/
git pull https://github.com/torvalds/linux.git
next prev parent reply other threads:[~2011-09-10 7:57 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
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 [this message]
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=1315641470.2606.26.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®