From: Roland Dreier <roland@purestorage.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: scameron@beardog.cce.hp.com, Jon Mason <mason@myri.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
stephenmcameron@gmail.com, thenzl@redhat.com,
akpm@linux-foundation.org, mikem@beardog.cce.hp.com
Subject: Re: [BUG] scsi: hpsa: how to destroy your files
Date: Thu, 1 Sep 2011 10:58:21 -0700 [thread overview]
Message-ID: <CAL1RGDWu4mBE3=0BC3iNnvfSSuT2pfGrXsBZBU-VB+tqZx7DeA@mail.gmail.com> (raw)
In-Reply-To: <1314898815.2823.33.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
> OK I found the bad commit,I got lucky... I lost some files but my
> machine was able to complete the bisection. CC involved people
> # bad: [b03e7495a862b028294f59fc87286d6d78ee7fa1] PCI: Set PCI-E Max Payload Size on fabric
Hi Eric,
I guess it would be useful to see "lspci -vv" output with a "good" kernel
and with that bad patch applied. Most likely we should see some difference
somewhere in the MaxPayload fields in the PCI Express capability of
some device.
Either the RAID controller or something else lies, and puts a value
in the DevCap that it can't actually support, or else the patch is
buggy and puts something out of range in a DevCtl somewhere.
- R.
next prev parent reply other threads:[~2011-09-01 17:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 18:16 [PATCH] hpsa: do not attempt to read from a write-only register Stephen M. Cameron
2011-07-21 18:17 ` Stephen Cameron
2011-07-22 22:39 ` Andrew Morton
2011-07-22 22:39 ` Andrew Morton
2011-09-01 15:24 ` [BUG] scsi: hpsa: how to destroy your files Eric Dumazet
2011-09-01 16:07 ` scameron
2011-09-01 16:18 ` Eric Dumazet
2011-09-01 16:18 ` Eric Dumazet
2011-09-01 17:40 ` Eric Dumazet
2011-09-01 17:40 ` Eric Dumazet
2011-09-01 17:58 ` Roland Dreier [this message]
2011-09-01 18:50 ` James Bottomley
2011-09-01 18:58 ` Jesse Barnes
2011-09-01 19:59 ` Jesse Barnes
[not found] ` <20110901200349.GO9189@beardog.cce.hp.com>
2011-09-01 20:09 ` Jesse Barnes
2011-09-01 20:09 ` Jesse Barnes
2011-09-01 20:44 ` scameron
2011-09-01 21:50 ` Jon Mason
2011-09-01 22:01 ` Eric Dumazet
2011-09-01 22:16 ` scameron
2011-09-02 5:32 ` Eric Dumazet
2011-09-02 5:32 ` Eric Dumazet
2011-09-02 9:39 ` Eric Dumazet
2011-09-02 10:08 ` Eric Dumazet
2011-09-02 15:03 ` scameron
2011-09-02 15:03 ` scameron
2011-09-01 19:36 ` Eric Dumazet
2011-09-01 18:01 ` scameron
2011-09-01 18:01 ` scameron
2011-09-01 19:03 ` scameron
2011-09-01 19:03 ` scameron
2011-09-02 23:13 ` Andrew Morton
2011-09-02 5:18 ` Mike Galbraith
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='CAL1RGDWu4mBE3=0BC3iNnvfSSuT2pfGrXsBZBU-VB+tqZx7DeA@mail.gmail.com' \
--to=roland@purestorage.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mason@myri.com \
--cc=mikem@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=stephenmcameron@gmail.com \
--cc=thenzl@redhat.com \
/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.