Date: Sun, 8 Jun 2008 20:48:54 -0700 From: "Garrett Cooper" <yanefbsd@gmail.com> To: current@freebsd.org Subject: Re: Hard lockup with recent CURRENT when using mount_smbfs -- recursive lock message Message-ID: <7d6fde3d0806082048n639310eav157c8d9def335d30@mail.gmail.com> In-Reply-To: <7d6fde3d0806082039r2a49ab77lf6f92b3699c12c7e@mail.gmail.com> References: <7d6fde3d0806081931h5df7b71dkdd4d6e3e2d144ff2@mail.gmail.com> <7d6fde3d0806082039r2a49ab77lf6f92b3699c12c7e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 8, 2008 at 8:39 PM, Garrett Cooper <yanefbsd@gmail.com> wrote: > On Sun, Jun 8, 2008 at 7:31 PM, Garrett Cooper <yanefbsd@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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0806082048n639310eav157c8d9def335d30>