Date: Tue, 3 Jun 2003 17:24:51 -0400 (EDT) From: Bryan Liesner <bleez@verizon.net> To: Scott Long <scottl@freebsd.org> Cc: Jeff Roberson <jroberson@chesapeake.net> Subject: Re: umtx/libthr SMP fixes. Message-ID: <20030603171044.U911@gravy.homeunix.net> In-Reply-To: <3EDD04CF.80101@freebsd.org> References: <20030602230746.U69975-100000@mail.chesapeake.net> <20030603115912.Q648@gravy.homeunix.net> <3EDCCB27.5020707@freebsd.org> <20030603132913.D761@gravy.homeunix.net> <3EDD04CF.80101@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 3 Jun 2003, Scott Long wrote: > It's very hard to imagine Jeff's patches causing a problem at the point > that the PR mentions. Have you confirmed the problem in a kernel that > was build in a totally clean environment? > > Scott If you mean a kernel build with standard optimizations, yes I have seen it. No local patches: cc -O -pipe -mcpu=pentiumpro The panic happens before running init. Sometimes I'm "lucky" and the kernel doesn't panic during boot, but it will panic shortly before or after login. It locks up tight afterwards, and doesn't do a dump. All this happened after kern_umtx.c v1.2 When I revert back, no panic... It won't panic if I turn off the USB drive, or compile a kernel without atapicam. Possible problem with EHCI? The driver finds an OHCI device, calls it umass0, detaches it, finds an EHCI device and calls it umass1. I'm sure it's not Jeffs patches that are the problem, but other potential problems are exacerbated by them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030603171044.U911>