mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21-rc7 hang on boot after spurious 8259A interrupt: IRQ15.
Date: Fri, 13 Jun 2003 11:36:36 +0800	[thread overview]
Message-ID: <200306130958.39707.mflt1@micrologica.com.hk> (raw)

Doing swsusp testing in endless loop. On a P4/2.4G (ACPI=off)
on 192nd boot:

spurious 8259A interrupt: IRQ15.
Calibrating delay loop... 

 hang

Hit Reset and it rebooted OK

This is the first spurious 8259A interrupt: IRQ15 seen.

I see spurious 8259A interrupt: IRQ7 quite frequently on
varying hardware on both 2.4 and 2.5.

By design, the 8259A delivers a vector 7 when the IRQ
line is deasserted before the IRQ is serviced. This
applies to both edge and level trigger modes. A floating
"wire" or crapy chipset can pickup noise, but the driver 
should handle it.  

No problems seen with mainboard/cpu/ram in three months. 
I dont' think it is HW, but it could be.  

Also, spurious 8259A interrupts are quite recent, could 
something be wrong with recent 8259A driver?

Regards
Michael

I am not subscribed, pls cc me

-- 
Powered by linux-2.5.70-mm3, compiled with gcc-2.95-3

My current linux related activities in rough order of priority:
- Testing of 2.4/2.5 kernel interactivity
- Testing of Swsusp for 2.4
- Testing of Opera 7.11 emphasizing interactivity
- Research of NFS i/o errors during transfer 2.4>2.5
- Learning 2.5 series kernel debugging with kgdb - it's in the -mm tree
- Studying 2.5 series serial and ide drivers, ACPI, S3
* Input and feedback is always welcome *



             reply	other threads:[~2003-06-13  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  3:36 Michael Frank [this message]
2003-06-13 19:48 ` Vojtech Pavlik
2003-06-14  3:24   ` Michael Frank
2003-06-14  8:17     ` Alan Cox
2003-06-14  8:57       ` Michael Frank

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=200306130958.39707.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --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

all inboxes | Powered by JetHome®