[OpenAFS] Re: kernel panics with 1.6.0 and 1.6.1pre2 on
openindiana
Logan O'Sullivan Bruns
logan@gedanken.org
Sat, 28 Jan 2012 12:38:55 -0800
Andrew,
I did a little bit more testing. I was also able to reproduce the
panic with VirtualBox 4.1.2 using the Oracle Solaris 64 bit
configuration with the oi 151a server iso only modifying the memory to
be a gigabyte. Starting from scratch I can see now that it is crashing
right after preparing or checking the cache directory structure. So
the first time it ran on the VM it didn't crash until it had made all
the cache subdirectories but subsequently it crashes almost
immediately.
So, if it isn't crashing for you perhaps this is an indicator that my
build is no good? I built mine with these options using Solaris Studio 12.3:
./configure --enable-transarc-paths --with-krb5 --enable-namei-fileserver --enable-bitmap-later
If you send me your amd64 afsd and afs binaries maybe I can give those
a try?
Thanks,
logan
On Fri, Jan 27, 2012 at 05:25:52PM -0800, Logan O'Sullivan Bruns wrote:
> Thanks for giving it a try. Responses inline.
>
> On Fri, Jan 27, 2012 at 05:48:47PM -0600, Andrew Deason wrote:
> > On Fri, 27 Jan 2012 10:34:45 -0800
> > "Logan O'Sullivan Bruns" <logan@gedanken.org> wrote:
> >
> > > With the 1.6.1pre2 afsd and kernel module it panics immediately upon
> > > afsd startup with a kernel panic that looks like this:
> >
> > Hm, I was assuming this would also panic immediately on startup for me
> > as well if I tried, but that didn't happen. It's actually working
> > surprisingly well.
>
> That is promising news.
>
> > So, a few questions before I look more deeply at it. What platform is
> > this, sparc/x86/amd64? Did you compile your own kernel or do anything
>
> This is amd64. I'm still running the 1.4 client on my sparc systems.
>
> It is an hp dl360g6 with 6 gigabytes of memory. The processor is:
>
> unix: [ID 950921 kern.info] cpu7: Intel(r) Xeon(r) CPU E5530 @ 2.40GHz
>
> $ isainfo -v
> 64-bit amd64 applications
> vmx sse4.2 sse4.1 ssse3 popcnt tscp cx16 sse3 sse2 sse fxsr mmx cmov
> amd_sysc cx8 tsc fpu
> 32-bit i386 applications
> vmx sse4.2 sse4.1 ssse3 popcnt tscp ahf cx16 sse3 sse2 sse fxsr mmx
> cmov sep cx8 tsc fpu
>
> It's a four core processor with hyperthreading so solaris reports it
> as 8 virtual processors.
>
> $ /usr/sbin/psrinfo -v
> Status of virtual processor 0 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:08.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 1 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 2 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 3 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 4 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 5 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 6 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
> Status of virtual processor 7 as of: 01/27/2012 17:13:36
> on-line since 01/27/2012 01:20:14.
> The i386 processor operates at 2400 MHz,
> and has an i387 compatible floating point processor.
>
> > else weird with it? What specific compiler version are you using to
> > compile OpenAFS? Could you verify the versions of various components are
> > what you think they are with:
>
> I can't think of anything weird about it. At this point other then
> OpenAFS it is still pretty close the basic 151a server install. I did
> install Solaris Studio 12.3 to build OpenAFS.
>
> $ /opt/SUNWspro/bin/cc -V
> cc: Sun C 5.12 SunOS_i386 2011/11/16
>
> > strings /kernel/drv/amd64/afs | grep built
> > strings /usr/vice/etc/afsd | grep built
>
> $ strings /kernel/drv/amd64/afs | grep built
> @(#) OpenAFS 1.6.1pre2 built 2012-01-26
> $ strings /usr/vice/etc/afsd-disabled | grep built
> @(#) OpenAFS 1.6.1pre2 built 2012-01-26
>
> What did you use for your test system? If you used a VM did you
> configure it as 64 bit with multiple processors and greater then a
> gigabyte of memory (to trigger the 64 bit kernel install.)
>
> Maybe you could email me the kernel module and afsd you used?
>
> Thanks again for taking a look.
>
> - logan
>
> >
> > ...or wherever afsd is. Substitute kernel module path for
> > drv/sparcv9/afs or just drv/afs as appropriate.
> >
> > --
> > Andrew Deason
> > adeason@sinenomine.net
> >
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info