Re: [sata] libata update

From: Jeff Garzik (jgarzik_at_pobox.com)
Date: 03/27/04

  • Next message: Alan Stern: "BUG: Problem with your patches for sysfs from 2 weeks ago"
    Date:	Sat, 27 Mar 2004 17:20:09 -0500
    To: Henrik Gustafsson <lkml@fnord.se>
    
    

    Henrik Gustafsson wrote:
    > (sorry for screwing with the thread, I was not subscribed when I read
    > the original post)
    >
    > The patch seems to work just fine. It's been running for six hours now
    > with varying amounts of load and no catastrophes has occurred so far.
    >
    > Only things are these lines saying 'abnormal status' (which has been
    > there all along). I assume the codes mean 'device not present' (which
    > would be correct, at least in my case) or something similar, but I don't
    > know for sure so I leave it to someone better informed to patch :)
    >
    > (also, there is the 'Unknown device'-thing in my lspci, but that's
    > neither related to libata nor is it a 'real' problem)
    >
    > Using a Promise FastTrack S150 SX4
    > Relevant piece of my dmesg, lspci follows (just let me know if you need
    > the rest)

    Thanks for testing.

    Yes, the SX4, unlike the TX2/TX4, does not directly give me access to
    the SATA ports, so I cannot test directly for device presence. Instead
    I let the normal error handling routines notice the behavior. I need to
    fix that up, but for now that's an annoying but harmless message.

            Jeff

    -
    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/


  • Next message: Alan Stern: "BUG: Problem with your patches for sysfs from 2 weeks ago"

    Relevant Pages

    • Re: [PATCH] optimize ia32 memmove
      ... When was the original post since I cant find ... The original patch is on the 2.5/2.6 commits mailing list, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • ADDITIONAL INFO: SUMMARY: 9_Recommended error codes (specifically return code 5)
      ... Because the pkgadd failed, the 68 patches ... A Google search (patch failure pkgadd) produced a message in the ... Previous summary: ./install_cluster calls patchadd script. ... Previous summary: Original post: To: sunmanagers@sunmanagers.org ...
      (SunManagers)
    • SUMMARY: 9_Recommended error codes (specifically return code 5)
      ... updates any of the individual patches in the cluster. ... Original post: To: sunmanagers@sunmanagers.org ... * "return code 8" means that the patch in question cannot be applied because the relevant Solaris modules ... Original post: Patchadd is terminating. ...
      (SunManagers)
    • Re: [parisc-linux] Re: [PATCH 3/9] mm: parisc pte atomicity
      ... using your own tmpalias area sounds much better than getting ... I've simply not wrapped my head around the races, ... it looks like we agree that my patch is necessary and valid as is; ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: keyboard - was: Re: Linux 2.6.0-test4
      ... >> I was able to get the key unstuck by switching back and forth between ... I rebuild my kernel including your patch; ... I'll get back to you once I verify that the problem doesn't occur ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)