linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@ucw.cz>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 hang on boot after spurious 8259A interrupt: IRQ15.
Date: Fri, 13 Jun 2003 21:48:32 +0200	[thread overview]
Message-ID: <20030613214832.A6366@ucw.cz> (raw)
In-Reply-To: <200306130958.39707.mflt1@micrologica.com.hk>; from mflt1@micrologica.com.hk on Fri, Jun 13, 2003 at 11:36:36AM +0800

On Fri, Jun 13, 2003 at 11:36:36AM +0800, Michael Frank wrote:

> Doing swsusp testing in endless loop. On a P4/2.4G (ACPI=off)
> on 192nd boot:
> 
> spurious 8259A interrupt: IRQ15.
> Calibrating delay loop... 

It looks like the IDE code didn't put the controller into sleep
properly.

>  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 *
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-06-13 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  3:36 2.4.21-rc7 hang on boot after spurious 8259A interrupt: IRQ15 Michael Frank
2003-06-13 19:48 ` Vojtech Pavlik [this message]
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=20030613214832.A6366@ucw.cz \
    --to=vojtech@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mflt1@micrologica.com.hk \
    /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).