Oops on APM wakeup on 2.4.22/23-pre, works with 2.6.0-test

From: Stanislav Meduna (stano_at_meduna.org)
Date: 10/12/03

  • Next message: Manfred Spraul: "Re: 2.6.0-test7 DEBUG_PAGEALLOC oops" 
    To: linux-kernel@vger.kernel.org
Date:	Sun, 12 Oct 2003 08:29:41 +0200 (CEST)

    Hi,

    I am trying to get the suspend to RAM working on an old
    Compaq Armada 1592 notebook.

    With the kernel 2.4.22 from Debian unstable or with vanilla
    2.4.23-pre7 I am getting an Oops on wakeup in apmd.
    Unfortunately I am not able to capture it, as there
    is an endless series of Oopsen with stacks longer
    than tens of screens - judging from the patterns in
    the addresses this actually looks like some recursive
    call somewhere. It is completely reproducible. Nothing
    is logged on the disk - the machine never comes up
    enough to be able to write something to disk.

    With 2.6.0-test7 the wakeup works fine - unfortunately I can't
    use 2.6.0 due to other problems such as unstable PCMCIA
    when removing devices and inability to compile standalone
    pcmcia-cs modules against it (I think both are known).

    apmd is 3.2.0 from Debian unstable.

    Getting the oops through a serial console is a bit complicated
    right now (have to solder null-modem cable first etc), so I would
    like to know first whether this kind of problem is known
    and whether there are some other suggested things/patches
    to try.

    Please, Cc: the followups to me, I don't read the lists
    regularly.

    Thanks 

    -- 
                                  Stano
-
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: Manfred Spraul: "Re: 2.6.0-test7 DEBUG_PAGEALLOC oops"

    Relevant Pages

    • Re: dev->release = (void (*)(struct device *))kfree;
      ... will still be unregistered (removed from the various lists) but the ... releasecallback won't be called until the last user. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: dev->release = (void (*)(struct device *))kfree;
      ... >> be so kind to remind me, why the attached patch cannot be used? ... > that frees your entire vmlogrdr_priv structure and of course not free it ... > will still be unregistered (removed from the various lists) but the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC][patch 0/2] mm: remove PageReserved
      ... As far as ioremap goes - I would rather completely disallow it from ... I will bring them up on the lists some time after ... Send instant messages to your online friends http://au.messenger.yahoo.com ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC 2.6.11-rc2-mm2 0/7] mm: manual page migration -- overview II
      ... But I can see your point that migration DEFAULT pages with first touch ... aware applications pretty much needs the old_node, new_node lists. ... is mapped into a management process. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [06/07] [PATCH] SCSI tape security: require CAP_ADMIN for SG_IO etc.
      ... >> lists but this did not result in any useful refinement of the ... > central areas of kernel is to wait and see if the problem disappears ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)