Re: Oops in swsusp
From: Pavel Machek (pavel_at_suse.cz)
Date: 04/11/05
- Previous message: Pavel Machek: "swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]"
- In reply to: Andreas Steinmetz: "Oops in swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 11 Apr 2005 13:00:23 +0200 To: Andreas Steinmetz <ast@domdv.de>
Hi!
> 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).
> This Oops seems to be unrelated to the encrypted image addition as I
> didn't touch any code in that area.
Could you still try to reproduce without any patches? Alocating memory
at wrong moment may cause something like that, and crypto routines
might do that.
Pavel
-- Boycott Kodak -- for their patent abuse against Java. - 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/
- Previous message: Pavel Machek: "swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]"
- In reply to: Andreas Steinmetz: "Oops in swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
