All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG at arch/x86_64/mm/pageattr.c:154
Date: Mon, 12 Dec 2005 22:11:28 +0100	[thread overview]
Message-ID: <1134421888.9370.0.camel@localhost> (raw)
In-Reply-To: <1134407505.2874.21.camel@laptopd505.fenrus.org>

On Mon, 2005-12-12 at 18:11 +0100, Arjan van de Ven wrote:
> On Mon, 2005-12-12 at 17:53 +0100, Kasper Sandberg wrote:
> > hello... i know my kernel is tainted,
> 
> ...
> 
> > Call Trace:<ffffffff80101810>{init_level4_pgt+2064}
> > <ffffffff8011e31b>{change_page_attr_addr+155}
> >        <ffffffff88479947>{:nvidia:nv_vm_free_pages+274}
> > <ffffffff88475b44>{:nvidia:nv_kern_vma_release+126}
> >        <ffffffff8015f80c>{remove_vma+44} <ffffffff8015fd78>{exit_mmap
> > +184}
> >        <ffffffff8012c37b>{mmput+27} <ffffffff80130633>{do_exit+547}
> >        <ffffffff80131029>{do_group_exit+169}
> > <ffffffff8010e96e>{system_call+126}
> 
> ... and the nvidia module is all over the backtrace. I think this is a
> clear one for reporting to nvidia instead....
okay, i just thought it was relevant to post here, since the warnings
came after the changes which made nvidia complain.. and since linus was
interrested in that i figured i might aswell post this
> 
> 


      reply	other threads:[~2005-12-12 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 16:53 Kernel BUG at arch/x86_64/mm/pageattr.c:154 Kasper Sandberg
2005-12-12 17:11 ` Arjan van de Ven
2005-12-12 21:11   ` Kasper Sandberg [this message]

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=1134421888.9370.0.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.