From: "Iain Sandoe" <iain@sandoe.co.uk>
To: William Blew <wblew@home.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-t5 lockup on shutdown.
Date: Thu, 03 Aug 2000 05:56:54 +0100 [thread overview]
Message-ID: <200008030457.FAA15430@hyperion.valhalla.net> (raw)
On Thu, Aug 3, 2000, William Blew wrote:
> Iain Sandoe wrote:
>>
>> Does anyone know the cause of the (sometimes) complete lock-up of 2.4.0-t5
[snip]
> layer, the VIA (CUDA) interrupt dies *grin*.
as in 'just disappears' ? i.e. as if some driver has requested it be
deleted?... this would certainly explain more than one phenomenon... (I
could see that also causing sound flakiness too - since we need the cuda for
that)...
Note that I haven't used IDE (AHAIK) in the cases mentioned - all my disk,
other than CDROM, is on SCSI... but I could try a controlled test (later).
what else causes the interrupt to 'disappear'?
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-03 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 4:56 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-02 21:20 2.4.0-t5 lockup on shutdown Iain Sandoe
2000-08-03 4:34 ` William Blew
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=200008030457.FAA15430@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wblew@home.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;
as well as URLs for NNTP newsgroup(s).