Re: Oops in swsusp

From: Rafael J. Wysocki (rjw_at_sisk.pl)
Date: 04/11/05

  • Next message: Andrew Morton: "Re: [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector"
    To: Andreas Steinmetz <ast@domdv.de>
    Date:	Mon, 11 Apr 2005 08:59:00 +0200
    
    

    Hi,

    On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
    > Pavel,
    > during testing of the encrypted swsusp_image on x86_64 I did get an Oops
    > from time to time at memcpy+11 called from swsusp_save+1090 which turns
    > out to be the memcpy in copy_data_pages() of swsusp.c.
    > The Oops is caused by a NULL pointer (I don't remember if it was source
    > or destination).

    It's quite important, however. If it's the destination, it's probably a bug in
    swsusp. Otherwise, the problem is more serious. Could you, please,
    add BUG_ON(!pbe->address) right before the memcpy() and retest?

    Greets,
    Rafael

    -- 
    - Would you tell me, please, which way I ought to go from here?
    - That depends a good deal on where you want to get to.
    		-- Lewis Carroll "Alice's Adventures in Wonderland"
    -
    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: Andrew Morton: "Re: [patch 2.6.12-rc1-mm4] fork_connector: add a fork connector"

    Relevant Pages

    • Re: Oops in swsusp
      ... > The Oops is caused by a NULL pointer (I don't remember if it was source ... > or destination). ... > This Oops seems to be unrelated to the encrypted image addition as I ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Oops in swsusp
      ... >>The Oops is caused by a NULL pointer (I don't remember if it was source ... >>or destination). ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Intel vs AMD x86-64
      ... > SpeedStep, etc.), there are few differences between the implementations ... > the destination are undefined. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: OT: why no file copy() libc/syscall ??
      ... Useful but still happening on the local system. ... EXDEV ) seems a better error code for cases ... where the source and destination are on different servers. ... 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/ ...
      (Linux-Kernel)
    • What driver for NetXtreme?
      ... what drivers I'm going to need for this sucker? ... Life is not a destination, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)