From: "Daniel T. Chen" <crimsun@fungus.sh.nu>
To: Andrew Morton <akpm@osdl.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, James@superbug.demon.co.uk,
Daniel T Chen <crimsun@ubuntu.com>,
Ben Collins <bcollins@ubuntu.com>
Subject: Re: [Ubuntu PATCH] FIx no mpu401 interface can cause hard freeze
Date: Tue, 04 Jul 2006 03:53:39 -0400 [thread overview]
Message-ID: <44AA1E83.5020809@fungus.sh.nu> (raw)
In-Reply-To: <20060704000551.be489377.akpm@osdl.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[Apologies in advance for duplicated subscribers]
Andrew Morton wrote:
>> http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=b422309cdd980cfefe99379796c04e961d3c1544
>
> Do we know who wrote this patch?
It's mine. [0], [1], and [2] contain relevant context as well. The above
commit is insufficient as a fix; the current Ubuntu Dapper kernel
(2.6.15-25.43) does not have the patch from [2].
I have been unable to reproduce the hard freeze using Dapper's current
kernel, but others commenting in [0] are able. The patch from [2] only
seems to lessen the frequency of the freezes on certain hardware.
[0] http://launchpad.net/bugs/34831
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376382
[2] https://bugtrack.alsa-project.org/alsa-bug/view.php?id=952
Thanks,
- --
Daniel T. Chen crimsun@ubuntu.com
GPG key: www.sh.nu/~crimsun/pubkey.gpg.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEqh35e9GwFciKvaMRAuFhAJ9ez+8Uwy//GfTVyvUpulBPnTxQeQCgpCLB
UAfNw1l1S9esliGWkvNA2so=
=RLDy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-04 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 20:47 [Ubuntu PATCH] FIx no mpu401 interface can cause hard freeze Randy Dunlap
2006-07-04 7:05 ` Andrew Morton
2006-07-04 7:53 ` Daniel T. Chen [this message]
2006-07-04 9:09 ` Clemens Ladisch
2006-07-04 13:02 ` Takashi Iwai
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=44AA1E83.5020809@fungus.sh.nu \
--to=crimsun@fungus.sh.nu \
--cc=James@superbug.demon.co.uk \
--cc=akpm@osdl.org \
--cc=bcollins@ubuntu.com \
--cc=crimsun@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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