Bryan Liesner wrote:
> A non disclosure agreement is a non disclosure agreement, so no crap
> from me.
>
> I'll give that a try and see if it makes a difference. I don't
> remember off of the top of my head from the previous posts on this
> subject, but does this bug apply to an Athlon XP as well?
On Thu, 5 Jun 2003, Terry Lambert wrote:
> I hesistate to suggest this because everyone always gives me
> crap about me not disclosing the bug, but unless you are ready
> to grovel around in locore, and figure out what the root cause
> is for the difference in behaviour, I'm going to say that
> th
Bryan Liesner wrote:
> On Thu, 5 Jun 2003, Terry Lambert wrote:
> > As I said: I still think there is a lost serialization here
> > that's at the root of the problem. I can't really dedicate
> > the equipment I have here to reproducing the issue at this
> > time, or I'd track down the race I think
On Thu, 5 Jun 2003, Terry Lambert wrote:
> As I said: I still think there is a lost serialization here
> that's at the root of the problem. I can't really dedicate
> the equipment I have here to reproducing the issue at this
> time, or I'd track down the race I think may be happening.
>
> -- Terr
Jeff Roberson wrote:
> On Tue, 3 Jun 2003, Terry Lambert wrote:
> > Scott Long wrote:
> > > Bryan Liesner 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 cl
On Tue, 3 Jun 2003, Robert Watson wrote:
>
> On Tue, 3 Jun 2003, Bryan Liesner wrote:
>
> > Actually, no it doesn't. I was able to use kern_umtx v 1.3 only if I
> > removed atapicam from my kernel config. These patches (now committed?)
> > panic the system whether I use atapicam or not. With ke
On Tue, 3 Jun 2003, Terry Lambert wrote:
> Scott Long wrote:
> > Bryan Liesner 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?
>
> The changed
Scott Long wrote:
> Bryan Liesner 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?
The changed code is not protecting a traversal of a proc
struct me
On Tue, 3 Jun 2003, Bryan Liesner wrote:
> Actually, no it doesn't. I was able to use kern_umtx v 1.3 only if I
> removed atapicam from my kernel config. These patches (now committed?)
> panic the system whether I use atapicam or not. With kern_umtx v1.2
> there is no panic at all, with or wit
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, ye
Bryan Liesner wrote:
On Tue, 3 Jun 2003, Scott Long wrote:
Actually, I think it's cam in general that's causing the panic with
these changes.
Please see kern/52718
I didn't see a backtrace in the PR. Is there one that you can share
with us?
It panics during boot and, unfortunately, no dump is
On Tue, 3 Jun 2003, Scott Long wrote:
> > Actually, I think it's cam in general that's causing the panic with
> > these changes.
> >
> > Please see kern/52718
>
> I didn't see a backtrace in the PR. Is there one that you can share
> with us?
>
It panics during boot and, unfortunately, no dump is
Bryan Liesner wrote:
On Mon, 2 Jun 2003, Jeff Roberson wrote:
If you have had issues with libthr on SMP or umtx panics, the following
patch may solve these issues.
http://www.chesapeake.net/~jroberson/umtxlocks.diff
This patch fixes several race conditions and other issues with umtx.
Actually,
On Mon, 2 Jun 2003, Jeff Roberson wrote:
> If you have had issues with libthr on SMP or umtx panics, the following
> patch may solve these issues.
>
> http://www.chesapeake.net/~jroberson/umtxlocks.diff
>
> This patch fixes several race conditions and other issues with umtx.
Actually, no it does
If you have had issues with libthr on SMP or umtx panics, the following
patch may solve these issues.
http://www.chesapeake.net/~jroberson/umtxlocks.diff
This patch fixes several race conditions and other issues with umtx.
Thanks,
Jeff
___
[EMAIL PROT
15 matches
Mail list logo
