Hi Ben,

Well, I was so hopeful that would fix the problem, but no.  I removed
any old headers and kernels on the box, and then purged and reinstalled
all of the afs packages, but I still get a kernel panic (below)

Here's the versions of everything now:
 dpkg -l | grep -e linux-image -e linux-headers | grep ii
ii  linux-headers-4.4.0-89               4.4.0-89.112~14.04.1
all          Header files related to Linux kernel version 4.4.0
ii  linux-headers-4.4.0-89-generic       4.4.0-89.112~14.04.1
amd64        Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
ii  linux-headers-generic-lts-xenial     4.4.0.89.74
amd64        Generic Linux kernel headers
ii  linux-image-4.4.0-89-generic         4.4.0-89.112~14.04.1
amd64        Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-89-generic   4.4.0-89.112~14.04.1
amd64        Linux kernel extra modules for version 4.4.0 on 64 bit x86
SMP
ii  linux-image-generic-lts-xenial       4.4.0.89.74
amd64        Generic Linux kernel image
ii  linux-image-hwe-generic-trusty       3.13.0.126.136
amd64        Depends on the generic hardware enablement kernel image.

dpkg -l | grep openafs | grep ii
ii  openafs-client                       1.6.21-1~ppa1~ubuntu14.04.1
amd64        AFS distributed filesystem client support
ii  openafs-krb5                         1.6.21-1~ppa1~ubuntu14.04.1
amd64        AFS distributed filesystem Kerberos 5 integration
ii  openafs-modules-dkms                 1.6.21-1~ppa1~ubuntu14.04.1
all          AFS distributed filesystem kernel module DKMS source

/usr/src/linux looks pretty clean:
ls /usr/src
linux-headers-4.4.0-89  linux-headers-4.4.0-89-generic  openafs-1.6.21
spl-0.6.5.11  zfs-0.6.5.11

Thanks,
Richard

