[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL1RGDWu4mBE3=0BC3iNnvfSSuT2pfGrXsBZBU-VB+tqZx7DeA@mail.gmail.com>
Date: Thu, 1 Sep 2011 10:58:21 -0700
From: Roland Dreier <roland@...estorage.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: scameron@...rdog.cce.hp.com, Jon Mason <mason@...i.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
james.bottomley@...senpartnership.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, stephenmcameron@...il.com,
thenzl@...hat.com, akpm@...ux-foundation.org,
mikem@...rdog.cce.hp.com
Subject: Re: [BUG] scsi: hpsa: how to destroy your files
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists