From: Michael Madore <mmadore@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Re: Lockups on 2.4.1
Date: Wed, 21 Feb 2001 19:32:47 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005182@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005178@msgid-missing>
I have seen this on a 4P Lion with BIOS 71, as well as with a 2P Big Sur.
This is with 2.4.1 kernel and the IA64 patch. I was not running X on
either machine.
The machines are completely dead when this happens. No response on the
console or the network.
On Wed, Feb 21, 2001 at 10:51:46AM -0800, David Mosberger wrote:
> >>>>> On Wed, 21 Feb 2001 13:12:41 -0500, Bill Nottingham <notting@redhat.com> said:
>
> Bill> David Mosberger (davidm@hpl.hp.com) said:
> >> Please be more specific when reporting bugs. At the least,
> >> include (a) what type of machine and (b) what kernel patch you
> >> were running at the time. Ideally, also describe what you where
> >> doing at the time and try to get a backtrace with kdb, if
> >> possible.
>
> Bill> 2P BigSur, using UP 010131 kernel, on top of 2.4.1-ac16
> Bill> (certainly, this could cause problems).
>
> Thanks for the info. I haven't looked at or tried the ac patches, so
> I don't know whether they are safe for IA-64.
>
> Bill> As to what I was doing, in one case, nothing at all, in
> Bill> another, untarring a tarball. The video shuts off and the
> Bill> machine is completely dead, which makes diagnosing what
> Bill> happened difficult (hm, need to find serial cable.)
>
> By completely dead you mean that it responded neither on the console
> nor to network pings?
>
> Bill> Since it has happened when I wasn't watching the machine
> Bill> intently, it's entirely possible it's related to when it turns
> Bill> off the monitor via DPMS, but that would just be weird.
>
> Don't know if that has been tested. Any of the X experts know?
>
> I have my Big Sur configured to run OpenGL screen savers as i figured
> that would be a good way to test long term stability even when I'm not
> actively using it. No problems so far.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Mike Madore
Software Engineer
TurboLinux, Inc.
prev parent reply other threads:[~2001-02-21 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 18:12 [Linux-ia64] Re: Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 18:51 ` David Mosberger
2001-02-21 19:15 ` Bill Nottingham
2001-02-21 19:32 ` Michael Madore [this message]
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=marc-linux-ia64-105590693005182@msgid-missing \
--to=mmadore@turbolinux.com \
--cc=linux-ia64@vger.kernel.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.