Hello, Thomas. (cc'ing linux-ide, you don't have to be subscribed to post) Thomas Evans wrote: > I usually go by "tom@xxxxxxxxxxxx" - unfortunately I am unable to get > that machine started so I am using gmail instead. > > I have run into an odd situation with that machine - the 4726 port > multiplier is no longer found by libata/sata_sil24. > I mean - not at all - I have 2.6.24-rc candidates all the back to rc3 or > so (was using rc8 most recently). > I've even tried 2.6.22.1 with your patches for that kernel. They all > fail to see the PM - it just tries to do softresets on the esata port > that has the connection - no iteration of the PM ports. Up to now, it sounds very much like hardware failure. > I went so far as to try a new 3124 based card, new cable and I even > found a copy of the eSata PMP enclosure at a local store to swap that > out (gotta return it all - way expensive). What do you mean by eSata PMP enclosure? Is it a different PMP device? > I can hook the card and storage enclosure to a windows box and can see > the PM and the drives (and the config space). Hmmm....... > The 1 thing I did do was attempt to migrate the machine from a DS20 to a > DS20L. What are DS20 and DS20L? > When I tried to bring up the array there (same card, same boot > disk) I would get constant SRST failures, -5. I migrated it back to the > original system, same thing. I figured I broke something, which is why > I tried to replace everything with no luck - it's as if something has > forgotten how to find the SiI4726. Hmmm....... > any idea what might be happening? I would post to the list, but cannot > right now until I resubscribe as this name ... That's one weird story. I don't have much idea at this point. Can you try to grab failing kernel log and post it? You can either connect a harddrive directly, get a system up from there and grab failing detection log or set up serial or netconsole. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
