> > See below. The other machine is mostly identifical, except for i8042 > > missing (probably due to running an older kernel, or small differences in > > the kernel config). > > > > Does the other machine have the same problems? No, but that machine has a lot less disk and networkactivity. > Are you able to rule out a hardware failure? 100% ? No, but the hardware is relatively new (about a year old), and of good quality. It's hard to reprodure, so looking at it when it starts to fault isn't possible either :( > The disk interrupt is unshared, which rules out a few software problems, I > guess. Indeed. Bah, I hate these kind of things :( Regards, Igmar - 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.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Andrew Morton <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Andrew Morton <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Andrew Morton <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Igmar Palsenberg <[email protected]>
- Re: 2.6.16.32 stuck in generic_file_aio_write()
- From: Andrew Morton <[email protected]>
- 2.6.16.32 stuck in generic_file_aio_write()
- Prev by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Next by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Previous by thread: Re: 2.6.16.32 stuck in generic_file_aio_write()
- Next by thread: [Patch -mm 1/2] s390: Use dev->groups for subchannel attributes.
- Index(es):