Re: 2.6.10-rc3-mm1-V0.7.33-03 and NVidia wierdness, withworkaround...
From: Steven Rostedt
Date: Fri Dec 17 2004 - 15:05:20 EST
On Fri, 2004-12-17 at 13:10 -0500, Valdis.Kletnieks@xxxxxx wrote:
> On Fri, 17 Dec 2004 12:03:31 EST, Steven Rostedt said:
> > Update: I just tried some of my fixes to the rc3-mm1 kernel, and that
> > worked without a problem. But I still didn't get by the sleep problem
> > in Ingo's RT patch. Did you get further, and did you make fixes to both
> > the nvidia module as well as the kernel?
> I have to admit I haven't *hit* a sleep problem specific to Ingo's code, unless
> you have a different config/hardware and my BKL wierdness and your sleep are
> 2 different manifestations of the same problem. Or maybe they're 2 different
> bugs... ;)
> I'm running Ingo's patch and the nvidia 6629 drivers as I'm typing this. Given
> you had to fool with pgd_offset_k and friends, you're probably trying an older
> driver (6111?) and should upgrade - the 6629 picked up a *bunch* of 2.6-related
> fixes. Maybe 6629 fixed your sleep issue?
Nope! I have the 6629. Actually, the patch you have for NV solved the
pgd_offset problem. But I'm amazed that you didn't get into the
may_sleep calls. In the nvidia code os-interface.c, would call hooks
into the kernel with interrupts turned off and hit the may_sleep. But
looking into it further now, one of the crashes came from
ioremap_nocache and the sleep happened in kmem_cache_alloc. So maybe
Ingo fixed this. I lied earlier (not intentionally), the last kernel I
tried with the NVidia was V0.7.32-18, so let me try again.
Thanks, for the references though.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/