From: Michel Dänzer <daenzer@relog.ch>
To: Gwyn Judd <b.judd@xtra.co.nz>
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: seemingly random lock-up with kernel 2.2.17p7
Date: Wed, 05 Jul 2000 16:10:22 +0200 [thread overview]
Message-ID: <396341CE.71DDB938@relog.ch> (raw)
In-Reply-To: 20000706020342.B986@thislove.dyndns.org
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.
Just two more of my cents,
Michel
--
True programmers never die, they just branch to an odd address.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-05 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2000-07-05 20:13 ` Magic SysRq key [was Re: seemingly random lock-up with kernel 2.2.17p7] phandel
[not found] ` <Pine.SGI.4.21.0007050845550.10655-100000@rainbow.uchicago.edu>
2000-07-05 14:03 ` seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 14:10 ` Michel Dänzer [this message]
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
[not found] ` <l03130300b58a3be9712a@[209.122.247.91]>
2000-07-06 22:17 ` Fixing dead Xservcfers (was Re: seemingly random lock-up with kernel 2.2.17p7) Gwyn Judd
2000-07-05 14:26 ` seemingly random lock-up with kernel 2.2.17p7 Benjamin Herrenschmidt
2000-07-05 14:36 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2000-07-05 14:18 Iain Sandoe
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=396341CE.71DDB938@relog.ch \
--to=daenzer@relog.ch \
--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 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).