Here's the panic (happens about 10 seconds after starting containers):
[  147.191552] openafs: Inconsistent file handles within cache
[  147.192457] ------------[ cut here ]------------
[  147.193133] kernel BUG at
/var/lib/dkms/openafs/1.6.21/build/src/libafs/MODLOAD-4.4.0-89-generic-SP/osi_file.c:133!
[  147.194863] invalid opcode: 0000 [#1] SMP 
[  147.195549] Modules linked in: sunrpc veth xt_CHECKSUM iptable_mangle
ipt_MASQUERADE nf_nat_masquerade_ipv4 openafs(POE) iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
xt_tcpudp iptable_filter ip_tables x_tables bridge stp llc kvm irqbypass
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64
lrw gf128mul glue_helper joydev ablk_helper input_leds cryptd serio_raw
i2c_piix4 k10temp fam15h_power amd64_edac_mod edac_mce_amd edac_core
8250_fintek shpchp mac_hid lp parport zfs(POE) zunicode(POE)
zcommon(POE) znvpair(POE) spl(OE) zavl(POE) ses enclosure hid_generic
usbhid hid uas usb_storage igb mpt3sas psmouse pata_acpi i2c_algo_bit
ahci dca raid_class pata_atiixp ptp libahci scsi_transport_sas pps_core
fjes
[  147.208323] CPU: 20 PID: 10397 Comm: afsd Tainted: P           OE
4.4.0-89-generic #112~14.04.1-Ubuntu
[  147.209831] Hardware name: Supermicro H8DGU/H8DGU, BIOS 3.5a
02/10/2015
[  147.210977] task: ffff8817d536c600 ti: ffff8817c9a6c000 task.ti:
ffff8817c9a6c000
[  147.212186] RIP: 0010:[<ffffffffc071ed20>]  [<ffffffffc071ed20>]
osi_get_fh+0xc0/0xe0 [openafs]
[  147.213623] RSP: 0018:ffff8817c9a6fc90  EFLAGS: 00010296
[  147.214474] RAX: 000000000000002f RBX: 0000000000000000 RCX:
0000000000000000
[  147.215625] RDX: 0000000000000001 RSI: ffff88381ec8dd98 RDI:
ffff88381ec8dd98
[  147.216759] RBP: ffff8817c9a6fc98 R08: 0000000000000000 R09:
ffffc90019431620
[  147.217899] R10: 0000000000000001 R11: 00000000000008ea R12:
000000000062d9c0
[  147.246545] R13: ffff8837d6bd0e00 R14: 0000000000000001 R15:
0000000000000007
[  147.275293] FS:  00007f7e68ee9740(0000) GS:ffff88381ec80000(0000)
knlGS:0000000000000000
[  147.332808] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  147.361685] CR2: 00000000026a1000 CR3: 00000037b723d000 CR4:
00000000000406e0
[  147.390661] Stack:
[  147.418621]  0000000300000001 ffff8817c9a6fcb0 ffffffffc071f0cf
ffff8837c21fea80
[  147.476081]  ffff8817c9a6fce8 ffffffffc06d01e8 00007f7e687cba90
ffff8817c9a6fcd8
[  147.533604]  ffffffff810878f8 ffffffff8180afe2 0000000000000000
ffff8817c9a6fda8
[  147.563011] Call Trace:
[  147.563038]  [<ffffffffc071f0cf>] osi_InitCacheInfo+0x3f/0x80
[openafs]
[  147.563050]  [<ffffffffc06d01e8>] afs_InitCacheInfo+0x28/0x120
[openafs]
[  147.563056]  [<ffffffff810878f8>] ? ns_capable_common+0x68/0x80
[  147.563060]  [<ffffffff8180afe2>] ? mutex_lock+0x12/0x2f
[  147.563075]  [<ffffffffc072ad1a>] afs_syscall_call+0xd9a/0x1c00
[openafs]
[  147.563078]  [<ffffffff8120b6ed>] ? terminate_walk+0xbd/0xd0
[  147.563080]  [<ffffffff8120f319>] ? path_openat+0x2e9/0x12d0
[  147.563096]  [<ffffffffc06dd189>] afs_syscall+0x319/0x590 [openafs]
[  147.563111]  [<ffffffffc0721652>] afs_unlocked_ioctl+0x92/0xc0
[openafs]
[  147.563116]  [<ffffffff8126baea>] proc_reg_unlocked_ioctl+0x3a/0x70
[  147.563118]  [<ffffffff8121474d>] do_vfs_ioctl+0x2dd/0x4c0
[  147.563120]  [<ffffffff812149a9>] SyS_ioctl+0x79/0x90
[  147.563122]  [<ffffffff8180ccb6>] entry_SYSCALL_64_fastpath+0x16/0x75
[  147.563136] Code: 8b 0d e5 4e 02 00 89 05 e3 4e 02 00 89 c2 85 c9 79
b0 8b 4d fc 89 0d d0 4e 02 00 eb a5 48 c7 c7 c0 eb 73 c0 31 c0 e8 4f 4f
a6 c0 <0f> 0b 48 c7 c7 98 eb 73 c0 31 c0 e8 3f 4f a6 c0 0f 0b 66 66 66 
[  147.563151] RIP  [<ffffffffc071ed20>] osi_get_fh+0xc0/0xe0 [openafs]
[  147.563151]  RSP <ffff8817c9a6fc90>
[  147.563837] ---[ end trace 4bac2c098078ad25 ]---


On Wed, Aug 09, 2017 at 09:04:09PM -0500, Benjamin Kaduk wrote:
> On Wed, Aug 09, 2017 at 06:58:34PM -0700, Richard Feltstykket wrote:
> > Hi Ben,
> > 
> > Sorry, was trying to squeeze in a quick reply in between classes.  
> 
> Understood, and if I had thought more about my reply the rebooting question
> would not have been asked in the first place.
> 
> > Yes, I did a dist-upgrade, and a new kernel was installed, and DKMS did 
> > run.  I will try purging and reinstalling the client tonight, that should 
> > address any mismatches, yes?  I'll also remove any other kernels and 
> > headers at the same time, just to be sure.
> 
> 
> purge+reinstall is definitely enough to rule out a mismatch, yes.
> And, probably the ubuntu version + package number you already sent is
> enough to find the ubuntu changelog entry for the kernel update you took, but
> it is perhaps slightly more authoritative for you to find it in
> /usr/share/doc/linux-<mumble>/ or via apt-listchanges.
> (But I am in the middle of something else and can't go look for it
> on my end right now.)
> 
> -Ben
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info

Attachment: signature.asc
Description: PGP signature

Reply via email to