How to avoid 'lost interrupt' messages post-resume?

From: Nigel Cunningham (ncunningham_at_clear.net.nz)
Date: 01/01/04

  • Next message: Henti Smith: "Re: error message in dmesg" 
    Date:	Thu, 01 Jan 2004 17:41:39 +1300
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>

    Hi all.

    I have Software Suspend successfully running under 2.4.23 on a dual
    Celeron at OSDL, with only one outstanding issue: sometimes, after
    copying back the original kernel, I see 'hda: lost interrupt' and after
    another pause 'hdb:lost interrupt' messages. Apart from that, everything
    works fine (the machine has just suspended for the 46th time on the
    trot). I'm wanting to know if there's something I can do to fix this
    issue.

    Currently, prior to suspending, I set all irq affinities to CPU 0 (which
    does the suspend), save the state of the APICs and disable them and
    disable interrupts. At resume time, I again set the affinities to CPU 0
    and disable the APICs and interrupts prior to copying the original
    kernel back. After copying the original kernel back, I restore the
    original (pre-suspend) affinities and APIC settings & reenable
    interrupts (incomplete list). I'm no hardware expert, so feel free to
    tell me I'm doing something lame! Apart from these lost interrupts, all
    seems to work just fine.

    Regards,

    Nigel 

    -- 
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
-
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/
  • Next message: Henti Smith: "Re: error message in dmesg"

    Relevant Pages

    • Re: How to avoid lost interrupt messages post-resume?
      ... > I have Software Suspend successfully running under 2.4.23 on a dual ... > copying back the original kernel, I see 'hda: ... > and disable the APICs and interrupts prior to copying the original ... After copying the original kernel back, ...
      (Linux-Kernel)
    • [RFC] Add some hooks to generic suspend code
      ... While consolidating the powermac suspend to ram and suspend to disk ... I use that one to do some housekeeping that I want to do before the interrupts are ... Additionally, I shut interrupts down myself in that callback, ... off as well (and thus become responsible for re-enabling them). ...
      (Linux-Kernel)
    • [AGP] intel_845_configure() at resume
      ... original kernel back). ... If X is started, and suspend is done from another VT, the system ... etc.) and hangs the system. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Remove process freezer from suspend to RAM pathway
      ... specifically the "suspend to RAM" parts:-D. ... Ensure that the other CPUs have finished any trailing interrupt handlers and put them to sleep ... At some point you shut off interrupts right before going to sleep, and at that point any remote wakeup event is just going to get dropped until you actually enter sleep mode and the hardware takes over again. ... If you have asynchronous probing then proper suspend handling includes being able to postpone driver probe events until after resume. ...
      (Linux-Kernel)
    • Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
      ... suspend: drivers got notified once when userspace is still running, ... with interrupts enabled, in process context; ... Most drivers suspended their hardware in the second call. ... You don't have to restrict yourself to character devices driving real ...
      (Linux-Kernel)