public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Wed, 21 Feb 2001 17:57:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005177@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>

>>>>> On Wed, 21 Feb 2001 11:05:12 -0500, Bill Nottingham <notting@redhat.com> said:

  Bill> Michael Madore (mmadore@turbolinux.com) said:
  >> Has anyone else seen lockups under the 2.4.1 kernel?  I saw two
  >> machines (one Lion, one Big Sur) hang over the weekend.  Both
  >> machines had black screens and wouldn't respond over the network.
  >> 
  >> I had several other boxes running over the weekend with no
  >> problems.  Sorry I don't have any more details at the moment.

  Bill> I've definitely seen some completely random deaths here.

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.

That way, we should be able to at least get an idea of what the
pattern of the failures are.

Having said that, except for the one-time "rpm" hang and the autofs4
instability, my Big Sur has been rock solid.

>>>>> On Wed, 21 Feb 2001 09:16:51 -0800, Gerrit Huizenga <gerrit@us.ibm.com> said:

  Gerrit> I've been seeing these even under 2.4.0 on a Lion.  And my
  Gerrit> current BIOS/EFI is making it difficult to get a serial
  Gerrit> console working to see what happens at the time of machine
  Gerrit> death.

Please don't bother with bug reports against the 2.4.0 patch---it is
known to hang in certain cases.  The latest patch is relative to
2.4.1.

Thanks,

	--david


  parent reply	other threads:[~2001-02-21 17:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger [this message]
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss
2001-02-25  2:43 ` Francis Galiegue
2001-02-26 20:52 ` Jim Wilson
2001-03-07  3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08  3:45 ` Tom King

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-105590693005177@msgid-missing \
    --to=davidm@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox