From owner-freebsd-current Fri Feb 23 10:54:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8BBD337B503 for ; Fri, 23 Feb 2001 10:54:08 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1NIrM788285; Fri, 23 Feb 2001 12:53:22 -0600 (CST) (envelope-from jlemon) Date: Fri, 23 Feb 2001 12:53:22 -0600 (CST) From: Jonathan Lemon Message-Id: <200102231853.f1NIrM788285@prism.flugsvamp.com> To: jhay@icomtek.csir.co.za, current@freebsd.org Subject: Re: tail -f kernel panic X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I found it is quite easy to panic a -current kernel with 2 login windows. > >In window 1 do a "tail -f /tmp/world.out" >In window 2 do a "tail -f /tmp/world.out" >In window 2 do "^C" to break out of tail -f >In window 1 do "^C" to break out of tail -f >The box panic immediately. Hmm. I reproduced this here; the panic is in SLIST_REMOVE() when it is removing the second event. Funny enough, this does not happen on -stable. Did something change in the list macros recently that would cause this? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message