From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: daenzerm@student.ethz.ch, b.judd@xtra.co.nz
Subject: Re: seemingly random lock-up with kernel 2.2.17p7
Date: Wed, 05 Jul 2000 15:18:49 +0100 [thread overview]
Message-ID: <200007051418.PAA26120@hyperion.valhalla.net> (raw)
Michel Dänzer wrote:
> Gwyn Judd wrote:
>>
>> On Wed, Jul 05, 2000 at 08:51:09AM -0500, me@johngrimes.com wrote:
>> > Gwyn,
>> > Might be related or might not but I have recently started having
>> > troubles too with random locks.
>> > Now I am running 2.2.15 (but this started happening soon after the
>> > upgrade)
>> > Now my error is not directly with the kernel though. If I am in
>> > the console it has never happened but only if I am in X. In fact its X
>> > that crashes but as no keys work it doesn't matter. Now I always have
>> > xmms open when I crash but it also might be a screensaver problem as it
>> > always happens when the screensaver is one (which is the majority of the
>> > time though).
>> > Does this sound similar?
>> > Do you have an ati rage 128gl card by chance?
>> > John
>>
>> This all sounds quite familiar. The lockups have happened with both xmms
>> and mpg123. I have no idea if it is a full system lock or just X since I
>> have no remote machine to ping it with, all I am able to do is force
>> reboot. It happened also with 2.2.15 I think as well as 2.2.16
>
> What versions of X are you using? Someone reported lockups with the 4.0 r128
> driver a long time ago and someone else suggested it might be bad interaction
> between the graphics and sound devices.
There is a little wierditude with sound. I've seen X grind to a halt on a
300MHz G3 with smaller buffer sizes - which may just be a manifestation of
the more general problem:
Quote from Geert "Richard Zidlicky found a bug that made the driver always
use 1 byte buffers, which gave very bad results on slow machines. It was
fixed in 2.3.x."
I'm on the case of back-porting the 2.3.xx dmasound stuff to 2.2.17pre7 -
but don't hold your breath (there's a lot of understanding to gain on my
part - because the sleep queue stuff changed).
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-05 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 14:18 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-05 13:36 seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 13:45 ` Michel Dänzer
2000-07-05 13:57 ` Gwyn Judd
[not found] ` <Pine.SGI.4.21.0007050845550.10655-100000@rainbow.uchicago.edu>
2000-07-05 14:03 ` Gwyn Judd
2000-07-05 14:10 ` Michel Dänzer
2000-07-05 14:17 ` Gwyn Judd
2000-07-05 14:47 ` me
2000-07-05 15:00 ` Michel Dänzer
2000-07-05 15:27 ` Mario Scarpa
2000-07-05 15:43 ` Benjamin Herrenschmidt
2000-07-05 14:26 ` Benjamin Herrenschmidt
2000-07-05 14:36 ` Michel Dänzer
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=200007051418.PAA26120@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=b.judd@xtra.co.nz \
--cc=daenzerm@student.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.