From: William Blew <wblew@home.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-t5 lockup on shutdown.
Date: Wed, 02 Aug 2000 21:34:38 -0700 [thread overview]
Message-ID: <3988F65E.9DBBAF68@home.com> (raw)
In-Reply-To: 200008022120.WAA28609@hyperion.valhalla.net
Iain Sandoe wrote:
>
> Does anyone know the cause of the (sometimes) complete lock-up of 2.4.0-t5
> when shutdown & restart is selected from run level 5?
>
> Observations/Symptoms:
>
> the switch of VC occurs OK
> Then *zilch*. No panic, no response to SysRq keys... no response to
> telnet... three finger salute is the only way I've found out of it.
It does sound familiar. I have found that occasionally (under high IDE?
loads
like digital audio CD ripping) the CUDA (VIA under 2.2) interrupt ceases
(as
in its /proc/interrupts counter stops increasing). Under these
circumstances
my beige G3/266's ADB bus has stopped at the software level as it is
handled
by the CUDA (noted as the VIA interrupt with 2.2 on my beige G3/266).
The symptoms that I observe are identical: An otherwise healthy mac
ignores
its keyboard completely (until the three finger salute is used).
I diagnosed my situation by ssh'ing in from another workstation and
watching
the /proc/interrupts file while ripping a digital audio CD.
I find that my bug is fairly easy to create on my beige G3/266. Just rip
a
cd with the grip under helix-gnome and wait. Anywhere from 1 to 11
tracks
layer, the VIA (CUDA) interrupt dies *grin*.
Another side effect of this interrupt failure is that the
'reboot/shutdown'
commands do not work. After all they are also via the CUDA on my G3. So,
when I reboot via ssh the G3 'hangs' at right at the end of the shutdown
sequence.
Be warned: my bug may be a red herring and unrelated to your issue. On
the
other hand... (isn't debugging fun?).
> bk-tree (linuxppc_2_3) as of 19:00 (BST) today. (but it's been happening on
> & off with the 2.4.0 tree since I've been trying it).
>
> Iain.
>
--
William Blew, wblew@home.com
Gamer by Choice, Geek by Birth
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-03 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 21:20 2.4.0-t5 lockup on shutdown Iain Sandoe
2000-08-03 4:34 ` William Blew [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 4:56 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=3988F65E.9DBBAF68@home.com \
--to=wblew@home.com \
--cc=iain@sandoe.co.uk \
--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).