From: Andrey Nekrasov <andy@spylog.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.11-pre2-xfs
Date: Fri, 5 Oct 2001 21:32:31 +0400 [thread overview]
Message-ID: <20011005213231.C13046@spylog.ru> (raw)
In-Reply-To: <andy@spylog.ru> <20011005022213.A8501@spylog.ru> <200110051420.f95EKVr12837@jen.americas.sgi.com>
In-Reply-To: <200110051420.f95EKVr12837@jen.americas.sgi.com>
Hello Steve Lord,
> Oh well, thats really useful, maybe __alloc_pages should report on its
> caller's caller.
I am use gcc gcc version 2.95.2 19991024 (release).
May be with egcs will be better result?
> > ...
> > swap_dup: Bad swap file entry 3f41e02c
> > VM: killing process forwarderng
> > swap_free: Bad swap offset entry 3ce50000
> > swap_free: Bad swap file entry 3f41e02c
> > swap_free: Bad swap offset entry 38bb5000
> > ...
> >
> > What is it? Kernel or may be my hardware problem?
> Probably kernel, but I am not really an expert on this part of the system,
> is your swap a device or a file on a filesystem?
/dev/hdg1 1 4145 2089048+ 82 Linux swap
--
bye.
Andrey Nekrasov, SpyLOG.
next prev parent reply other threads:[~2001-10-05 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 9:52 [BUG] Symlinks broken on 2.4.10-ac[3-4] nfs Nicolas Mailhot
2001-10-04 10:15 ` 2.4.11-pre2-xfs Andrey Nekrasov
2001-10-04 14:01 ` 2.4.11-pre2-xfs Steve Lord
2001-10-04 14:39 ` 2.4.11-pre2-xfs Keith Owens
2001-10-04 22:22 ` 2.4.11-pre2-xfs Andrey Nekrasov
2001-10-05 14:20 ` 2.4.11-pre2-xfs Steve Lord
2001-10-05 17:32 ` Andrey Nekrasov [this message]
2001-10-04 20:51 ` 2.4.11-pre2-xfs Eric Sandeen
2001-10-04 11:02 ` [BUG] Symlinks broken on 2.4.10-ac[3-4] nfs Trond Myklebust
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=20011005213231.C13046@spylog.ru \
--to=andy@spylog.ru \
--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.