mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: pgallen@randomlogic.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 18:00:34 -0700	[thread overview]
Message-ID: <200108130100.f7D10YH07664@penguin.transmeta.com> (raw)
In-Reply-To: <3B772126.F23DB1D7@randomlogic.com>
In-Reply-To: <20010812155520.A935@ulthar.internal.mclure.org> <Pine.LNX.4.33.0108121557060.2102-100000@penguin.transmeta.com> <20010812161544.A947@ulthar.internal.mclure.org>

In article <3B772126.F23DB1D7@randomlogic.com> you write:
>Call me dumb, but what was wrong with the SB Live! code in the 2.4.7
>trees? Mine works fine and has since I first installed RH 7.1 on this
>system. The only problem I had was when I compiled it into the kernel
>(instead of compiling as a module), sound would not work and I could not
>configure it with sndconfig.

Well, the fact that it didn't work when compiled into the kernel means
(for me), that it doesn't work at all.

Also, if you followed the other thread on the Tyan Thunder lockup,
you'll have noticed that it locked up under heavy PCI loads. At least on
that machine it stopped with the 2.4.8 driver.

Does the new driver not work for you? There seems to be a bug at close()
time, in that the driver uses "tasklet_unlock_wait()" instead of
"tasklet_kill()" to kill the tasklets, and that wouldn't work reliably.

Anything else you can find?

		Linus

  parent reply	other threads:[~2001-08-13  1:01 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 ` 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
2001-08-13  0:36                     ` Paul G. Allen
2001-08-13  1:39                       ` Justin A
2001-08-13  1:00                     ` Linus Torvalds [this message]
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=200108130100.f7D10YH07664@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgallen@randomlogic.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

all inboxes | Powered by JetHome®