From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Todd Shetter <tshetter-lkml@earthlink.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernel BUG at filemap.c:81
Date: Wed, 9 Feb 2005 10:10:11 -0200 [thread overview]
Message-ID: <20050209121011.GA13614@logos.cnet> (raw)
In-Reply-To: <42099C57.9030306@earthlink.net>
On Wed, Feb 09, 2005 at 12:15:03AM -0500, Todd Shetter wrote:
> Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28,
> 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system
> lockup. This happens in both X and console. Happens with and without my
> Nvidia drivers loaded. I cannot determine what makes this bug present it
> self besides highmem and high i/o support enabled. Im guessing the
> system is fine until highmem is actually used to some point and then it
> borks, but I really have no idea and so im just making a random guess. I
> ran memtest86 for a few hours a while ago thinking that it may be bad
> memory, but that did not seem to be the problem.
>
> If you need anymore information, or have questions, or wish me to test
> anything, PLEASE feel free to contact me, I would really like to see
> this bug resolved. =)
>
> --
> Todd Shetter
>
>
> Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81!
> Feb 8 19:49:31 quark kernel: invalid operand: 0000
> Feb 8 19:49:31 quark kernel: CPU: 0
> Feb 8 19:49:31 quark kernel: EIP: 0010:[<c01280d1>] Tainted: P
Hi Todd,
Why is your kernel tainted ?
next prev parent reply other threads:[~2005-02-09 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 5:15 2.4.x kernel BUG at filemap.c:81 Todd Shetter
2005-02-09 12:10 ` Marcelo Tosatti [this message]
2005-02-09 16:30 ` Todd Shetter
2005-02-09 13:03 ` Marcelo Tosatti
2005-02-09 20:47 ` Todd Shetter
2005-02-09 17:42 ` Marcelo Tosatti
2005-02-10 4:23 ` Todd Shetter
2005-02-10 22:05 ` Marcelo Tosatti
2005-02-13 18:37 ` Jeff Garzik
2005-02-13 22:51 ` Todd Shetter
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=20050209121011.GA13614@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tshetter-lkml@earthlink.net \
/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