mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Thomas Kaeding <kaeding@kaeding.homelinux.org>,
	linux-kernel@vger.kernel.org
Subject: Re: more info for last message (bug at page_alloc.c:102)
Date: Thu, 5 Jun 2003 14:12:16 +0200	[thread overview]
Message-ID: <200306051410.32138.m.c.p@wolk-project.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306050801200.854-100000@kaeding.localdomain>

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

On Thursday 05 June 2003 14:04, Thomas Kaeding wrote:

Hi Thomas.

> Here is more info that you might need.  The problem occurred overnight.
> In the morning, the mouse worked until I tried to start an app
> in KDE, then everything froze.  Ctl-alt-bkspc gave only a black screen.
> I had to hit restart.
> NVdriver             1065216  10
well, this won't help you right now, but you know how to proceed if you read 
the attached patch. It fits your situation ;)

ciao, Marc



[-- Attachment #2: nvidia-bug-explaination.patch --]
[-- Type: text/x-diff, Size: 584 bytes --]

diff -urN a/mm/page_alloc.c b/mm/page_alloc.c
--- a/mm/page_alloc.c	Sat Aug  3 17:08:40 2002
+++ b/mm/page_alloc.c	Thu Oct 17 16:42:24 2002
@@ -98,8 +98,12 @@
 
 	if (page->buffers)
 		BUG();
-	if (page->mapping)
-		BUG();
+	if (page->mapping) {
+		printk(KERN_CRIT "Page has mapping still set. This is a serious situation. However if you\n");
+		printk(KERN_CRIT "are using the NVidia binary only module please report this bug to\n");
+		printk(KERN_CRIT "NVidia and not to the Linux Kernel Mailinglist!\n");
+ 		BUG();
+	}
 	if (!VALID_PAGE(page))
 		BUG();
 	if (PageLocked(page))

      reply	other threads:[~2003-06-05 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 12:04 Thomas Kaeding
2003-06-05 12:12 ` Marc-Christian Petersen [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=200306051410.32138.m.c.p@wolk-project.de \
    --to=m.c.p@wolk-project.de \
    --cc=kaeding@kaeding.homelinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®