public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amiga affs support broken in 2.4.x kernels??
Date: Tue, 17 Apr 2001 08:09:06 -0400	[thread overview]
Message-ID: <3ADC3262.C97B475@compro.net> (raw)
In-Reply-To: <3AD59EB9.35F3A535@compro.net> <3AD9FEDD.2B636582@linux-m68k.org> <3ADAEA9B.D70DC130@compro.net> <3ADB1837.A0AE3020@linux-m68k.org>

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

Roman Zippel wrote:
> 
> Hi,
> 
> Mark Hounschell wrote:
> 
> > Thanks, I can now mount affs filesystems. However when I try to write
> > to it via "cp somefile /amiga/somefile" I get a segmentation fault. If
> > I then do a "df -h" it hangs the system very much like the mount command
> > did before I installed your tar-ball. Was write support expected from
> > it.
> 
> Yes, it should work.
> What sort of filesystem is it (ffs or ofs)? Did you check the dmesg
> output for an oops? Which kernel version did you use?
> 
> > Are you the NEW maintainer of the affs stuff.
> 
> Yes and as soon this problem is solved, I'm sending the changes to Linus
> and Alan.
> 
> bye, Roman

Hello Roman,
 Sorry I didn't get back to you yesterday afternoon. I was out of town.
 Attached is the output from dmesg and the relavent info from
/var/log/messages. I am using a vanilla 2.4.3 kernel with the
affs support compiled in. (No Modules). I beleive the filesystem is ffs
but not exactly sure. How do I tell?

Mark

[-- Attachment #2: xx.dmesg --]
[-- Type: application/octet-stream, Size: 832 bytes --]

Unable to handle kernel NULL pointer dereference at virtual address 00000034
 printing eip:
c01ac1f2
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c01ac1f2>]
EFLAGS: 00010246
eax: c12e8ee0   ebx: 00000000   ecx: c6a0eecc   edx: 00000c09
esi: c6a0ee00   edi: 00000000   ebp: 00000c09   esp: c39b1e3c
ds: 0018   es: 0018   ss: 0018
Process cp (pid: 659, stackpage=c39b1000)
Stack: 00000001 0000000a c2f834e0 c6a0ee00 c6a0eecc c12e8ee0 c01ab00d c6a0ee00
       00000c0b c3a86a64 c39b1f0c 00000000 00000000 00000000 00000000 0000000a
       00000000 00000000 00000000 c011f1b0 c3a869c0 00000048 c39b1f0c c3a869c0
Call Trace: [<c01ab00d>] [<c011f1b0>] [<c013fcfe>] [<c01a9157>] [<c013fe41>] [<c012bc09>] [<c0137c24>]
       [<c012ca17>] [<c012cd2c>] [<c0106e2f>]
 
Code: 8b 43 34 89 e9 c1 ed 05 8d 14 a8 8b 42 04 0f c8 83 e1 1f bf

[-- Attachment #3: xx.messages --]
[-- Type: application/octet-stream, Size: 1521 bytes --]

Apr 17 07:49:30 harley kernel: Unable to handle kernel NULL pointer dereference at virtual address
00000034
Apr 17 07:49:30 harley kernel:  printing eip:
Apr 17 07:49:30 harley kernel: c01ac1f2
Apr 17 07:49:30 harley kernel: *pde = 00000000
Apr 17 07:49:30 harley kernel: Oops: 0000
Apr 17 07:49:30 harley kernel: CPU:    0
Apr 17 07:49:30 harley kernel: EIP:    0010:[affs_free_block+174/364]
Apr 17 07:49:30 harley kernel: EFLAGS: 00010246
Apr 17 07:49:30 harley kernel: eax: c12e8ee0   ebx: 00000000   ecx: c6a0eecc   edx: 00000c09
Apr 17 07:49:30 harley kernel: esi: c6a0ee00   edi: 00000000   ebp: 00000c09   esp: c39b1e3c
Apr 17 07:49:30 harley kernel: ds: 0018   es: 0018   ss: 0018
Apr 17 07:49:30 harley kernel: Process cp (pid: 659, stackpage=c39b1000)
Apr 17 07:49:30 harley kernel: Stack: 00000001 0000000a c2f834e0 c6a0ee00 c6a0eecc c12e8ee0 c01ab00d c6a0ee00
Apr 17 07:49:30 harley kernel:        00000c0b c3a86a64 c39b1f0c 00000000 00000000 00000000 00000000 0000000a
Apr 17 07:49:30 harley kernel:        00000000 00000000 00000000 c011f1b0 c3a869c0 00000048 c39b1f0c c3a869c0
Apr 17 07:49:30 harley kernel: Call Trace: [affs_truncate+601/956] [vmtruncate+316/328] [inode_setattr+54/164] [affs_notify_change+127/152] [notify_change+97/192] [do_truncate+73/96] [open_namei+1108/1440]
Apr 17 07:49:30 harley kernel:        [filp_open+59/92] [sys_open+56/180] [system_call+51/56]
Apr 17 07:49:30 harley kernel:
Apr 17 07:49:30 harley kernel: Code: 8b 43 34 89 e9 c1 ed 05 8d 14 a8 8b 42 04 0f c8 83 e1 1f bf

  reply	other threads:[~2001-04-17 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 12:25 amiga affs support broken in 2.4.x kernels?? Mark Hounschell
2001-04-15 20:04 ` Roman Zippel
2001-04-16 12:50   ` Mark Hounschell
2001-04-16 16:05     ` Roman Zippel
2001-04-17 12:09       ` Mark Hounschell [this message]
2001-04-17 18:04         ` Roman Zippel
2001-04-17 19:11           ` Mark Hounschell

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=3ADC3262.C97B475@compro.net \
    --to=markh@compro.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox