public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: Sun, 12 Aug 2001 22:31:57 +0000 (UTC)	[thread overview]
Message-ID: <9l704t$1rp$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108121509310.974-100000@penguin.transmeta.com> <E15W3ZC-0006IC-00@the-village.bc.nu>

In article <E15W3ZC-0006IC-00@the-village.bc.nu>,
Alan Cox  <alan@lxorguk.ukuu.org.uk> wrote:
>> The problem with backing it out is that apparently nobody has tried to
>> really maintain it for a year, and if it gets backed out nobody will even
>> bother to try to fix it. So I'll let it be for a while, at least.
>
>I thought this was a stable kernel tree not 2.5 ?

Well, considering that the _old_ driver is also not stable and doesn't
work on all machines, we're really screwed whichever way we turn. 

If the old driver was a known working one, this would be a no-brainer. 
As it is, the old driver doesn't work for people _either_ - but they
probably aren't piping up, because the old driver has been broken
forever. 

So we have a situation that the new driver works better on some
machines, and the old driver works better on others. The old driver will
obviously neevr get fixed (we've given it several years now), so the old
driver is _known_ to be terminally broken. The new driver is a question
mark in that regard.

So I'd rather give the new driver a chance, and see if people can get it
fixed.  For example, the oops that people have reported _seems_ to be
due to initializing the tasklet before actually having initialized all
the data structures the tasklet depends on.  It may well be that moving
the two "tasklet_init()"s down two lines would fix it.

		Linus

  parent reply	other threads:[~2001-08-12 22:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-12  2:52 Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Eric S. Raymond
     [not found] ` <997611708.29909.22.camel@DESK-2>
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-13  3:27             ` Robert Love
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  3:08                       ` Mike Frisch
2001-08-13  1:00                     ` Linus Torvalds
2001-08-13  1:33                       ` Paul G. Allen
2001-08-13  1:50                         ` Nicholas Knight
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 [this message]
2001-08-16 23:28               ` Pavel Machek
2001-08-17 20:33                 ` Alan Cox
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
  -- strict thread matches above, loose matches on Subject: below --
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='9l704t$1rp$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.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