From: Manuel Estrada Sainz <ranty@debian.org>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: firmware.agent Opps
Date: Wed, 25 Feb 2004 00:06:03 +0100 [thread overview]
Message-ID: <20040224230603.GB18091@ranty.pantax.net> (raw)
In-Reply-To: <20040224221900.GA5954@bougret.hpl.hp.com>
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.
prev parent reply other threads:[~2004-02-24 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 22:19 Jean Tourrilhes
2004-02-24 23:06 ` Manuel Estrada Sainz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040224230603.GB18091@ranty.pantax.net \
--to=ranty@debian.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®