Could you try to boot with "slub_debug" on the kernel command line? That may help you to diagnose the problem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- git-current: slub breaks s2ram with fglrx...
- From: Soeren Sonnenburg <[email protected]>
- Re: git-current: slub breaks s2ram with fglrx...
- From: "Rafael J. Wysocki" <[email protected]>
- Re: git-current: slub breaks s2ram with fglrx...
- From: Soeren Sonnenburg <[email protected]>
- Re: git-current: slub breaks s2ram with fglrx...
- From: "Michal Piotrowski" <[email protected]>
- Re: git-current: slub breaks s2ram with fglrx...
- From: Soeren Sonnenburg <[email protected]>
- git-current: slub breaks s2ram with fglrx...
- Prev by Date: Re: [PATCH] clarify the GPL version of contributions by Jesper Juhl in CREDITS
- Next by Date: Re: [patch 00/14] Page cache cleanup in anticipation of Large Blocksize support
- Previous by thread: Re: git-current: slub breaks s2ram with fglrx...
- Next by thread: way of managing the kernel development involvement process (was: Re: [ck] It is the end of -ck)
- Index(es):
 |