> On 2.6.23 it could happen even without loopback Let's focus on this point, because we already know how the lockup happens _with_ loopback and any other kind of bdi stacking. Can you describe the setup? Or better still, can you reproduce it and post the sysrq-t output? Thanks, Miklos - 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: Temporary lockup on loopback block device
- From: Mikulas Patocka <[email protected]>
- Re: Temporary lockup on loopback block device
- References:
- Temporary lockup on loopback block device
- From: Mikulas Patocka <[email protected]>
- Re: Temporary lockup on loopback block device
- From: Andrew Morton <[email protected]>
- Re: Temporary lockup on loopback block device
- From: Peter Zijlstra <[email protected]>
- Re: Temporary lockup on loopback block device
- From: Mikulas Patocka <[email protected]>
- Re: Temporary lockup on loopback block device
- From: Miklos Szeredi <[email protected]>
- Re: Temporary lockup on loopback block device
- From: Mikulas Patocka <[email protected]>
- Temporary lockup on loopback block device
- Prev by Date: Re: [linux-usb-devel] [2.6 patch] usb/serial/oti6858.c: cleanups
- Next by Date: Re: [kvm-devel] [PATCH 3/8] KVM: PVDMA Guest: Guest-side routines for paravirtualized DMA
- Previous by thread: Re: Temporary lockup on loopback block device
- Next by thread: Re: Temporary lockup on loopback block device
- Index(es):