If 110 is ETIMEDOUT, cifs isn't likely to have returned this directly (although on SMB2 mounts it could be mapped) so problems with build of the crypto libraries seems more likely as you suggested. On Thu, Apr 18, 2013 at 10:38 AM, Sachin Prabhu <sprabhu@xxxxxxxxxx> wrote: > On Thu, 2013-04-18 at 09:14 -0600, Daniel Taualii wrote: >> http://pastebin.com/nW1utsYB > > From the pastebin, > > [ 156.124070] CIFS VFS: could not setup hash structures rc -110 > [ 156.124095] BUG: unable to handle kernel NULL pointer dereference at > 0000000000000008 > [ 156.124098] IP: [<ffffffff812deb2b>] crypto_larval_kill+0x2b/0x90 > [ 156.124104] PGD 226547067 PUD 22669f067 PMD 0 > [ 156.124108] Oops: 0002 [#1] SMP > [ 156.124110] CPU 2 > [ 156.124111] Modules linked in: vmnet(O) vsock(O) vmci(O) vmmon(O) > ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE > > You seem to have had an Oops. > The message "CIFS VFS: could not setup hash structures rc -110" suggests > that there was a problem enabling the crypto structures which are used > for the hashing of the passwords and signing of packets. > > Can you please provide the entire Oops message along with a few lines > which preceed it since it should contain the reason why we were not able > to allocate the structure. > > Sachin Prabhu > > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
