From: Todd Shetter <tshetter-lkml@earthlink.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernel BUG at filemap.c:81
Date: Wed, 09 Feb 2005 11:30:05 -0500 [thread overview]
Message-ID: <420A3A8D.9030705@earthlink.net> (raw)
In-Reply-To: <20050209121011.GA13614@logos.cnet>
Marcelo Tosatti wrote:
>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 ?
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
I had the nvidia 1.0-6629 driver loaded when I got that error. I
compiled the kernel using the slackware 10.1 config, enabled highmem 4GB
support, highmem i/o, and then some kernel hacking options including
debugging for highmen related things.
I booted, loaded X with KDE, opened firefox a few times, and then
started running hdparm because some newer 2.4.x kernels dont play nice
with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive
read access portion of its tests, and things locked up from there in
about 30secs.
I've gotten the same error with the nvidia driver not loaded, so I dont
think that is part of the problem.
As I said, if you want me to test or try anything feel free to ask. =)
--
Todd Shetter
next prev parent reply other threads:[~2005-02-09 16:29 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
2005-02-09 16:30 ` Todd Shetter [this message]
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=420A3A8D.9030705@earthlink.net \
--to=tshetter-lkml@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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