Thanks Tilghman.
I am using zaptel SVN branch revision 1467, so I applied the patch manually as attached
below. I am not sure if I did the "diff" correctly though :)
There is no "[ INFO: hard-safe -> hard-unsafe lock order detected ]" anymore on
/var/log/messages after reboot.
Cheers,
Anto
----
==================================================================================
--- zaptel.c.ORIG (SVN branch revision 1467)
+++ zaptel.c.with_20060815__bug7620.diff.txt (working copy)
@@ -1092,7 +1092,16 @@
if ((zone >= ZT_TONE_ZONE_MAX) || (zone < -1))
return -EINVAL;
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,11)
+ /* Since this routine is called both from IRQ as well as from userspace,
+ * it is possible that we could be called during an IRQ while userspace
+ * has locked this. However unlikely, this could possibly cause a
+ * deadlock. */
+ if (! read_trylock(&zone_lock))
+ return -EWOULDBLOCK;
+#else
read_lock(&zone_lock);
+#endif
if (zone == -1) {
zone = default_zone;
}
==================================================================================
----- Original Message -----
From: "Tilghman Lesher" <tilghman at mail.jeffandtilghman.com>
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Sent: Saturday, September 16, 2006 1:24 AM
Subject: Re: [asterisk-dev] Zaptel issue in FC6
> On Friday 15 September 2006 18:11, Aryanto Rachmad wrote:
> > I have posted this issue on Fedora-test-list and suggested to
> > report it here. It was said that this is an indication of a bug in
> > zaptel driver. Is it not?
>
> Please test the patch located at:
> http://bugs.digium.com/view.php?id=7620
>
> As you can see, we already have a fix, but we really need people
> to test the fix and submit feedback.
>
> --
> Tilghman
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>