On Tue, 2010-11-02 at 18:11 +0100, Ralf Gerbig wrote:
> >> Nov 2 10:40:57 gerlin1 kernel: [45977.560407] RIP: 0010:[<ffffffff811d2290>] [<ffffffff811d2290>] scsi_dispatch_cmd+0x92/0x22e
>
> > This is the faulting location ... could you run addr2line on this
> > address to map it to a line of source code?
>
> addr2line id only say ??:0
>
> I recompiled vmlinux with debugging symbols, and gdb says:
>
> Reading symbols from /usr/src/linux-git/linux-2.6/vmlinux...done.
> (gdb) l *(scsi_dispatch_cmd + 0x92)
> 0xffffffff811d2290 is in scsi_dispatch_cmd (drivers/scsi/scsi.c:707).
> 702 * We will wait MIN_RESET_DELAY clock ticks after the
> last reset so
> 703 * we can avoid the drive not being ready.
> 704 */
> 705 timeout = host->last_reset + MIN_RESET_DELAY;
> 706
> 707 if (host->resetting && time_before(jiffies, timeout)) {
> 708 int ticks_remaining = timeout - jiffies;
> 709 /*
> 710 * NOTE: This may be executed from within an interrupt
> 711 * handler! This is bad, but for now, it'll do. The irq
Um, that's bad. It's saying the junk pointer is host on line 707 but
when it was dereferenced on line 705 it was fine. This is most likely
to indicate either memory corruption (another thread overwrote the host
location or even a hardware fault).
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
