lkml.org 
[lkml]   [2011]   [Sep]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [BUG] scsi: hpsa: how to destroy your files
    From
    Date
    Le jeudi 01 septembre 2011 à 17:16 -0500, scameron@beardog.cce.hp.com a
    écrit :
    > On Thu, Sep 01, 2011 at 04:50:45PM -0500, Jon Mason wrote:
    > > On Thu, Sep 1, 2011 at 3:44 PM, <scameron@beardog.cce.hp.com> wrote:
    > > > On Thu, Sep 01, 2011 at 01:09:30PM -0700, Jesse Barnes wrote:
    > > >> On Thu, 1 Sep 2011 15:03:49 -0500
    > > >> scameron@beardog.cce.hp.com wrote:
    > > >>
    > > >> > On Thu, Sep 01, 2011 at 12:59:38PM -0700, Jesse Barnes wrote:
    > > >> > > On Thu, 01 Sep 2011 11:50:38 -0700
    > > >> > > James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
    > > >> > >
    > > >> > > > On Thu, 2011-09-01 at 10:58 -0700, Roland Dreier wrote:
    > > >> > > > > > 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.
    > > >> > > >
    > > >> > > >
    > > >> > > > While we investigate, I think the problems produced by the patch (data
    > > >> > > > corruption) are serious enough to warrant reverting it, please Jesse.
    > > >> > >
    > > >> > > Hm I haven't been paying attention to the compromise thread; how should
    > > >> > > I share these changes? Is master.kernel.org down indefinitely? Is
    > > >> > > there a new server at kernel.org I can use?
    > > >> >
    > > >> > I can't answer that question, but I would like a copy of your revert
    > > >> > patch(es) to test (as a simple patch --reverse of the original commit on the 3.1-rc4
    > > >> > tree didn't go in cleanly).
    > > >>
    > > >> Attached is the series. Applies on top of my for-linus branch.
    > > >
    > > > Thanks. I tried them out vs. 3.1-rc4, and they applied cleanly and
    > > > make things work on my BL460g7.
    > >
    > > I believe modifying the MRRS values is what is causing the issues.
    > > Can you try the attached patch and verify that it also resolves the
    > > issue?
    >
    > Ok, just tried it.
    >
    > The mrrs_removal patch does also appear to resolve the issue.
    >

    I cannot say that right now, as it appears the last "bad" kernel
    destroyed my distro enough that I cannot test this patch without a full
    reinstall. (/root partition is busted, even after several fsck -f -y)

    [ 42.501569] EXT3-fs error (device cciss/c0d0p1): ext3_free_inode: bit already cleared for inode 424649
    [ 42.501721] Aborting journal on device cciss/c0d0p1.
    [ 42.516101] Remounting filesystem read-only
    [ 42.529563] EXT3-fs error (device cciss/c0d0p1) in ext3_delete_inode: IO failure


    I'll have to do this reinstall when I am at the office, in a couple of
    hours.


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2011-09-02 07:35    [W:0.024 / U:151.688 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site