linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22pre6aa1
Date: Fri, 25 Jul 2003 01:28:18 -0400	[thread overview]
Message-ID: <20030725052818.GA6440@x30.random> (raw)
In-Reply-To: <200307231521.15897.rathamahata@php4.ru>

On Wed, Jul 23, 2003 at 03:21:15PM +0400, Sergey S. Kostyliov wrote:
> Hello Andrea,
> 
> This is during `swapoff -a`, on a heavily loaded box:
> 
> ksymoops 2.4.9 on i686 2.4.22-pre6aa1.  Options used
>      -V (default)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.4.22-pre6aa1/ (default)
>      -m /usr/src/linux/System.map (default)
> 
> Warning: You did not tell me where to find symbol information.  I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc.  ksymoops -h explains the options.
> 
> Error (regular_file): read_system_map stat /usr/src/linux/System.map failed
> ksymoops: No such file or directory
> kernel BUG at shmem.c:490!

hmm, 2.4.22pre6aa1 was the first 2.4 largepages port to the >=22pre
shmfs backport from 2.5. It could be a bug in 2.5, or a bug present only
in the backport of the 2.5 code to 22pre, or even a bug only present in
-aa due the largepage patch ported on top of the backport included in
22pre. I'll have a closer look at it tomorrow. The place where it
crashed is:

	BUG_ON(inode->i_blocks);

it might be only a minor accounting issue. It needs some auditing.

I'm afraid you're the first one testing the shmfs backport in 22pre +
the largepage support patch in my tree with a big app doing swapoff at
the same time.

Are you using bigpages btw?

thank you very much for the feedback,

Andrea

PS. shall this give us relevant problems in the debugging/auditing, I'll
just give you a patch to backout the backport and go back to the shmfs
code in 2.4.21rc8aa1 that is running rock solid in production with
largepages (I doubt you need the loop device on top of shmfs anyways). I
prefer not to spend much time on new 2.4 features.

  reply	other threads:[~2003-07-25  5:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 11:21 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25  5:28 ` Andrea Arcangeli [this message]
2003-07-25 11:10   ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 19:02     ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-03 17:12       ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-08-16 11:56         ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-16 13:54           ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:00             ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:50               ` 2.4.22pre6aa1 Sergey S. Kostyliov
  -- strict thread matches above, loose matches on Subject: below --
2003-07-17 10:28 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 10:42 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 10:52   ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 10:53   ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 15:42 ` 2.4.22pre6aa1 Dave Jones
2003-07-17 20:31   ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:13 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:26   ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:27   ` 2.4.22pre6aa1 Mike Fedyk
2003-07-17 22:32     ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:30   ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:50     ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18  0:30       ` 2.4.22pre6aa1 Chris Mason
2003-07-22 12:28         ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 14:04           ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18  5:47       ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-22 13:34       ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 13:59         ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-24 12:27           ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-24 14:14             ` 2.4.22pre6aa1 Chris Mason
2003-07-18 18:18 ` 2.4.22pre6aa1 Christoph Hellwig
2003-07-18 22:27   ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 22:48     ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 22:53       ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:04         ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 23:12           ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:53             ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-19  0:04               ` 2.4.22pre6aa1 Andrea Arcangeli

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=20030725052818.GA6440@x30.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rathamahata@php4.ru \
    /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;
as well as URLs for NNTP newsgroup(s).