From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Daniel Taualii <dtaualii-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mount.cifs hangs when connecting
Date: Thu, 18 Apr 2013 16:38:26 +0100 [thread overview]
Message-ID: <1366299506.6759.5.camel@localhost> (raw)
In-Reply-To: <CAJV-E0qB3u4pcLf-zG45cCchonRMi30_Skn-XwC_ZLctzoBW4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
next prev parent reply other threads:[~2013-04-18 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 20:23 mount.cifs hangs when connecting Daniel Taualii
[not found] ` <CAJV-E0rWpTK08u3bFszkEHL69qEm0noh=LLmUmo_kY5aTxyORw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 14:40 ` Sachin Prabhu
2013-04-18 15:14 ` Daniel Taualii
[not found] ` <CAJV-E0qB3u4pcLf-zG45cCchonRMi30_Skn-XwC_ZLctzoBW4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 15:38 ` Sachin Prabhu [this message]
2013-04-18 15:50 ` Steve French
[not found] ` <CAH2r5muOTECmyi9DemPfhFLcKXwbP-pWxYtUuwaJzqU8XAtgGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 16:21 ` Daniel Taualii
[not found] ` <CAJV-E0pggon=o_i47Bcy+G97VeLpgwq7uNBU_Rs0LF=HB=s-sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 17:45 ` Daniel Taualii
[not found] ` <CAJV-E0oOQUJ0US9Lxah19rnBs9t4a9sUseQisgiGWfAcnKqV+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 18:05 ` Daniel Taualii
[not found] ` <CAJV-E0qFK+6n2yP4BkWM=eoZd5LpWGy8TQQRFu4YyCPgdg_5cA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 18:10 ` Steve French
[not found] ` <CAH2r5msviOzZDj+kubsoVq1a9spDmpDn8NQuB+c=AjgymLC--Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 18:22 ` Daniel Taualii
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=1366299506.6759.5.camel@localhost \
--to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dtaualii-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.