All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Valdis.Kletnieks@vt.edu
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc3-mm1-V0.7.33-03 and NVidia wierdness, with workaround...
Date: Fri, 17 Dec 2004 15:04:21 -0500	[thread overview]
Message-ID: <1103313861.12664.71.camel@localhost.localdomain> (raw)
In-Reply-To: <200412171810.iBHIAQP3026387@turing-police.cc.vt.edu>

On Fri, 2004-12-17 at 13:10 -0500, Valdis.Kletnieks@vt.edu 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.

-- Steve



  reply	other threads:[~2004-12-17 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 16:26 2.6.10-rc3-mm1-V0.7.33-03 and NVidia wierdness, with workaround Valdis.Kletnieks
2004-12-17 16:19 ` Steven Rostedt
2004-12-17 17:03   ` Steven Rostedt
2004-12-17 18:10     ` Valdis.Kletnieks
2004-12-17 20:04       ` Steven Rostedt [this message]
2004-12-17 21:49         ` Valdis.Kletnieks
2004-12-17 21:55           ` Steven Rostedt
2004-12-17 21:52         ` Steven Rostedt
2004-12-17 22:42           ` Valdis.Kletnieks
2004-12-19 16:20             ` Steven Rostedt
2004-12-20  2:46               ` Joe
2004-12-20  4:22                 ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1103313861.12664.71.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.