On Thu, Mar 08 2007, Andre Noll wrote: > On 19:46, Jens Axboe wrote: > > On Wed, Feb 28 2007, Andre Noll wrote: > > > On 16:18, Andre Noll wrote: > > > > > > > With 2.6.21-rc2 I am unable to reproduce this BUG message. However, > > > > writing to both raid systems at the same time via lvm still locks up > > > > the system within minutes. > > > > > > Screenshot of the resulting kernel panic: > > > > > > http://systemlinux.org/~maan/shots/kernel-panic-21-rc2-huangho2.png > > > > Do you have the full oops as well? > > Unfortunately not, as there's no way to scroll up after a kernel panic > (the screenshot was taken by using a KVM switch which just sends the > video output over ethernet).
Do you still have the vmlinux? It'd be interesting to see what $ gbd vmlinux (gdb) l *cfq_dispatch_insert+0x28 says, here that'd be cfqq dereference. And that must be valid, it's set on allocation time and only cleared after free. So unless lvm issues private requests that aren't properly allocated, this whole thing looks very bizarre. -- Jens Axboe - 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/
