Date: Tue, 7 Sep 1999 19:30:25 -0500 (CDT) From: Jeremy McMillan <aphor@228-121.ppp.ripco.net> To: stable@freebsd.org Subject: Re: newly introduced repeatable SMP hang in STABLE/3.3-RC Message-ID: <Pine.BSF.4.05.9909071919430.38952-100000@www.notrecords.com> In-Reply-To: <19990907195604.7CC3214F5C@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Isn't this *wedged* instead of *hung*? (Re: info jargon) and what *exactly* is wedged/hung? I'm trying to get a better idea about how the SMP kernel works (ie. on what levels SMP code enters the picture). Could this be that one kernel thread is wedged in a state where it has a lock on a resource, but it can still do low level functions like handle ICMP? Maybe the other thread hung, and thus cannot release the lock on whatever resource the working (ICMP reachable kernel thread) needs to resume process managment services? What kernel resource do threads take turns locking? --- PLEASE NOTICE: THERE MAY BE NOSPAM IN THE HEADERS WHEN YOU HIT "REPLY"!!! Jeremy McMillan <aphor at ripco.com> | Ask for PGP-2.6.2 or 5.0i Chicago FreeBSD Users Group http://pages.ripco.com/~aphor/ChiFUG.html On Tue, 7 Sep 1999, Alan Judge wrote: > Following up to my own message. I've discovered that using ping -f on > the SMP machine is enough to hang the machine in seconds, which at > least takes more complex things like NFS and so on out of the picture. > (This is a 100Mb switched environment; both machines have Intel Pro > 100+ cards.) > > Entertainly, the partially hung SMP box will still answer pings, so you can > ping -f it from elsewhere fine. > -- > Alan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9909071919430.38952-100000>