> Yeah. (But X doesn't run -- this is maybe the known issue in this release). What do you mean with not run? -Andi - 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: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Jiri Slaby <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- References:
- 2.6.23-rc6-mm1
- From: Andrew Morton <[email protected]>
- X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Jiri Slaby <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Jiri Slaby <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Jiri Slaby <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Andrew Morton <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Andi Kleen <[email protected]>
- Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- From: Jiri Slaby <[email protected]>
- 2.6.23-rc6-mm1
- Prev by Date: Re: [RFC][PATCH 2/6] lockdep: validate rcu_dereference() vs rcu_read_lock()
- Next by Date: Re: CFS: some bad numbers with Java/database threading [FIXED]
- Previous by thread: Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- Next by thread: Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
- Index(es):
 |