public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: "do_IRQ: 0.189 No irq handler for vector" message and hard lockup
Date: Sun, 16 Nov 2008 04:05:54 +0000	[thread overview]
Message-ID: <491F9C22.1010006@blueyonder.co.uk> (raw)

I first had this happen on 15th with 2.6.28-rc4-git5 and reverted to
2.6.28-rc4-git2. Just as I was composing this email, it happened,
followed by a hard lockup after some bleeps about 30 secs. later.
At the time of this latest occurrence I was building 2.6.28-rc5.
I shall supply any further info deemed relevant.
Using openSUSE 11.1 Beta5.1 x86_64 on this box, the others are running
on stock openSUSE kernels at present.
One further effect, no keys are repeating after the latest hang.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


                 reply	other threads:[~2008-11-16  4:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=491F9C22.1010006@blueyonder.co.uk \
    --to=g3vbv@blueyonder.co.uk \
    --cc=linux-kernel@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