* Norbert Kiesel ([email protected]) wrote: > system is stable again (I'm way beyond the point where I got lockups > before). Thanks a bunch for the quick fix! I'd recommend to include > this patch in 2.6.13.2. Thanks, it's already been added to the queue. -chris - 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:
- 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Norbert Kiesel <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Linus Torvalds <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Norbert Kiesel <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Linus Torvalds <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Norbert Kiesel <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Linus Torvalds <[email protected]>
- Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- From: Norbert Kiesel <[email protected]>
- 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- Prev by Date: Re: [PATCH] cpuset semaphore depth check optimize
- Next by Date: Re: [PATCH 2.6.13 5/14] sas-class: sas_discover.c Discover process (end devices)
- Previous by thread: Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine
- Next by thread: Kernel 2.6.13 BUG tg3.c:2805 = crash
- Index(es):
