From: Frank van Maarseveen <frankvm@xs4all.nl>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Andrew Morton <akpm@osdl.org>,
sdake@mvista.com, liste@jordet.nu, linux-kernel@vger.kernel.org,
sct@redhat.com
Subject: Re: [2.4] page->buffers vanished in journal_try_to_free_buffers()
Date: Sat, 19 Jun 2004 21:50:13 +0200 [thread overview]
Message-ID: <20040619195013.GA6672@janus> (raw)
In-Reply-To: <20040619194849.GA2843@logos.cnet>
On Sat, Jun 19, 2004 at 04:48:49PM -0300, Marcelo Tosatti wrote:
>
> However, he also mentioned that his crashes started after upgrading
> from v2.4.19->2.4.22. Should search the diff between them looking for
> anything suspicious.
>
> I can't figure out from the archived reports if this is UP or SMP only.
>
> Frank van Maarseveen has also seen the journal_try_to_free_buffers() NULL
> b_this_page. Frank, were you running SMP or UP when you reported the oops
> with 2.4.23?
UP
--
Frank
next prev parent reply other threads:[~2004-06-19 20:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 18:26 Oopses with both recent 2.4.x kernels and 2.6.x kernels Stian Jordet
2004-02-05 23:51 ` Marcelo Tosatti
2004-03-02 11:03 ` Stian Jordet
2004-03-02 12:31 ` Stian Jordet
2004-03-09 19:22 ` Marcelo Tosatti
2004-03-09 22:28 ` Stian Jordet
2004-06-14 17:07 ` Steven Dake
2004-06-14 18:26 ` Chris Shoemaker
2004-06-15 13:16 ` Marcelo Tosatti
2004-06-15 14:35 ` Stian Jordet
2004-06-15 17:56 ` Steven Dake
2004-06-17 13:16 ` [2.4] page->buffers vanished in journal_try_to_free_buffers() Marcelo Tosatti
2004-06-18 3:08 ` Andrew Morton
2004-06-19 19:48 ` Marcelo Tosatti
2004-06-19 19:50 ` Frank van Maarseveen [this message]
2004-06-19 22:17 ` Marcelo Tosatti
2004-06-19 22:44 ` Frank van Maarseveen
2004-06-19 20:04 ` Andrew Morton
2004-06-20 7:56 ` Willy Tarreau
2004-06-21 15:06 ` Stephen C. Tweedie
2004-06-21 15:53 ` Marcelo Tosatti
2004-06-22 22:13 ` Stephen C. Tweedie
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=20040619195013.GA6672@janus \
--to=frankvm@xs4all.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.nu \
--cc=marcelo.tosatti@cyclades.com \
--cc=sct@redhat.com \
--cc=sdake@mvista.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 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.