From: Bryan Andersen <bryan@bogonomicon.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21-pre3-ac4 oops in free_pages_ok
Date: Fri, 17 Jan 2003 18:05:39 -0600 [thread overview]
Message-ID: <3E289A53.40203@bogonomicon.net> (raw)
I too have been seeing this oops crash problem. I can
consistantly reproduce mine by running:
$ mke2fs -c -j -i 16768 /dev/hdc6
The interesting thing is running:
$ mke2fs -j -i 16768 /dev/hdc6
does not cause an oops crash. The only difference being
the bad block scan.
These are the outputs of ksymoops for the stack trace part
of the oops output from. Kernel version is
linux-2.4.21-pre3-ac4.
Adhoc c013f4b7 <try_to_free_buffers+c7/140>
Adhoc c013d8c9 <try_to_release_page+49/50>
Adhoc c01348ac <__free_pages+1c/20>
Adhoc c0133863 <shrink_cache+383/3b0>
Adhoc c01339f6 <shrink_caches+56/80>
Adhoc c0133a5c <try_to_free_pages_zone+3c/60>
Adhoc c013452e <balance_classzone+5e/1d0>
Adhoc c01347b2 <__alloc_pages+112/160>
Adhoc c012ebc1 <generic_file_write+3f1/710>
Adhoc c01344c6 <_alloc_pages+16/20>
Adhoc c012ebdd <generic_file_write+40d/710>
Adhoc c013b316 <sys_write+96/110>
Adhoc c0106f8b <system_call+33/38>
Adhoc c0134239 <__free_pages_ok+279/2a0>
I'm going to do further tests with the generic IDE
driver instead of the NVIDIA one. Then I plan on
teasing out the NVIDIA2 specific stuff from the ac4
patch and only applying them to a pre3 patched kernel.
- Bryan
next reply other threads:[~2003-01-17 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 0:05 Bryan Andersen [this message]
2003-01-19 11:01 ` 2.4.21-pre3-ac4 oops in free_pages_ok Bryan Andersen
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 16:28 Phil Oester
2003-01-16 19:13 ` Tupshin Harper
2003-01-17 7:47 ` Ralf Hildebrandt
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=3E289A53.40203@bogonomicon.net \
--to=bryan@bogonomicon.net \
--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