RE: Intel 6300ESB SATA and TIMEOUT - WRITE_DMA

On Tor, 2006-03-23 at 14:55 -0500, Alain Hebert wrote: > Hi, > > I'm about to invest in some Tyan Transport GT20 B5350G20S2H-LC. > > But since my epic battle trying to make the Promise Fasttrak 2300TX > (PDC20580?) works right in Raid1, 2 weeks ago I'm a bit concern about > those ne

RE: Intel 6300ESB SATA and TIMEOUT - WRITE_DMA

Hi, I'm about to invest in some Tyan Transport GT20 B5350G20S2H-LC. But since my epic battle trying to make the Promise Fasttrak 2300TX (PDC20580?) works right in Raid1, 2 weeks ago I'm a bit concern about those new SATA controllers. Myself I have a PDC20378 in (heavy) productio

Re: Installation from USB pen

Brooks Davis wrote: > One minor nit, you might want to put a check that the user is root at the > top of the script since that is a requirement. Nice hint, I'll add it. >> P.S.: beer-ware license > > Are you going to be at BSDCan. :) No funds for that. Hope to see you here in Milan at EuroBSDCo

Re: [patch] Re: dlopen() and dlclose() are not MT-safe?

Kostik Belousov wrote: The reasoning behind releasing the lock is to allow calls to dl*() functions from constructors/destructors. This is common practice and shall be supported. Yes, leaving the lock taken will lead to deadlock. Please, try the following patch and report results. I can run (mod

Re: [patch] Re: dlopen() and dlclose() are not MT-safe?

On Thu, Mar 23, 2006 at 12:54:40PM +0200, Kostik Belousov wrote: > On Thu, Mar 23, 2006 at 05:57:24AM +0900, Kazuaki Oda wrote: > > BTW do you know the reason why lock is released before calling > > objlist_call_fini()? If we don't release the lock, what problem will > > occur? deadlock? > The re

[patch] Re: dlopen() and dlclose() are not MT-safe?

On Thu, Mar 23, 2006 at 05:57:24AM +0900, Kazuaki Oda wrote: > Kostik Belousov wrote: > > Oops. Completely reversed condition in the if. :(. Also, I don't think it > > shall returns the error in this situation. New take: > > > > Index: libexec/rtld-elf/rtld.c > > ==