Date: Tue, 28 Jun 2005 23:22:24 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Mitch Parks <mitch@kuoi.asui.uidaho.edu> Cc: freebsd-stable@freebsd.org, Robert Watson <rwatson@FreeBSD.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: 5.4-p1 crash Message-ID: <20050628232206.Q3088@carver.gumbysoft.com> In-Reply-To: <20050625012751.U98651@kuoi.asui.uidaho.edu> References: <20050617150950.F1236@kuoi.asui.uidaho.edu> <20050617235352.GA80058@xor.obsecurity.org> <42B40173.6070600@crc.u-strasbg.fr> <20050619184650.T6413@fledge.watson.org> <20050625012751.U98651@kuoi.asui.uidaho.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 25 Jun 2005, Mitch Parks wrote: > On Sun, 19 Jun 2005, Robert Watson wrote: > > >> there is a PR for it : kern/74319 > > > > This sounds very similar to a serial console related tty bug I was > > experiencing on -STABLE a few months ago, and that is believed may have been > > worked around in 5.4 tweaks before release. In particular, that there are > > reference counting related bugs in the 5.x tty code that are fixed by a > > partial rewrite of the tty code in 6.x, but that are too large and disruptive > > to merge to RELENG_5. If the problem is persisting, it may be worth trying > > to merge anyway, but it is a pretty big change and would break device driver > > binary compatibility, etc. What we might want to do here is wait until 6.x > > has settled out a bit more, then consider merging it to 5.x once 6.x has > > gotten burned in with similar workloads and continued to not illustrate the > > 5.x tty reference bugs. > > On Fri, 24 Jun 2005, Doug White wrote: > > > I've run out of time to debug this, unfortunately... > > I went back to reports I made in January about 5.3: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/010898.html > which appears to be the same issue. I _thought_ this was resolved when I > disabled HT, but maybe I was just lucky between the last reboot and the 5.4 > upgrade. > > It sounds like there's a reasonable chance this has been squashed in code > for 6.0? Since this box is already unstable, I'd be tempted to be an early 6 > adopter to see if it is actually resolved. Especially so if that would be > helpful to the cause. 6.x is not affected by the tty-related problems that 5.x is having. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050628232206.Q3088>