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-3My 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 *
- 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/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:39 EST