9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Waters" <jcwjr215@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] ilock error/kernel panic (Plan9 hates SciAm)
Date: Sun, 20 Jul 2008 10:40:02 +0300	[thread overview]
Message-ID: <d5ac01e10807200040j2feb6588i5c422f1a216fb403@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

Hello 9fans,

I was fooling around with a fresh install of plan9 on VMWare fusion,
copying some files via ftpfs from my hypervisor (Leopard) to my Plan 9
Guest. Everything was fine until I tried to copy my latest copy of
Scientific American (14.7mb pdf). It was then that I got the
error/kernel panic shown. For giggles renamed the file from 200808.pdf
to sciam-august.pdf, with the same results, I also then bzipped the
file (which only shaved 1 meg off the file size) and again had the
same result.

I then created a set of test files (using dd) of 256k, 512k, 768k,
1mb, 2mb, 4mb, and 8mb in size and proceeded to attempt to copy them
in the same manner (via ftpfs to glenda's $home using cp). All
attempts to copy the files (even the 256k) causes a panic.

Interestingly the 9.intro.pdf file (1.3 meg) copied w/o any issues.
The *.xls files are between 15 and 60kb. (see attacked image (104k).

For those who don't want to look at the image the error reads:
ilock :: 00 00 00 00 06 02 00 00 60 7e 11 f0 80 b8 3f f0 00 00 00 00
(and some other stuff)
panic: corrupt ilock f0049f40 pc=f0117e60 m=0 isilock=0
panic: corrupt ilock f0049f40 pc=f0117e60 m=0 isilock=0
dumpstack disabled
cpu1: exiting
cpu0: exiting

Any help or advice regarding this issue would be greatly appreciated.


Thanks in advance,
John

[-- Attachment #2: sciam-oopsie.jpg --]
[-- Type: image/jpeg, Size: 105368 bytes --]

             reply	other threads:[~2008-07-20  7:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20  7:40 John Waters [this message]
2008-07-20  8:24 ` Russ Cox
2008-07-20  8:26 Russ Cox
2008-07-20  8:42 ` John Waters

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=d5ac01e10807200040j2feb6588i5c422f1a216fb403@mail.gmail.com \
    --to=jcwjr215@gmail.com \
    --cc=9fans@9fans.net \
    /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).