From: "Bogdan Antonovici" <bantonovici@priority.mb.ca>
To: "Dan Malek" <dan@embeddededge.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
ppckernel <ppckernel@ppckernel.org>,
linuxppc-embedded@ozlabs.org
Subject: Re: swap_dup: Bad swap file entry 00480020
Date: Fri, 5 Aug 2005 14:12:33 -0500 [thread overview]
Message-ID: <00ca01c599f1$a2411730$cd01a8c0@DESIGNLAB> (raw)
In-Reply-To: 1a928a85f53f5dcd972161356611a312@embeddededge.com
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Dan,
It hasn't crashed since i corrected that pointer initialization in driver. You were right.
Thank you.
Bogdan
----- Original Message -----
From: Dan Malek
To: bogdan antonovici
Cc: linuxppc-dev ; linuxppc-embedded@ozlabs.org ; ppckernel
Sent: Thursday, July 21, 2005 12:59 PM
Subject: Re: swap_dup: Bad swap file entry 00480020
On Jul 21, 2005, at 11:29 AM, bogdan antonovici wrote:
> At the time of swap messages i was running a proprietary driver, my
> application and few daemons.
Looks like your driver may have written over some of the page
tables in the kernel space.
> I look on the net for some clues but it's quite confusing, i noticed
> many emails on swap_dup/swap_free error messages but i couldn't figure
> out what should i search for.
Those messages are likely due to a bug with swapping to disk
that has been in some 2.4 kernels, but I don't believe that is
the case here, since you don't have a disk or swapping enabled.
-- Dan
[-- Attachment #2: Type: text/html, Size: 2462 bytes --]
next prev parent reply other threads:[~2005-08-05 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 15:29 swap_dup: Bad swap file entry 00480020 bogdan antonovici
2005-07-21 17:59 ` Dan Malek
2005-07-21 18:14 ` Bogdan Antonovici
2005-07-22 15:46 ` bogdan antonovici
2005-07-22 12:57 ` Marcelo Tosatti
2005-07-25 13:16 ` Bogdan Antonovici
2005-07-25 17:36 ` Benjamin Herrenschmidt
2005-08-05 19:12 ` Bogdan Antonovici [this message]
2005-08-05 19:29 ` Dan Malek
2005-08-05 21:12 ` Geoff Levand
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='00ca01c599f1$a2411730$cd01a8c0@DESIGNLAB' \
--to=bantonovici@priority.mb.ca \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ppckernel@ppckernel.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.