From: Michael Frank <mflt1@micrologica.com.hk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vojtech Pavlik <vojtech@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21-rc7 hang on boot after spurious 8259A interrupt: IRQ15.
Date: Sat, 14 Jun 2003 16:57:19 +0800 [thread overview]
Message-ID: <200306141657.19854.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <1055578663.7651.1.camel@dhcp22.swansea.linux.org.uk>
On Saturday 14 June 2003 16:17, Alan Cox wrote:
> > The system executes a regular boot from _reset_ at this stage.
> > swsusp takes over once the kernel is up and restores the
> > suspended kernel
> > Could it be that the kernel does not handle a spurious int at
> > this early stage in the boot process ?
>
> It may also be BIOS SMI handling or reset handling problems as a
> similar case a vendor investigated showed to be. The first thing is
> to make life easier for the BIOS - make sure your kernel doesnt have
> APIC support included
APIC is not in the kernel
I put
__asm__("int $0x2f");
before calibrate_delay and inside as well for testing.
spurious 8259A int15 was reported and up to 18000 counted in
/proc/interrupts, but no hang ;-)
I suppose have to settle for hardware/BIOS (IRQ misrouted/8259
init problem or timer not working) as the cause for the hang
Regards
Michael
--
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 Swsusp for 2.4
- 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 *
prev parent reply other threads:[~2003-06-14 8:44 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
2003-06-14 3:24 ` Michael Frank
2003-06-14 8:17 ` Alan Cox
2003-06-14 8:57 ` Michael Frank [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=200306141657.19854.mflt1@micrologica.com.hk \
--to=mflt1@micrologica.com.hk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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).