lkml.org 
[lkml]   [2007]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH 3/3] faster workaround
    Date
    Hello Tejun,

    On Tuesday 23 October 2007 10:08:01 Tejun Heo wrote:
    > Jeff Garzik wrote:
    > > Alan Cox wrote:
    > >>> 2) Once we identified, over time, the set of drives affected by this
    > >>> 3112 quirk (aka drives that didn't fully comply to SATA spec), the
    > >>> debugging of corruption cases largely shifted to the standard
    > >>> routine: update the BIOS, replace the
    > >>> cables/RAM/power/mainboard/slot/etc. to be certain of problem location.
    > >>
    > >> Except for the continued series of later SI + Nvidia chipset (mostly)
    > >> pattern which seems unanswered but also being later chips I assume
    > >> unrelated to this problem.
    > >
    > > The SIL_FLAG_MOD15WRITE flag is set in sil_port_info[] is set according
    > > to the best info we have from SiI, which indicates that 3114 and 3512 do
    > > not have the same problem as the 3112.
    >
    > I don't think this data corruption problem w/ sil3114 is related to
    > m15w. m15w workaround slows down things quite a bit and is likely to
    > hide problems on PCI bus side. There are reports of data corruption
    > with 3114 on nvidia (most common), via and now amd chipsets. There's
    > one on intel too but IIRC wasn't too definite.
    >
    > According to a user, freebsd didn't have data corruption problem on the
    > same hardware. I copied PCI FIFO setup code (ours is broken BTW) but it
    > didn't fix the problem.
    >
    > I'll try to reproduce the problem locally and hunt it down.

    thanks for your help and please tell me, if I can do anything. We have this
    problem on a production system, but the node in question will be rebooted in
    Thursday (ups needs to be replaced). If there are some tests/reboots/whatever
    I could do, it would be best to do it shortly after the scheduled reboot.

    Actually I now would have attempted to port your mod15 patch
    (http://home-tj.org/wiki/index.php/Sil_m15w#Patches) to 2.6.23, hoping it
    would solve Soerens problem and ours as well (ours magically already went
    away using the mod15 fix). Well, maybe I port it anyway to 2.6.23 to see if
    it also solves our problem.


    Thanks,
    Bernd


    --
    Bernd Schubert
    Q-Leap Networks GmbH
    -
    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: 2007-10-23 19:31    [W:5.839 / U:0.088 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site