From: Bryan Andersen <bryan@bogonomicon.net>
To: Hugh Dickins <hugh@veritas.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.21-pre3-ac oops
Date: Sun, 19 Jan 2003 15:27:15 -0600 [thread overview]
Message-ID: <3E2B1833.5060203@bogonomicon.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301191347310.2280-100000@localhost.localdomain>
Patch looks like it solved the problem. 6 kernel compiles
and 6 mke2fs with bad block scans and the system is still
up.
The only thing I'm still seeing that is unusual is this kernel
message:
ide: no cache flush required.
which only shows up in the file:
./drivers/ide/ide-disk.c:
Nothing seams to come of them, but in the average boot I see
25 or so of them. They did not show up under linux-2.4.21-pre3.
As near as I can tell they are generated when an ide device is
closed.
- Bryan
Hugh Dickins wrote:
> If you got 2.4.21-pre3-ac __free_pages_ok oops, please try this patch.
>
> Hugh
>
> --- 2.4.21-pre3-ac4/kernel/fork.c Mon Jan 13 18:56:12 2003
> +++ linux/kernel/fork.c Sun Jan 19 13:39:37 2003
> @@ -688,6 +688,8 @@
> p->lock_depth = -1; /* -1 = no lock */
> p->start_time = jiffies;
>
> + INIT_LIST_HEAD(&p->local_pages);
> +
> retval = -ENOMEM;
> /* copy all the process information */
> if (copy_files(clone_flags, p))
>
> -
> 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/
>
next prev parent reply other threads:[~2003-01-19 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 14:08 [PATCH] 2.4.21-pre3-ac oops Hugh Dickins
2003-01-19 18:17 ` Jurriaan
2003-01-19 20:13 ` Tupshin Harper
2003-01-19 21:27 ` Bryan Andersen [this message]
2003-01-19 21:28 ` Andre Hedrick
2003-01-19 21:58 ` Tupshin Harper
2003-01-19 22:15 ` Bryan Andersen
2003-01-19 23:27 ` Andre Hedrick
2003-01-20 18:51 ` Bryan Andersen
2003-01-19 22:13 ` Ralf Hildebrandt
2003-01-20 8:37 ` Alan Cox
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=3E2B1833.5060203@bogonomicon.net \
--to=bryan@bogonomicon.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--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.