Bug#510859: zaptel: rmmod of zaphfc gives kernel stack trace

2009-01-20 Thread Tristan Hill
Based on the code reference in the warning (referring to http://lxr.linux.no/linux+v2.6.26/arch/x86/kernel/smp.c#L207) I believe its due to using the interrupt disabling spinlock functions. I have not have the system deadlock as indicated by comments in the code near the above link and the code

Bug#510859: zaptel: rmmod of zaphfc gives kernel stack trace

2009-01-05 Thread Tzafrir Cohen
On Mon, Jan 05, 2009 at 01:45:48PM +, s...@saticed.me.uk wrote: Package: zaptel Version: 1:1.4.11~dfsg-3 Severity: normal Has this happened once, or is it a reproducable issue? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406

Bug#510859: zaptel: rmmod of zaphfc gives kernel stack trace

2009-01-05 Thread Tristan Hill
On Mon, 2009-01-05 at 16:23 +0200, Tzafrir Cohen wrote: On Mon, Jan 05, 2009 at 01:45:48PM +, s...@saticed.me.uk wrote: Package: zaptel Version: 1:1.4.11~dfsg-3 Severity: normal Has this happened once, or is it a reproducable issue? occurs every rmmod so far -- To

Bug#510859: zaptel: rmmod of zaphfc gives kernel stack trace

2009-01-05 Thread stan
Package: zaptel Version: 1:1.4.11~dfsg-3 Severity: normal rmmod of zaphfc gives: Jan 5 12:26:13 tiber kernel: [184286.468286] zaphfc: stop Jan 5 12:26:13 tiber kernel: [184286.468286] zaphfc: shutting down card at e0a6. Jan 5 12:26:13 tiber kernel: [184286.496037] [ cut here