> hello there, i have freebsd 6.1 pentiumII 355mhz processor and 128mb
> of ram. everytime i put my samsung 512mb in tha usb the machine doesnt
> boot it halts where the error be at if i pull it out it
> boots.........then if i put it back in i get an error.......whats with
> umass? i basically installed everybit and software of the unix i have
> so i dont know why i get the error anyhelp will be highly appreciated!
>
> this is the error:
>
> da0 at umass-sim0 bus0 target0wn0
> da0: Removable Direct Access SCSI-0 device
> da0:1.000MB/s transfers
> da0:511mb(1046720 512 byte sectors:64H 32s/T s11c)
> umass0:phase Error, residue = 0
> (da0:umass-sim0:0:0:0):synchronize cache failed, status == 0x4,scsi
> status == 0x0 opened disk da0->5!
>
> thank...

> Ivan Frosty wrote:

>> hello there, i have freebsd 6.1 pentiumII 355mhz processor and 128mb
>> of ram. everytime i put my samsung 512mb in tha usb the machine doesnt
>> boot it halts where the error be at if i pull it out it
>> boots.........then if i put it back in i get an error.......whats with
>> umass? i basically installed everybit and software of the unix i have
>> so i dont know why i get the error anyhelp will be highly appreciated!
>>
>> this is the error:
>>
>> da0 at umass-sim0 bus0 target0wn0
>> da0: Removable Direct Access SCSI-0 device
>> da0:1.000MB/s transfers
>> da0:511mb(1046720 512 byte sectors:64H 32s/T s11c)
>> umass0:phase Error, residue = 0
>> (da0:umass-sim0:0:0:0):synchronize cache failed, status == 0x4,scsi
>> status == 0x0 opened disk da0->5!
>>
>> thank you for your time ...

> Hello.
> I've got two different servers running FreeBSD 6.1 and hanging:
> _ one is a Dual Core Opteron running amd64 and experienced frequent
> hangs until I decided to turn off SMP;
> _ the other one was an old Athlon XP working flawlessly with 5.x/i386; I
> upgraded to 6.1/i386 and started seeing sporadic hangs; I had an
> hardware upgrade to an Athlon64 x2 and decided to turn SMP on, but then
> the system wouldn't last half a day. I turned SMP back off again and the
> system is more or less working.
>
> I don't get any core dump (altough I configured it properly) and DDB
> does not work. The only way out of this is hard resetting.
>
> What this machines have in common is a RAID-1 gmirror setup on an
> Adaptec 29320 controller: one is PCI, the other on the MB (Acer Altos
> server), but both are obvioulsy driven by the ahd driver.
> So my *guess* is that the problem might be related to this.
>
> What I'm looking for is any help in solving or at least diagnosing this. ...

> unable to determine wwn within freebsd, is there a way (already
> done)? thanks.
>
> my logs of isp0 :
>
> isp0: port 0x4000-0x40ff mem
> 0xdefff000-0xdeffffff irq 72 at device 3.0 on pci3
> isp0: [GIANT-LOCKED]
> isp0: bad hard address 125- resetting to zero

> 2006/12/5, mjacob@freebsd.org freebsd.org>:

>>
>>
>> Was there ever a consensus about this to the point of:
>>
>> a) Yes, this is a nice thing to have
>> b) Should it be a define or a function?
>>
>> I obviously think yes for #a. I lean toward a function. Comments?

>
> a) yes
> b) define
>

> On Dec 04, 2006, at 20:27 , mjacob@freebsd.org wrote:

>>> On Dec 04, 2006, at 19:27 , mjacob@freebsd.org wrote:

>>>> IOCCC?

>>>
>>> http://www.ioccc.org/

>>> Consider this another vote for "function" ;)

>>
>> Bruce is usually less indirect. What gives?

> Multi-line #define's are 'orrible (IMO) -- of course, our tree is littered
> with them, but it's highly preferable to have a function over a define,
> particularly when it comes to reading the code n months later, trying to
> track something down. In this particular case, the minimal overhead of
> calling a function rather than having it inline (via #define) is vastly
> outweighed by code-readability, and reduction in kernel size.

>> On Dec 04, 2006, at 19:27 , mjacob@freebsd.org wrote:

>>> IOCCC?

>>
>> http://www.ioccc.org/
>>
>> Consider this another vote for "function" ;)

>
> Bruce is usually less indirect. What gives?