From: Shawn Starr <Shawn.Starr@Home.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ps hang in 241-pre10
Date: Sat, 27 Jan 2001 19:36:09 -0500 [thread overview]
Message-ID: <3A736979.C12CCC04@Home.net> (raw)
In-Reply-To: <3A724FD2.3DEB44C@reptechnic.com.au> <3A7295F6.621BBEC4@Home.com> <3A731E65.8BE87D73@pobox.com> <3A7359BB.7BBEE42A@linux.com> <94voof$17j$1@penguin.transmeta.com>
This system is the following:
AcerOPEN AP53/AX Motherboard, Intel Pentium 200Mhz w/o MMX (1996-1997)
Chipsets: 430HX, PIIX3 (EIDE)
64MB RAM EDO 60ns (Kingston brand)
Linus Torvalds wrote:
> In article <3A7359BB.7BBEE42A@linux.com>, David Ford <david@linux.com>
> wrote:
> >
> >We've narrowed it down to "we're all running xmms" when it happend.
>
> Does anybody have a clue about what is different with xmms?
>
> Does it use KNI if it can, for example? We used to have a problem with
> KNI+Athlons, for example.
>
> It might also be that it's threading-related, and that XMMS is one of
> the few things that uses threads. Things like that. I'm not an XMMS
> user, can somebody who knows XMMS comment on things that it does that
> are unusual?
>
> Linus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-28 0:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 4:34 ps hang in 241-pre10 John Sheahan
2001-01-27 4:43 ` Aaron Lehmann
2001-01-27 7:03 ` Shawn Starr
2001-01-27 8:06 ` J Sloan
2001-01-27 8:24 ` David Ford
2001-01-27 9:33 ` Shawn Starr
2001-01-27 11:26 ` John Sheahan
2001-01-27 19:15 ` J Sloan
2001-01-27 23:28 ` David Ford
2001-01-28 0:22 ` Linus Torvalds
2001-01-28 0:36 ` Shawn Starr [this message]
2001-01-28 0:43 ` David Ford
2001-01-28 1:05 ` David Ford
2001-01-28 1:55 ` Linus Torvalds
2001-01-28 2:20 ` Marcelo Tosatti
2001-01-28 4:37 ` Linus Torvalds
2001-01-28 3:42 ` Marcelo Tosatti
2001-01-28 4:01 ` Marcelo Tosatti
2001-01-28 17:21 ` Linus Torvalds
2001-01-28 6:10 ` Shawn Starr
2001-01-28 1:15 ` David Ford
[not found] ` <fa.ikhc52v.e68327@ifi.uio.no>
2001-01-28 3:46 ` Håvard Kvålen
2001-01-28 8:59 ` James Sutherland
2001-01-29 15:08 ` Zdenek Kabelac
2001-01-28 0:42 ` J Sloan
2001-01-28 0:44 ` Aaron Lehmann
2001-01-28 1:11 ` David Ford
2001-01-28 1:30 ` J Sloan
2001-01-28 1:51 ` Shawn Starr
2001-01-27 21:14 ` Aaron Lehmann
2001-01-27 16:19 ` Linus Torvalds
2001-01-27 23:42 ` David Ford
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=3A736979.C12CCC04@Home.net \
--to=shawn.starr@home.net \
--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