Hard lockup with recent CURRENT when using mount_smbfs --
recursive lock message
Garrett Cooper
yanefbsd at gmail.com
Mon Jun 9 03:48:56 UTC 2008
On Sun, Jun 8, 2008 at 8:39 PM, Garrett Cooper <yanefbsd at gmail.com> wrote:
> On Sun, Jun 8, 2008 at 7:31 PM, Garrett Cooper <yanefbsd at gmail.com> wrote:
>> Hi guys,
>> First hard lockup in a while.
>> Just synced current to latest sources yesterday after having to
>> apply some patches to get things to cleanly compile. PR's posted at
>> the bottom of the message.
>> When I run the following command:
>>
>> optimus# mount_smbfs -I 192.168.10.47 -W WORKGROUP
>> //gcooper at orangebox/c$ /mnt/smbfs/
>> Password:
>>
>> My system just locked up. Nothing else that I can say other
>> than it says the following on the console (and it refuses to let me
>> login / interrupt the processor):
>>
>> smb_co_lock: recursive lock for object 1
>>
>> The kernel hasn't panicked and I don't have any means of
>> accessing the machine, so I can't capture output from the kernel right
>> now :(.
>>
>> I'll post my kernel / system stats in a second once I reboot
>> the machine.
I've tied down the following issue (recursive lock for ...) to line
352 of sys/netsmb/smb_conn.c.
I'll manually add in a coredump'able statement to get this thing to
stop before it locks up my system so I can get a backtrace.
-Garrett
More information about the freebsd-current
mailing list