From: Keith Owens <kaos@ocs.com.au>
To: scole@lanl.gov
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test12-pre4 + cs46xx + KDE 2.0 = frozen system
Date: Tue, 05 Dec 2000 08:55:58 +1100 [thread overview]
Message-ID: <4743.975966958@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 04 Dec 2000 14:27:10 PDT." <00120414271000.01254@spc.esa.lanl.gov>
On Mon, 4 Dec 2000 14:27:10 -0700,
Steven Cole <scole@lanl.gov> wrote:
>If I have the cs46xx driver compiled either as a module or into
>the kernel, then 2.4.0-test12-pre4 locks up when KDE 2.0
>is started.
>[snip]
>When I say the system freezes, I mean it completely locks up, and
>ALT-SYSRQ-<whatevercommand> does not do a thing. The magic
>key combo gives the expected result before freezup.
Try the kdb patch, it is very good at getting data out when a machine
has hung. You will need a serial console to see kdb output, it does
not work with X.
ftp://oss.sgi.com/projects/kdb/download/ix86/
kdb-v1.6-2.4.0-test11-pre7.gz should still fit 2.4.0-test12-pre4.
-
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:[~2000-12-04 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 21:27 2.4.0-test12-pre4 + cs46xx + KDE 2.0 = frozen system Steven Cole
2000-12-04 21:55 ` Keith Owens [this message]
2000-12-04 22:47 ` Roger Larsson
2000-12-04 23:22 ` Alan Cox
2000-12-04 23:29 ` Alan Cox
2000-12-05 17:16 ` Steven Cole
2000-12-05 22:02 ` Alan Cox
2000-12-05 22:47 ` Steven Cole
2000-12-06 1:00 ` Alan Cox
2000-12-06 14:55 ` Steven Cole
2000-12-06 16:04 ` Steven Cole
2000-12-06 18:40 ` Nils Faerber
2000-12-07 13:28 ` Alan Cox
2000-12-07 14:27 ` Steven Cole
-- strict thread matches above, loose matches on Subject: below --
2000-12-05 1:42 Steven Cole
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=4743.975966958@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=scole@lanl.gov \
/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