From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Rechenberg, Andrew" <ARechenberg@shermanfinancialgroup.com>,
linux-kernel@vger.kernel.org
Cc: "Kevin P. Fleming" <kpfleming@cox.net>
Subject: RE: OOPS in do_try_to_free_pages with VERY large software RAID array
Date: Tue, 11 Mar 2003 11:39:30 -0800 [thread overview]
Message-ID: <25390000.1047411570@flay> (raw)
In-Reply-To: <8075D5C3061B9441944E137377645118012E97@cinshrexc03.shermfin.com>
> Thanks for the help Martin. It looks like that was the problem. The
> kernel mdstat statistics must have been overwriting some other kernel
> memory and giving me my panics. With the help of Kevin's 2.5 patch I
> patched the Red Hat 2.4.18-26 md code to use seq_file and now my big
> RAID arrays are syncing and I haven't had a panic yet :D
>
> Thanks again to everyone for the help. I'll submit the patch to the
> linux-raid list as md-seq_file-2.4.18-26.7.x.patch if anyone's
> interested.
Cool. If I get bored at some point, I might try to make a debug option
to put some minefield trap after /proc functions to catch them doing
this. Or we change the interface ;-)
I got burnt by the same thing for being the first twit to try booting
a 16 CPU ia32 machine ... /proc/cpuinfo went a bit wild.
M.
next prev parent reply other threads:[~2003-03-11 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 19:38 OOPS in do_try_to_free_pages with VERY large software RAID array Rechenberg, Andrew
2003-03-11 19:39 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 20:18 Rechenberg, Andrew
2003-03-11 17:38 Rechenberg, Andrew
2003-03-11 17:49 ` Randy.Dunlap
2003-03-10 21:23 Rechenberg, Andrew
2003-03-10 21:52 ` Martin J. Bligh
2003-03-10 19:20 Rechenberg, Andrew
2003-03-10 19:27 ` Martin J. Bligh
2003-03-10 19:48 ` Kevin P. Fleming
2003-03-10 19:19 Rechenberg, Andrew
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=25390000.1047411570@flay \
--to=mbligh@aracnet.com \
--cc=ARechenberg@shermanfinancialgroup.com \
--cc=kpfleming@cox.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 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.