Peter Memishian writes: > > Mon Jan 16 17:54:59 EST 2006 > > + /sbin/ifconfig e1000g0 plumb <----- slow command > > + date > > Mon Jan 16 17:57:52 EST 2006 > > > > Can anyone provide guidance on what I should be checking to see why the > > ifconfig command is so slow? > > Is it reproducible after boot? I'd start the analysis with truss, and > then use DTrace to home in on the problem.
I've seen this in the past and I've broken into kmdb to get to the bottom of it, because it's irritating. I'm pretty sure that e1000g is one of the drivers that blocks inside the Style 1 open / Style 2 attach until the autonegotiation is complete. This is often a second or more and, on some switches, can be even longer. I've never seen it block for three _minutes_, but that doesn't seem impossible to me. Breaking into the debugger and listing threads while this thing is stuck should make it clear. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
