From: Manuel McLure <manuel@mclure.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: Sun, 12 Aug 2001 16:15:44 -0700 [thread overview]
Message-ID: <20010812161544.A947@ulthar.internal.mclure.org> (raw)
In-Reply-To: <20010812155520.A935@ulthar.internal.mclure.org> <Pine.LNX.4.33.0108121557060.2102-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0108121557060.2102-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sun, Aug 12, 2001 at 15:59:21 -0700
On 2001.08.12 15:59 Linus Torvalds wrote:
> Mind trying an alternate approach: remove the "if (!woinst)" thing, and
> instead move the line that initializes the tasklets down two lines
> (there's two places, they look something like
>
> tasklet_init(&wiinst->timer.tasklet, emu10k1_wavein_bh,
> (unsigned long) wave_dev);
> wave_dev->wiinst = wiinst;
> emu10k1_wavein_setformat(wave_dev, &wiinst->format);
>
> and they _should_ do the "tasklet_init()" _after_ the other
> initializations, ie move that line down a bit, like so:
>
> wave_dev->wiinst = wiinst;
> emu10k1_wavein_setformat(wave_dev, &wiinst->format);
> tasklet_init(&wiinst->timer.tasklet, emu10k1_wavein_bh,
> (unsigned long) wave_dev);
>
> Does that also fix it?
>
> And sure, I realize that you want to run it for a while..
Done - I'll post any Oops that might show up. No news will good news :-)
--
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<manuel@mclure.org> | and significant law, no man may kill a cat.
<http://www.mclure.org> | -- H.P. Lovecraft
next prev parent reply other threads:[~2001-08-12 23:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <997611708.29909.22.camel@DESK-2>
2001-08-12 2:52 ` Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Eric S. Raymond
2001-08-12 10:23 ` Jeffrey Ingber
2001-08-12 12:04 ` Alan Cox
2001-08-12 18:31 ` Manuel McLure
2001-08-12 20:15 ` Alan Cox
2001-08-12 20:30 ` Nerijus Baliunas
2001-08-12 20:35 ` Manuel McLure
2001-08-12 21:59 ` Manuel McLure
2001-08-12 22:24 ` Linus Torvalds
2001-08-12 22:55 ` Manuel McLure
2001-08-12 22:59 ` Linus Torvalds
2001-08-12 23:15 ` Manuel McLure [this message]
2001-08-13 0:36 ` Paul G. Allen
2001-08-13 1:39 ` Justin A
2001-08-13 1:00 ` Linus Torvalds
2001-08-13 1:33 ` Paul G. Allen
2001-08-13 1:50 ` Nicholas Knight
2001-08-13 3:08 ` Mike Frisch
2001-08-12 22:10 ` Linus Torvalds
2001-08-12 22:18 ` Alan Cox
2001-08-12 22:21 ` Dax Kelson
2001-08-12 22:31 ` Linus Torvalds
2001-08-16 23:28 ` Pavel Machek
2001-08-17 20:33 ` Alan Cox
2001-08-13 3:27 ` Robert Love
2001-08-13 11:08 ` rui.p.m.sousa
[not found] <no.id>
2001-08-12 22:30 ` Alan Cox
2001-08-13 12:16 ` Alan Cox
2001-08-13 12:19 ` rui.p.m.sousa
2001-08-13 12:19 ` Alan Cox
2001-08-13 12:35 ` Alan Cox
2001-08-13 12:43 ` Tobias Ringstrom
2001-08-13 12:47 ` Anton Altaparmakov
2001-08-13 18:53 Ryan C. Bonham
2001-08-13 18:58 ` Daniel T. Chen
2001-08-13 18:54 Anton Altaparmakov
2001-08-13 19:11 Ryan C. Bonham
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=20010812161544.A947@ulthar.internal.mclure.org \
--to=manuel@mclure.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).