|
|
Jason, thanks, this will please many people in my organization. I was
wondering if there was a way to track when this patch will become
available as part of a new kernel release in up2date. As far as
deployment of the fix, I'm wondering if I should wait for it to be
part of up2date or deploy it manually. I'm worried if I deploy it
manually, then a newer kernel comes out without the fix I'd have to
skip doing that update as to not undo the fix for this problem.
On Mon, 7 Mar 2005 09:29:26 -0500 (EST), Jason Baron <jbaron@xxxxxxxxxx> wrote:
>
> On Tue, 1 Mar 2005, Jason Baron wrote:
>
> >
> > This does indeed match 144059. Unfortunately, i'm not sure what is causing
> > it. The most useful thing would be to narrow down a reproducer for it. One
>
> I believe we have gotten to the bottom of this issue. I've posted a test
> kernel with the fixes in bz #144059, comment #100.
>
> -Jason
>
--
Taroon-list mailing list
Taroon-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/taroon-list
|
|