From: Takashi Iwai <tiwai@suse.de>
To: karsten wiese <annabellesgarden@yahoo.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Devel Alsa <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH]usx2y: prevent oops & dead keyboard on hot usb unplugging
Date: Tue, 19 Apr 2005 11:23:23 +0200 [thread overview]
Message-ID: <s5h8y3fce7o.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050416003107.68080.qmail@web26501.mail.ukl.yahoo.com>
At Sat, 16 Apr 2005 02:31:06 +0200 (CEST),
karsten wiese wrote:
>
> [1 <text/plain; iso-8859-1 (8bit)>]
>
> --- Clemens Ladisch <clemens@ladisch.de> wrote:
> > Takashi Iwai wrote:
> > > karsten wiese wrote:
> > > > (-: You apply my patch now?
> > >
> > > No, not enough :) This is exactly why
> > snd_card_free_in_thread() was
> > > introduced.
> > >
> > > As I asked, please make sure that the files are all
> > released before
> > > snd_card_free(). Otherwise the disconnect callback
> > hangs at this
> > > point because of this check.
> >
> > Most programs close the device file when an error occurs,
> > so you have
> > to test it with something like this to keep the file
> > open:
> >
> > #include <stdio.h>
> > int main()
> > {
> > fopen("/dev/snd/hwC1D0", "rb");
> > getchar();
> > }
> >
> Tested with it, see attached shell log (copied+pasted).
> Any more tests needed?
> I bet a kasten bier that it oopses reliably on first try,
> if I revert to snd_card_free_in_thread() nothing else
> changed.
> And I'll inform you , if any oops should show when i shut
> down (pc is still in the state like @ the end of the log).
>
> Regards,
> Karsten
>
> P.S.: how about adding a kernelversion depending macro for
> backward compatibility,... when was
> snd_card_free_in_thread() introduced?
Agreed. The problem is that how to know which version has still this
problem..? At least, 2.4 kernel must have a problem without
snd_card_free_in_thread().
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
next prev parent reply other threads:[~2005-04-19 9:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 0:31 [PATCH]usx2y: prevent oops & dead keyboard on hot usb unplugging karsten wiese
2005-04-19 9:23 ` Takashi Iwai [this message]
2005-04-19 14:27 ` Clemens Ladisch
2005-04-19 9:32 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 22:14 karsten wiese
2005-04-19 21:22 karsten wiese
2005-04-20 9:17 ` Takashi Iwai
2005-04-15 15:15 karsten wiese
2005-04-15 15:14 karsten wiese
2005-04-15 15:22 ` Takashi Iwai
2005-04-15 15:45 ` karsten wiese
2005-04-15 15:50 ` Takashi Iwai
2005-04-15 16:25 ` Clemens Ladisch
2005-04-15 15:32 ` Clemens Ladisch
2005-04-15 14:28 karsten wiese
2005-04-15 14:36 ` Takashi Iwai
2005-04-15 13:59 karsten wiese
2005-04-15 14:16 ` Takashi Iwai
2005-04-15 13:31 karsten wiese
2005-04-14 18:59 karsten wiese
2005-04-14 22:25 ` Lee Revell
2005-04-15 7:07 ` Clemens Ladisch
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=s5h8y3fce7o.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=annabellesgarden@yahoo.de \
--cc=clemens@ladisch.de \
/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