On Wed, 2005-11-30 at 15:41 +0100, Grzegorz Nosek wrote: > > I'm lost. Any assistance will be invaluable. OK, Remove your patches, run the system where you can capture the log, and provide a full output of the oops. Make sure you have CONFIG_KALLSYMS set. -- Steve - 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/
- Follow-Ups:
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- References:
- [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Andrew Morton <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- [PATCH] race condition in procfs
- Prev by Date: Re: [PATCH 0/9] x86-64 put current in r10
- Next by Date: Re: [PATCH 0/9] x86-64 put current in r10
- Previous by thread: Re: [PATCH] race condition in procfs
- Next by thread: Re: [PATCH] race condition in procfs
- Index(es):
 |