Date: Thu, 27 Mar 2008 00:45:13 +0100 From: Peter Much <pmc@citylink.dinoex.sub.org> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org, Peter Much <pmc@citylink.dinoex.sub.org> Subject: Re: "s/stable/broken/g" Message-ID: <20080326234513.GA30601@gate.oper.dinoex.org> In-Reply-To: <200803261700.12851.jhb@freebsd.org> References: <Jy5EA6.1n3@citylink.dinoex.sub.org> <Jy75oC.Es7@citylink.dinoex.sub.org> <200803261700.12851.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 26, 2008 at 05:00:12PM -0400, John Baldwin wrote: ! Try this patch for de(4). Thanks fpr the reply. I'll try this patch at next reboot. ! You need to supply the panic details for the devfs ! one (I've used devfs rules w/o issue on lots of machines ! via /etc/devfs.conf). I have found, eh, not the solution but the problem. ;) This one: kern/89784 describes the same symptom and nearly the same backtrace. And it is still open, so this, well, just seems to exist. And, things being this way, I don't think there is need for me to do any more about it for now, as this does not really hurt and workaround is easy. Actually, the horror is not that something does not work - the horror is when, in an ambitiously complex setup which isn't fun to upgrade anyway, the next pagefault derisively grins at you, at the point when you would like to finish and go for a sleep, or a beer - and you know there are some good friends who have placed some web-stuff onto the machine, and you don't want to disappoint them... It's a situation where one enjoys reaching a good availability, but far from worth setting up an identical test environment (which would be the appropriate strategy to really avoid such surprizes). rgds, PMc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080326234513.GA30601>