Date: Mon, 12 Jan 1998 20:25:52 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: julian@whistle.com (Julian Elischer), dyson@freebsd.org, current@freebsd.org Subject: Re: random (?) SIGBUS in -current Message-ID: <948.884633152@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 12 Jan 1998 14:23:25 EST." <199801121923.OAA00277@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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... >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!"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?948.884633152>