> I would like to chime in on this one also.  I am
> setting up two 1TB drives mirrored using the
> SUNWsmbskr and SUNWsmbs packages, not samba, and am
> experiencing the same issue.  I was thinking bout
> switching to samba to see if it worked better.  I am
> trying to use this a my NAS device instead  of moving
> to Free NAS.  I do not experience the problem
> transferring between two windows machines.  I get
> this error recored to the messages file multiple
> times when the OpenSolaris box locks up 
> Jan  8 11:06:02 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 1 -> 0
> Jan  8 11:06:03 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 0 -> 1
> Jan  8 11:06:03 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 1 -> 0
> Jan  8 11:06:03 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 0 -> 1
> Jan  8 11:06:03 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 1 -> 0
> Jan  8 11:06:03 masstore atge: [ID 989255 kern.info]
> atge0: atge_get_packet_1e: switching rx0 ring 0 -> 1
> 
> I just purchased an ASUS P5KPL-CM mother board with a
> built in GIGE  that did not have a driver.  The nic
> stats are as follows:: 
> node name:                     pci1043,8304
> Vendor:                        Attansic Technology
> Corp.
> Device:                        L1 Gigabit Ethernet
> Adapter
> binding name:                  pciex1969,1026
> 
> I used this website to get a driver installed and
> running
> http://homepage2.nifty.com/mrym3/taiyodo/eng/
> If anyone can shed some light on this issue that
> would be great!
> 
> Message was edited by: exp_02

I found the root cause of the hang. I missed to clear statistics overflow
interrupts. atge-2.6.4  in my page below  has fixed the problem. Please try it.

http://homepage2.nifty.com/mrym3/taiyodo/eng/

-masa
-- 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to