From: "steve j. kondik" <shade@chemlab.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: encrypted swap on loop in 2.4.10-pre12?
Date: 19 Sep 2001 13:38:39 -0400 [thread overview]
Message-ID: <1000921119.2693.6.camel@discord> (raw)
In-Reply-To: <20010919173725.B11991@suse.de>
In-Reply-To: <1000912739.17522.2.camel@discord> <20010919173725.B11991@suse.de>
[-- Attachment #1: Type: text/plain, Size: 3869 bytes --]
read in the wrong file. here it is:
Sep 19 13:15:09 discord kernel: Unable to handle kernel NULL pointer
dereference at virtual
Sep 19 13:15:09 discord kernel: 00000000
Sep 19 13:15:09 discord kernel: *pde = 0f602067
Sep 19 13:15:09 discord kernel: Oops: 0000
Sep 19 13:15:09 discord kernel: CPU: 0
Sep 19 13:15:09 discord kernel: EIP: 0010:[<00000000>]
Using defaults from ksymoops -t elf32-i386 -a i386
Sep 19 13:15:09 discord kernel: EFLAGS: 00010206
Sep 19 13:15:09 discord kernel: eax: c02fbca0 ebx: cf613000 ecx:
00000400 edx: cfb428c0
Sep 19 13:15:09 discord kernel: esi: 00001000 edi: 00000c00 ebp:
c139aca0 esp: cf605efc
Sep 19 13:15:09 discord kernel: ds: 0018 es: 0018 ss: 0018
Sep 19 13:15:09 discord kernel: Process mkswap (pid: 5695,
stackpage=cf605000)
Sep 19 13:15:09 discord kernel: Stack: c012a371 cfb428c0 c139aca0
00000400 00001000 cfcd61b0 001828c4 00000000
Sep 19 13:15:09 discord kernel: 00000000 00001000 00000400
00000c00 fffffff4 00000000 00000400 00000000
Sep 19 13:15:09 discord kernel: cfa9210c cfa92060 00000000
c01a1ba0 00126000 00001000 00000003 32000022
Sep 19 13:15:09 discord kernel: Call Trace: [<c012a371>] [<c01a1ba0>]
[<c01359c0>] [<c01357fe>] [<c0106ebb>]
Sep 19 13:15:09 discord kernel: Code: Bad EIP value.
>>EIP; 00000000 Before first symbol
Trace; c012a370 <generic_file_write+410/810>
Trace; c01a1ba0 <write_chan+0/1c0>
Trace; c01359c0 <sys_write+b0/d0>
Trace; c01357fe <sys_llseek+fe/140>
Trace; c0106eba <system_call+32/38>
On Wed, 2001-09-19 at 11:37, Jens Axboe wrote:
> On Wed, Sep 19 2001, steve j. kondik wrote:
> > i've been using encrypted swap over loopdev using the new cryptoapi
> > patches. i just built a 2.4.10-pre12 kernel and i got a panic doing
> > mkswap on the loopdev. the mkswap process becomes unkillable after this
> > and never finishes. this is repeatable everytime. i've had no problems
> > whatsoever until this kernel even under high load.. any ideas? :>
> >
> > Sep 19 11:06:13 discord kernel: Unabl
> > Sep 19 11:06:13 discord kernel: e to handle kernel NULL pointer
> > dereference at virtual address 00000000
> > Sep 19 11:06:13 discord kernel: printing eip:
> > Sep 19 11:06:13 discord kernel: 00000000
> > Sep 19 11:06:13 discord kernel: *pde = 0f444067
> > Sep 19 11:06:13 discord kernel: *pte = 00000000
> > Sep 19 11:06:13 discord kernel: Oops: 0000
> > Sep 19 11:06:13 discord kernel: CPU: 0
> > Sep 19 11:06:13 discord kernel: EIP: 0010:[<00000000>]
> > Sep 19 11:06:13 discord kernel: EFLAGS: 00010206
> > Sep 19 11:06:13 discord kernel: eax: c02fbca0 ebx: cf47d000 ecx:
> > 00000400 edx: cfb428c0
> > Sep 19 11:06:13 discord kernel: esi: 00001000 edi: 00000c00 ebp:
> > c1394d78 esp: cf447efc
> > Sep 19 11:06:13 discord kernel: ds: 0018 es: 0018 ss: 0018
> > Sep 19 11:06:13 discord kernel: Process mkswap (pid: 9902,
> > stackpage=cf447000)
> > Sep 19 11:06:13 discord kernel: Stack: c012a371 cfb428c0 c1394d78
> > 00000400 00001000 cfcd61b0 001828c4 00000000
> > Sep 19 11:06:13 discord kernel: 00000000 00001000 00000400
> > 00000c00 fffffff4 00000000 00000400 00000000
> > Sep 19 11:06:13 discord kernel: cfa9210c cfa92060 00000000
> > c01a1ba0 00126000 00001000 00000003 32000022
> > Sep 19 11:06:13 discord kernel: Call Trace: [<c012a371>] [<c01a1ba0>]
> > [<c01359c0>] [<c01357fe>] [<c0106ebb>]
> > Sep 19 11:06:13 discord kernel:
> > Sep 19 11:06:13 discord kernel: Code: Bad EIP value.
> > Sep 19 11:06:13 discord kernel: Unable to find swap-space signature
>
> ksymoops it please
>
--
http://chemlab.org - email shade-pgpkey@chemlab.org for pgp public key
chemlab radio! - drop out @ http://mp3.chemlab.org:8000 24-7-365
"i could build anything if i could just find my tools.."
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-09-19 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 15:18 encrypted swap on loop in 2.4.10-pre12? steve j. kondik
2001-09-19 15:37 ` Jens Axboe
2001-09-19 17:38 ` steve j. kondik [this message]
2001-09-19 21:02 ` Jari Ruusu
2001-09-20 6:13 ` Jens Axboe
2001-09-20 12:08 ` Jari Ruusu
2001-09-20 12:25 ` Jens Axboe
2001-09-20 13:17 ` steve j. kondik
2001-09-20 17:04 ` Jari Ruusu
2001-09-20 17:20 ` steve j. kondik
2001-09-20 17:55 ` Jari Ruusu
2001-09-20 18:59 ` Michael H. Warfield
2001-09-21 0:36 ` steve j. kondik
2001-09-21 9:15 ` Jari Ruusu
2001-09-21 14:52 ` steve j. kondik
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=1000921119.2693.6.camel@discord \
--to=shade@chemlab.org \
--cc=axboe@suse.de \
--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.