Hmm ... it may actually look like though I have a hosed controller
on my hands, and that it is actually the SCSI error handling (or lack thereof)
that causes the oops ... something tells me that 2.4.19 is able to 'offline'
the controller correctly, but 2.5.32 is not ...
Bill, have you looked closer into this ? Even though a hosed controller
is the reason for my OOPS, I guess that won`t explain the OOPS you`re seing.
>
> >
> > Anyone on lkml with comments ? I don`t get this OOPS with 2.4.19, and
> > the changes from qlogicisp.c in 2.4.19 to qlogicisp.c in 2.5.32 look
> > minimal. Only cli -> spinlock and io_request_lock -> host->host_lock
> > as far as I can see from a quick glance.
> >
>
> [snip]
>
== Morten
--"Livet er ikke for nybegynnere" - sitat fra en klok person.
mvh Morten Helgesen UNIX System Administrator & C Developer Nextframe AS admin@nextframe.net / 93445641 http://www.nextframe.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/