From owner-freebsd-current Mon Jan 12 12:51:29 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA28363 for current-outgoing; Mon, 12 Jan 1998 12:51:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28343; Mon, 12 Jan 1998 12:51:13 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA14211; Mon, 12 Jan 1998 12:40:24 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd014208; Mon Jan 12 12:40:14 1998 Message-ID: <34BA7EF3.167EB0E7@whistle.com> Date: Mon, 12 Jan 1998 12:37:07 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Poul-Henning Kamp CC: "John S. Dyson" , dyson@freebsd.org, current@freebsd.org Subject: Re: random (?) SIGBUS in -current References: <948.884633152@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > In message <199801121923.OAA00277@dyson.iquest.net>, "John S. Dyson" writes: > >Julian Elischer said: > >> > >> kernel from late last night > >> system got 85% through 'make world' before a process hung in 'D' state. > >> The rest of the system seemed ok. > >> > >> no sign of SIGBUS though. > >> > >I cannot reproduce the problem, with testing and compiles on 8MB, 16MB, and > >112MB systems. PHK, could you tell me more about your system? Are you > >running anything special, that I can reproduce the problem? > > HP800 laptop. 48M Ram. Pretty much vanilla -current. > > For instance, I use mh to read email. the "inc" program will often > sigbus when I have been running something else and rerun it to > see if there is new email. > > It looks like some page gets stolen, and the object isn't updated > accordingly... ahhhhh this looks very much like the problem I showed you when you were here last time john.. a page seems to be unmapped from a running process we see sig-11s from things such as cron, sendmail, perl not enough to stop the world, or make our product unreliable, but annnoying.. (our system is basically a batch system if the user clicks on a button and nothing happens they just assume it's windows and click onit again :) but this is on 2.2.5+x.. maybe the bug is older and is only being shown up by the new code. (you may be looking at the wrong place :) > > >Note that the new code follows the "rules" fairly precisely regarding the > >vnode free list. Some parts of the system might not be able to deal with > >it yet (maybe.) > > But this would be related to pages, they die with a pagefault... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "Drink MONO-tonic, it goes down but it will NEVER come back up!"