[Unionfs] Kernel Panic on startup

[Ngo, Andrew]

All,

I re-compile my system (RHEL5 kernel 2.6.18.el5), patched with unionfs
(unionfs-2.3.3_for_2.6.18.8.centos5.diff.gz).  Instead of making an iso
image as I did on my previous email, I reboot the machine right after I
compile my kernel.  The machine has kernel panic again, but this time
the message is different than what I posted last time.  I captured what
is left over from my frozen screen less the machine address on each
line:

[<address>]open_nami
[<address>]mntput_no_expired
[<address>]do_filp_open
[<address>]alternate_node_alloc
[<address>]do_sys_open
[<address>]do_name
[<address>]write_buffer
[<address>]flush_window
[<address>]inflate_codes
[<address>]unpack_to_rootfs
[<address>]populate_root_fs
[<address>]init
[<address>]child_rip
[<address>]acpi_ds_init_one_object
[<address>]init
[<address>]child_rip

Code: 4c 8b 60 10 74 0a 83 64 24 0c 04 83 4c 24 0c 01 83 4d 20 04
RIP [<address>] __link_path_walk
 RSP <address>
CR2:0000000000010
<0>Kernel panic - not syncing: Fatal exception

Does anyone know how to resolve this problem?  Your help is greatly
appreciated.

Andy Ngo

-----Original Message-----
From: unionfs-bounces at fsl.cs.sunysb.edu
[mailto:unionfs-bounces at fsl.cs.sunysb.edu] On Behalf Of Erez Zadok
Sent: Friday, May 09, 2008 9:50 AM
To: Ngo, Andrew
Cc: Johnson, Je; unionfs at fsl.cs.sunysb.edu
Subject: Re: [Unionfs] Kernel Panic on startup

In message
<AC33E917323B7F429C94A5B919B4CD18067C9CE5 at emss04m05.us.lmco.com>, "Ngo,
Andrew" writes:

> Hi,
>  
> I am trying to bootup my newly built OS with unionfs compiled in it.  
> I have kernel panic.  I am running RHEL5 kernel 2.6.18-8.el5, patched 
> with unionfs-2.3.3_for_2.6.18.8.centos5.diff.gz.  The following are 
> the message that I manually copied from whatever was left on the 
> frozen
> screen:

> [<address>] link_path_walk+0xd3/0xe5
> [<address>] do_path_lookup+0x2aa/0x326 [<address>] 
> __path_lookup_intent_open+0x56/0x97
> [<address>] open_namei+0xb0/0x6d6
> [<address>] do_filp_open+0x1c/0x38
> [<address>] do_sys_open+0x44/0xbe
> [<address>] do_name+0xc0/0x180
> [<address>] write_buffer+01d/0x2b
> [<address>] flush_window+0x6c/0xca
> [<address>] inflate_codes+0x38f/0x3ec
> [<address>] inflate_dynamic+0x4ff/0x54c [<address>] 
> unpack_to_rootfs+0x4be/0x923 [<address>] populate_rootfs+0x8a/0xde 
> [<address>] init+0x18d/0x3c5 [<address>] clild+rif+0xa/0x11 
> [<address>] acpi_ds_init_one_object+0x0/0x80 [<address>] 
> init+0x0/0x3c5 [<address>] child_rip+0x0/0x11

Hard to tell what's going on.  Did you compile unionfs w/ debugging on?
Do your logs (usually in /var/log) show anything during or after the
reboot?
Can you provide an iso or vmware image with everything in it to try and
reproduce it here on my end?

Thanks,
Erez.
_______________________________________________
unionfs mailing list: http://unionfs.filesystems.org/
unionfs at mail.fsl.cs.sunysb.edu
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs