Messages in this thread | | | Date | Wed, 25 Feb 2004 00:06:03 +0100 | From | Manuel Estrada Sainz <> | Subject | Re: firmware.agent Opps |
| |
On Tue, Feb 24, 2004 at 02:19:01PM -0800, Jean Tourrilhes wrote: > Hi, > > Using 2.6.3 (SMP), prism54 driver and firmware.agent from > Debian unstable. I got the following nice Ooops :
[snip]
> kernel: Oops: 0000 [#1] > kernel: CPU: 0 > kernel: EIP: 0060:[dnotify_flush+17/120] Not tainted > kernel: EFLAGS: 00010246 > kernel: EIP is at dnotify_flush+0x11/0x78 [snip] > kernel: Call Trace: > kernel: [filp_close+84/108] filp_close+0x54/0x6c > kernel: [sys_close+84/108] sys_close+0x54/0x6c > kernel: [syscall_call+7/11] syscall_call+0x7/0xb > kernel: > kernel: Code: 0f b7 41 20 25 00 f0 ff ff 66 3d 00 40 75 54 b8 a4 06 29 c0 > ----------------------------------------- > > If you think the driver is at fault, please tell me and I'll > forward that to the prism54 guys. If you need more info, just yell at > me.
No, the driver is not at fault.
It is a known problem, I have some pending patches which fix some races and should fix that. I´ll update them and send them to Andrew for inclusion (Simon Kelley promised to bug me until I do so :-)). I´ll cc lkml like usual.
Thanks for the report, Have a nice day
Manuel
-- --- Manuel Estrada Sainz <ranty@debian.org> <ranty@bigfoot.com> <ranty@users.sourceforge.net> ------------------------ <manuel.estrada@hispalinux.es> ------------------- Let us have the serenity to accept the things we cannot change, courage to change the things we can, and wisdom to know the difference. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |